Romain,
If the changes only contains version update with no bug fixes. Basically, teams need to release their final version of the product like JavaMail is doing here, they don't need to have CCP approval. I will send an email about it today.
thanks,
Michael
On Apr 10, 2013, at 11:45 AM, Romain Grecourt wrote:
> I thought Michael would approve this with the CCP approval.
>
> I've just integrated spec-version-maven-plugin:1.0, please update the javamail data under appserver/pom.xml
> You can verify that there is no warning related to javamail when running the following command from appserver/distributions/glassfish:
> > mvn spec-version:check-distribution
>
> Thanks,
> Romain
>
> On 4/9/13 9:59 PM, Bill Shannon wrote:
>> This is the final integration of JavaMail 1.5 into GlassFish 4.0 for Java EE 7.
>> Quicklook passes.
>>
>> $ svn diff
>> Index: nucleus/pom.xml
>> ===================================================================
>> --- nucleus/pom.xml (revision 61234)
>> +++ nucleus/pom.xml (working copy)
>> @@ -134,7 +134,7 @@
>>
>> <source-annotation-processor.version>1.0</source-annotation-processor.version>
>>
>> <logging-annotation-processor.version>1.5</logging-annotation-processor.version>
>> <command-security-plugin.version>1.0.4</command-security-plugin.version>
>> - <mail.version>1.5.0-b02</mail.version>
>> + <mail.version>1.5.0</mail.version>
>> <javax.annotation-api.version>1.2-b04</javax.annotation-api.version>
>> <copyright-plugin.version>1.39</copyright-plugin.version>
>> <jdk.version>1.7.0-09</jdk.version>
>