Hi, Thanks for your response. The dependency's scope is "provided", so that if the user supplies the relevant classes at runtime, extra features are enabled dynamically. The project is Tapestry, but the new component will be added to the contrib module, not the core module. Since it is a new component and the code is not yet in Subversion, there's not much for you to look at as of yet...it looks like it's time to start reading up on custom Maven plugins.
Regards, Daniel Gredler On 7/12/06, D&J Gredler <[EMAIL PROTECTED]> wrote: > I'm trying to add some code to an Apache project that depends on an > LGPL-licensed jar (the dependency is scoped "provided"). In order to > satisfy > legal, we need to add an alert or warning the first time a user builds the > project, telling the user about the dependency and allowing them to either > continue building or cancel the build. Is there currently a way to do > this? > If not, what's the best extension point? I don't think Maven 2.0 supports this. Having 'click through' licensing has been discussed with respect to some Sun jars that require it. It's probably in JIRA, though I couldn't say which component. For Struts 2 we have an 'extras' profile that includes the additional dependencies and builds a separate jar. The user has to explicitly enable it. Your description sounds like it's impossible to build the project without the LGPL dependency -- is it really required at runtime, or is it optional? (Which project? I can take a look if you want.) -- Wendy -- View this message in context: http://www.nabble.com/-m2--dependency-license-warning-tf1931002.html#a5356672 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
