cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies" <>
Subject RE: Eclipse and the manifest jar
Date Tue, 31 Jul 2007 13:55:20 GMT

I've built plugins, and this isn't the issue. I'm not trying to make
Eclipse use this code, I'm wishing that, when Eclipse compiles my code,
it respected the manifest class-path and didn't force me to list out all
the constituent jars in my project's classpath.


> -----Original Message-----
> From: Oisin Hurley []
> Sent: Tuesday, July 31, 2007 9:52 AM
> To:
> Subject: Re: Eclipse and the manifest jar
> Hi Benson
> > I am disappointed to note that Eclipse doesn't seem to be able to
> > the manifest jar on the classpath. I send this message in case I'm
> > missing something stupid.
> Eclipse doesn't respond to anything on the classpath I'm afraid. It's
> do with the fact that Eclipse is an OSGi application, and that the
> provision
> and consumption of classes and APIs within an OSGi application is
> strictly regulated by a set of rules and special classloaders. There
> is no
> access to the system classloader.
> Providing classes to Eclipse involves the construction of an Eclipse
> plugin that contains the classes and the directives on accessibility
> of those classes, formalized in a separate MANIFEST.MF file.
> Such a plugin is available in the snapshot repository - e.g. if you
> check you will see zip files  (usually
> something like
> which represent the CXF all-in-one plugin. If you put this in the
> Eclipse plugins directory and restart Eclipse, then the CXF classes
> will be available.
>   best regards
>    Oisin
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4,

View raw message