This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 142480 - [65cat] Prompt for unresolved projects when using Eclipse importer
Summary: [65cat] Prompt for unresolved projects when using Eclipse importer
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Eclipse project importer (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@projects
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 21:45 UTC by dynamite
Modified: 2016-07-07 08:39 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dynamite 2008-07-31 21:45:43 UTC
[ JDK VERSION : 1.6.0_07 ]

We have individual Eclipse projects checked in, but not workspaces. 
The importer indicates missing project references, but provides no
immediate option to find them.  This is a shame as they Eclipse
projects are located alongside, whereas starting another import takes
me back a long way to my root directory - tedious.  Ideally I just
want to import my root project and then be prompted to search for
dependent projects as the importer finds them.
Comment 1 David Konecny 2008-08-04 05:44:33 UTC
Re. "We have individual Eclipse projects checked in, but not workspaces." - how do you do your daily development in
Eclipse? You have to have a workspace into which you import projects, no?

This is how I thought the workflow would work: a team is using Eclipse for couple of projects; they decide to evaluate
NetBeans; all projects from an Eclipse workspace are imported (this sets up besides other things variables, user defined
libraries, global encoding, run configurations, etc.); NetBeans projects were generated into Eclipse project folders; NB
projects are tested/tweaked and committed to VCS. When a new team member is brought on board and he/she prefers NB he is
not required to have Eclipse installed nor Eclipse workspace is needed and he is using directly NB projects. Any
classpath synchronization is preferably done again by somebody who has both Eclipse and NB - first because they can
check that everything is setup the same way; second as in import case synchronization may need to setup whole bunch of
things and may result into import of newly required projects.

We can implement what you are asking for but I think it will always be inferior to workspace based import.

I would like to learn more about how do you use Eclipse and how would you want to use NB projects. Thanks.

Btw. issue 142482 you filed - there is silly NPE which after fixed will tell you that MyEclipse libraries cannot be
automatically imported without workspace (there is one more issue to be fixed first though: issue 141504).
Comment 2 dynamite 2008-08-04 19:05:42 UTC
I am a lone NetBeans user amongst a number of MyEclipse users.  As such I develop solely with NetBeans.  I suspect that
if I requested MyEclipse that they would probably expect me to use just that.  In any case, the upshot is that I have no
workspace to import - only the checked-in MyEclipse projects.

Now the source code + non-MyEclipse libraries are sufficient for building and running as part of an overnight build, so
my suspicion is that everything will work without the MyEclipse (fingers firmly crossed).
Comment 3 Martin Balin 2016-07-07 08:39:02 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss