| Key: |
CIB-1639
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
4
|
| Assignee: |
Unassigned
|
| Reporter: |
Daniel Ostermeier
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 16/Sep/08 08:08 PM
Updated: 12/Dec/08 01:43 AM
|
|
| Component/s: |
Scm
|
| Affects Version/s: |
2.0.10
|
| Fix Version/s: |
2.x
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related
|
|
This issue is relates to:
|
|
CIB-1641
Scm properties not available in pulse...
|
|
|
|
CIB-1746
Look at ways of shortening the build ...
|
|
|
|
|
|
|
|
It would be nice if I could use the property ${cvs.module}, everywhere (or ${cvs.module.0}, ${cvs.module.1} if multiple are supported), or somehow specify that everything gets checked out to simply "cvs_module". There are actually some projects that will fail to build due to path length limitations on Windows, depending on where the Pulse working directory is located, and the length of the cvs module path and resulting output filenames.
|
|
Description
|
It would be nice if I could use the property ${cvs.module}, everywhere (or ${cvs.module.0}, ${cvs.module.1} if multiple are supported), or somehow specify that everything gets checked out to simply "cvs_module". There are actually some projects that will fail to build due to path length limitations on Windows, depending on where the Pulse working directory is located, and the length of the cvs module path and resulting output filenames. |
Show » |
|
CIB-1641Now that this is in place, we can internally tweak the checkout path to something like cvs_module and so long as the project is using the ${cvs.module} where necessary, things will be ok.
The question that comes to mind is how much this will help with the path length limitation on windows machines. How much of the path is contributed by the cvs module and how much comes from the project path itself (com/zutubi/pulse/core/... for example) or the pulse data directory path. I have raised CIB-1746 to look at this issue directly.