You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/13 07:18:54 UTC
[jira] Created: (GERONIMO-876) console-standard change doesn't make it into console-ear
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
[jira] Updated: (GERONIMO-876) build problems
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=all ]
Aaron Mulder updated GERONIMO-876:
----------------------------------
Summary: build problems (was: console-standard change doesn't make it into console-ear)
Description: see below (original issue was hijacked by comments) (was: 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.)
> build problems
> --------------
>
> 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
>
> see below (original issue was hijacked by comments)
--
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
[jira] Commented: (GERONIMO-876) console-standard change doesn't make it into console-ear
Posted by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=comments#action_12318779 ]
Jeremy Boynes commented on GERONIMO-876:
----------------------------------------
I upgraded to V1.7 of the EAR plugin and am still not having any problems (Sun JDK1.4.2_08 on WinXP)
> 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
Re: [jira] Updated: (GERONIMO-876) build problems
Posted by Jeff Genender <jg...@savoirtech.com>.
JIRA is spewing errors...so I cannot read the issue...but...
I *just* did a fresh checkout and build on my
never-berfore-touched-geronimo-source Windows machine lst night. It
built and ran fine. No problems here.
Jeff
Aaron Mulder (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/GERONIMO-876?page=all ]
>
> Aaron Mulder updated GERONIMO-876:
> ----------------------------------
>
> Fix Version: 1.0-M5
>
> Don't think this is currently a problem, but we need someone with a fresh Windows machine to try the checkout and build to be sure.
>
>
>>build problems
>>--------------
>>
>> 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
>> Fix For: 1.0-M5
>
>
>>see below (original issue was hijacked by comments)
>
>
[jira] Updated: (GERONIMO-876) build problems
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=all ]
Aaron Mulder updated GERONIMO-876:
----------------------------------
Fix Version: 1.0-M5
Don't think this is currently a problem, but we need someone with a fresh Windows machine to try the checkout and build to be sure.
> build problems
> --------------
>
> 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
> Fix For: 1.0-M5
>
> see below (original issue was hijacked by comments)
--
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
[jira] Commented: (GERONIMO-876) console-standard change doesn't make it into console-ear
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Resolved: (GERONIMO-876) build problems
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=all ]
Aaron Mulder resolved GERONIMO-876:
-----------------------------------
Resolution: Cannot Reproduce
Jeff reports that a clean Windows machine built fine last night.
> build problems
> --------------
>
> 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
> Fix For: 1.0-M5
>
> see below (original issue was hijacked by comments)
--
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
[jira] Commented: (GERONIMO-876) console-standard change doesn't make it into console-ear
Posted by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=comments#action_12318777 ]
Jeremy Boynes commented on GERONIMO-876:
----------------------------------------
I am not seeing the application.xml problem:
C:\apache\geronimo\trunk\applications\console-ear>maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download geronimo-console-framework-1.0-SNAPSHOT.war.
Artifact /geronimo/wars/geronimo-console-framework-1.0-SNAPSHOT.war doesn't exists in remote repository, but it exists locally
Attempting to download geronimo-console-standard-1.0-SNAPSHOT.war.
Artifact /geronimo/wars/geronimo-console-standard-1.0-SNAPSHOT.war doesn't exists in remote repository, but it exists locally
Attempting to download pluto-1.0.1-SNAPSHOT.jar.
Attempting to download geronimo-console-core-1.0-SNAPSHOT.jar.
Artifact /geronimo/jars/geronimo-console-core-1.0-SNAPSHOT.jar doesn't exists in remote repository, but it exists locally
build:start:
ear:init:
ear:ear:
[mkdir] Created dir: C:\apache\geronimo\trunk\applications\console-ear\target\plan
[copy] Copying 1 file to C:\apache\geronimo\trunk\applications\console-ear\target
[echo] Building EAR geronimo-console-1.0-SNAPSHOT with appxml "C:\apache\geronimo\trunk\applications\console-ear/target/applicat
ion.xml"
[echo] Bundling: war - geronimo:geronimo-console-framework - 1.0-SNAPSHOT
[echo] Dependency geronimo-console-framework-1.0-SNAPSHOT.war will be bundled as /geronimo-console-framework-1.0-SNAPSHOT.war
[copy] Copying 1 file to C:\apache\geronimo\trunk\applications\console-ear\target\tmpEarDeps
[echo] Bundling: war - geronimo:geronimo-console-standard - 1.0-SNAPSHOT
[echo] Dependency geronimo-console-standard-1.0-SNAPSHOT.war will be bundled as /geronimo-console-standard-1.0-SNAPSHOT.war
[copy] Copying 1 file to C:\apache\geronimo\trunk\applications\console-ear\target\tmpEarDeps
[mkdir] Created dir: C:\apache\geronimo\trunk\applications\console-ear\target\ear
[ear] Building ear: C:\apache\geronimo\trunk\applications\console-ear\target\geronimo-console-1.0-SNAPSHOT.ear
[delete] Deleting directory C:\apache\geronimo\trunk\applications\console-ear\target\tmpEarDeps
ear:install:
[echo] Installing...
Uploading to geronimo/ears/geronimo-console-1.0-SNAPSHOT.ear:
.................... (5769K)
Uploading to geronimo/poms/geronimo-console-1.0-SNAPSHOT.pom:
.................... (12K)
BUILD SUCCESSFUL
Total time: 13 seconds
Finished at: Sun Aug 14 19:20:41 PDT 2005
C:\apache\geronimo\trunk\applications\console-ear>jar tvf target\geronimo-console-1.0-SNAPSHOT.ear
0 Sun Aug 14 19:20:40 PDT 2005 META-INF/
413 Sun Aug 14 19:20:38 PDT 2005 META-INF/MANIFEST.MF
3037 Sun Aug 14 19:20:38 PDT 2005 META-INF/geronimo-application.xml
2485511 Sun Aug 14 19:20:38 PDT 2005 geronimo-console-framework-1.0-SNAPSHOT.war
3516105 Sun Aug 14 19:20:40 PDT 2005 geronimo-console-standard-1.0-SNAPSHOT.war
742 Sun Aug 14 19:20:38 PDT 2005 META-INF/application.xml
C:\apache\geronimo\trunk\applications\console-ear>
> 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
[jira] Closed: (GERONIMO-876) build problems
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=all ]
Dain Sundstrom closed GERONIMO-876:
-----------------------------------
> build problems
> --------------
>
> 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
> Fix For: 1.0-M5
>
> see below (original issue was hijacked by comments)
--
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
[jira] Commented: (GERONIMO-876) console-standard change doesn't make it into console-ear
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-876?page=comments#action_12318778 ]
Donald Woods commented on GERONIMO-876:
---------------------------------------
I recreated it multiple times on the Sun 1.4.2_08 and 1.4.2_09 JDK with clean extracts of HEAD and clean Maven repositories - on WinXP Pro w/ SP2 and Windows Firewall and Windows 2003 Server w/ SP1 and Windows Firewall.... I'm using Maven 1.0.2 and the latest plug-ins that are listed on their website -
maven plugin:download -DgroupId=maven -DartifactId=maven-ant-plugin -Dversion=1.9
maven plugin:download -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion=1.5.2
maven plugin:download -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.8.2
maven plugin:download -DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.9.1
maven plugin:download -DgroupId=maven -DartifactId=maven-cruisecontrol-plugin -Dversion=1.7
maven plugin:download -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.8
maven plugin:download -DgroupId=maven -DartifactId=maven-ear-plugin -Dversion=1.7
maven plugin:download -DgroupId=maven -DartifactId=maven-ejb-plugin -Dversion=1.6
maven plugin:download -DgroupId=maven -DartifactId=maven-gump-plugin -Dversion=2.0.1
maven plugin:download -DgroupId=maven -DartifactId=maven-hibernate-plugin -Dversion=1.3
maven plugin:download -DgroupId=maven -DartifactId=maven-jar-plugin -Dversion=1.7
maven plugin:download -DgroupId=maven -DartifactId=maven-multiproject-plugin -Dversion=1.4.1
maven plugin:download -DgroupId=maven -DartifactId=maven-plugin-plugin -Dversion=1.6
maven plugin:download -DgroupId=maven -DartifactId=maven-scm-plugin -Dversion=1.5
maven plugin:download -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.6.1
maven plugin:download -DgroupId=maven -DartifactId=maven-tasklist-plugin -Dversion=2.4
maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.9
If no one else has seen this build problem on Windows, then maybe its a problem with the order of my path statements or another software package I have installed.....
Thanks for looking into it.
> 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