OK, I've done the following: downloaded each and every -src.tar.gz
provided, validated the signature and md5 sums; extracted them, build
them and validated there functionality;

So from that point of view +1;

Still, the process was really kind of a PITA. On one hand I need to
download and validate each and every release for it's own, but on the
other hand I can only build them all together since the parent has the
child modules in it's sections and the childs couldn't be build
because they reference the parent... --> The current source release
structure is worst than useless IMHO (for a src only build). We should
either (1) release the entire specs in one big source release (since
they're released together anyhow) or (2) provide a way to build the
parent independently from the children or (3) release the parent
independently; although I'm strongly in favor of option (1).

WDYT?

Kind regards,
Andreas

On Wed, Sep 26, 2012 at 2:57 PM, Freeman Fang <[email protected]> wrote:
> +1
>
> Freeman
> -------------
> Freeman Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://fusesource.com | http://www.redhat.com/
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
> http://blog.sina.com.cn/u/1473905042
> weibo: http://weibo.com/u/1473905042
>
> On 2012-9-26, at 下午2:23, Jean-Baptiste Onofré wrote:
>
>> Hi all,
>>
>> We solved three issues in this release:
>> - SMX4-1248   Update saaj-api to latest geronimo-specs version
>> - SMX4-1229   Create a spec bundle for javax.ws.rs-api 2.0-m10
>> - SMX4-1190   saaj-api bundle jar doesn't work when put it in endorsed folder
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapacheservicemix-045/
>>
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Do not the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>> Thanks
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> [email protected]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>

Reply via email to