Maybe someone else can chime in here, but if XXX:AAA is not the parent of
XXX:BBB I don't think XXX:BBB will have the buildVersion property defined.
If that property isn't defined then XXX:BBB will not be able to resolve a
dependency to XXX:CCC because it doesn't know which version you want, since
${buildVersion} isn't defined.
Perhaps I am missing something?
-Evan
On 5/23/07, Steinhauer, Frank <[EMAIL PROTECTED]> wrote:
Hi Evan,
XXX:AAA is not the parent of XXX:BBB. I've tried two scenarios, one
multi-module project, where 10 JARs are built, and some jars depending on
previous built ones (here I'm using <dependencyManagement> in the top most
POM, setting the version number for the jar/module dependencies to the same
as used for that POM), and for testing purpose some single projects, that
are depending on each other.
Here's my setting.xml snippet:
<profiles>
<profile>
<id>setting_label</id>
<properties>
<point>-</point> <!-- use "." on the CC server, "-" local
-->
<label>SNAPSHOT</label><!-- is set automatically by CC, use
"SNAPSHOT" locally -->
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>setting_label</activeProfile>
</activeProfiles>
-Frank
-----Ursprüngliche Nachricht-----
Von: Evan Worley [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 23. Mai 2007 17:30
An: Maven Developers List
Betreff: Re: install:install - variables in POM are not replaced/filtered
during installation in repository
Hi Frank,
From the information you posted, I have a few questions.
1. Is XXX:AAA the parent of XXX:BBB? If not, I don't believe XXX:BBB
would
not inherit the definition of the ${buildVersion} property.
2. Where do you set ${label}, in your settings.xml? If so can you post
the
relevant snippet?
-Evan
On 5/23/07, Steinhauer, Frank <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> during installation of the POM in the local repository the variables are
> not replaced/filtered. Is this a bug or purpose? Or did I a make a
> mistake somewhere?
> Explanation:
> In our POMs we set the version numbers according to local settings and
> given CLI parameters, and do this in our multi module projects for the
> intern dependecies (dependencies to other modules) as well. So when Jar
> AAA depends on Jar BBB that depends on Jar CCC (all version numbers are
> variables), the POM of BBB is loaded, but then the further load of Jar
> CCC fails, it tries to load XXX:CCC:jar:1.2${point}${label} or
> XXX:CCC:jar:1.2${buildVersion} (the later in the multi module build).
> Any suggestions? I'm glad for any assistence, since it cost me already
> three days figuring that out....
>
>
> Cheers,
>
> Frank
>
>
>
> Example POM for AAA:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
>
> <groupId>XXX</groupId>
> <artifactId>AAA</artifactId>
> <version>${buildVersion}</version> <!-- used throughout all of our
> projects/modules -->
> <packaging>jar</packaging>
> <properties>
> <versionNo>1.2</versionNo>
> <buildVersion>${versionNo}${point}${label}</buildVersion>
> <!-- point and label are set differently in a local build and in the
> CruiseControl build -->
> </properties>
> ...
> <dependencies>
> <dependency>
> <groupId>XXX</groupId>
> <artifactId>BBB</artifactId>
> <version>${buildVersion}</version>
> <type>jar</type>
> </dependency>
> </dependencies>
> ...
> </project>
>
>
> Similiar example POM for BBB:
>
> ...
> <artifactId>BBB</artifactId>
> <version>${buildVersion}</version> <!-- used throughout all of our
> projects/modules -->
> ...
> <dependency>
> <groupId>XXX</groupId>
> <artifactId>CCC</artifactId>
> <version>${buildVersion}</version>
> <type>jar</type>
> </dependency>
> ...
> </project>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
