Talk:Development Lifecycle
(Difference between revisions)
Cschoenfeld (Talk | contribs) m (added link to my user page) |
Cschoenfeld (Talk | contribs) m (changed preformatted text to a bullet list to avoid long lines) |
||
| Line 1: | Line 1: | ||
We have an additional step between 1) and 2) where we use ant to copy all files from our working directory to the directory that is actually synchronized. | We have an additional step between 1) and 2) where we use ant to copy all files from our working directory to the directory that is actually synchronized. | ||
To us, this has the following advantages | To us, this has the following advantages | ||
| − | + | * ant builds a jar from our classes | |
| − | + | * prevent unnecessary files to be synchronized (like .svn-directories) | |
| − | + | * have the possiblity to organize our working directory the way we do it in every project and don't be tied to the structure that opencms expects for a module | |
---- | ---- | ||
Revision as of 15:28, 2 December 2006
We have an additional step between 1) and 2) where we use ant to copy all files from our working directory to the directory that is actually synchronized. To us, this has the following advantages
- ant builds a jar from our classes
- prevent unnecessary files to be synchronized (like .svn-directories)
- have the possiblity to organize our working directory the way we do it in every project and don't be tied to the structure that opencms expects for a module
I do the same as well, though I am using Maven for my builds.
I wrote a small library which creates the folder structure required for OpenCms modules and use it in a Maven plug-in which also creates the module ZIP archive. Though, this is not yet complete because I cannot automatically create the manifest.xml yet. I could write a small Ant plugin for my library.
