2.5 will include an "excludes" parameter : <excludes> <exclude>groupId:artifactId</exclude>
</excludes> But this is equivalent to <exclusions> in dependencies 2008/2/1, TM <[EMAIL PROTECTED]>: > > > > nicolas de loof-3 wrote: > > > > For 1), you should use <exclusions> to block transitive dependencies. > > > > For 2), any code generation plugin that runs before generate-resource > > phase > > will get executed by mvn eclipse:eclipse and the generated source folder > > added to the .classpath. If you don't get this behaviour, maybe you > > missuse > > the plugin, or this one is not compliant with maven standards. > > > > I'm sorry to say that but <exclusions> are not an option. The effort to > maintain them for large projects are too high. I guess I have to live with > that for the time being. Maybe I should open a feature request for the > Eclipse plugin and see if there are more people wishing that. > > Regarding the second point: I tried to run "mvn install eclipse:eclipse" > and > it works, i.e., it will include the additional source folder. Thanks! > > Thorsten > -- > View this message in context: > http://www.nabble.com/Two-question-regarding-the-Eclipse-plugin-tp15207989s177p15231842.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
