| Multiple sources versions in one project [message #226573] |
Mon, 27 March 2006 11:28  |
Eclipse User |
|
|
|
Originally posted by: adrian.fitzpatrick.gmail.com
Hi All,
I am working on a project where we have a number of developers working on
different releases of our application simulateanously. To accommodate
this, we have multiple versions of the source code within the project
(v1.4 is live fix branch, v1.5 is april release, v1.6 may release). See
below for outline of the project structure (thou this make not make sense
until you read the full text!!).
We use Apache ANT to build the project for EAR deployments, this uses a
property file to determine what souce branch to build and outputs compiled
Java to \build\classes. However, I also want the developments to be able
to build as they go using the Java builder in Eclipse. They can currently
do this by configuring their Eclipse instance locally to point its java
build path to the appropriate source directory.
I would prefer if we could maintain one .classpath file for each project
and the developers didnt have to do this configuration. As a alternative
approach, I tried adding multiple source locations, each with a different
output folder - resulting in the \build\classes_v1.4, \build\classes_v1.5,
etc. below. This is not working for me because it results in repeated
entries on the classpath, as a lot of the files are duplicated in
different versions on the source. Is there any way to get around this?
Can anyone suggest an alternate approach (so long as its not too dramatic
- don't want to deviate too much from current setup!)? One other option I
considered was to read what version of the source to use in eclipse for
each developer from the ANT property file, but I don't know how to do this
or if its even possible. Sorry for the wordy post, any help would be much
apprectiated.
Regards,
Adrian
project structure:
\build\classes
\build\classes_v1.4
\build\classes_v1.5
\build\classes_v1.6
\src\java_v1.4
\src\java_v1.5
\src\java_v1.6
\build.xml
|
|
|
| Re: Multiple sources versions in one project [message #226871 is a reply to message #226573] |
Thu, 30 March 2006 14:46  |
| Eclipse User |
|
|
|
Originally posted by: eclipse3.rizzoweb.com
Adrian Fitzpatrick wrote:
> Hi All,
>
> I am working on a project where we have a number of developers working
> on different releases of our application simulateanously. To accommodate
> this, we have multiple versions of the source code within the project
> (v1.4 is live fix branch, v1.5 is april release, v1.6 may release). See
> below for outline of the project structure (thou this make not make
> sense until you read the full text!!).
This really sounds like the need that SCM tools are designed to meet.
Are you using CVS or some other SCM? If so, you're talking about
branches here.
Anyway, I'd recommend having different project for the different
versions. Even when using CVS I've done that when I needed to frequently
switch between different versions of a code base, because swapping
branches is pretty straightforward but can take a bit of time.
Hope this helps,
Eric
> We use Apache ANT to build the project for EAR deployments, this uses a
> property file to determine what souce branch to build and outputs
> compiled Java to \build\classes. However, I also want the developments
> to be able to build as they go using the Java builder in Eclipse. They
> can currently do this by configuring their Eclipse instance locally to
> point its java build path to the appropriate source directory.
> I would prefer if we could maintain one .classpath file for each project
> and the developers didnt have to do this configuration. As a alternative
> approach, I tried adding multiple source locations, each with a
> different output folder - resulting in the \build\classes_v1.4,
> \build\classes_v1.5, etc. below. This is not working for me because it
> results in repeated entries on the classpath, as a lot of the files are
> duplicated in different versions on the source. Is there any way to get
> around this?
> Can anyone suggest an alternate approach (so long as its not too
> dramatic - don't want to deviate too much from current setup!)? One
> other option I considered was to read what version of the source to use
> in eclipse for each developer from the ANT property file, but I don't
> know how to do this or if its even possible. Sorry for the wordy post,
> any help would be much apprectiated.
> Regards,
>
> Adrian
>
> project structure:
>
> \build\classes \build\classes_v1.4
> \build\classes_v1.5
> \build\classes_v1.6
> \src\java_v1.4
> \src\java_v1.5
> \src\java_v1.6
> \build.xml
>
|
|
|
Powered by
FUDForum. Page generated in 0.03125 seconds
Home