[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.platform.swt] Re: bundles vs. .project file

Are you planning on dstributing your project in an OSGI Enviroment? Is the visibility of packages the only reason why you are considering bundles?
If not I would not use the manifest approach since you are not using any of the features that it is intended for.


If you are distributing in an OSGI Enviroment I would recommend going the bundle way.

Regards
Stefan

Philipp Kutter wrote:
Dear all. I asked the following in the newcommers newsgroup, but got never an answer.
We are still very interested in the topic.


Dear all.
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 advantage.

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