| How to declare dependencies between plug-in and plain old java projects [message #257401] |
Mon, 17 November 2008 06:12 |
Eclipse User |
|
|
|
Hello,
I am (almost) sure, there is a better way to do this in Eclipse, but I
have not figured it out as of yet.
We have an application that consists of client and server components
which each are composed of bunch of modules. On the server side we use
the traditional jar packaging and some of the projects build several
JAR's for multiple target deployments (e.g. one for server side and one
for client side deployment).
On te client side we use Eclipse RCP project and some of the plug-ins
include the jars built from the server side (as well as bunch of jar's
from the 3rd party libraries).
Up to this day I've used the following workflow when synchronizing with
service projects:
1. Update service projects.
2. Perform full build of the service projects
3. Copy produced client jars to their respective plug-ins
4. Develop our RCP app.
To make my life at least a little bit easier, I've encapsulated steps 2
and 4 into their own launcher configurations, but still my feeling is
that this workflow is suboptimal and is not really IDE friendly.
There are few problems that I see with this approach:
1. Full rebuild of the entire server side libraries is robust, but
takes too much time and should not be necessary. (the optimization
of that build system is another topic altogether, but I essentially
know what needs to be done there, to make it more IDE friendly)
2. Steps 2 and 3 trigger full workspace refresh, which can take
considerable amount of time in each case (not to speak of server
side build that takes minutes to complete).
3. It takes separate 2 manual steps performed just in this specific
order, to get the workspace into a consistent state.
4. Limited usefulness of the refactoring support due to the fact that
service libraries are linked to the plug-in projects via copying of
the prebuilt jar libraries.
Now what I'm asking is if there is a better way to do this:
- Have eclipse RCP link to the actual sources of the services modules
in self-hosted development/debugging environment
- Have still the actual jar files to be copied to the plug-ins in
export/build time for easy deployment.
- (automagically?) ensure that the changes in the self-hosted
environment will be mirrored in the build time.
--
Roland Tepp
|
|
|
Powered by
FUDForum. Page generated in 0.03242 seconds
Home