On 7 Jun 2010, at 03:09, Paul Gier wrote:
Aleksandar Kostadinov wrote:
> Andrew Lee Rubinger wrote, On 06/04/2010 09:54 PM (EEST):
>> I stand by it. Just because there's no guard to prevent transitive
>> unversioned SNAPSHOT deps. I say "generally" because you can manually
>
> Not a maven expert but it shouldn't be hard to write a plug-in to
> validate there are no unversioned snapshot dependencies if it really
> causes so much hassle. Perhaps fail the build if an artifact's version
> ends with "SNAPSHOT".
>
> Or perhaps it will be possible to have the plug-in look at an xml file
> (in our case the component-matrix) and compare all dependencies defined
> in that file to the project dependencies. In case there are project
> dependencies not defined in the component-matrix (or with a different
> version), the build should fail with a descriptive error message.
>
> Not sure if it will be worth the effort though.
>
>> certify your stuff OK for inclusion into AS trunk, a valid exception.
>>
>> S,
>> ALR
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
The Maven enforcer plugin can already prevent snapshot dependencies [1]. I'm
not sure if this would mess up the inter-module snapshot dependencies though.
[
1]http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
Last time I checked, it doesn't ignore the other modules in a multi-module project
which makes it a bit useless.
http://jira.codehaus.org/browse/MENFORCER-85