Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Java WorkFlow Tooling (JWT) » how can I handle project jars, that get loaded by my app dynamically
how can I handle project jars, that get loaded by my app dynamically [message #544531] Sat, 03 July 2010 12:14 Go to next message
geronimo013 is currently offline geronimo013
Messages: 4
Registered: July 2010
Junior Member
Hello,

I'm using eclipse quite a while, but I did not found out (yet), how I can create a workflow for an eclipse project, that is a java library used by another eclipse project (the app).

No problem at all, if the app gets bound against that library.

But the app does not know nothing about that library but starts to load it at runtime from a defined directory.

How can I build an eclipse-project, that automatically updates a jarfile, so that runtime-loading will lead to the same result than sharing a project?
Lately I read about project facelets - would that be a way to go ahead?

Any hint is appreciated.

kind regards

Geronimo
Re: how can I handle project jars, that get loaded by my app dynamically [message #544773 is a reply to message #544531] Mon, 05 July 2010 13:34 Go to previous messageGo to next message
Marc Dutoo is currently offline Marc Dutoo
Messages: 71
Registered: July 2009
Member
Hi Geronimo

It seems to be a devtime/runtime classpath problem and not to have much
to do with JWT.

In your place, I'd use a build & packaging tool such as ant or maven to
assemble and produce my application runtime.

There are a lot of other solutions : e.g. if your runtime application is
a web application (.war) to be run in tomcat, you can use an Eclipse Web
Project. If it is an OSGi application, you've got specific build tools
as well.

Please look up further information in those places, ex. google up
"eclipse ant build".

Regards,
Marc

geronimo013@gmx.de a écrit :
> Hello,
>
> I'm using eclipse quite a while, but I did not found out (yet), how I
> can create a workflow for an eclipse project, that is a java library
> used by another eclipse project (the app).
>
> No problem at all, if the app gets bound against that library.
>
> But the app does not know nothing about that library but starts to load
> it at runtime from a defined directory.
>
> How can I build an eclipse-project, that automatically updates a
> jarfile, so that runtime-loading will lead to the same result than
> sharing a project?
> Lately I read about project facelets - would that be a way to go ahead?
>
> Any hint is appreciated.
>
> kind regards
>
> Geronimo
Re: how can I handle project jars, that get loaded by my app dynamically [message #544789 is a reply to message #544773] Mon, 05 July 2010 14:15 Go to previous messageGo to next message
geronimo013 is currently offline geronimo013
Messages: 4
Registered: July 2010
Junior Member
Hi Marc,

thank you for your attention!

Quote:
It seems to be a devtime/runtime classpath problem and not to have much
to do with JWT.
In your place, I'd use a build & packaging tool such as ant ...

Looks like I was not able to express what I mean Sad

I already use a multi-project-build with ant, which works fine - same does my app.

I just wanted to know, whether there's a way to extend the incremental build capabilities of eclipse to handle a target jarfile too.
I know, that a jarfile can be exported from eclipse, but that's not an acceptable choice instead of a projects target.
I've no idea about what would be possible by extending eclipse - as til now I used eclipse just as an editor Wink

When I discovered project facelets, I thought: hey, may be some other guy had the same thoughts like me and he build an addon, so the projects target could be user defineable now ... Smile

kind regards

Geronimo
Re: how can I handle project jars, that get loaded by my app dynamically [message #544810 is a reply to message #544789] Mon, 05 July 2010 14:54 Go to previous messageGo to next message
Marc Dutoo is currently offline Marc Dutoo
Messages: 71
Registered: July 2009
Member
Hi Geronimo

geronimo013@gmx.de a écrit :
> Hi Marc,
>
> thank you for your attention!
>
> Quote:
>> It seems to be a devtime/runtime classpath problem and not to have much
>> to do with JWT.
>> In your place, I'd use a build & packaging tool such as ant ...
>
> Looks like I was not able to express what I mean :(

Looks like I'm not the right person and this is not the right place ;)

>
> I already use a multi-project-build with ant, which works fine - same
> does my app.
>
> I just wanted to know, whether there's a way to extend the incremental
> build capabilities of eclipse to handle a target jarfile too.
> I know, that a jarfile can be exported from eclipse, but that's not an
> acceptable choice instead of a projects target.
> I've no idea about what would be possible by extending eclipse - as til
> now I used eclipse just as an editor ;)
>
> When I discovered project facelets, I thought: hey, may be some other
> guy had the same thoughts like me and he build an addon, so the projects
> target could be user defineable now ... :)

Eclipse's incremental build capabilities are only there to serve its own
"build while coding" features. They've been extended ex. by maven
integration projects, but at some point that means that when you save
your java file it starts an mvn command, which is certainly not as light
as the default behaviour. That's all about compromise : either you want
something quick enough not to disturb you while you code, or powerful
enough to build any kind of runtime application.

>
> kind regards
>
> Geronimo
Re: how can I handle project jars, that get loaded by my app dynamically [message #544817 is a reply to message #544810] Mon, 05 July 2010 15:23 Go to previous message
geronimo013 is currently offline geronimo013
Messages: 4
Registered: July 2010
Junior Member
Hi Marc,

Quote:
and this is not the right place

any hint about a propper place?

Quote:
Eclipse's incremental build capabilities are only there to serve its own
"build while coding" features. They've been extended ex. by maven
integration projects,...

so the first sounds reasonable, but maven ... ? - not at all!
I never wonna get in touch with that stuff ...

Quote:
That's all about compromise : either you want
something quick enough not to disturb you while you code ...

Quite sure and for 99% of the projects I was envolved that decision was right.
Just wondered whether I would be possible to trigger the jar-export automatically for certain project(s). I don't want to enable the jar-creation for any project!

kind regards

Geronimo
Previous Topic:Java Code Formatter as extension point - contribution
Next Topic:JWT Nodes palette
Goto Forum:
  


Current Time: Wed Sep 03 04:41:46 GMT 2014

Powered by FUDForum. Page generated in 0.03317 seconds