[iam-dev] Re: [q4e-dev] Re: PDE Build based build system

["Joakim Erdfelt" <joakim.erdfelt@xxxxxxxxx>]

Just so others can see the work.

https://q4e.googlecode.com/svn/branches/maven-embedder-2.1.x-no-lib/

I have a test case in there to validate the setup, but I'm having issues with the plexus resolution of the "/META-INF/plexus/components.xml" resources.

https://q4e.googlecode.com/svn/branches/maven-embedder-2.1.x-no-lib/org.apache.maven.embedder.test/

If we do consider merging all of the embedder classes into a single uncompressed plugin, then we'll need to also merge all of those "/META-INF/plexus/components.xml" files together.

I was also pondering if we should just consolidate some of the codebases together into logical units.

Such as

1) org.apache.maven.embedded (new plugin which is a combination of the following packages)
   org.apache.maven.artifact
   org.apache.maven.core
   org.apache.maven.doxia.sink.api
   org.apache.maven.embedder
   org.apache.maven.lifecycle
   org.apache.maven.model
   org.apache.maven.plugin.api
   org.apache.maven.profile
   org.apache.maven.project
   org.apache.maven.reporting.api
   org.apache.maven.toolchain
   org.apache.maven.workspace
2) org.apache.maven.wagon
   org.apache.maven.wagon.http.shared
   org.apache.maven.wagon.provider.api
   org.apache.maven.wagon.providers.file
   org.apache.maven.wagon.providers.http.lightweight
   org.apache.maven.wagon.providers.ssh.common
   org.apache.maven.wagon.providers.ssh.external
   org.apache.maven.wagon.providers.ssh.jsch
3) org.codehaus.plexus.embedded
   org.codehaus.plexus.classworlds
   org.codehaus.plexus.container.default
   org.codehaus.plexus.interactivity.api
   org.codehaus.plexus.interpolation
   org.codehaus.plexus.utils

Would this approach have any merit?

- Joakim Erdfelt

On Thu, Dec 18, 2008 at 3:25 AM, Abel Muiño <amuino@xxxxxxxxx> wrote:

On Thu, Dec 18, 2008 at 12:49 AM, Abel Muiño Vizcaino <amuino@xxxxxxxxx> wrote:

2.- Proper packaging of the embedder. In my tests, the current packaging does not work well with PDE. But everything seem to be resolved by installing the embedder bundle as an uncompressed folder (instead of a jar file). See note on http://tinyurl.com/3zjknc

I've found more information on this (by chance).
Bug 252800 (https://bugs.eclipse.org/252800) seems to imply that uncompressed bundles are not welcome. Instead, the jars should be uncompressed (and the result compressed in a bundle, just like now).

The same bug explains why having several jars nested in a bundle works fine at run time but causes build errors (equinox can reach the nested jars, but the compiler can not).

This affects our packaging of the embedder.

Joakim has been experimenting with a branch for 1 bundle per embedder jar (some classpath issues were present, I don't know if this has improved lately). The other (probably simpler) option would be to uncompress the jars but still package everything in a single bundle.

--
Abel Muiño - http://ramblingabout.wordpress.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Q for Eclipse developers list" group.
To post to this group, send email to q4e-dev@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to q4e-dev+unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at http://groups.google.com/group/q4e-dev?hl=en
-~----------~----~----~----~------~----~------~--~---