| copy/import of project configuration [message #196543] |
Wed, 23 February 2005 04:46  |
Eclipse User |
|
|
|
Originally posted by: pbruehlmann.NO_SPAMaastra.com
Hi!
We have a java project with several packages and several source directories.
This structure is locally stored on my PC.
I've created a project in Ecplise and all works fine.
Now, my collegues are also working on this project and would like to
switch to Ecplise platform also.
They have all the same structure of java source files locally stored.
But the location of this structure can be different. Some are on "C"
drive, some on "D" and so on.
I'd like to avoid all of them to create the project in Ecplipse having
to specify the list of source files, the list of files to exclude, ....
Is it possible to do this ?
TIA
Cheers,
Patrick Brühlmann
|
|
|
|
| Re: copy/import of project configuration [message #196648 is a reply to message #196632] |
Wed, 23 February 2005 10:07  |
| Eclipse User |
|
|
|
Originally posted by: pbruehlmann.NO_SPAMaastra.com
Eric Rizzo wrote:
> Patrick Brühlmann wrote:
>
>> Hi!
>>
>> We have a java project with several packages and several source
>> directories.
>>
>> This structure is locally stored on my PC.
>> I've created a project in Ecplise and all works fine.
>>
>> Now, my collegues are also working on this project and would like to
>> switch to Ecplise platform also.
>>
>> They have all the same structure of java source files locally stored.
>> But the location of this structure can be different. Some are on "C"
>> drive, some on "D" and so on.
>>
>> I'd like to avoid all of them to create the project in Ecplipse having
>> to specify the list of source files, the list of files to exclude, ....
>>
>> Is it possible to do this ?
>
>
> I would assume that you are using CVS or some other form of source
> control/configuration management. If so, you can check in the Eclipse
> Project files (.project and .classpath) into your SCM system and then
> everyone who checks out the project will get the configuration.
> If you're not CVS or some other SCM, well you should be. You might be
> able to just copy those files to other machines.
>
> HTH,
> Eric
>
HI Eric!
Thanks for your answer.
The problem is that the different paths in these files (.project and
..classpath) are absolut paths and this way contains the drive also f.e.
But as written above, every user can have different drive letter f.e.
Cheers,
Patrick
|
|
|
| Re: copy/import of project configuration [message #196664 is a reply to message #196648] |
Wed, 23 February 2005 12:20 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Patrick Brühlmann wrote:
> Eric Rizzo wrote:
>> Patrick Brühlmann wrote:
>>
>>> Hi!
>>>
>>> We have a java project with several packages and several source
>>> directories.
>>>
>>> This structure is locally stored on my PC.
>>> I've created a project in Ecplise and all works fine.
>>>
>>> Now, my collegues are also working on this project and would like to
>>> switch to Ecplise platform also.
>>>
>>> They have all the same structure of java source files locally stored.
>>> But the location of this structure can be different. Some are on "C"
>>> drive, some on "D" and so on.
>>>
>>> I'd like to avoid all of them to create the project in Ecplipse having
>>> to specify the list of source files, the list of files to exclude, ....
>>>
>>> Is it possible to do this ?
>>
>>
>> I would assume that you are using CVS or some other form of source
>> control/configuration management. If so, you can check in the Eclipse
>> Project files (.project and .classpath) into your SCM system and then
>> everyone who checks out the project will get the configuration.
>> If you're not CVS or some other SCM, well you should be. You might be
>> able to just copy those files to other machines.
>>
>> HTH,
>> Eric
>>
> HI Eric!
> Thanks for your answer.
> The problem is that the different paths in these files (.project and
> ..classpath) are absolut paths and this way contains the drive also f.e.
> But as written above, every user can have different drive letter f.e.
> Cheers,
> Patrick
The only paths in these files that should be absolute would be an entry
for an external jar file. All other paths should be relative to the
project.
If you have defined external jar files, you can change these to be
extensions of variables instead of absolute references. On the Java Build
Path->Libraries tab, select Add Variable instead of Add External Jar.
Select Configure Variables to add a new new variable to your workspace and
point at the root of the external jar file. Go back to the New Variable
Classpath Entry dialog, select the variable, and select Extend. Navigate
to the jar file to be added to the project. This will save the reference
in the .classpath file as an entry relative to the variable.
Have the other developers define the variable in their workspace from
Preferences->Java->Build Path->Classpath Variables page. You can now all
use the same .project and .classpath files.
|
|
|
Powered by
FUDForum. Page generated in 0.05807 seconds
Home