You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/05/05 17:41:41 UTC
[jira] Created: (MNG-2277) aggregating plugins in submodules of the
reactor return all projects causing a chicken/egg issue
aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
------------------------------------------------------------------------------------------------
Key: MNG-2277
URL: http://jira.codehaus.org/browse/MNG-2277
Project: Maven 2
Type: Bug
Components: Reactor and workspace, Plugins and Lifecycle, Plugin API
Versions: 2.0.4
Reporter: Brett Porter
eg, assembly:attached
when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Closed: (MNG-2277) aggregating plugins in submodules of the
reactor return all projects causing a chicken/egg issue
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MNG-2277.
--------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1)
2.0.8
When a dependency can't be resolved AND the same is found in the reactor AND the plugin is an aggregator, we produce a large warning and then skip it. A clone of this issue has been created for possible further solution in 2.1: MNG-3260
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Alfie Kirkpatrick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133691#action_133691 ]
Alfie Kirkpatrick commented on MNG-2277:
----------------------------------------
For info I had already raised MNG-3283 for the specific issue we're facing. I'll comment on MECLIPSE-380 now to link to it.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
> Attachments: maven-dependency-bug.zip
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102125 ]
Brian Fox commented on MNG-2277:
--------------------------------
I debugged another problem caused by enforcer:enforce-once (aggregator and requiresDependencyResolution) and confirm this. The resolveTransitively doesn't consider artifacts in the reactor.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Fix For: 2.1.x
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112054 ]
Brian Fox commented on MNG-2277:
--------------------------------
What you are seeing is normal. The dependency doesn't exist so it's going to fail. MNG-2277 is about aggregating plugins that make it impossible to build the project from any phase because of the aggregation.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
> Attachments: maven-dependency-bug.zip
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Martin Höller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133684#action_133684 ]
Martin Höller commented on MNG-2277:
------------------------------------
Alfie, an issue for your problem exists in JIRA for maven-eclipse-plugin as MECLIPSE-380. Probably it's not just maven-eclipse-plugin related and should be moved to maven, I'm not sure.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
> Attachments: maven-dependency-bug.zip
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Alfie Kirkpatrick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112056 ]
Alfie Kirkpatrick commented on MNG-2277:
----------------------------------------
Hi Brian, thanks for taking a look at the project. Maybe this isn't the right forum to discuss this now you've made it clear this is a different issue. However, I can't see how this is 'normal' behaviour because the dependency does exist in the reactor and targeting a later phase is successful. Also we only see the problem if a plugin is invoked by the build at an early phase and the plugin requires dependency resolution. At the moment our team is working around this issue by running 'mvn package eclipse:eclipse' which just seems crazy to me. If you need a fuller description of what we tried see my post on the mailing list (http://www.mail-archive.com/users@maven.apache.org/msg75053.html) where someone identified it (perhaps wrongly) as an instance of MNG-2277 -- hence my interest in this issue. Many thanks, Alfie.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
> Attachments: maven-dependency-bug.zip
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Alfie Kirkpatrick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111929 ]
Alfie Kirkpatrick commented on MNG-2277:
----------------------------------------
I checked out this evening from https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x (identifies itself as version 2.0.8-SNAPSHOT) and I'm still seeing an error when running mvn generate-sources on my simple test project where child1 depends on child2 (with single parent project that includes both child1 and child2).
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Commented: (MNG-2277) aggregating plugins in submodules of
the reactor return all projects causing a chicken/egg issue
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111934 ]
Brian Fox commented on MNG-2277:
--------------------------------
Alfie, can you attach your sample project?
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Updated: (MNG-2277) aggregating plugins in submodules of the
reactor return all projects causing a chicken/egg issue
Posted by "Alfie Kirkpatrick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alfie Kirkpatrick updated MNG-2277:
-----------------------------------
Attachment: maven-dependency-bug.zip
See attached. Running 'mvn generate-sources' returns an error, whereas running 'mvn package' completes successfully.
Best regards, Alfie.
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
> Attachments: maven-dependency-bug.zip
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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
[jira] Updated: (MNG-2277) aggregating plugins in submodules of the
reactor return all projects causing a chicken/egg issue
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2277?page=all ]
John Casey updated MNG-2277:
----------------------------
Fix Version: 2.1
> aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Type: Bug
> Components: Reactor and workspace, Plugins and Lifecycle, Plugin API
> Versions: 2.0.4
> Reporter: Brett Porter
> Fix For: 2.1
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.
--
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