You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Mikael Edlund <mi...@easit.se> on 2009/02/26 11:32:19 UTC
Can't use properties in version for parent
Hi
I can't build a multimodule project structure.
The parent builds fine without "--non-recursive" option
but children gets:
[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/se/mycompany/fir/fir-gem/${firGemVersion}/fir-gem-${firGemVersion}.pom
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: se.mycompany.fir
ArtifactId: fir-gem
Version: ${firGemVersion}
Reason: Unable to download the artifact from any repository
se.mycompany.fir:fir-gem:pom:${firGemVersion}
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: se.mycompany.fir:fir-gem for project: se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion} for project se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion}
The parent is installed in both local and internal repository.
The child has following snippet to point out the parent:
<relativePath>../pom.xml</relativePath>
In the "Working Copy" the parent isn't checked out, so there is no way for Continuum to solve ${firGemVersion}=2.0.0!
What can I do?
I don't want to just build the parent recursively, I want to build the children separately as well.
/MikaelE
SV: Can't use properties in version for parent
Posted by Mikael Edlund <mi...@easit.se>.
Thank you!
I've just realized how stupid that was.
/MikaelE
________________________________
Från: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Skickat: to 2009-02-26 13:21
Till: users@continuum.apache.org
Ämne: Re: Can't use properties in version for parent
It is a bad practice to define the parent version with a property.If you
checkout only your module and try to build it with maven, you'll have the
same error.
The parent version must be define explicitly in your modules POMS
Emmanuel
On Thu, Feb 26, 2009 at 11:32 AM, Mikael Edlund <mi...@easit.se>wrote:
> Hi
> I can't build a multimodule project structure.
>
> The parent builds fine without "--non-recursive" option
> but children gets:
>
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/se/mycompany/fir/fir-gem/${firGemVersion}/fir-gem-${firGemVersion}.pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> GroupId: se.mycompany.fir
> ArtifactId: fir-gem
> Version: ${firGemVersion}
>
> Reason: Unable to download the artifact from any repository
>
> se.mycompany.fir:fir-gem:pom:${firGemVersion}
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> se.mycompany.fir:fir-gem for project:
> se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion} for project
> se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion}
>
> The parent is installed in both local and internal repository.
>
> The child has following snippet to point out the parent:
> <relativePath>../pom.xml</relativePath>
>
> In the "Working Copy" the parent isn't checked out, so there is no way for
> Continuum to solve ${firGemVersion}=2.0.0!
>
> What can I do?
>
> I don't want to just build the parent recursively, I want to build the
> children separately as well.
>
> /MikaelE
>
Re: Can't use properties in version for parent
Posted by Emmanuel Venisse <em...@gmail.com>.
It is a bad practice to define the parent version with a property.If you
checkout only your module and try to build it with maven, you'll have the
same error.
The parent version must be define explicitly in your modules POMS
Emmanuel
On Thu, Feb 26, 2009 at 11:32 AM, Mikael Edlund <mi...@easit.se>wrote:
> Hi
> I can't build a multimodule project structure.
>
> The parent builds fine without "--non-recursive" option
> but children gets:
>
> [INFO] Scanning for projects...
> Downloading:
> http://repo1.maven.org/maven2/se/mycompany/fir/fir-gem/${firGemVersion}/fir-gem-${firGemVersion}.pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> GroupId: se.mycompany.fir
> ArtifactId: fir-gem
> Version: ${firGemVersion}
>
> Reason: Unable to download the artifact from any repository
>
> se.mycompany.fir:fir-gem:pom:${firGemVersion}
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> se.mycompany.fir:fir-gem for project:
> se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion} for project
> se.mycompany.fir.gem:fir-gem-ear:ear:${firGemVersion}
>
> The parent is installed in both local and internal repository.
>
> The child has following snippet to point out the parent:
> <relativePath>../pom.xml</relativePath>
>
> In the "Working Copy" the parent isn't checked out, so there is no way for
> Continuum to solve ${firGemVersion}=2.0.0!
>
> What can I do?
>
> I don't want to just build the parent recursively, I want to build the
> children separately as well.
>
> /MikaelE
>