You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gabriele Garuglieri (JIRA)" <ji...@codehaus.org> on 2007/06/25 12:19:57 UTC
[jira] Created: (MNG-3070) ${x} properties no longer expanded in
tag after 2.0.3
${x} properties no longer expanded in </version> tag after 2.0.3
----------------------------------------------------------------
Key: MNG-3070
URL: http://jira.codehaus.org/browse/MNG-3070
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.7
Reporter: Gabriele Garuglieri
I was experimenting with maven using killer-app sample (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
Maven 2.0.3 is able to build the sample out of the box, but any later version up to 2.0.7 chokes telling that it's not able to find the parent project:
C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: com.training.killerapp
ArtifactId: killerapp
Version: 1.0-SNAPSHOT
Reason: Unable to download the artifact from any repository
com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.training.killerapp:killerapp for project: null:killerapp-model:jar:null for project null:killerapp-model:jar:null
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
All the problems looks to be caused by the fact that the root POM has the following construct (that should be perfectly legal) in it:
<version>${killerappVersion}</version>
<properties>
<killerappVersion>1.0-SNAPSHOT</killerappVersion>
</properties>
If i substitute the version tag in the root POM with the following everything works with all versions.
<version>1.0-SNAPSHOT</version>
I was not able to find anywhere in the doc that ${x} substitution is no longer legal in </version> tag, so i think this is a regression from 2.0.3.
Btw, all the test were done with clean local repository.
--
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-3070) ${x} properties no longer expanded in
tag after 2.0.3
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-3070.
---------------------------
Assignee: John Casey
Resolution: Incomplete
The zip you reference in this description no longer exists, and there isn't enough information in this bug report to reproduce the problem. If you have a failing test case that you can attach, please don't hesitate to reopen this issue.
> ${x} properties no longer expanded in </version> tag after 2.0.3
> ----------------------------------------------------------------
>
> Key: MNG-3070
> URL: http://jira.codehaus.org/browse/MNG-3070
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Gabriele Garuglieri
> Assignee: John Casey
> Fix For: 2.0.10
>
>
> I was experimenting with maven using killer-app sample (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
> Maven 2.0.3 is able to build the sample out of the box, but any later version up to 2.0.7 chokes telling that it's not able to find the parent project:
> C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: com.training.killerapp
> ArtifactId: killerapp
> Version: 1.0-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.training.killerapp:killerapp for project: null:killerapp-model:jar:null for project null:killerapp-model:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> All the problems looks to be caused by the fact that the root POM has the following construct (that should be perfectly legal) in it:
> <version>${killerappVersion}</version>
> <properties>
> <killerappVersion>1.0-SNAPSHOT</killerappVersion>
> </properties>
> If i substitute the version tag in the root POM with the following everything works with all versions.
> <version>1.0-SNAPSHOT</version>
> I was not able to find anywhere in the doc that ${x} substitution is no longer legal in </version> tag, so i think this is a regression from 2.0.3.
> Btw, all the test were done with clean local repository.
--
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-3070) ${x} properties no longer expanded in
tag after 2.0.3
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3070:
---------------------------
Affects Version/s: (was: 2.0.7)
2.0.9
will need to verify, even maven uses properties in versions.
> ${x} properties no longer expanded in </version> tag after 2.0.3
> ----------------------------------------------------------------
>
> Key: MNG-3070
> URL: http://jira.codehaus.org/browse/MNG-3070
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Gabriele Garuglieri
> Fix For: 2.0.10
>
>
> I was experimenting with maven using killer-app sample (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
> Maven 2.0.3 is able to build the sample out of the box, but any later version up to 2.0.7 chokes telling that it's not able to find the parent project:
> C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: com.training.killerapp
> ArtifactId: killerapp
> Version: 1.0-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.training.killerapp:killerapp for project: null:killerapp-model:jar:null for project null:killerapp-model:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> All the problems looks to be caused by the fact that the root POM has the following construct (that should be perfectly legal) in it:
> <version>${killerappVersion}</version>
> <properties>
> <killerappVersion>1.0-SNAPSHOT</killerappVersion>
> </properties>
> If i substitute the version tag in the root POM with the following everything works with all versions.
> <version>1.0-SNAPSHOT</version>
> I was not able to find anywhere in the doc that ${x} substitution is no longer legal in </version> tag, so i think this is a regression from 2.0.3.
> Btw, all the test were done with clean local repository.
--
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-3070) ${x} properties no longer expanded in
tag after 2.0.3
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3070:
---------------------------
Affects Version/s: (was: 2.0.9)
2.0.7
Fix Version/s: (was: 2.0.x)
2.0.10
> ${x} properties no longer expanded in </version> tag after 2.0.3
> ----------------------------------------------------------------
>
> Key: MNG-3070
> URL: http://jira.codehaus.org/browse/MNG-3070
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Gabriele Garuglieri
> Fix For: 2.0.10
>
>
> I was experimenting with maven using killer-app sample (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
> Maven 2.0.3 is able to build the sample out of the box, but any later version up to 2.0.7 chokes telling that it's not able to find the parent project:
> C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: com.training.killerapp
> ArtifactId: killerapp
> Version: 1.0-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.training.killerapp:killerapp for project: null:killerapp-model:jar:null for project null:killerapp-model:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> All the problems looks to be caused by the fact that the root POM has the following construct (that should be perfectly legal) in it:
> <version>${killerappVersion}</version>
> <properties>
> <killerappVersion>1.0-SNAPSHOT</killerappVersion>
> </properties>
> If i substitute the version tag in the root POM with the following everything works with all versions.
> <version>1.0-SNAPSHOT</version>
> I was not able to find anywhere in the doc that ${x} substitution is no longer legal in </version> tag, so i think this is a regression from 2.0.3.
> Btw, all the test were done with clean local repository.
--
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-3070) ${x} properties no longer expanded in
tag after 2.0.3
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3070:
------------------------------
Fix Version/s: 2.0.x
> ${x} properties no longer expanded in </version> tag after 2.0.3
> ----------------------------------------------------------------
>
> Key: MNG-3070
> URL: http://jira.codehaus.org/browse/MNG-3070
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Gabriele Garuglieri
> Fix For: 2.0.x
>
>
> I was experimenting with maven using killer-app sample (http://www.sonatype.com/book/examples/book-killerapp.zip) from Sonatipe book (http://www.sonatype.com/book/index.html) and immediately hit a show stopper.
> Maven 2.0.3 is able to build the sample out of the box, but any later version up to 2.0.7 chokes telling that it's not able to find the parent project:
> C:\home\prjHome\mavenTest\killerapp>mvn help:effective-pom
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: com.training.killerapp
> ArtifactId: killerapp
> Version: 1.0-SNAPSHOT
> Reason: Unable to download the artifact from any repository
> com.training.killerapp:killerapp:pom:1.0-SNAPSHOT
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.training.killerapp:killerapp for project: null:killerapp-model:jar:null for project null:killerapp-model:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> All the problems looks to be caused by the fact that the root POM has the following construct (that should be perfectly legal) in it:
> <version>${killerappVersion}</version>
> <properties>
> <killerappVersion>1.0-SNAPSHOT</killerappVersion>
> </properties>
> If i substitute the version tag in the root POM with the following everything works with all versions.
> <version>1.0-SNAPSHOT</version>
> I was not able to find anywhere in the doc that ${x} substitution is no longer legal in </version> tag, so i think this is a regression from 2.0.3.
> Btw, all the test were done with clean local repository.
--
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