The simple answer to your inquiry is that the PDE Classpath Container only knows about bundles and not about maven artifacts.
To solve your problem, we would have to open up the PDE Classpath Container to other parties interested in providing the information we need to build a classpath.
On Wed, Aug 6, 2008 at 4:55 PM, Abel Muiño Vizcaino
<amuino@xxxxxxxxx> wrote:
I'm cross-posing this request from the eclipse.technology.iam newgroup
for input from the PDE team.
The original request has a custom classpath container (the
MavenClasspathContainer) defined in his project, but PDE does not seem
to find the referenced libraries (in the original layout, they were
managed as Referenced Libraries).
We would be interested in knowing the reason and what can be done from
the IAM side to let PDE know about the contents of its classpath container.
Thanks!
Abel Muiño.
Chris Audley wrote:
I'm trying to find a way to use Q4E to support my plug-in development.
I have a project based on a number of plug-ins that require externally developed JAR files, either from other groups in the same company or third party libraries. My current practice is to include a copy of the JAR in my plug-in projects as 'Referenced Libraries' (classpath container) during development, with a custom post.gather.bin.parts ant callback task that expands the contents of the jars into my plugin before it is JAR'ed.
We use maven to manage our dependencies for pretty much every other project we have here, so I'd like to find a good way to update our plug-in development.
My first thought was to use Q4E to create a 'Maven Dependencies' container in my plug-in project classpath, and use Maven Tasks for Ant with the pom.xml to find and expand the dependency jars during export.
My first problem is that the PDE manifest compiler won't work with the MavenClasspathContainer. When I have the plugin project configured with Q4E and a pom.xml, the 'Maven Dependencies' container shows up with the required jars, but the manifest compiler complains that packages in these JAR files don't exist when I try to export them with Export-Package. In my previous configuration, these same jars appeared in the 'Referenced Library' container and the manifest compiler could find them just fine. What is the difference with the Maven Dependencies container?
My other question is about copying the jars into the plugin during export. The Q4E website mentions having maven copy runtime dependencies to the WEB-INF/lib directory in WTP. How does that work and can I apply it here?
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
--
Cheers,
~ Chris Aniszczyk
