headers
Brett Porter | 1 Apr 2011 02:47
Picon
Favicon
Gravatar

Re: Cobertura: in codehaus or out

The main advantage is not having to change the group ID. I don't think you'd be able to publish to o.c.mojo via ossrh.

I think there has been some miscommunication. Combining the plugin under it's license and Cobertura under
GPL certainly creates a work that is more restrictive - but it's still open source and Codehaus have said
that from a policy PoV they are ok with that.

What should change is the license headers, which use the ASF ones instead. It might be better to use a BSD
license for better compatibility with the GPL. For my contributions, I'm fine with that.

I'm fine with Benson having commit rights if he is keen to maintain it.

- Brett

On 01/04/2011, at 6:53 AM, Benson Margulies wrote:

> Hello Mojo Developers,
> 
> We're using cobertura at my job, and we'd really like aggregation to
> work. So, I picked up MCOBERTURA-65 and added some testing to it in
> the hopes of a commit.
> 
> I just got bad news from Robert Scholte. There is a longstanding
> problem of license friction with this plugin where the cobertura
> license and the codehaus license don't play well together. The
> original MCOBERTURA-65 patch already trangressed a 'what can you call'
> boundary here.
> 
> Hypothetically, the patch could be reworked to stay in bounds.
> 
> However, it seems to me to be wasteful to build and maintain a maven
(Continue reading)

Permalink | Reply | 21 comments |
headers
Benson Margulies | 1 Apr 2011 03:33
Picon
Gravatar

Re: Cobertura: in codehaus or out

Folks,

Yes, the gid change would be a brief but sharp pain, and if there
really isn't a license problem, who needs it?

I don't claim to know anything about codehaus governance or licensing
policy. If you give me commit, I'll clean up the headers, neaten up
anything else in need of neatening, and push out a release.

If you need some sort of Codehaus CLA from me, just point me at it,
though I did have commit at codehaus for wstx at one point so I may
already be assimilated.

I trust that you two (Brett and Robert) can sort this out soonishly.

--benson

On Thu, Mar 31, 2011 at 8:47 PM, Brett Porter <brett <at> apache.org> wrote:
> The main advantage is not having to change the group ID. I don't think you'd be able to publish to o.c.mojo
via ossrh.
>
> I think there has been some miscommunication. Combining the plugin under it's license and Cobertura
under GPL certainly creates a work that is more restrictive - but it's still open source and Codehaus have
said that from a policy PoV they are ok with that.
>
> What should change is the license headers, which use the ASF ones instead. It might be better to use a BSD
license for better compatibility with the GPL. For my contributions, I'm fine with that.
>
> I'm fine with Benson having commit rights if he is keen to maintain it.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anders Sørensen (JIRA | 1 Apr 2011 09:42

[jira] Assigned: (MOJO-1637) Ability to draw graphs from additional CSVs specified


     [
http://jira.codehaus.org/browse/MOJO-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Sørensen reassigned MOJO-1637:
-------------------------------------

    Assignee: Anders Sørensen  (was: Kent Soelvsten)

> Ability to draw graphs from additional CSVs specified
> -----------------------------------------------------
>
>                 Key: MOJO-1637
>                 URL: http://jira.codehaus.org/browse/MOJO-1637
>             Project: Mojo
>          Issue Type: New Feature
>          Components: chronos
>            Reporter: Anders Sørensen
>            Assignee: Anders Sørensen
>
> eg, the app might leave a CSV somewhere, or a system monitoring tool might leave a CSV which would need to be graphed

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anders Sørensen (JIRA | 1 Apr 2011 09:44

[jira] Closed: (MOJO-1637) Ability to draw graphs from additional CSVs specified


     [
http://jira.codehaus.org/browse/MOJO-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Sørensen closed MOJO-1637.
---------------------------------

       Resolution: Fixed
    Fix Version/s: chronos-maven-plugin-1.0

See MOJO-1636

> Ability to draw graphs from additional CSVs specified
> -----------------------------------------------------
>
>                 Key: MOJO-1637
>                 URL: http://jira.codehaus.org/browse/MOJO-1637
>             Project: Mojo
>          Issue Type: New Feature
>          Components: chronos
>            Reporter: Anders Sørensen
>            Assignee: Anders Sørensen
>             Fix For: chronos-maven-plugin-1.0
>
>
> eg, the app might leave a CSV somewhere, or a system monitoring tool might leave a CSV which would need to be graphed

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anders Sørensen (JIRA | 1 Apr 2011 09:44

[jira] Assigned: (MOJO-1635) Ability to pass in some meta data about the build, eg build number, svn revision, etc


     [
http://jira.codehaus.org/browse/MOJO-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Sørensen reassigned MOJO-1635:
-------------------------------------

    Assignee: Anders Sørensen  (was: Kent Soelvsten)

> Ability to pass in some meta data about the build, eg build number, svn revision, etc
> -------------------------------------------------------------------------------------
>
>                 Key: MOJO-1635
>                 URL: http://jira.codehaus.org/browse/MOJO-1635
>             Project: Mojo
>          Issue Type: New Feature
>          Components: chronos
>            Reporter: Anders Sørensen
>            Assignee: Anders Sørensen
>

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:
(Continue reading)

Permalink | Reply | 0 comments |
headers
nodje (JIRA | 1 Apr 2011 09:47

[jira] Commented: (MASPECTJ-94) <excludes> could also filter aspects included in <aspectLibrary>


    [
http://jira.codehaus.org/browse/MASPECTJ-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262213#action_262213
] 

nodje commented on MASPECTJ-94:
-------------------------------

I'll give a try to m-dependency-p asaic
and will try to think about some good way to present the end user the option to include JARS in the filtering system.

> <excludes> could also filter aspects included in <aspectLibrary>
> ----------------------------------------------------------------
>
>                 Key: MASPECTJ-94
>                 URL: http://jira.codehaus.org/browse/MASPECTJ-94
>             Project: Mojo AspectJ Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.3.1
>         Environment: all
>            Reporter: nodje
>         Attachments: AcpectLibraryExclusionsAntStyle.zip
>
>
> I was trying to exclude an aspect contained in spring-aspects library, that I was specifying as
<aspectLibrary> in the config, when I realized it couldn't be filtered.
> I've created a test that fails when aspectLibrary aspect are woven despite their exclusion. It is to be
added to the src/it tests.
> It's not very clean as it's based on an external aspect library (spring-aspects), but it shows what is
expected clearly I believe.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lucas POUZAC (JIRA | 1 Apr 2011 11:28

[jira] Issue Comment Edited: (MOJO-1657) Chornos not compatible with maven 3


    [
http://jira.codehaus.org/browse/MOJO-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262218#action_262218
] 

Lucas POUZAC edited comment on MOJO-1657 at 4/1/11 4:27 AM:
------------------------------------------------------------

Attached is an example. We need only change the versions of plugins in the pom.xml maven-site-plugin and
maven-project-info-reports-plugin between maven2 and maven3.

Thanks

      was (Author: lpouzac):
    Attached is an example. We need only change the versions of plugins in the pom.xml maven-site-plugin and
maven-project-info-reports-plugin between maven2 and maven3

> Chornos not compatible with maven 3
> -----------------------------------
>
>                 Key: MOJO-1657
>                 URL: http://jira.codehaus.org/browse/MOJO-1657
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>    Affects Versions: chronos-maven-plugin-1.0
>            Reporter: Lucas POUZAC
>            Assignee: Anders Sørensen
>         Attachments: test_chronos.tar
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lucas POUZAC (JIRA | 1 Apr 2011 11:28

[jira] Issue Comment Edited: (MOJO-1657) Chornos not compatible with maven 3


    [
http://jira.codehaus.org/browse/MOJO-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262218#action_262218
] 

Lucas POUZAC edited comment on MOJO-1657 at 4/1/11 4:27 AM:
------------------------------------------------------------

Attached is an example. You need only change the versions of plugins in the pom.xml maven-site-plugin and
maven-project-info-reports-plugin between maven2 and maven3.

Thanks

      was (Author: lpouzac):
    Attached is an example. We need only change the versions of plugins in the pom.xml maven-site-plugin and
maven-project-info-reports-plugin between maven2 and maven3.

Thanks

> Chornos not compatible with maven 3
> -----------------------------------
>
>                 Key: MOJO-1657
>                 URL: http://jira.codehaus.org/browse/MOJO-1657
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>    Affects Versions: chronos-maven-plugin-1.0
>            Reporter: Lucas POUZAC
>            Assignee: Anders Sørensen
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lucas POUZAC (JIRA | 1 Apr 2011 11:28

[jira] Updated: (MOJO-1657) Chornos not compatible with maven 3


     [
http://jira.codehaus.org/browse/MOJO-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas POUZAC updated MOJO-1657:
-------------------------------

    Attachment: test_chronos.tar

Attached is an example. We need only change the versions of plugins in the pom.xml maven-site-plugin and
maven-project-info-reports-plugin between maven2 and maven3

> Chornos not compatible with maven 3
> -----------------------------------
>
>                 Key: MOJO-1657
>                 URL: http://jira.codehaus.org/browse/MOJO-1657
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>    Affects Versions: chronos-maven-plugin-1.0
>            Reporter: Lucas POUZAC
>            Assignee: Anders Sørensen
>         Attachments: test_chronos.tar
>
>
> When I run chronos-maven-plugin with maven3, just one report is generated when two reports are configured.
> With maven 2 : testNominal and testNominal2 report are generated
> With maven 3 : only testNominal2 is generated.
> Maven 2.0.9 - Plugin site 2.0.1
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jochen Wiedmann | 1 Apr 2011 13:51
Picon
Gravatar

Re: Cobertura: in codehaus or out

On 01/04/2011, at 6:53 AM, Benson Margulies wrote:

> I just got bad news from Robert Scholte. There is a longstanding
> problem of license friction with this plugin where the cobertura
> license and the codehaus license don't play well together. The
> original MCOBERTURA-65 patch already trangressed a 'what can you call'
> boundary here.

Would you please explain what the problem is? The author himself is
releasing the Ant tasks for Cobertura under ASL 1.1, so it's hard for
me to understand what the problem could be?

Jochen

--

-- 
I Am What I Am And That's All What I Yam (Popeye)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 19 comments |

Gmane