[jira] Commented: (MREACTOR-15) mvn reactor:make-scm-changes doesn't work in windows with subversion
[ http://jira.codehaus.org/browse/MREACTOR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219878#action_219878 ] Chris Wewerka commented on MREACTOR-15: --- Another hint: don't use cygwin on windows for this, it only works with cmd.exe > mvn reactor:make-scm-changes doesn't work in windows with subversion > > > Key: MREACTOR-15 > URL: http://jira.codehaus.org/browse/MREACTOR-15 > Project: Maven 2.x Reactor Plugin > Issue Type: Bug >Affects Versions: 1.0 > Environment: windows xp, subversion 1.6.2 command line >Reporter: Roger Pack >Priority: Minor > Attachments: patch.txt > > > In my project, if I update a file, call it > root > /updatemigrationdb > pom.xml > If I update pom.xml and have uncommitted changes there, in linux I get > [INFO] Reactor Summary: > [INFO] > > [INFO] Migration updatemigrationdb ... SUCCESS > [3.741s] > [INFO] Migration TapeWriter .. SUCCESS > [4.361s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Mon Oct 19 17:22:49 MDT 2009 > [INFO] Final Memory: 43M/731M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > however, on windows I get > C:\dev\trunk>mvn reactor:make-scm-changes > ... > [INFO] Executing: cmd.exe /X /C "svn --non-interactive status" > [INFO] Working directory: C:\dev\trunk > [INFO] Going to make dependents for: > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] No folders matched: > ... > The output of said command line is > C:\dev\trunk>cmd /X /C "svn --non-interactive status" > M pom.xml > M updatemigrationdb\pom.xml > (i.e. ? cmd.exe\nM pom.xml\nM updatemigrationdb\\pom.xml\n") > Thanks! > -r -- 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: (MREACTOR-15) mvn reactor:make-scm-changes doesn't work in windows with subversion
[ http://jira.codehaus.org/browse/MREACTOR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Wewerka updated MREACTOR-15: -- Attachment: patch.txt The cause of this problem is that the Maven SCM RepoManager returns an empty list of changed files. This can be fixed by using the newest maven scm components. See the attached patch file. > mvn reactor:make-scm-changes doesn't work in windows with subversion > > > Key: MREACTOR-15 > URL: http://jira.codehaus.org/browse/MREACTOR-15 > Project: Maven 2.x Reactor Plugin > Issue Type: Bug >Affects Versions: 1.0 > Environment: windows xp, subversion 1.6.2 command line >Reporter: Roger Pack >Priority: Minor > Attachments: patch.txt > > > In my project, if I update a file, call it > root > /updatemigrationdb > pom.xml > If I update pom.xml and have uncommitted changes there, in linux I get > [INFO] Reactor Summary: > [INFO] > > [INFO] Migration updatemigrationdb ... SUCCESS > [3.741s] > [INFO] Migration TapeWriter .. SUCCESS > [4.361s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Mon Oct 19 17:22:49 MDT 2009 > [INFO] Final Memory: 43M/731M > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > however, on windows I get > C:\dev\trunk>mvn reactor:make-scm-changes > ... > [INFO] Executing: cmd.exe /X /C "svn --non-interactive status" > [INFO] Working directory: C:\dev\trunk > [INFO] Going to make dependents for: > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] No folders matched: > ... > The output of said command line is > C:\dev\trunk>cmd /X /C "svn --non-interactive status" > M pom.xml > M updatemigrationdb\pom.xml > (i.e. ? cmd.exe\nM pom.xml\nM updatemigrationdb\\pom.xml\n") > Thanks! > -r -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141192#action_141192 ] Chris Wewerka commented on MNG-2871: May there be any hope that this very annoying bug will also be fixed in 2.0.x version of maven? > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, > MNG-2871-core-integration-testing-2.diff, > MNG-2871-core-integration-tests.diff, > MNG-2871-maven-project-2.1-SNAPSHOT.diff, MNG-2871-maven-project.diff, > root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > --
[jira] Commented: (MRELEASE-230) release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies
[ http://jira.codehaus.org/browse/MRELEASE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113512 ] Chris Wewerka commented on MRELEASE-230: No, sorry. > release:prepare cannot update the version of a module in a multi-module build > if you have both normal artifact and attached artifact in dependencies > > > Key: MRELEASE-230 > URL: http://jira.codehaus.org/browse/MRELEASE-230 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Chris Wewerka > Attachments: release-test.zip > > > Following situation: > you have a multimodule build with 2 modules A,B, and B has two dependencies > to A, one for the "normal" jar artifact and one for an attached artifact > (e.g. the test-jar of A). > The release will fail with: > ... > [INFO] Transforming 'O2 Release test Base Module'... > [INFO] Checking out file: > E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\pom.xml > [INFO] Transforming 'release-test-module-one'... > [INFO] Checking out file: > E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\release-test-module-one\pom.xml > [INFO] Transforming 'release-test-module-two'... > [INFO] Updating release-test-module-one to 5.0.2 > [INFO] Updating release-test-module-one to 5.0.2 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] The version could not be updated: 5.0.2 > [INFO] > > [INFO] For more information, run Maven with the -e switch -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104986 ] Chris Wewerka commented on MNG-2871: Piotr, I've tested it and it's working with test jars. Thanks. Hopefully the new version of the jar plugin is to be released soon! > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor >Assignee: John Casey > Fix For: 2.1-alpha-1 > > Attachments: MavenProject.java, MNG-2871-core-integration-tests.diff, > root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) pl.waw.tabor:ejb3:ejb-
[jira] Updated: (MNG-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Wewerka updated MNG-2871: --- Attachment: MavenProject.java Hack in MavenProject.java (Line 1643 ff.) and commented sysouts. > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor > Attachments: MavenProject.java, root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, i
[jira] Commented: (MNG-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[
http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95563
]
Chris Wewerka commented on MNG-2871:
I tested the supplied patch (extended for test-jars) by piotr (i know it's a
hack, but we need it working too) with maven 2.0.6 and release plugin
2.0-beta-5, and it doesn't work during release:prepare.
I've added some sysouts to track down the problem (see attached
MavenProject.java) and I think the problem in m2.0.6(at least with test-jars)
lies in a loss of the type information "test-jar".
Attached artifact: org.apache.maven.project.artifact.AttachedArtifact
Attached artifact: release-test-module-one:com.o2.release-test:jar:null
attached.getDependencyConflictId():
com.o2.release-test:release-test-module-one:jar:tests
;pluginArtifact.getDependencyConflictId():com.o2.release-test:release-test-module-one:test-jar:tests
Here you can see that "attached.getDependencyConflictId()" returns
com.o2.release-test:release-test-module-one:jar:tests.
I would expect com.o2.release-test:release-test-module-one:test-jar:tests, so
the next code line returns false during release:prepare:
...
if(
attached.getDependencyConflictId().equals(pluginArtifact.getDependencyConflictId())
...
So what I`ve done is to add the following hack:
if(
attached.getDependencyConflictId().equals(pluginArtifact.getDependencyConflictId())
||
(
attached.getArtifactId().equals(pluginArtifact.getArtifactId()) &&
attached.getGroupId().equals(pluginArtifact.getGroupId()) &&
attached.getClassifier() != null &&
attached.getClassifier().equals(pluginArtifact.getClassifier())
)
) {
...
But I'm very sure the real problem lies somewhere else.
> Subartifact (ejb-client for example) are not reselved as active project
> artifacts
> -
>
> Key: MNG-2871
> URL: http://jira.codehaus.org/browse/MNG-2871
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.4, 2.0.5
> Environment: Not platform dependent
>Reporter: Piotr Tabor
> Attachments: root.tar
>
>
> I have prepared simple project to show the bug.
> It contains three artifacts:
> |-root
> \--- ejb3
> \--- client
> Client depends on ejb3 with ejb-client.
> The local and remote repository must not contain those artifacts.
> When I do "mvn -X compile" (or even integration-tests) on root project I will
> get those errors:
> ...
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' -->
> [DEBUG] (f) filters = []
> [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes
> [DEBUG] (f) project = [EMAIL PROTECTED]
> [DEBUG] (f) resources = [EMAIL PROTECTED]
> [DEBUG] -- end configuration --
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null)
> [DEBUG] junit:junit:jar:3.8.1:test (selected for test)
> [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected
> for compile)
> [DEBUG] Skipping disabled repository Newitech-repository
> [DEBUG] Skipping disabled repository central
> [DEBUG] ejb3: using locally installed snapshot
> [DEBUG] Trying repository Newitech-snapshots-repository
> Downloading:
> scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar
> [WARNING] Unable to get resource
> 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository
> Newitech-snapshots-repository
> (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots)
> [DEBUG] Skipping disabled repository Newitech-repository
> [DEBUG] Trying repository Newitech-publiczne
> Downloading:
> scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar
> [WARNING] Unable to get resource
> 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository
> Newitech-publiczne
> (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/)
> [DEBUG] Trying repository Maven Snapshots
> Downloading:
> http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar
> [WARNING] Unable to get resource
> 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven
> Snapshots (http://people.apache.org/maven-snapshot-repository)
> [DEBUG] Trying repository codehausSnapshots
> Downloading:
> http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-
[jira] Commented: (MNG-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95537 ] Chris Wewerka commented on MNG-2871: Maven 2.0.6 with release plugin 2.0-beta 5 also has the problem. See http://jira.codehaus.org/browse/MRELEASE-161 > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor > Attachments: root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > Try downloading the file manually from the proj
[jira] Updated: (MRELEASE-161) If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated
[ http://jira.codehaus.org/browse/MRELEASE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Wewerka updated MRELEASE-161: --- Attachment: release-test.zip Testcase for the above comment > If there is more than one artifact with the same artifactId in > dependencyManagement only the first one is updated > - > > Key: MRELEASE-161 > URL: http://jira.codehaus.org/browse/MRELEASE-161 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: Maven 2.0.4 under windows >Reporter: Sébastien Cesbron > Attachments: multipleArtifacts.patch, release-test.zip > > > I have a multi module project. When I do release:prepare, the release plugin > update the version tag of all my submodules in the dependencyManagement > section. > For the same module I have declared two artifacts like this : > > com.bla > blabla > 1.0-SNAPSHOT > test-jar > test > > > com.bla > blabla > 1.0-SNAPSHOT > > In this case, the release plugin only update the first dependency. > This is due to element search in the "updateDomVersion" method of the > AbstractRewritePomsPhase class. I've attached a patch to solve the problem. I > don't know if this is the right way to do. I change all the artifacts in the > same pass. I don't take car of different type/classifier -- 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: (MRELEASE-161) If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated
[ http://jira.codehaus.org/browse/MRELEASE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95484 ] Chris Wewerka commented on MRELEASE-161: With 2.0-beta-5 and maven 2.0.6 a related issue (two dependencies to a project, one to the normal artifact, one to the test-jar) results in an error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.o2.release-test:release-test-module-one:test-jar:tests:5.0.2 I've attached a testcase to reproduce this bug. > If there is more than one artifact with the same artifactId in > dependencyManagement only the first one is updated > - > > Key: MRELEASE-161 > URL: http://jira.codehaus.org/browse/MRELEASE-161 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: Maven 2.0.4 under windows >Reporter: Sébastien Cesbron > Attachments: multipleArtifacts.patch > > > I have a multi module project. When I do release:prepare, the release plugin > update the version tag of all my submodules in the dependencyManagement > section. > For the same module I have declared two artifacts like this : > > com.bla > blabla > 1.0-SNAPSHOT > test-jar > test > > > com.bla > blabla > 1.0-SNAPSHOT > > In this case, the release plugin only update the first dependency. > This is due to element search in the "updateDomVersion" method of the > AbstractRewritePomsPhase class. I've attached a patch to solve the problem. I > don't know if this is the right way to do. I change all the artifacts in the > same pass. I don't take car of different type/classifier -- 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] Created: (MRELEASE-230) release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies
release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies Key: MRELEASE-230 URL: http://jira.codehaus.org/browse/MRELEASE-230 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Reporter: Chris Wewerka Attachments: release-test.zip Following situation: you have a multimodule build with 2 modules A,B, and B has two dependencies to A, one for the "normal" jar artifact and one for an attached artifact (e.g. the test-jar of A). The release will fail with: ... [INFO] Transforming 'O2 Release test Base Module'... [INFO] Checking out file: E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\pom.xml [INFO] Transforming 'release-test-module-one'... [INFO] Checking out file: E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\release-test-module-one\pom.xml [INFO] Transforming 'release-test-module-two'... [INFO] Updating release-test-module-one to 5.0.2 [INFO] Updating release-test-module-one to 5.0.2 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The version could not be updated: 5.0.2 [INFO] [INFO] For more information, run Maven with the -e switch -- 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-2931) DefaultArtifactCollector changes the version of the originatingArtifact if it's in the dependencyManagement with another version
[ http://jira.codehaus.org/browse/MNG-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93982 ] Chris Wewerka commented on MNG-2931: Very, very ugly effect of this bug is that already deployed versions are overwritten by newer versions without notice. Maven changes the artifact version to the managed version and deploys it to the repository > DefaultArtifactCollector changes the version of the originatingArtifact if > it's in the dependencyManagement with another version > > > Key: MNG-2931 > URL: http://jira.codehaus.org/browse/MNG-2931 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts >Affects Versions: 2.0.5, 2.0.6 >Reporter: Carlos Sanchez > Attachments: MNG-2931.patch > > > DefaultDependencyTreeBuilder > https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree/src/main/java/org/apache/maven/shared/dependency/tree/DefaultDependencyTreeBuilder.java > calls collect like this > collector.collect( project.getDependencyArtifacts(), > project.getArtifact(), managedVersions, repository, >project.getRemoteArtifactRepositories(), > metadataSource, null, >Collections.singletonList( listener ) ); > Problem: > This pom > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-22/plexus-component-api-1.0-alpha-22.pom > extends > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0-alpha-22/plexus-containers-1.0-alpha-22.pom > that in dependencyManagement has > org.codehaus.plexus:plexus-component-api:1.0-alpha-19 > so during collect project.getArtifact().getVersion() is changed to the > managedVersion instead of the original one > Either this is a bug or an exception should be thrown when > originatingArtifact is in managedVersions -- 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: (MRM-268) Archivas relocation feature should be configurable
[ http://jira.codehaus.org/browse/MRM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85639 ] Chris Wewerka commented on MRM-268: --- Hello Nicolas, thanks for your comment. I think there is something broken then with your described behavior in archivas latest checkouts. If I use an relocated artifact with our archiva, I do get the maven1 behavior although I'm using maven 2. E.g. I request activation/activation/1.0.2 with my maven 2.0.4 client I do not get the pom under activation/activation with the relocation info to javax.activation but the pom which resides under javax.activation in our archivas cache. Looks like a bug to me. > Archivas relocation feature should be configurable > -- > > Key: MRM-268 > URL: http://jira.codehaus.org/browse/MRM-268 > Project: Archiva > Issue Type: Improvement >Reporter: Chris Wewerka > > Archiva automatically delivers the new pom and jar for a relocated artifact > to a maven client. > The downside of this feature is that clients do not get a warning that the > artifact is relocated anymore. > In a "All-Maven2" environment this warning is quite good, and gives the > developer a hint and a motivation (get rid of the warning ;-) ) to use the > new groupId. > So I think it would be a good idea to make this feature configurable, so the > archiva admin can turn it off. -- 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] Created: (MRM-268) Archivas relocation feature should be configurable
Archivas relocation feature should be configurable -- Key: MRM-268 URL: http://jira.codehaus.org/browse/MRM-268 Project: Archiva Issue Type: Improvement Reporter: Chris Wewerka Archiva automatically delivers the new pom and jar for a relocated artifact to a maven client. The downside of this feature is that clients do not get a warning that the artifact is relocated anymore. In a "All-Maven2" environment this warning is quite good, and gives the developer a hint and a motivation (get rid of the warning ;-) ) to use the new groupId. So I think it would be a good idea to make this feature configurable, so the archiva admin can turn it off. -- 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: (MRM-243) 507 Insufficient Storage when deploying artifact with webdav
[ http://jira.codehaus.org/browse/MRM-243?page=comments#action_83898 ] Chris Wewerka commented on MRM-243: --- We have the same problem in the following environment: Client Side : mvn 2.0.4, slide 2.1, wagon-webdav-1.0-beta-2 Archiva Side: Java 1.5.0_10, Tomcat 5.5.20 > 507 Insufficient Storage when deploying artifact with webdav > > > Key: MRM-243 > URL: http://jira.codehaus.org/browse/MRM-243 > Project: Archiva > Issue Type: Bug > Components: web application > Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK > 1.5.0_08, archiva HEAD >Reporter: Magne Rasmussen > Fix For: 1.0 > > > Sometimes when deploying with dav I get a "507 Insufficient Storage" error. > The artifact (.../group/artifact/version/artifact-version.jar) gets deployed > (with checksums). > The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed > (with checksums). > It seems to happen when maven tries to upload the updated parent metadata > (.../group/artifact/maven-metadata.xml). The checksums for this metadata > deploys OK. -- 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] Created: (MWAR-63) Online available docu (corresponds to 2.0.2) is not in sync with released version 2.0.1 on ibiblio
Online available docu (corresponds to 2.0.2) is not in sync with released version 2.0.1 on ibiblio -- Key: MWAR-63 URL: http://jira.codehaus.org/browse/MWAR-63 Project: Maven 2.x War Plugin Issue Type: Task Reporter: Chris Wewerka Priority: Critical The documentation of the plugin (especially http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html) refers to features only available in versions of the plugin which are not yet deployed (2.0.2 and later) on ibiblio. This is very misleading. Example: the property 'targetPath' If you try to access the source code and build the plugin by yourself, you'll notice that the version was already raised to 2.1-SNAPSHOT. Will the 2.0.2 never be released? -- 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] Created: (MPLUGIN-21) Use of Java 5 annotations in Mojos produce error in QDox Parser
Use of Java 5 annotations in Mojos produce error in QDox Parser
---
Key: MPLUGIN-21
URL: http://jira.codehaus.org/browse/MPLUGIN-21
Project: Maven 2.x Plugin Plugin
Type: Bug
Versions: 2.1
Environment: Windows 2000
JAVA5 1.5.0_06
Reporter: Chris Wewerka
If you use Java5 annotations in Mojos, the java extractor throws the following
exception:
com.thoughtworks.qdox.parser.ParseException: syntax error @[16,5] in
file:/E:/prj/o2/o2-sg/sd_area51_3/OcToPuS/tools/maven/plugins/maven-jax
wstools-plugin/src/main/java/com/o2/m2/plugins/jaxwstools/TestMojo.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
[...]
The mojo I've used:
package com.o2.m2.plugins.jaxwstools;
import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.maven.plugin.MojoFailureException;
/**
* @goal testgoal
* @phase process-classes
*
*/
public class TestMojo extends AbstractMojo
{
@Override
public boolean equals(Object obj)
{ return super.equals(obj); }
public void execute() throws MojoExecutionException, MojoFailureException
{}
}
--
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
