Hi Lachlan, On Tue, Apr 22, 2008 at 9:31 PM, Lachlan Deck <[EMAIL PROTECTED]> wrote: > The documentation, for WOProject-Maven2 is not very verbose however.
Yeah. The documentation is poor. :( >My dependent frameworks are not of packaging woframework, but jar I think you really should try to use the woframework packaging. You will have to write much less configuration. > - so I can't see what options/configurations to provide to bundle the > relevant dependent > jars (or indeed - what scope they should be). Why do you need the dependencies packaged inside a woframework jar? The dependencies are declared in the pom.xml. When you declare a woframework as dependency, Maven automatically adds the transitive dependencies to your project. For example, if you have a woframework that depends upon a library A. When you add this woframework to a project, Maven will add the dependency A transitively to your project. Cheers, Henrique > I've got the relevant repo and plugin repo declarations in my parent pom > but I'm getting this in the app project: > Cannot find lifecycle mapping for packaging: 'woapplication'. > Component descriptor cannot be found in the component repository: > org.apache.maven.lifecycle.mapping.LifecycleMappingwoapplication. > > > > with regards, > -- > > Lachlan Deck > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
