> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 12, 2005 11:09 AM
> To: Maven Users List
> Subject: Re: [m2] Dependencies as resources
>
> I saw this going the other way - constructing
> Bundle-ClassPath with the information from the POM that you
> also include in the JAR.
>
Absolutely. That is, when my osgi plugin actually has the code to
create manifest entries from POM configuration tags. :) It's time I got
busy adding this functionality.
Currently, it only merges an existing manifest file with the maven
generated one -- thus the reason for the parsing of the manifest entry.
> If you are going this way, however, iterate
> ${project.artifacts}, looking for instances of
> ${artifactId}-${version}.jar being in the file list.
>
Thanks. Will post more if I have questions along the way.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
