There aren't custom scopes (the war plugin doesn't do anything except use the standard ones).
If you only want to include a couple of them, you can specify their id's in your plugin's configuration. Wouldn't you be including everything that gets an appropriate manifest entry? So you should already know what they are. Generally, scope is used though - probably one of runtime, compile or provided. - Brett On 8/13/05, Bennett, Timothy (JIS - Applications) <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 12, 2005 9:50 AM > > To: Maven Users List > > Subject: Re: [m2] Dependencies as resources > > > > On 8/13/05, Bennett, Timothy (JIS - Applications) > > <[EMAIL PROTECTED]> wrote: > > > Ok... So the steps are jar:jar to jar my target, then > > > assembly:assembly to add a dependency jar file to that > > target archive? > > > > No, assembly is to distribute a jar differently, it would > > produce a different artifact. > > > > Is this an OSGi feature? If so, it should be added to your > > OSGi plugin. > > > > In essence, yeah. So... (thinking out loud here)... I could code my > osgi plug-in perhaps to recognize a custom dependency scope value (like > the war goal) and embed the dependency in the target jar that way, > perhaps? > > > > --------------------------------------------------------------------- > 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]
