You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Benson Margulies <bi...@basistech.com> on 2007/07/30 02:58:44 UTC
Eclipse and the manifest jar
I am disappointed to note that Eclipse doesn't seem to be able to use
the manifest jar on the classpath. I send this message in case I'm
missing something stupid.
Re: Eclipse and the manifest jar
Posted by Daniel Kulp <dk...@apache.org>.
On Sunday 29 July 2007 20:58, Benson Margulies wrote:
> I am disappointed to note that Eclipse doesn't seem to be able to use
> the manifest jar on the classpath. I send this message in case I'm
> missing something stupid.
No. It's not you. Eclipse is stupid.
This bites us when we try to "import" the ant based demos into eclipse as
well. Eclipse finds the manifest jar and puts that in the list of
jars, but that doesn't work.
Ideally, eclipse would either use the manifest for compile/run, or at
import time, look at the manifest and grab all the jars it points to as
well.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
Re: Eclipse and the manifest jar
Posted by Oisin Hurley <oh...@iona.com>.
> 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.
My apologies - I took your email up completely incorrectly!
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
RE: Eclipse and the manifest jar
Posted by Benson Margulies <bi...@basistech.com>.
Oisin,
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.
--benson
> -----Original Message-----
> From: Oisin Hurley [mailto:ohurley@iona.com]
> Sent: Tuesday, July 31, 2007 9:52 AM
> To: cxf-dev@incubator.apache.org
> Subject: Re: Eclipse and the manifest jar
>
> Hi Benson
>
> > I am disappointed to note that Eclipse doesn't seem to be able to
use
> > 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
to
> 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 http://tinyurl.com/26nrsg you will see zip files (usually
called
> something like
>
> cxf-eclipse-plugin-2.1-incubator-20070729.204751-4.zip
>
> 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,
Ireland
Re: Eclipse and the manifest jar
Posted by Oisin Hurley <oh...@iona.com>.
Hi Benson
> I am disappointed to note that Eclipse doesn't seem to be able to use
> 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 to
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 http://tinyurl.com/26nrsg you will see zip files (usually called
something like
cxf-eclipse-plugin-2.1-incubator-20070729.204751-4.zip
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, Ireland