Talk:Development Lifecycle
Cschoenfeld (Talk | contribs) m (added more info on the library/plugin) |
|||
| (4 intermediate revisions by one user not shown) | |||
| 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 | |
| + | |||
| + | ---- | ||
| + | |||
| + | 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 also creates the module ZIP archive. Though, this is not yet complete because I cannot automatically create the manifest.xml yet. However, the library works quite well if you have a valid manifest.xml. You can then just import the module into any OpenCms server using the import function. I use this library in a Maven plug-in I wrote. I could write an Ant plugin as well if anyone's interested and make the thing available. | ||
| + | |||
| + | [[User:Cschoenfeld]] | ||
Latest revision as of 15:32, 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 also creates the module ZIP archive. Though, this is not yet complete because I cannot automatically create the manifest.xml yet. However, the library works quite well if you have a valid manifest.xml. You can then just import the module into any OpenCms server using the import function. I use this library in a Maven plug-in I wrote. I could write an Ant plugin as well if anyone's interested and make the thing available.
