You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <de...@geronimo.apache.org> on 2005/08/15 04:09:54 UTC
[jira] Commented: (GERONIMO-876) console-standard change doesn't make it into console-ear
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=comments#action_12318776 ]
Donald Woods commented on GERONIMO-876:
---------------------------------------
There is also a build problem for new checkouts and a clean Maven repository on Windows machines, where the application.xml is not being included in the built EAR file. For build error traces, see my post on 8/12 in the archive at http://mail-archives.apache.org/mod_mbox/geronimo-dev/200508.mbox/%3c20050812201250.92102.qmail@web32603.mail.mud.yahoo.com%3e
The following patches can be used to fix the Windows build -
applications\console-ear\maven.xml
Index: maven.xml
===================================================================
--- maven.xml (revision 232395)
+++ maven.xml (working copy)
@@ -5,12 +5,13 @@
>
<goal name="default">
+ <attainGoal name="ear:ear"/>
<attainGoal name="ear:install"/>
</goal>
<preGoal name="ear:ear">
- <ant:mkdir dir="${basedir}/target/plan"/>
- <velocity:merge basedir="${basedir}/src/application/META-INF" template="application.xml" name="${basedir}/target/plan/application.xml"/>
- <velocity:merge basedir="${basedir}/src/plan" template="geronimo-application.xml" name="${basedir}/src/application/META-INF/geronimo-application.xml"/>
+ <ant:mkdir dir="${basedir}/target"/>
+ <velocity:merge basedir="${basedir}/src/application/META-INF" template="application.xml" name="${basedir}/target/application.xml"/>
+ <velocity:merge basedir="${basedir}/src/plan" template="geronimo-application.xml" name="${basedir}/src/application/META-INF/geronimo-application.xml"/>
</preGoal>
</project>
applications\console-ear/project.properties
Index: project.properties
===================================================================
--- project.properties (revision 232395)
+++ project.properties (working copy)
@@ -1,2 +1,2 @@
maven.multiproject.type=ear
-maven.ear.appxml=target/plan/application.xml
+maven.ear.appxml=target/application.xml
> console-standard change doesn't make it into console-ear
> --------------------------------------------------------
>
> Key: GERONIMO-876
> URL: http://issues.apache.org/jira/browse/GERONIMO-876
> Project: Geronimo
> Type: Bug
> Components: buildsystem, console
> Versions: 1.0-M5
> Reporter: Aaron Mulder
>
> If code in the console-standard module is changed, a new artifact for that module is built. However, the console-ear module does not consider itself out of date as a result of that, so the change is not reflected in the new assembly until the console-ear module is manually cleaned and rebuilt. It should be that a normal build of Geronimo recreates the console-ear if the console-standard has been updated. As a shortcut, we could recreate console-ear every time since it's quite fast.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira