Hello,
I've been using properties-maven-plugin bound to validation phase in
order to set some environment properties that is needed for the
different targets. it's been working pretty well.
I have a case now where I'll need different artifact versions for each
different target environments.
Then I tried to add the versions in the same properties files being used
and set the pom to use them. for example:
<dependency>
<groupId>com.hawk</groupId>
<artifactId>runtime.controller</artifactId>
<version>${runtime.controller.version}</version>
</dependency>
But that didn't work as I expected. The ide/m2e is complained about a
non existing dependency and I could see a
"${runtime.controller.version}" directory was created in the local
repository.
questions:
- is dependencies resolution done before the plugins lifecycle to start ?
- is the properties written in the pom the only way to set
dependencies versions?
many thanks,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
