geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1492) Many "org/apache/geronimo" configIds still live in source tree
Date Fri, 26 May 2006 02:12:30 GMT
     [ ]

Paul McMahan updated GERONIMO-1492:

    Attachment: GERONIMO-1492.diff

I ran the following command in branches/1.1 to find all occurrences of org/apache/geronimo

  grep -r org/apache/geronimo . | grep -v /.svn/ | grep -v '^Binary file' | grep -v '^[^ ]*/target/'

The output from that command is in the attached file annotated-grep-output.txt.  Each entry
in that file is sorted into one of the following categories:

-  occurrences patched in the attached file GERONIMO-1492.diff
-  occurrences in XML that have been commented out
-  occurrences referring to filesystem resources
-  occurrences in obsolete/archived code
-  occurrences in openejb test files
-  occurrences in documentation

I would not consider any of the occurrences to be a serious problem that must be fixed in
1.1.  Probably the only one addressed by the patch that's worth mentioning is in the documentation
section of modules/system/src/schema/local-attributes-1.1.xsd.  The other ones are mostly
just in plans based on the old configId format that are used by various test cases.

> Many "org/apache/geronimo" configIds still live in source tree
> --------------------------------------------------------------
>          Key: GERONIMO-1492
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: GERONIMO-1492.diff, annotated-grep-output.txt
> 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