Repository Code Structure Problem
In our current SCM library, files are stored directly off the root directory:
/<build>
/src/<source>
etc...
Playing with RTC source control, I extracted this structure, added a .project file and then imported this existing Eclipse project into RTC. I then shared it with my repository workspace and delivered it to a stream. When our build system extracted this code, I notice that the project name is now included in the code structure:
<project>/<build>
<project>/src/<source>
Our build system is not pure Java Build Engine and the introduction of the <project> directory causes my build to fail because files are not where the build and build scripts expect them to be. I expect this means I have to rework the build scripts, but I'm wondering if the files can be loaded into the stream without the <project> included in the file paths.
Chris
/<build>
/src/<source>
etc...
Playing with RTC source control, I extracted this structure, added a .project file and then imported this existing Eclipse project into RTC. I then shared it with my repository workspace and delivered it to a stream. When our build system extracted this code, I notice that the project name is now included in the code structure:
<project>/<build>
<project>/src/<source>
Our build system is not pure Java Build Engine and the introduction of the <project> directory causes my build to fail because files are not where the build and build scripts expect them to be. I expect this means I have to rework the build scripts, but I'm wondering if the files can be loaded into the stream without the <project> included in the file paths.
Chris
One answer
If you had just added .project files to your /<build> and /src
directories, then you would not have this issue (you must have created a
directory name <project>, and put the .project file into that directory).
You can get into that state now by using your existing project for one
of these projects, and creating a new project for the other one, and
move the files around appropriately.
Cheers,
Geoff
On 1/27/2012 1:08 PM, cbarlock wrote:
directories, then you would not have this issue (you must have created a
directory name <project>, and put the .project file into that directory).
You can get into that state now by using your existing project for one
of these projects, and creating a new project for the other one, and
move the files around appropriately.
Cheers,
Geoff
On 1/27/2012 1:08 PM, cbarlock wrote:
In our current SCM library, files are stored directly off the root
directory:
/<build
/src/<source>/<build>/src/<source
Our build system is not pure Java Build Engine and the introduction of
the<project> directory causes my build to fail because files
are not where the build and build scripts expect them to be. I
expect this means I have to rework the build scripts, but I'm
wondering if the files can be loaded into the stream without the
project> included in the file paths.
Chris