[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-03-15 Thread Commented

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230823#comment-13230823
 ] 

Hervé Boutemy commented on MPOM-32:
---

AFAIK, the bug is in Maven Core: see https://jira.codehaus.org/browse/MNG-5155

> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
> Attachments: MPOM-32-1.xml, MPOM-32-2.xml
>
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-01-05 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180986#comment-13180986
 ] 

Sebb commented on MPOM-32:
--

PING

> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-03-08 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225583#comment-13225583
 ] 

Sebb commented on MPOM-32:
--

Furthermore, the "license" report is not supposed to be used on ASF websites: 
sites should link to the ASF license page instead => 
http://www.apache.org/licenses/

> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-03-08 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225705#comment-13225705
 ] 

Sebb commented on MPOM-32:
--

In ASF-9, the list of reports was left empty.

That worked fine; if a child pom did not specify any reports, all of them were 
generated. 
And if the child specified just some of the reports, just those were generated.

However, with ASF-10, all the reports are always generated - it does not appear 
to be possible to override the set of reports.

I tried using false as per [1] but that does not work.


[1]http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_inherited_Tag_In_Reporting_Plugins


> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-03-08 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225718#comment-13225718
 ] 

Sebb commented on MPOM-32:
--

See attached sample POMs.

Both attempt to change the list of generated reports; neither has any effect.

> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
> Attachments: MPOM-32-1.xml, MPOM-32-2.xml
>
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2012-03-15 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230835#comment-13230835
 ] 

Sebb commented on MPOM-32:
--

As far as I can see, adding the report list to the Apache pom has no benefit.

There several disadvantages:
- Maven 2.x projects cannot override the list
- poms which derive from Apache have to remember to disable inheritance in 
order to change the set of reports.
- the behaviour of projects that update from v9 to v10 is changed (and this is 
not documented)

> Apache POM 10 forces all child projects to generate the project info reports
> 
>
> Key: MPOM-32
> URL: https://issues.apache.org/jira/browse/MPOM-32
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: Sebb
>Priority: Blocker
> Attachments: MPOM-32-1.xml, MPOM-32-2.xml
>
>
> One of the changes between ASF-9 and ASF-10 was to configure 
> maven-project-info-reports-plugin with a full set of reports.
> This means that all inheriting projects now get the full set of reports, 
> whether they want them or not.
> Note that this feature is not documented on the overview page [1]
> The other changes in 10 seem benign.
> [1] http://maven.apache.org/pom/asf/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (MPOM-35) Apache POM 10 does not allow -Darguments

2012-03-15 Thread Hudson (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/MPOM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230865#comment-13230865
 ] 

Hudson commented on MPOM-35:


Integrated in ASF Parent Pom #32 (See 
[https://builds.apache.org/job/ASF%20Parent%20Pom/32/])
[MPOM-35] allow -Darguments when using release plugin
Submitted by: David Blevins (Revision 1301314)

 Result = SUCCESS
hboutemy : http://svn.apache.org/viewvc/?view=rev&rev=1301314
Files : 
* /maven/pom/trunk/asf/pom.xml


> Apache POM 10 does not allow -Darguments
> 
>
> Key: MPOM-35
> URL: https://issues.apache.org/jira/browse/MPOM-35
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf
>Affects Versions: ASF-10
>Reporter: David Blevins
>Assignee: Hervé Boutemy
> Fix For: ASF-11
>
> Attachments: MPOM-35.diff
>
>
> The usage of -Darguments as noted in the release plugin documentation doesn't 
> work due to an issue with the apache parent pom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira