[jboss-jira] [JBoss JIRA] Closed: (JBAS-5117) Update jboss metadata to 1.0.0.Beta5 (from 1.0.0.Beta4)

Dimitris Andreadis (JIRA) jira-events at lists.jboss.org
Sat Jan 12 11:18:19 EST 2008


     [ http://jira.jboss.com/jira/browse/JBAS-5117?page=all ]

Dimitris Andreadis closed JBAS-5117.
------------------------------------


I've flipped trunk to this new Beta5 version. I had to move the release to the legacy position. Was that on purpose?

Added:
   jboss/metadata/1.0.0.Beta5/
Removed:
   jboss/jboss-metadata/1.0.0.Beta5/

We don't have a consistent naming convention. Some modules are jboss/xxx others jboss/jboss-xxx, yet others jboss/jbossxxx:

    <componentref name="jboss/aop" version="2.0.0.CR1"/>
    <componentref name="jboss/cache" version="2.1.0.CR2"/>
    <componentref name="jboss/common-core" version="2.2.3.GA"/>
    <componentref name="jboss/common-logging-jdk" version="2.0.2.GA"/>
    <componentref name="jboss/common-logging-log4j" version="2.0.2.GA"/>
    <componentref name="jboss/common-logging-spi" version="2.0.2.GA"/>
    <componentref name="jboss/integration" version="5.0.0.Beta4"/>
    <componentref name="jboss/jaxr" version="1.2.0.GA"/>
    <componentref name="jboss/jboss-ejb3-cache" version="0.11.1"/>
    <componentref name="jboss/jboss-ejb3-ext-api" version="0.1.2.Beta1"/>
    <componentref name="jboss/jboss-ejb3-impl" version="0.1.2.Beta1"/>
    <componentref name="jboss/jboss-ha-client" version="1.0.0.BETA1"/>
    <componentref name="jboss/jboss-ha-server-api" version="1.0.0.BETA2-SNAPSHOT"/>
    <componentref name="jboss/jboss-jaspi-api" version="1.0-BETA1"/>
    <componentref name="jboss/jboss-javaee" version="5.0.0.Beta3Update1"/>
    <componentref name="jboss/jboss-security-spi" version="2.0.2.Beta3"/>
    <componentref name="jboss/jbosssx" version="2.0.2.Beta3"/>
    <componentref name="jboss/jbosssx-client" version="2.0.2.Beta3"/>
    <componentref name="jboss/jbossts" version="4.3.0.BETA2"/>
    <componentref name="jboss/jboss-vfs" version="2.0.0.Beta6"/>
    <componentref name="jboss/jbossws-native50" version="2.0.2.GA"/>
    <componentref name="jboss/jbossxb" version="2.0.0.CR5"/>
    <componentref name="jboss/jms-integration-tests" version="1.0.1.GA"/>
    <componentref name="jboss/messaging" version="1.4.0.SP3"/>
    <componentref name="jboss/metadata" version="1.0.0.Beta5"/>         
    <componentref name="jboss/microcontainer" version="snapshot"/>
    <componentref name="jboss/profiler/jvmti" version="1.0.0.CR5"/>
    <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/>
    <componentref name="jboss/serialization" version="1.0.3.GA"/>
    <componentref name="jboss/test" version="1.0.4.GA"/>
    <componentref name="jboss/web" version="2.1.0.CR11"/>

> Update jboss metadata to 1.0.0.Beta5 (from 1.0.0.Beta4)
> -------------------------------------------------------
>
>                 Key: JBAS-5117
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5117
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions:  JBossAS-5.0.0.Beta3
>            Reporter: Dimitris Andreadis
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For: JBossAS-5.0.0.Beta4
>
>
> Need another metadata release to resolve JBAS-5097.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list