You should always ensure that you have a default value for properties set by profiles. Most likely you're running into some scenario where the profile just isn't active. So, in your pom you should define the property as well.
May I also add that what you're trying to do is not good. IMHO you should never alter dependencies through profiles as this will cause problem for people consuming your artifact. As well as for people trying to build your project as they would get a different result (different dependency). /Anders On Sat, Oct 1, 2011 at 02:55, <[email protected]> wrote: > > Using Maven 2.2.1 > I have defined a profile in my settings.xml file, and specified some > properties. This profile is also listed as an active profile. > > For example: > <profile> > <id>third-party-lib-versions</id> > <properties> > <log4j.version>1.2.16</log4j.version> > </properties> > </profile> > <activeProfiles> > <activeProfile>third-party-lib-versions</activeProfile> > </activeProfiles> > > Then I have a dependency in my pom, which references the property: > > <dependency> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > <version>${log4j.version}</version> > </dependency> > > In most cases Maven 2.2.1 will inject the property just fine. But it seems > to also end up creating a $M2_REPO/log4j/log4j/${log4j.version}, and when I > run "mvn test", it complains > [INFO] Unable to find resource 'log4j:log4j:pom:${log4j.version}' in > repository central (xxx) > > Is there something else that I need to do to ensure that properties defined > in settings.xml are always processed ? > > Thanks > Aspi Engineer > Putnam Investments > > > > This message is intended for the recipient only and is not meant to be > forwarded or distributed in any other format. This communication is for > informational purposes only. It is not intended as an offer or solicitation > for the purchase or sale of any financial instrument, or security, or as an > official confirmation of any transaction. Putnam does not accept purchase or > redemptions of securities, instructions, or authorizations that are sent via > e-mail. All market prices, data and other information are not warranted as to > completeness or accuracy and are subject to change without notice. Any > comments or statements made herein do not necessarily reflect those of Putnam > Investments, LLC (DBA Putnam Investments) and its subsidiaries and > affiliates. If you are not the intended recipient of this e-mail, please > delete the e-mail. > > --------------------------------------------------------------------- > 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]
