Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » Project transfer problem.
Project transfer problem. [message #31142] Tue, 17 February 2004 22:19 Go to next message
Eclipse UserFriend
Originally posted by: user.domain.invalid

Hello All,

I am in the processes of configuring Eclipse for use by a larger
group with an existing code base stored in clearcase. I have gone
through the process of setting up the projects and would now like the
ability to transfer the projects created so that each person in the
group does not have to recreate the wheel.

The details of the projects I've created are as follows.

1. There are 3 "library" project files whose sole purpose is to provide
a convenient way to group a large number of jar files.
2. There are 21 source projects. The number of projects is large to
prevent inadvertently creating dependencies between different projects.
3. Each "source" project contains at least one link directory that is
linked through a clearcase view (ie /view/<myview>/vobs/<vob_name>) to
the directory where the source is stored.

I have had success in transferring the project files if I use
absolute path names and massage the entries in the .classpath and
..project files to reflect their new location. This is not the best
solution but it seems to work.

What I'd like to do is use classpath variables and have each user
create their own instance of two classpath variables. Using this method
a user could change either the version of the source or the dependent
libraries with a single variable change. However, every time I attempt
to import a project that contains variables, the "library" project files
import fine while the "source" project files import with an empty source
folder.

Importing the "library" projects without the CLASSPATH variable
results in an "This project was not built due to classpath errors"
message. Importing the "source" projects without the CLASSPATH variable
does not result in any error message, just an empty source directory.

Also if I remove the CLASSPATH variable that the source file link is
based on, it will invalidate the other source file links that are based
on that variable. Replacing the variable does not fix the situation.

I have examined the .classpath and .project files of the original
and imported projects and they are identical. I'm at a loss and any
help would be appreciated.

Currently using 3.0M6 on sun 5.8 and w2k but I have also tried 2.1.2
with the same symptoms.

Cheers

Frank Rouse
Re: Project transfer problem. [message #31177 is a reply to message #31142] Tue, 17 February 2004 22:22 Go to previous message
Eclipse UserFriend
Originally posted by: user.domain.invalid

Posted to the wrong group,

my apologies.

Frank Rouse wrote:
> Hello All,
>
> I am in the processes of configuring Eclipse for use by a larger
> group with an existing code base stored in clearcase. I have gone
> through the process of setting up the projects and would now like the
> ability to transfer the projects created so that each person in the
> group does not have to recreate the wheel.
>
> The details of the projects I've created are as follows.
>
> 1. There are 3 "library" project files whose sole purpose is to provide
> a convenient way to group a large number of jar files.
> 2. There are 21 source projects. The number of projects is large to
> prevent inadvertently creating dependencies between different projects.
> 3. Each "source" project contains at least one link directory that is
> linked through a clearcase view (ie /view/<myview>/vobs/<vob_name>) to
> the directory where the source is stored.
>
> I have had success in transferring the project files if I use
> absolute path names and massage the entries in the .classpath and
> .project files to reflect their new location. This is not the best
> solution but it seems to work.
>
> What I'd like to do is use classpath variables and have each user
> create their own instance of two classpath variables. Using this method
> a user could change either the version of the source or the dependent
> libraries with a single variable change. However, every time I attempt
> to import a project that contains variables, the "library" project files
> import fine while the "source" project files import with an empty source
> folder.
>
> Importing the "library" projects without the CLASSPATH variable
> results in an "This project was not built due to classpath errors"
> message. Importing the "source" projects without the CLASSPATH variable
> does not result in any error message, just an empty source directory.
>
> Also if I remove the CLASSPATH variable that the source file link is
> based on, it will invalidate the other source file links that are based
> on that variable. Replacing the variable does not fix the situation.
>
> I have examined the .classpath and .project files of the original
> and imported projects and they are identical. I'm at a loss and any
> help would be appreciated.
>
> Currently using 3.0M6 on sun 5.8 and w2k but I have also tried 2.1.2
> with the same symptoms.
>
> Cheers
>
> Frank Rouse
>
Re: Project transfer problem. [message #575565 is a reply to message #31142] Tue, 17 February 2004 22:22 Go to previous message
Frank Rouse is currently offline Frank RouseFriend
Messages: 2
Registered: July 2009
Junior Member
Posted to the wrong group,

my apologies.

Frank Rouse wrote:
> Hello All,
>
> I am in the processes of configuring Eclipse for use by a larger
> group with an existing code base stored in clearcase. I have gone
> through the process of setting up the projects and would now like the
> ability to transfer the projects created so that each person in the
> group does not have to recreate the wheel.
>
> The details of the projects I've created are as follows.
>
> 1. There are 3 "library" project files whose sole purpose is to provide
> a convenient way to group a large number of jar files.
> 2. There are 21 source projects. The number of projects is large to
> prevent inadvertently creating dependencies between different projects.
> 3. Each "source" project contains at least one link directory that is
> linked through a clearcase view (ie /view/<myview>/vobs/<vob_name>) to
> the directory where the source is stored.
>
> I have had success in transferring the project files if I use
> absolute path names and massage the entries in the .classpath and
> .project files to reflect their new location. This is not the best
> solution but it seems to work.
>
> What I'd like to do is use classpath variables and have each user
> create their own instance of two classpath variables. Using this method
> a user could change either the version of the source or the dependent
> libraries with a single variable change. However, every time I attempt
> to import a project that contains variables, the "library" project files
> import fine while the "source" project files import with an empty source
> folder.
>
> Importing the "library" projects without the CLASSPATH variable
> results in an "This project was not built due to classpath errors"
> message. Importing the "source" projects without the CLASSPATH variable
> does not result in any error message, just an empty source directory.
>
> Also if I remove the CLASSPATH variable that the source file link is
> based on, it will invalidate the other source file links that are based
> on that variable. Replacing the variable does not fix the situation.
>
> I have examined the .classpath and .project files of the original
> and imported projects and they are identical. I'm at a loss and any
> help would be appreciated.
>
> Currently using 3.0M6 on sun 5.8 and w2k but I have also tried 2.1.2
> with the same symptoms.
>
> Cheers
>
> Frank Rouse
>
Previous Topic:Project transfer problem.
Next Topic:-> Developerversion 1.1.6 is not Lancaster right?
Goto Forum:
  


Current Time: Mon Feb 19 17:36:16 GMT 2018

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

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