> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Friday, August 12, 2005 10:15 AM > To: Maven Users List > Subject: Re: [m2] Dependencies as resources > > 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. >
Ah, yes. Good idea. The full jar name would be included in the Bundle-ClassPath manifest entry. Then, it's just a matter of parsing the artifactId and version number from the filename(s) specified in the manifest entry, and then using them in the same way the war goal does for including dependencies in the war target. Should be fairly easy. I imagine there might already be some maven utility class(es) for parsing the artifactId out of a full jar filename, perhaps? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
