You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2012/11/28 02:48:57 UTC
[jira] [Created] (MPOM-39) use only non-aggregate reports in parent
pom
Hervé Boutemy created MPOM-39:
---------------------------------
Summary: use only non-aggregate reports in parent pom
Key: MPOM-39
URL: https://issues.apache.org/jira/browse/MPOM-39
Project: Maven POMs
Issue Type: Bug
Components: maven
Affects Versions: MAVEN-22
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
Priority: Critical
Fix For: MAVEN-23
Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
Now I understand why I'm experiencing twice PMD or Checkstyle runs in components lately...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MPOM-39) use only non-aggregate reports in
parent pom
Posted by "Hervé Boutemy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy resolved MPOM-39.
-------------------------------
Resolution: Fixed
fixed in [r1414507|http://svn.apache.org/viewvc?rev=1414507&view=rev]
> use only non-aggregate reports in parent pom
> --------------------------------------------
>
> Key: MPOM-39
> URL: https://issues.apache.org/jira/browse/MPOM-39
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Affects Versions: MAVEN-22
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Priority: Critical
> Fix For: MAVEN-23
>
>
> Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
> In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
> But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
> Now I understand why I'm experiencing twice Checkstyle runs in components lately...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-39) use only non-aggregate reports in parent
pom
Posted by "Hervé Boutemy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy closed MPOM-39.
-----------------------------
> use only non-aggregate reports in parent pom
> --------------------------------------------
>
> Key: MPOM-39
> URL: https://issues.apache.org/jira/browse/MPOM-39
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Affects Versions: MAVEN-22
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Priority: Critical
> Fix For: MAVEN-23
>
>
> Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
> In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
> But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
> Now I understand why I'm experiencing twice Checkstyle runs in components lately...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-39) use only non-aggregate reports in parent
pom
Posted by "Hervé Boutemy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy updated MPOM-39:
------------------------------
Description:
Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
Now I understand why I'm experiencing twice Checkstyle runs in components lately...
was:
Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
Now I understand why I'm experiencing twice PMD or Checkstyle runs in components lately...
> use only non-aggregate reports in parent pom
> --------------------------------------------
>
> Key: MPOM-39
> URL: https://issues.apache.org/jira/browse/MPOM-39
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Affects Versions: MAVEN-22
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Priority: Critical
> Fix For: MAVEN-23
>
>
> Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
> In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
> But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
> Now I understand why I'm experiencing twice Checkstyle runs in components lately...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-39) use only non-aggregate reports in
parent pom
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505205#comment-13505205 ]
Hudson commented on MPOM-39:
----------------------------
Integrated in maven-parent #127 (See [https://builds.apache.org/job/maven-parent/127/])
[MPOM-39] use only non-aggregate reports in parent pom (Revision 1414507)
Result = SUCCESS
hboutemy : http://svn.apache.org/viewvc/?view=rev&rev=1414507
Files :
* /maven/pom/trunk/maven/pom.xml
> use only non-aggregate reports in parent pom
> --------------------------------------------
>
> Key: MPOM-39
> URL: https://issues.apache.org/jira/browse/MPOM-39
> Project: Maven POMs
> Issue Type: Bug
> Components: maven
> Affects Versions: MAVEN-22
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Priority: Critical
> Fix For: MAVEN-23
>
>
> Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate previously, aggregate was a parameter).
> In the maven parent pom, we're explicitely setting a reportSet configuration for m-javadoc-p, which is the first plugin implementing this pattern IIRC.
> But for other plugins, we don't define reportSets: then by default, every reporting goals are used, ie aggregate and non-aggregate.
> Now I understand why I'm experiencing twice Checkstyle runs in components lately...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira