geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1492) Many "org/apache/geronimo" configIds still live in source tree
Date Fri, 14 Jul 2006 20:13:15 GMT
    [ ] 
Paul McMahan commented on GERONIMO-1492:

The attached patch (GERONIMO-1492-1.patch) removes all org/apache/geronimo configIds found
by the grep command specified above.  It was created before 1.1 was released so I just rechecked
it and verified that it works correctly when applied to both 1.1.1-SNAPSHOT and trunk.

To test the patch do the following:
-  cd to top level geronimo dir
-  patch -p0 < GERONIMO-1492-1.patch
-  make sure you don't have maven tests disabled
-  maven -o clean new, all test should pass
-  start the console and you should no longer see the system-database listed in the started
application modules.  instead it should say:

  Started Application Modules:
    EAR: geronimo/webconsole-tomcat/1.2-SNAPSHOT/car
    RAR: geronimo/activemq/1.2-SNAPSHOT/car
    WAR: geronimo/remote-deploy-tomcat/1.2-SNAPSHOT/car
    WAR: geronimo/welcome-tomcat/1.2-SNAPSHOT/car

> Many "org/apache/geronimo" configIds still live in source tree
> --------------------------------------------------------------
>                 Key: GERONIMO-1492
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>         Assigned To: Paul McMahan
>            Priority: Blocker
>             Fix For: 1.1.1
>         Attachments: annotated-grep-output.txt, GERONIMO-1492-1.patch, GERONIMO-1492.diff
> I created a couple separate issues, but beyond those a quick search brought up a few
more in magic G ball and day trader -- I stopped before it went any further, but we should
grep for that and try to eliminate all the references to old-style config IDs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message