|bundles vs. .project file [message #464731]
||Tue, 29 November 2005 04:35
Originally posted by: philipp.kutter.org|
I asked the following in the newcommers newsgroup, but got never an answer.
We are still very interested in the topic.
We work on a large Java project, and we have used the normal project file
for dependencies between Java projects.
Some people in the project propose that we switch completly
to bundles, using manifest.mf files to define the dependencies
and the jar files which we use.
Since we are not using runtime workbenches and since
we do not create plugins, not all people do see the
Especially they noted that the use of visility rules in
the .project file give exactly the same advantage as package import and
export in bundles.
Can you please advice us whether to move to bundles or not?
Best Regards, Philipp
|Re: bundles vs. .project file [message #464842 is a reply to message #464731]
||Wed, 30 November 2005 11:11
| Alex Blewitt
Registered: July 2009
Bundles (and the OSGI manifest) are necessary when you're running in an OSGI environment, such as you get with Eclipse plugins. However, if you're just using Eclipse as a Java IDE, then it's really unlikely that it will bring you any benefit at all.|
In order for Manifest.MF files to be useful (as OSGI bundles), you'll have to have them hosted in another OSGI-aware system. It's highly unlikely you've got that.
Lastly, Eclipse uses the .project to track dependencies between projects (and the corresponding entries in .classpath), so if you want Eclipse to have inter-project dependencies for compilation, you *have* to use the .project/.classpath dependencies.
Powered by FUDForum
. Page generated in 0.01679 seconds