Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » Using Q4E with PDE
Using Q4E with PDE [message #12589] Wed, 06 August 2008 16:56 Go to next message
Eclipse UserFriend
Originally posted by: chris.audley.beaconcs.com

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?
Re: Using Q4E with PDE [message #12612 is a reply to message #12589] Wed, 06 August 2008 20:11 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Chris

Chris Audley wrote:
> I'm trying to find a way to use Q4E to support my plug-in development.
PDE integration, although planned is not yet implemented. Anything we
can learn from your experience will be very useful.
> 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?
It is a "regular" classpath container. I'll be forwarding your question
to the PDE group and see if we can find out what's not working between
iam/q4e and pde.

> 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?

That's specific to web development, so you'll need to configure maven to
do so. I'll start by looking at the dependency:copy goal (maybe binding
it to the prepare-package phase).

Thanks!
--
Abel Muiño Vizcaino
Re: Using Q4E with PDE [message #566908 is a reply to message #12589] Wed, 06 August 2008 20:11 Go to previous message
Abel Mui is currently offline Abel MuiFriend
Messages: 247
Registered: July 2009
Senior Member
Hello Chris

Chris Audley wrote:
> I'm trying to find a way to use Q4E to support my plug-in development.
PDE integration, although planned is not yet implemented. Anything we
can learn from your experience will be very useful.
> 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?
It is a "regular" classpath container. I'll be forwarding your question
to the PDE group and see if we can find out what's not working between
iam/q4e and pde.

> 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?

That's specific to web development, so you'll need to configure maven to
do so. I'll start by looking at the dependency:copy goal (maybe binding
it to the prepare-package phase).

Thanks!
--
Abel Muiño Vizcaino
Previous Topic:Using Q4E with PDE
Next Topic:Eclipse IAM project plan
Goto Forum:
  


Current Time: Fri Nov 28 11:38:22 GMT 2014

Powered by FUDForum. Page generated in 0.03212 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software