[news.eclipse.platform.rcp] Re: Hibernate dependency in exported product

[Patrick Paulin <patrick@xxxxxxxxxxxxxxxxx>]

Hi Geoff,

Well the log file doesn't offer much help. And I'm not aware of 
anything that has changed in Eclipse 3.3 that would break your build. 
When you say that everything was working fine 8 months ago, was that 
with the same version of Hibernate as well?

Hibernate is tricky to package properly. I usually recommend that 
Hibernate be packaged as a collection of jars (including asm, cglib, 
etc.) in a single plug-in that is then deployed as a folder. You may 
want to try that as a test, just to see if it works.

And yes you're right, I meant exporting Hibernate as a deployable plug-in.

Regards,

--- Patrick
patrick@xxxxxxxxxxxxxxxxx


On 2007-06-29 11:46:03 -0500, "Geoff Draper" <thirstynellan@xxxxxxxxx> said:

> 1. Inside my Eclipse workspace, Hibernate is a folder (created using  =
>
> Eclipse's "create a plugin from existing JAR" wizard).  When I export th=
> e  =
>
> product, Hibernate gets exported as a JAR.  I also have another plugin  =
>
> that contains all the libraries Hibernate depends on.  It likewise is a =
>  =
>
> folder in my workspace, but a JAR in the export.
>
> 2. I'm not sure what you mean by exporting the Hibernate plug-in on its =
>  =
>
> own.  Doesn't a plugin have to be part of a product and application in  =
>
> order to be exported?  Or do you mean export it as a "deployable plug-in=
> "  =
>
> rather than an Eclipse product?  If you mean "deployable plug-in", then =
>  =
>
> yes, my two Hibernate plugins seem to export without any apparent errors=
> .
>
> 3. I've attached one of the log files from one of the Hibernate-dependen=
> t  =
>
> plugins, produced during the product export process.
>
> Incidentally, I'm currently using Eclipse 3.3RC4 on Linux/GTK, but I get=
>   =
>
> the exact same errors when I do the product export in Windows.  The expo=
> rt  =
>
> was working fine with an earlier version of our software 8 months ago,  =
>
> when we were using Eclipse 3.2.  I'm not sure whether it's due to  =
>
> something I've changed on my end, or if it's a 3.3-specific issue.  When=
>  I  =
>
> compare my MANIFEST.MF files from then and now, I don't see any changes =
> in  =
>
> how I've set up the "buddy" classloading for Hibernate.
>
> Thanks,
> Geoff
>
> On Fri, 29 Jun 2007 11:24:19 -0400, Patrick Paulin  =
>
> <patrick@xxxxxxxxxxxxxxxxx> wrote:
>
> > Hi Geoff,
> >
> > Are you packaging the Hibernate plug-in as a folder or jar? Are you ab=
> le  =
>
> > to export the Hibernate plug-in on it's own? Also, could you post the =
>  =
>
> > section of the log where the error occurs? It's hard to say what's goi=
> ng  =
>
> > on without more information.
> >
> > --- Patrick
> > patrick@xxxxxxxxxxxxxxxxx
> >
> >
> > On 2007-06-28 17:30:55 -0500, "Geoff Draper" <thirstynellan@xxxxxxxxx>=
>   =
>
> > said:
> >
> > > Hi Patrick,
> > > Thanks for your reply.  The answer is "yes" to both questions.  It's=
>  a
> > > plugin (not feature) based build, and all the relevant folders are
> > > included in the build.properties file.
> > > --Geoff
>
>
>
> This message has one or more attachments. Select "Save Attachments" 
> from the File menu to save.