On 8/13/05, Bennett, Timothy (JIS - Applications)
<[EMAIL PROTECTED]> wrote:
> 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?
I saw this going the other way - constructing Bundle-ClassPath with
the information from the POM that you also include in the JAR.
If you are going this way, however, iterate ${project.artifacts},
looking for instances of ${artifactId}-${version}.jar being in the
file list.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
