| Build Automation Questions [message #307884] |
Tue, 05 September 2006 17:50  |
Eclipse User |
|
|
|
I've been using Eclipse for about a year, and have been using commands
presented by the plugin manifest editor, plus a few of my own ant
builds. This approach has now become prohibitively labor-intensive, and
I need to automate the build process under Cruise control or Maven, but
I suspect my roll-your-own ant scripts will complicate going to headless
builds.
At present, I have two kinds of projects:
'lib' Projects
-------------- produce useful packages in the form of libraries (jars),
not plugins, and
'plugin' Projects
----------------- produce RCP apps and workbench plugins that depend on
the jar files built from the lib projects.
I added ant build scripts to the lib projects, to create jar files from
their .class and .java files, and added build scripts to the Dependent
plugin projects, to grab copies of the jar files they need from the lib
projects. This seems clumsy, and I suspect that I have overlooked some
elegant Workbench facility for achieving the same result (automated
production and migration of supporting library jars into plugin projects)
1. Have I overlooked a built in facility in Eclipse to create and
migrate jars from lib projects to UI project builds, that would make it
unnecessary for me to add my own ant scripts for this purpose?
2. Should I be making (core) plugins of my lib jars, as the way to
automate dependency management?
Bill
|
|
|
|
| Re: Build Automation Questions [message #308034 is a reply to message #307915] |
Sun, 10 September 2006 13:07  |
| Eclipse User |
|
|
|
Paul Webster wrote:
> Bill Winspur wrote:
>
>>
>> 1. Have I overlooked a built in facility in Eclipse to create and
>> migrate jars from lib projects to UI project builds, that would make
>> it unnecessary for me to add my own ant scripts for this purpose?
>
>
> I don't believe this is available per se. Eclipse and PDE does support
> automated or headless builds, though.
>
>> 2. Should I be making (core) plugins of my lib jars, as the way to
>> automate dependency management?
>
>
> This is far and away the easiest approach. You can convert a normal
> java project into a plugin project. Really, it updates a few things in
> the .project file you don't care about, and adds OSGi headers to the
> manifest. When you export the jar, it would work as a normal java jar
> for other java applications and as a plugin for your RCP application.
>
> Later,
> PW
Paul, thanks for your reply of a few days ago. I 'm going to convert all
my lib projects to core plugin projects. In retro it is obviously the
way to go. I suppose my pre-eclipse orientation to lib jars being
'manually' assembled into a classpath had me in mindlock. Thanks again,
Bill.
|
|
|
Powered by
FUDForum. Page generated in 0.06204 seconds
Home