This is a bad idea and you should not do this. You need to have repeatable builds.
If you are building something that will last, you will eventually have to maintain many versions of your application and if you do not control the versions of your dependencies, you will have very bad things happen to you when you are need to make a patch to a production system. It may build OK and your tests of your patches might work but a subtle change to one of your dependencies might cause a completely unrelated part of your application to suddenly fail after you have deployed your patch.
Fix your dependencies once per release. It takes a bit of time but it is part of the process of starting a new release.
Ron On 17/01/2011 8:26 AM, [email protected] wrote:
In the archetype I don´t want to use in dependencies the real versions (they change very often and the maintenance of them would be very time-consuming). Instead I would like to set something like <version>9.9.9-SNAPSHOT</version>, so using the archetype it would not be possible to forget setting the correct version. Unfortunatelly I get the message 'Unable to download the artifact from any repository' during creating the archetype. Is it any possibility to do it? Many thanks for your hints, Sonja
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
