+1 

On Sep 28, 2011, at 3:26 AM, Freeman Fang wrote:

> +1
> 
> Freeman
> On 2011-9-20, at 下午10:07, Jean-Baptiste Onofré wrote:
> 
>> Hi all,
>> 
>> in order to align the ServiceMix Archetypes with the Components, I submit 
>> ServiceMix Archetypes 2011.01 release.
>> 
>> This release includes:
>> 
>> * Bug
>>   [SM-988] - WSDL generation fails (SU built by 
>> servicemix-jsr181-annotated-service-unit archetype)
>>   [SM-1490] - The ServiceMix Maven archetypes are not being recognized as 
>> Maven Archetypes by the Nexus indexer
>>   [SM-1970] - Schema location is incorrect for 
>> servicemix-quartz-2010.01.0-fuse-02-00.xsd in servicemix-quartz archetype
>>   [SM-2002] - Maven3 is not happy with poms
>>   [SM-2015] - servicemix camel archtype generates camel-context.xml with 
>> wrong namespace
>>   [SM-2112] - Component archetypes should create the blueprint descriptor
>>   [SM-2121] - Multiple versions in catalog files generated by archetypes 
>> build
>> * Improvement
>>   [SM-1339] - Provide better default values when using the archetype catalog
>>   [SM-1946] - Upgrade archetypes and provide a clean version
>>   [SM-2022] - Replace commons logging in servicemix-camel-osgi-bundle 
>> archetype with java.util.logging to simplify example
>> * Task
>>   [SM-2059] - Release archetypes 2011.01
>> * Test
>>   [SM-2046] - Maven Archetypes itests only tests one of the archetypes
>> 
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-080/
>> 
>> Please vote to approve this release:
>> 
>> [ ] +1 Approve the release
>> [ ] -1 Refuse the release (please provide specific comments)
>> 
>> This vote will be open for 72 hours.
>> 
>> Thanks all,
>> 
>> Regards
>> JB
>> -- 
>> Jean-Baptiste Onofré
>> [email protected]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
> 
> ---------------------------------------------
> Freeman Fang
> 
> FuseSource
> Email:[email protected]
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
> 
> 
> 
> 
> 
> 
> 
> 
> 

Reply via email to