The source file
"demos/smx4web/src/main/java/org/apache/servicemix/smx4webex/WebAppListener.java"
also has the SNAPSHOT hardcoded
(https://issues.apache.org/activemq/browse/SMX4KNL-235). With the
SNAPSHOT included users will have to manually update the pom & source
file in order to have this demo work. If we are ok with this than we
just need to have it release noted.

+1 regarding the rest of the Kernel 1.1.0 (passes all my build tests
on AIX/Linux/Mac)

On Mon, Mar 9, 2009 at 12:45 PM, jgoodyear <[email protected]> wrote:
>
>
> Hi All,
>
>  I have found one issue with the release canidate:
>  https://issues.apache.org/activemq/browse/SMX4KNL-235
>
>  The smx4web demo is looking for 1.1.0-SNAPSHOT instead of the release
> version, this should be changed. As far as kit issues go however do we
> consider this a blocker?
>
> Cheers,
> Jamie Goodyear
>
>
>
> gnodet wrote:
>>
>> I've uploaded a release of ServiceMix Kernel 1.1.0 at
>>      http://people.apache.org/~gnodet/staging/kernel-1.1.0
>> Tag is available at
>>
>> https://svn.apache.org/repos/asf/servicemix/smx4/kernel/tags/kernel-1.1.0/
>> The download page is available at
>>     http://cwiki.apache.org/SMX4KNL/servicemix-kernel-110.html
>>
>> I've kept trunk with 1.1.0-SNAPSHOT version to not break nightly builds
>> until the binaries are published.  At that time, we'll be able to upgrade
>> trunk to 1.2.0-SNAPSHOT and update nmr/features to 1.1.0
>>
>> The vote is open until wednesday 11/03
>> Happy review and vote !
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>>
>
>
> -----
> Jamie Goodyear
> ------------------------
> Blog: http://icodebythesea.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
> --
> View this message in context: 
> http://www.nabble.com/-VOTE--Release-ServiceMix-Kernel-1.1.0-tp22372547p22413450.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
>
>

Reply via email to