Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] bundle builds using Maven

I took a quick look and have some questions

There are a couple of compilers, using the Sun and the Eclipse
compiler, right? would that fit as part of the usual eclipse compiler
integration https://svn.codehaus.org/plexus/plexus-components/trunk/plexus-compiler/plexus-compilers/plexus-compiler-eclipse

How is the targetplatform stuff different from the eclipse:make-artifacts?

How are the several osgi plugins different from the felix bundle plugin?

I'm trying to get all the different options out there together in
something widely used instead of scattered.

On 5/20/07, Tom Huybrechts <tom.huybrechts@xxxxxxxxx> wrote:
It's not just the manifest. Generally PDE expects all non-classpath
entries (anything you'd access via Bundle.getEntry and not via
getResource) to be relative to the root of your project. This is
because when running in the IDE, Eclipse tries to use the project
itself as a bundle (with some hacks to allow classes to be loaded from
the right places).

The build.properties file contains the configuration for what gets
included into the bundle jar. I've written an alternative to the
maven-jar-plugin that uses this information to build bundles in Maven.

Another issue is when you have embedded jars in your bundles. You
can't use these as ordinary dependencies with the normal
maven-compiler-plugin. I also wrote a maven-osgi-compiler-plugin that
calculates classpaths based on the manifests using the equinox
resolver.

Both are available here http://svn.codehaus.org/m2eclipse/tycho/trunk/
although it could use some documentation...


On 5/18/07, Carlos Sanchez <carlos@xxxxxxxxxx> wrote:
> right, but you can say maven to generate the manifest where PDE
> expects it ${basedir}/META-INF/MANIFEST.MF
>
> On 5/18/07, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
> > On 17/05/07, Carlos Sanchez <carlos@xxxxxxxxxx> wrote:
> > > you can easily set the destination folder of the manifest generated in
> > > maven as a configuration option "manifestLocation" in the felix bundle
> > > plugin, or PDE could support some configuration property in the
> > > future.
> >
> > The problem is not that Maven is configurable, it is that PDE is not.
> > And it's not just the manifest; it's any resource issue generally.
> >
> > Alex
> > _______________________________________________
> > equinox-dev mailing list
> > equinox-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
>                              -- The Princess Bride
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev



--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                            -- The Princess Bride


Back to the top