Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » When to use import
When to use import [message #44048] Thu, 29 May 2003 22:44 Go to next message
Eclipse UserFriend
Assume somebody copies a project tree from a server: can they open that
project up or do they have to import it? This is related to my previous
question where the open project item is disabled after installing Eclipse.
Why would Open Project be grayed out?
Re: When to use import [message #44353 is a reply to message #44048] Fri, 30 May 2003 08:46 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: daniel.megert.gmx.net

Rod Macpherson wrote:

>Assume somebody copies a project tree from a server: can they open that
>project up or do they have to import it?
>
Import or more accurate: in the new Java project wizard select your
existing location as project contents.

Dani
Re: When to use import [message #45278 is a reply to message #44353] Fri, 30 May 2003 16:19 Go to previous messageGo to next message
Eclipse UserFriend
Lots of responses to this and my previous post but no answers. Everybody
seems to be in agreement here so it is not a personal observation that this
simple process is very badly defined.

To review we understand the notion of project and workspace and we have a
working project on my machine. That project and all of its contents are
checked into CVS. We cannot open the project in the workspace of a new
Eclipse installation because it's not available in their workspace. This is
logical so the next question is how do we import an existing project so we
can open it? Import does not work because you end up with all manner of
source directories and jar files that were never part of the project yet
that structure and those files are specified explicitly as the Project
Properties. That behavior is neither intuitive nor reasonabe.

Let's put aside the broken Import function and the inability to just open a
project that would simultaneously be incorporated in to your workspace -- as
you migh reasonably expect. You are saying that to open an EXISTING project
in your workspace you run the New Java Project Wizard. Yikes, can't convince
me that is reaonsable.

Anyhoo, I hope I am not being too snippy about this but this simple
project/workspace sharing thing seems needlessly arcane. If the answer is
you are SOL and you cannot create a project and check it in and expect to
import it with the same directory structure on every machine that's fine. I
just need to know if that's true and if so we can have all developers
configure their respective workspaces.

Heck, it works on my machine and I am very impressed with Eclipse. Now if
only we can get the other guys to open my project...:)
Re: When to use import [message #45447 is a reply to message #45278] Fri, 30 May 2003 16:45 Go to previous messageGo to next message
Eclipse UserFriend
Rod Macpherson wrote:
> Anyhoo, I hope I am not being too snippy about this but this simple
> project/workspace sharing thing seems needlessly arcane. If the answer is
> you are SOL and you cannot create a project and check it in and expect to
> import it with the same directory structure on every machine that's fine. I
> just need to know if that's true and if so we can have all developers
> configure their respective workspaces.

It sounds like you are making this WAY more complicated than it needs to
be. Is there some reason you cannot simply do this?:

1. Create a new project on your machine.
2. Right click on the project and select Team > Share Project.
3. Have other developers navigate to the project in the CVS Repository
Exploring perspective, then right click and select "Check Out As Project".
4. There is no step 4.

Jeff
Re: When to use import [message #45625 is a reply to message #45447] Fri, 30 May 2003 18:16 Go to previous messageGo to next message
Eclipse UserFriend
The project is already shared in CVS. Several developers have changes to
many files they are not ready to check in. What they want to do is get the
dot project and dot classpath files from CVS and open Eclipse.

What we are doing is checkout the project and installing Eclipse and then
configuring everybody's workspace/project individually. That seems to work
but we were hoping that we could avoid the individual workstation
workspace/project configuration.
Re: When to use import [message #45685 is a reply to message #45447] Fri, 30 May 2003 18:25 Go to previous message
Eclipse UserFriend
I will suggest that everybody check in their work and then get the project
from CVS. Thanks for the suggestions.
Previous Topic:Sharing Project with CVS
Next Topic:plugin development demo for a new view with treeview dont work
Goto Forum:
  


Current Time: Sun Jul 13 01:04:39 EDT 2025

Powered by FUDForum. Page generated in 0.07980 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top