You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mirko Jahn (JIRA)" <ji...@codehaus.org> on 2010/05/20 17:40:12 UTC
[jira] Created: (MNG-4683) Can't find parent poms in multi project
build, if on the same level
Can't find parent poms in multi project build, if on the same level
-------------------------------------------------------------------
Key: MNG-4683
URL: http://jira.codehaus.org/browse/MNG-4683
Project: Maven 2 & 3
Issue Type: Bug
Components: Bootstrap & Build, Reactor and workspace
Affects Versions: 3.0-beta-1, 3.0-alpha-7, 3.0-alpha-6
Environment: Tested on WinXP sp3, Java 1.6.20 (Sun)
Reporter: Mirko Jahn
Attachments: mvn2cleanInstall.txt, mvn3cleanInstall.txt, TestCase.zip
I created a test project to verify the behavior. Basically, in Maven 3 the build failed due to missing parent poms. However, these poms are part of the actual multi module build.
To verify the bug:
1. unzip the project and jump into the root folder to the first pom.xml
2. execute with maven 3: "mvn clean install" (see file mvn3cleanInstall.txt)
==> the build will fail
3. execute the same command with maven 2 (I used 2.2.1) (see file mvn2cleanInstall.txt)
==> you'll see it will work without any problems (warning, because my plugins do not contain any code)
4. execute the same command as done in step 2 again (see file mvn3cleanInstall2.txt)
==> now it'll build, because it can find the artifacts in the local repo (created by the maven 2 build). It will eventually still fail, but not due to the above mentioned error but the fact, that I didn't include any source code for the plug-ins to keep it as simple as possible)
The really nasty thing about this bug is that you might not even notice that there is a bug, as long as you have such an artifact in your repository. Unfortunately then, only the wrong version get's picked up. Of course, as soon as you want to release this will fail.
--
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-4683) Can't find parent poms in multi project
build, if on the same level
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4683.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
Your POMs are missing the proper {{<relativePath>}} specification to the parent, cf. the [compat notes|https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ParentPOMResolution].
> Can't find parent poms in multi project build, if on the same level
> -------------------------------------------------------------------
>
> Key: MNG-4683
> URL: http://jira.codehaus.org/browse/MNG-4683
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Bootstrap & Build, Reactor and workspace
> Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1
> Environment: Tested on WinXP sp3, Java 1.6.20 (Sun)
> Reporter: Mirko Jahn
> Assignee: Benjamin Bentmann
> Attachments: mvn2cleanInstall.txt, mvn3cleanInstall.txt, mvn3cleanInstall2.txt, TestCase.zip
>
>
> I created a test project to verify the behavior. Basically, in Maven 3 the build failed due to missing parent poms. However, these poms are part of the actual multi module build.
> To verify the bug:
> 1. unzip the project and jump into the root folder to the first pom.xml
> 2. execute with maven 3: "mvn clean install" (see file mvn3cleanInstall.txt)
> ==> the build will fail
> 3. execute the same command with maven 2 (I used 2.2.1) (see file mvn2cleanInstall.txt)
> ==> you'll see it will work without any problems (warning, because my plugins do not contain any code)
> 4. execute the same command as done in step 2 again (see file mvn3cleanInstall2.txt)
> ==> now it'll build, because it can find the artifacts in the local repo (created by the maven 2 build). It will eventually still fail, but not due to the above mentioned error but the fact, that I didn't include any source code for the plug-ins to keep it as simple as possible)
> The really nasty thing about this bug is that you might not even notice that there is a bug, as long as you have such an artifact in your repository. Unfortunately then, only the wrong version get's picked up. Of course, as soon as you want to release this will fail.
--
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-4683) Can't find parent poms in multi project
build, if on the same level
Posted by "Mirko Jahn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mirko Jahn updated MNG-4683:
----------------------------
Attachment: mvn3cleanInstall2.txt
the last file missing from my explanations of the bug.
> Can't find parent poms in multi project build, if on the same level
> -------------------------------------------------------------------
>
> Key: MNG-4683
> URL: http://jira.codehaus.org/browse/MNG-4683
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Bootstrap & Build, Reactor and workspace
> Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1
> Environment: Tested on WinXP sp3, Java 1.6.20 (Sun)
> Reporter: Mirko Jahn
> Attachments: mvn2cleanInstall.txt, mvn3cleanInstall.txt, mvn3cleanInstall2.txt, TestCase.zip
>
>
> I created a test project to verify the behavior. Basically, in Maven 3 the build failed due to missing parent poms. However, these poms are part of the actual multi module build.
> To verify the bug:
> 1. unzip the project and jump into the root folder to the first pom.xml
> 2. execute with maven 3: "mvn clean install" (see file mvn3cleanInstall.txt)
> ==> the build will fail
> 3. execute the same command with maven 2 (I used 2.2.1) (see file mvn2cleanInstall.txt)
> ==> you'll see it will work without any problems (warning, because my plugins do not contain any code)
> 4. execute the same command as done in step 2 again (see file mvn3cleanInstall2.txt)
> ==> now it'll build, because it can find the artifacts in the local repo (created by the maven 2 build). It will eventually still fail, but not due to the above mentioned error but the fact, that I didn't include any source code for the plug-ins to keep it as simple as possible)
> The really nasty thing about this bug is that you might not even notice that there is a bug, as long as you have such an artifact in your repository. Unfortunately then, only the wrong version get's picked up. Of course, as soon as you want to release this will fail.
--
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