I think its a good idea to have the upgrades blessed. Other than
validating the impact on other
product modules including packager, the review request help us to avoid
unplanned component
upgrades, track updates per build if required.
Thanks
Sathyan
On 11/28/11 10:41 AM, Ryan Lubke wrote:
> Just a general process question. Do we really need to have pom
> reviews for simple version bumps? I can can understand reviews for
> more complex build changes, but this seems to be overkill....
>
>
>
> On 11/28/11 10:27 AM, Snjezana Sevo-Zenzerovic wrote:
>> Looks fine...
>>
>> Thanks,
>>
>> Snjezana
>>
>> ----- Original Message -----
>> From: pavel.bucek_at_oracle.com
>> To: dev_at_glassfish.java.net
>> Sent: Monday, November 28, 2011 12:27:43 AM GMT -08:00 US/Canada Pacific
>> Subject: Re: pom change review - jersey 1.11-b02 integration
>>
>> bump
>>
>> On 11/25/11 10:47 AM, Pavel Bucek wrote:
>>> *trunk* + *3.1.2* branch
>>>
>>> Index: pom.xml
>>> ===================================================================
>>> --- pom.xml (revision 51133)
>>> +++ pom.xml (working copy)
>>> @@ -152,7 +152,7 @@
>>> <javadb.version>10.6.2.1</javadb.version>
>>> <jaxr.version>JAXR_RA_20091012</jaxr.version>
>>> <weld.version>1.1.3.SP1</weld.version>
>>> -<jersey.version>1.11-b01</jersey.version>
>>> +<jersey.version>1.11-b02</jersey.version>
>>> <jbi.version>1.0</jbi.version>
>>> <wsdl4j.version>1.6.2</wsdl4j.version>
>>>
>>> <glassfish-management-api.version>3.1.0-b001</glassfish-management-api.version>
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>> Pavel
>>>
>