Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-11-15 Thread diroussel
How are you setting your property? we use: mvn -DbuildVersion=MYAPP_01234 clean install and the substitution ${buildVersion} works fine. David -- View this message in context:

Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-11-14 Thread pjungwir
If you're installing the artifact every build, you might want to use a -SNAPSHOT version. Paul Arne Saeten wrote: Hi, I have the same problem. Any solutions out there? Thanks, Arne - To unsubscribe,

Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-11-08 Thread Arne Saeten
Hi, I have the same problem. Any solutions out there? Thanks, Arne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-05-04 Thread LaCasse, John
Hi, If the version in the pom is specified using a property such as ${env.version} the install plugin is installing the pom in the repository without expanding this property. Hence the pom that gets installed into the repository has a version of ${env.version} which is a totally bogus version.

Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-05-04 Thread Brett Porter
Please reply to your original message asking for a response in future. Creating new threads gets confusing. On 5/5/06, LaCasse, John [EMAIL PROTECTED] wrote: Hi, If the version in the pom is specified using a property such as ${env.version} the install plugin is installing the pom in the