Eclipse Community Forums: Eclipse Platform » importing existing (non eclipse) project?

Home » Eclipse Projects » Eclipse Platform » importing existing (non eclipse) project?

importing existing (non eclipse) project? [message #199713]

Mon, 23 February 2004 06:20

Eclipse User

Originally posted by: m.brinkers.pobox.com

I have problems importing existing (non eclipse) projects into eclipse.
For example when I import jboss project ie. the complete source, the
compiler always complains about invalid packages. The reason is that
the jboss directory structure does not have a single src directory. It
has lots of sub-dirs with lots of src directories.

One approach would be to import each src directory one after the other
but this is a lot of work and its easy to miss a source directory.

Is it possible for the import action to infer the correct packages and
create the correct source folders?

Am I doing something wrong or is the import of non-eclipse projects not
an easy thing to do?

Thanks

Martijn Brinkers

Re: importing existing (non eclipse) project? [message #199765 is a reply to message #199713]

Mon, 23 February 2004 09:13

Eclipse User

This is currently a work (feature) in progress for Ant/JDT. If you have an
associated Ant buildfile, we will likely be able to do the right thing -
i.e. create the proper source directories/buildpath for you.

Keep track of the following bug report for progress:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=51381

Darin

"Martijn Brinkers" <m.brinkers@pobox.com> wrote in message
news:c1cnlm$j18$1@eclipse.org...
> I have problems importing existing (non eclipse) projects into eclipse.
> For example when I import jboss project ie. the complete source, the
> compiler always complains about invalid packages. The reason is that
> the jboss directory structure does not have a single src directory. It
> has lots of sub-dirs with lots of src directories.
>
> One approach would be to import each src directory one after the other
> but this is a lot of work and its easy to miss a source directory.
>
> Is it possible for the import action to infer the correct packages and
> create the correct source folders?
>
> Am I doing something wrong or is the import of non-eclipse projects not
> an easy thing to do?
>
> Thanks
>
> Martijn Brinkers

Re: importing existing (non eclipse) project? [message #199825 is a reply to message #199765]

Mon, 23 February 2004 10:02

Eclipse User

Originally posted by: m.brinkers.pobox.com

That would be most helpful. I will take a look at the plugin

But what to do if you do not have an ant buildfile?

In principle it would be possible for the importer to determine the
correct source paths just by looking at the packages. This requires
that the importer parses the java files which could take some time but
in principle its possible.

Thanks

Martijn Brinkers

Darin Wright wrote:

> This is currently a work (feature) in progress for Ant/JDT. If you
> have an associated Ant buildfile, we will likely be able to do the
> right thing - i.e. create the proper source directories/buildpath for
> you.
>
> Keep track of the following bug report for progress:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51381
>

Re: importing existing (non eclipse) project? [message #199911 is a reply to message #199713]

Mon, 23 February 2004 11:33

Eclipse User

Originally posted by: eclipse-user.jibeinc.com

Martijn Brinkers wrote:

> I have problems importing existing (non eclipse) projects into eclipse.
> For example when I import jboss project ie. the complete source, the
> compiler always complains about invalid packages. The reason is that
> the jboss directory structure does not have a single src directory. It
> has lots of sub-dirs with lots of src directories.
>
> One approach would be to import each src directory one after the other
> but this is a lot of work and its easy to miss a source directory.
>
> Is it possible for the import action to infer the correct packages and
> create the correct source folders?
>
> Am I doing something wrong or is the import of non-eclipse projects not
> an easy thing to do?

I would try simply copying the directory tree into your Eclipse
workspace under a project name. Then in Eclipse create a new Project
using that name (by default, the workspace subdirectory is the same as
the Project name). Eclipse will recognize there are already files in
that directory and you can then specify your source dirs easily since
they are already in the Project.

HTH,
Eric
--
Eric Rizzo
Software Architect
Jibe, Inc.
http://www.jibeinc.com

Re: importing existing (non eclipse) project? [message #199942 is a reply to message #199911]

Mon, 23 February 2004 11:43

Eclipse User

Originally posted by: m.brinkers.pobox.com

The 'problem' is that there are multiple source dirs ( >> 20 ) which
takes a lot of time to specify even when you know exactly what the
source directories are.

Eric Rizzo wrote:
> I would try simply copying the directory tree into your Eclipse
> workspace under a project name. Then in Eclipse create a new Project
> using that name (by default, the workspace subdirectory is the same
> as the Project name). Eclipse will recognize there are already files
> in that directory and you can then specify your source dirs easily
> since they are already in the Project.
>
> HTH,
> Eric

Re: importing existing (non eclipse) project? [message #200295 is a reply to message #199942]

Mon, 23 February 2004 18:05

Eclipse User

Originally posted by: eclipse-user.jibeinc.com

Martijn Brinkers wrote:

> The 'problem' is that there are multiple source dirs ( >> 20 ) which
> takes a lot of time to specify even when you know exactly what the
> source directories are.

Then I'm not sure what you'd expect Eclipse to do. I don't think it is
reasonable to expect it to examine an entire directory tree and somehow
figure out which directories would be source ones, especially since I
don't think it is required that source file directories follow the
package structure like class files do. IOW, I think it is possible to
put all source files in one directory - not a _good_ idea, but still legal.
In any case, a project that has that many different source directories
has some organizational problems, IMHO. Perhaps it should be multiple
Projects instead of one big one. Or perhaps not all of the source needs
to be compiled all the time (some of it may be tools, optional, tests, etc.)

HTH,
Eric
--
Eric Rizzo
Software Architect
Jibe, Inc.
http://www.jibeinc.com

Previous Topic:	how to make a extension to assign the xml editor to a concrete file
Next Topic:	-> Import Platformsource [3.0M7]

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Apr 27 01:23:33 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter