Eclipse Community Forums: Eclipse Platform » What makes a package be a package (and not a folder)?

Help

Home

Home » Eclipse Projects » Eclipse Platform » What makes a package be a package (and not a folder)?

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

What makes a package be a package (and not a folder)? [message #332750]

Fri, 07 November 2008 15:08

Jan Kohnert

Messages: 196
Registered: July 2009

Senior Member

Hello,

What makes a package be a package? When checking the sources of a projekt
in filesystem each package (that I see in the package explorer) is basicly
a folder in the filesystem. Currently I have the problem, that I've a
imported project where the source folders children are are handled as
folders and not as packages as they should. As a result the plugin is not
working :(

Any Ideas?

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332754 is a reply to message #332750]

Fri, 07 November 2008 15:34

Ed Merks

Messages: 33264
Registered: July 2009

Senior Member

Jan,

If you look at the Properties... of a project, and look at the Java
Build Path's Source tab, you'll see that here you can specify which
folders acts as roots for packages.

Jan Kohnert wrote:
> Hello,
>
> What makes a package be a package? When checking the sources of a
> projekt in filesystem each package (that I see in the package
> explorer) is basicly a folder in the filesystem. Currently I have the
> problem, that I've a imported project where the source folders
> children are are handled as folders and not as packages as they
> should. As a result the plugin is not working :(
>
> Any Ideas?
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332758 is a reply to message #332754]

Fri, 07 November 2008 15:48

Jan Kohnert

Messages: 196
Registered: July 2009

Senior Member

Something must be really wrong with my plugin :(
I don'nt eaven have a buildpath option in the Properties. If I right click
the plugin in package explorer the entry 'Build Path' says 'No actions
available'

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332760 is a reply to message #332758]

Fri, 07 November 2008 15:51

Ed Merks

Messages: 33264
Registered: July 2009

Senior Member

Jan,

It is even a Java project? I.e., is the little "J" in the upper right
corner? I'm not sure there's a way to convert a project to a Java
project once it exists. Best to create the right type of project and
then copy the rest into that...

Jan Kohnert wrote:
> Something must be really wrong with my plugin :(
> I don'nt eaven have a buildpath option in the Properties. If I right
> click the plugin in package explorer the entry 'Build Path' says 'No
> actions available'
>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332764 is a reply to message #332760]

Fri, 07 November 2008 16:03

Jan Kohnert

Messages: 196
Registered: July 2009

Senior Member

Ed,

No there is no 'J' :(
I've created this project as java project on one machine. I shared it
using SVN and exportet it to another machine. Somehow I mus have missed
something important. It seems something defines a java project. And it
seems that I must have forgotten to share that 'thing'.

Thank you for your help Ed. It is allways impressive how fast you keep
answering questions and how anxious your are!

Jan Kohnert

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332768 is a reply to message #332764]

Fri, 07 November 2008 16:32

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

You might be able to just edit the .project file (use the navigator view
to see it) and add the Java nature:
<natures>
<nature>org.eclipse.pde.PluginNature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>

Just create a new Java project to see what the default java contents are.

-Andrew

Jan Kohnert wrote:
> Ed,
>
> No there is no 'J' :(
> I've created this project as java project on one machine. I shared it
> using SVN and exportet it to another machine. Somehow I mus have missed
> something important. It seems something defines a java project. And it
> seems that I must have forgotten to share that 'thing'.
>
> Thank you for your help Ed. It is allways impressive how fast you keep
> answering questions and how anxious your are!
>
> Jan Kohnert
>

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332772 is a reply to message #332764]

Fri, 07 November 2008 17:53

Chetan Kumar

Messages: 70
Registered: July 2009

Member

Jan,

I faced a similar problem. I copied project from one system to another
using a shared folder. When i finished importing project onto the new
workspace, there was no package structure rather just a folder structure
was displayed in the package explorer.

To fix this i used the PDE Tools -> update classpath option by right
clicking on the project in package explorer. This solved it for me.

- Chetan Kumar

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332774 is a reply to message #332764]

Fri, 07 November 2008 18:39

Ed Merks

Messages: 33264
Registered: July 2009

Senior Member

Jan,

Note the other comments about the .project file... It's important that
the .classpath and .project files are also checked into SVN. You can
unfilter .* resource so you'll see them in the navigator/explorer...

Jan Kohnert wrote:
> Ed,
>
> No there is no 'J' :(
> I've created this project as java project on one machine. I shared it
> using SVN and exportet it to another machine. Somehow I mus have
> missed something important. It seems something defines a java project.
> And it seems that I must have forgotten to share that 'thing'.
>
> Thank you for your help Ed. It is allways impressive how fast you keep
> answering questions and how anxious your are!
>
> Jan Kohnert
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: What makes a package be a package (and not a folder)? [message #332784 is a reply to message #332774]

Fri, 07 November 2008 22:36

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

And in addition is important that the .settings folder is also checked
into SVN. That's the only way that the project is sure to look and act
the same on everyone's system.

Ed Merks wrote:
> Jan,
>
> Note the other comments about the .project file... It's important that
> the .classpath and .project files are also checked into SVN. You can
> unfilter .* resource so you'll see them in the navigator/explorer...
>

--
Thanks,
Rich Kulp

Report message to a moderator

Previous Topic:	project.create() and nature configuration
Next Topic:	Generalizing CellEditor

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jan 18 19:45:27 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter