|
If you were logged in you would be able to see more operations.
|
|
|
Several points:
- Right now we have an ant build with ivy setup. Since we have all 3rd party libraries checked into our source control, ivy brings us nothing more then categorizing the libraries (into test, compile, etc..). This could be done easily with plain ant and would make exchanging libraries less painful.
- Also we have the katta-core code under src and some other code under extras. The integration of the extra modules is sub-optimal from my experience. It lacks a good eclipse setup and it requires always extra work to check if a katta-core change breaks any of the extra modules
|
|
Description
|
Several points:
- Right now we have an ant build with ivy setup. Since we have all 3rd party libraries checked into our source control, ivy brings us nothing more then categorizing the libraries (into test, compile, etc..). This could be done easily with plain ant and would make exchanging libraries less painful.
- Also we have the katta-core code under src and some other code under extras. The integration of the extra modules is sub-optimal from my experience. It lacks a good eclipse setup and it requires always extra work to check if a katta-core change breaks any of the extra modules
|
Show » |
|
Improvement
Resolved
Major
simplify katta build
There is a folder 'modules' which contains:
Ant commands are almost the same, the most important are:
The lib folder(s) have now a categorized layout with following subdirs:
For adding, updating or deleting a dependency you just have to do that on the physical level and run ant eclipse again (no update of ivy entry or anything required).