[ 
http://issues.apache.org/jira/browse/GERONIMO-2495?page=comments#action_12442649
 ] 
            
Mark DeLaFranier commented on GERONIMO-2495:
--------------------------------------------

In order to test your theory, I did the followin:

1. Reverted j2ee-corba-sun/src/plan/plan.xml
2. From within the server/configs/j2ee-corba-sun directory ran the following:

mvn -o clean
mvn -o compile
mvn -o install

This did not reproduce the original error.

3. I then decided to perform a clean and build via (from the server directory)

mvn -o clean
mvn -o install

It seems that after I changed then plan and did a full build, that I can no 
longer reproduce this problem anymore.  :-(

> Build error: server/config/j2ee-corba-* plans refer to corba-tss-config-2.0 
> instead of corba-tss-config-2.1
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2495
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2495
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.2
>         Environment: windows xp
>            Reporter: Mark DeLaFranier
>         Attachments: corba-plan-patch.txt
>
>
> While building the latest codeline, the build failed due to bad references in 
> the xml namespace.  The following plans:
> j2ee-corba-sun/src/plan/plan.xml
> j2ee-corba-yoko/src/plan/plan.xml
> refer to the namespace:
> http://www.openejb.org/xml/ns/corba-tss-config-2.0
> but looking at the openejb2 codeline, I only find:
> http://www.openejb.org/xml/ns/corba-tss-config-2.1
> From:
> openejb/openejb2/modules/openejb-builder/src/main/xsd/corba-tss-config-2.1.xsd

-- 
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

        

Reply via email to