Eclipse Community Forums: Standard Widget Toolkit (SWT)

Help

Home

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » bundles vs. .project file

Show: Today's Messages :: Show Polls :: Message Navigator

bundles vs. .project file [message #464731]

Tue, 29 November 2005 09:35

Eclipse User

Originally posted by: philipp.kutter.org

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

Report message to a moderator

Re: bundles vs. .project file [message #464735 is a reply to message #464731]

Tue, 29 November 2005 10:13

Stefan Langer

Messages: 236
Registered: July 2009

Senior Member

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
>
>
>

Report message to a moderator

Re: bundles vs. .project file [message #464823 is a reply to message #464731]

Wed, 30 November 2005 14:31

Veronika Irvine

Messages: 1272
Registered: July 2009

Senior Member

You will probably get a better response to this Eclipse Workbench question
on the eclipse platform newsgroup.

news://news.eclipse.org/eclipse.platform

"Philipp Kutter" <philipp@kutter.org> wrote in message
news:c05796decf728691385f1e15f59a4226$1@www.eclipse.org...
> 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
>
>
>

Report message to a moderator

Re: bundles vs. .project file [message #464842 is a reply to message #464731]

Wed, 30 November 2005 16:11

Alex Blewitt

Messages: 946
Registered: July 2009

Senior Member

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.

Alex.

Report message to a moderator

Previous Topic:	OleAutomation parameters problem
Next Topic:	ProgressBar.getSelection()

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 26 15:25:32 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter