You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matt Ryall (JIRA)" <ji...@codehaus.org> on 2007/08/29 09:54:11 UTC
[jira] Created: (MDEP-106) Unpacking primary artifact from sibling
module uses repository rather than reactor
Unpacking primary artifact from sibling module uses repository rather than reactor
----------------------------------------------------------------------------------
Key: MDEP-106
URL: http://jira.codehaus.org/browse/MDEP-106
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: unpack
Affects Versions: 2.0-alpha-4
Reporter: Matt Ryall
Assignee: Brian Fox
Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
{quote}
[INFO] [dependency:unpack \{execution: unpack-tests}]
[INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
[INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
[INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
9125K downloaded
[INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
{quote}
To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
- app-core (jar)
- app-acceptance-tests (jar)
- app-webapp (war)
The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
Running 'mvn clean integration-test' does the following relevant tasks:
- in the app-acceptance-test module, compiles and packages a JAR of tests
- in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
{quote}
[INFO] Failed to resolve artifact.
GroupId: com.example.app
ArtifactId: app-acceptance-test
Version: 2.6
Reason: Unable to download the artifact from any repository
{quote}
Maven details:
{noformat}
$ mvn -version
Maven version: 2.0.7
Java version: 1.4.2_12
OS name: "mac os x" version: "10.4.10" arch: "i386"
{noformat}
--
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: (MDEP-106) Unpacking primary artifact from
sibling module uses repository rather than reactor
Posted by "Samuel Le Berrigaud (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223878#action_223878 ]
Samuel Le Berrigaud commented on MDEP-106:
------------------------------------------
If you want to unpack dependencies that are in the reactor the {{dependency:unpack-dependencies}} is the goal you're after. To my understanding {{dependency:unpack}} will only ever look in the local and remote repositories.
> Unpacking primary artifact from sibling module uses repository rather than reactor
> ----------------------------------------------------------------------------------
>
> Key: MDEP-106
> URL: http://jira.codehaus.org/browse/MDEP-106
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Matt Ryall
> Assignee: Brian Fox
>
> Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
> {quote}
> [INFO] [dependency:unpack \{execution: unpack-tests}]
> [INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
> Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
> 9125K downloaded
> [INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
> {quote}
> To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
> - app-core (jar)
> - app-acceptance-tests (jar)
> - app-webapp (war)
> The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
> Running 'mvn clean integration-test' does the following relevant tasks:
> - in the app-acceptance-test module, compiles and packages a JAR of tests
> - in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
> I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
> {quote}
> [INFO] Failed to resolve artifact.
>
> GroupId: com.example.app
> ArtifactId: app-acceptance-test
> Version: 2.6
>
> Reason: Unable to download the artifact from any repository
> {quote}
> Maven details:
> {noformat}
> $ mvn -version
> Maven version: 2.0.7
> Java version: 1.4.2_12
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> {noformat}
--
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: (MDEP-106) Unpacking primary artifact from
sibling module uses repository rather than reactor
Posted by "Matt Ryall (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273301#comment-273301 ]
Matt Ryall commented on MDEP-106:
---------------------------------
Thanks for the update, Stephen.
> Unpacking primary artifact from sibling module uses repository rather than reactor
> ----------------------------------------------------------------------------------
>
> Key: MDEP-106
> URL: https://jira.codehaus.org/browse/MDEP-106
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Matt Ryall
> Assignee: Brian Fox
> Fix For: 2.3
>
>
> Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
> {quote}
> [INFO] [dependency:unpack \{execution: unpack-tests}]
> [INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
> Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
> 9125K downloaded
> [INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
> {quote}
> To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
> - app-core (jar)
> - app-acceptance-tests (jar)
> - app-webapp (war)
> The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
> Running 'mvn clean integration-test' does the following relevant tasks:
> - in the app-acceptance-test module, compiles and packages a JAR of tests
> - in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
> I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
> {quote}
> [INFO] Failed to resolve artifact.
>
> GroupId: com.example.app
> ArtifactId: app-acceptance-test
> Version: 2.6
>
> Reason: Unable to download the artifact from any repository
> {quote}
> Maven details:
> {noformat}
> $ mvn -version
> Maven version: 2.0.7
> Java version: 1.4.2_12
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEP-106) Unpacking primary artifact from sibling
module uses repository rather than reactor
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly closed MDEP-106.
---------------------------------
Resolution: Duplicate
Fix Version/s: 2.3
MDEP-316
> Unpacking primary artifact from sibling module uses repository rather than reactor
> ----------------------------------------------------------------------------------
>
> Key: MDEP-106
> URL: https://jira.codehaus.org/browse/MDEP-106
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Matt Ryall
> Assignee: Brian Fox
> Fix For: 2.3
>
>
> Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
> {quote}
> [INFO] [dependency:unpack \{execution: unpack-tests}]
> [INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
> Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
> 9125K downloaded
> [INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
> {quote}
> To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
> - app-core (jar)
> - app-acceptance-tests (jar)
> - app-webapp (war)
> The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
> Running 'mvn clean integration-test' does the following relevant tasks:
> - in the app-acceptance-test module, compiles and packages a JAR of tests
> - in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
> I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
> {quote}
> [INFO] Failed to resolve artifact.
>
> GroupId: com.example.app
> ArtifactId: app-acceptance-test
> Version: 2.6
>
> Reason: Unable to download the artifact from any repository
> {quote}
> Maven details:
> {noformat}
> $ mvn -version
> Maven version: 2.0.7
> Java version: 1.4.2_12
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-106) Unpacking primary artifact from
sibling module uses repository rather than reactor
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223853#action_223853 ]
Brian Fox commented on MDEP-106:
--------------------------------
It conceivably could be fixed in the plugin to check the reactor, but I'm unlikely to do it since M3 solves this for us. If someone wants to attach a patch then I'll take a look
> Unpacking primary artifact from sibling module uses repository rather than reactor
> ----------------------------------------------------------------------------------
>
> Key: MDEP-106
> URL: http://jira.codehaus.org/browse/MDEP-106
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Matt Ryall
> Assignee: Brian Fox
>
> Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
> {quote}
> [INFO] [dependency:unpack \{execution: unpack-tests}]
> [INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
> Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
> 9125K downloaded
> [INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
> {quote}
> To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
> - app-core (jar)
> - app-acceptance-tests (jar)
> - app-webapp (war)
> The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
> Running 'mvn clean integration-test' does the following relevant tasks:
> - in the app-acceptance-test module, compiles and packages a JAR of tests
> - in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
> I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
> {quote}
> [INFO] Failed to resolve artifact.
>
> GroupId: com.example.app
> ArtifactId: app-acceptance-test
> Version: 2.6
>
> Reason: Unable to download the artifact from any repository
> {quote}
> Maven details:
> {noformat}
> $ mvn -version
> Maven version: 2.0.7
> Java version: 1.4.2_12
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> {noformat}
--
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: (MDEP-106) Unpacking primary artifact from
sibling module uses repository rather than reactor
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223701#action_223701 ]
Dennis Lundberg commented on MDEP-106:
--------------------------------------
As mentioned in MNG-2877, this doesn't seem to be a bug in the Dependency Plugin itself, but rather a bug in the dependency resolution code in Maven core. We've just ran into this very problem. Using Maven 2.0.11 or 2.2.1 the build fails, but using Maven 3.0-beta-1 it is successful.
> Unpacking primary artifact from sibling module uses repository rather than reactor
> ----------------------------------------------------------------------------------
>
> Key: MDEP-106
> URL: http://jira.codehaus.org/browse/MDEP-106
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Matt Ryall
> Assignee: Brian Fox
>
> Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:
> {quote}
> [INFO] [dependency:unpack \{execution: unpack-tests}]
> [INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
> Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
> 9125K downloaded
> [INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes
> {quote}
> To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:
> - app-core (jar)
> - app-acceptance-tests (jar)
> - app-webapp (war)
> The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.
> Running 'mvn clean integration-test' does the following relevant tasks:
> - in the app-acceptance-test module, compiles and packages a JAR of tests
> - in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.
> I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:
> {quote}
> [INFO] Failed to resolve artifact.
>
> GroupId: com.example.app
> ArtifactId: app-acceptance-test
> Version: 2.6
>
> Reason: Unable to download the artifact from any repository
> {quote}
> Maven details:
> {noformat}
> $ mvn -version
> Maven version: 2.0.7
> Java version: 1.4.2_12
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> {noformat}
--
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