Because it appears we didn't update this package number with previous
integrations and for our tracking it would be best to match the metro
promoted build version (b10) in the package version,
MartiNG
On 12/05/2011 06:53 PM, Jane Young wrote:
> Question...
> Why is the IPS packaging version changed from 2.2,0-4 to 2.2,0-10?
>
> -metro_version="2.2,0-4"
> +metro_version="2.2,0-10"
>
>
> On 12/5/11 9:40 AM, Martin Grebac wrote:
>> Including packager diff as well:
>>
>> Index: pom.xml
>> ===================================================================
>> --- pom.xml (revision 51271)
>> +++ pom.xml (working copy)
>> @@ -142,11 +142,11 @@
>> <uc-pkg-client.version>1.122-55.2842</uc-pkg-client.version>
>>
>> <uc-pkg-bootstrap.version>1.122-55.2842</uc-pkg-bootstrap.version>
>>
>> -<webservices.version>2.2-b09</webservices.version>
>> +<webservices.version>2.2-b10</webservices.version>
>> <woodstox.version>4.1.2</woodstox.version>
>> <woodstox-stax2.version>3.1.1</woodstox-stax2.version>
>> -<jaxb-api.version>2.2.5</jaxb-api.version>
>> -<jaxb.version>2.2.5-b05</jaxb.version>
>> +<jaxb-api.version>2.2.6</jaxb-api.version>
>> +<jaxb.version>2.2.5-b06</jaxb.version>
>> <jaxrpc-api.version>1.1</jaxrpc-api.version>
>> <jaxrpc-api-osgi.version>1.1-b01</jaxrpc-api-osgi.version>
>> <jaxr-api-osgi.version>1.0-b01</jaxr-api-osgi.version>
>>
>> Index: packager/resources/pkg_conf.py
>> ===================================================================
>> --- packager/resources/pkg_conf.py (revision 51271)
>> +++ packager/resources/pkg_conf.py (working copy)
>> @@ -66,7 +66,7 @@
>> corba_version="3.1.0,0-30"
>> jsf_version="2.1.5,0-4"
>> grizzly_version="1.9.41,0-1"
>> -metro_version="2.2,0-4"
>> +metro_version="2.2,0-10"
>> javahelp_version="2.0.2,0-1"
>> shoal_version="1.6.14,0-0"
>>
>> MartiNG
>>
>
--
Martin Grebac, GlassFish/Metro/JAXWS/JAXB/Tooling at Oracle
http://blogs.oracle.com/mgrebac
ICQ: 93478885