Steve responded: |
2013-12-13 11:41 |
Hi Micah:
Thanks for note. Yes, the build process has changed. I will reply to this thread when I have more details for you.
Thanks, Steve |
|
Steve responded: |
2013-12-16 23:16 |
|
|
micahs responded: |
2013-12-17 09:30 |
Hi Steve,
Thanks for the updates. Are there corresponding docs for a build and deploy of the module? These docs are great but they seem to focus on the initial module layout.
Micah |
|
Steve responded: |
2013-12-17 11:42 |
|
|
micahs responded: |
2013-12-17 12:05 |
Thanks. Is that link valid for Java modules? It looked (via jar -tvf on an existing module) like if a Java module contained JSP files they were pre-compiled and placed in the lib dir. Can I just jar up a Java module with the structure detailed in the previous post and drop it in the external modules dir? |
|
adam responded: |
2013-12-17 13:12 |
The "moduleDevelopmentDeployment" page is intended for non-Java modules. As you've seen, we simplified the Java module build process recently to remove the need for a build.xml file in most cases. The main build should build and deploy your custom module, assuming its source directory is referenced in the "standard.modules" file (either explicitly or implicitly via wildcards). The main build will compile your Java files and JSPs, package all code and resources into a .module file, and deploy that module.
Adam |
|