On Wed, Feb 9, 2011 at 2:53 PM, Stephen Connolly <[email protected]> wrote: > this is a result of somebody having put dependencies in a profile activated > by java version. > > a mistake was made when the pom schema was defined in allowing dependencies > to be part of profiles.
Are you saying that in version 3.1 dependencies won't be allowed per schema? I use that capability to make sure that some "debug" jars (specifically the Struts config-browser plugin) won't be included on a production deploy. Is there a better way to do that? -- Greg Akins http://twitter.com/akinsgre --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
