You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by Ate Douma <at...@douma.nu> on 2011/10/31 12:31:58 UTC
Re: Rave 0.5-incubating
I don't really like to (only temporary) using svn:externals.
The wookie connector should come from Wookie, not us.
And I'd prefer to have a wookie server module and not rely on an external one
which only makes sense for a very minimal/restricted demo only.
If we only are trying to 'squeeze' this in for the 0.5-incubator release to show
on the ApacheCon, I'd rather just build my demo locally for which I don't need
this in the 0.5-incubator release anyway.
My preference is to do this the 'right' way, meaning: wait until Wookie is ready
and not hack something together which needs to be 'fixed' right after the
release again. If this means temporarily disabling again (commenting out) the
SNAPSHOT based wookie integration, so be it.
And the same goes for Wookie (cross-posting this therefore also to wookie-dev@).
IMO the wookie-connector should become a separate module with its own and
independent release cycle (separate trunk). AFAIK this is already anticipated
for wookie 0.9.2 (trunk). The current security issue for Wookie also wouldn't
affect the wookie-connector then, which is good.
For Wookie, I'd prefer skipping the 0.9.1 release then altogether and simply
focus on getting the 0.9.2 release ready. Rave 0.6-incubator than can pick up
that version instead. Trying to get a RCx version for 0.9.1 released until no
further issues are found, while trunk already has this fixed is an inefficient
and confusing to say the least (how many 0.9.1 votes can you have?)
Ate
On 10/31/2011 12:11 PM, Ross Gardler wrote:
> On 31 October 2011 11:01, Jasha Joachimsthal
> <j....@onehippo.com> wrote:
>> On 31 October 2011 11:56, Ross Gardler<rg...@opendirective.com> wrote:
>>
>>> On 31 October 2011 10:49, Ross Gardler<rg...@opendirective.com> wrote:
>>>> Well, the 0.9.2 vote was passed, but unfortunately yesterday we
>>>> uncovered a serious issue that is going to block it's release
>>>> (security issue).
>>>>
>>>> I'm afraid the 0.5 Rave release will have to go without Wookie
>>>> integration. Is it possible to exclude the Wookie module from the
>>>> build or do you want me to roll back the wookie commits in order to
>>>> remove the snapshot dependency?
>>>
>>> A third option would be for us to use svn:external to pull in the
>>> necessary connector code from the tagged 0.9.1 release of Wookie.
>>> Doing this we would not bundle the Wookie server with Rave 0.5, the
>>> Oxford server is pretty stable and should be OK for a month of an
>>> undocumented feature.
>>>
>>
>> This is an option for local development, but if we do that would that mean
>> - if you want to use Rave 0.5 you have to build the project yourself
>> instead of having all the artifacts in the central maven repository?
>> - Rave pushes a Wookie artifact into the central repository?
>
> Wookie provides a connector framework. In 0.9 it was not released as a
> separate artifact, in 0.9.1 it will be but I have been forced to vote
> -1 on the release today.
>
> If we use svn:external the necessary code will be checked out from a
> release tag onto the local development machine. When the module is
> built by the release manager it would be compiled as if it were a part
> of the rave-wookie module and deployed to Maven as part of that jar.
>
> The code in question is just a few classes found at
> http://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.0-incubating/connector/java/src/
>
> Ross
>
>>
>>
>>> Ross
>>>
>>>>
>>>> Ross
>>>>
>>>>
>>>>
>>>> On 31 October 2011 10:40, Jasha Joachimsthal
>>>> <j....@onehippo.com> wrote:
>>>>> On 30 October 2011 17:53, Franklin, Matthew B.<mf...@mitre.org>
>>> wrote:
>>>>>
>>>>>> In order to get the release out before ApacheCon, I need to start the
>>>>>> process tomorrow afternoon. Please make sure any last minute tweaks
>>> are in
>>>>>> by 4:00 pm eastern.
>>>>>>
>>>>>> -Matt
>>>>>>
>>>>>> Sent via a mobile device. Please excuse typos or brevity.
>>>>>>
>>>>>
>>>>> There's still a snapshot dependency on Wookie. @Ross or @Scott can you
>>> fix
>>>>> this?
>>>>>
>>>>> Jasha Joachimsthal
>>>>>
>>>>> Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522
>>> 4466
>>>>> US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll
>>> free)
>>>>>
>>>>> www.onehippo.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ross Gardler (@rgardler)
>>>> Programme Leader (Open Development)
>>>> OpenDirective http://opendirective.com
>>>>
>>>
>>>
>>>
>>> --
>>> Ross Gardler (@rgardler)
>>> Programme Leader (Open Development)
>>> OpenDirective http://opendirective.com
>>>
>>
>
>
>
RE: Rave 0.5-incubating
Posted by "Franklin, Matthew B." <mf...@mitre.org>.
>________________________________________
>From: Ate Douma [ate@douma.nu]
>Sent: Monday, October 31, 2011 7:31 AM
>To: rave-dev@incubator.apache.org
>Cc: wookie-dev@incubator.apache.org
>Subject: Re: Rave 0.5-incubating
>
>I don't really like to (only temporary) using svn:externals.
>The wookie connector should come from Wookie, not us.
>And I'd prefer to have a wookie server module and not rely on an external one
>which only makes sense for a very minimal/restricted demo only.
>
>If we only are trying to 'squeeze' this in for the 0.5-incubator release to show
>on the ApacheCon, I'd rather just build my demo locally for which I don't need
>this in the 0.5-incubator release anyway.
>
>My preference is to do this the 'right' way, meaning: wait until Wookie is ready
>and not hack something together which needs to be 'fixed' right after the
>release again. If this means temporarily disabling again (commenting out) the
>SNAPSHOT based wookie integration, so be it.
+1. I will comment out the additions to the POM before I push the button on the release
>
>And the same goes for Wookie (cross-posting this therefore also to wookie-dev@).
>IMO the wookie-connector should become a separate module with its own and
>independent release cycle (separate trunk). AFAIK this is already anticipated
>for wookie 0.9.2 (trunk). The current security issue for Wookie also wouldn't
>affect the wookie-connector then, which is good.
>
>For Wookie, I'd prefer skipping the 0.9.1 release then altogether and simply
>focus on getting the 0.9.2 release ready. Rave 0.6-incubator than can pick up
>that version instead. Trying to get a RCx version for 0.9.1 released until no
>further issues are found, while trunk already has this fixed is an inefficient
>and confusing to say the least (how many 0.9.1 votes can you have?)
>
>Ate
>
>
>On 10/31/2011 12:11 PM, Ross Gardler wrote:
>> On 31 October 2011 11:01, Jasha Joachimsthal
>> <j....@onehippo.com> wrote:
>>> On 31 October 2011 11:56, Ross Gardler<rg...@opendirective.com> wrote:
>>>
>>>> On 31 October 2011 10:49, Ross Gardler<rg...@opendirective.com> wrote:
>>>>> Well, the 0.9.2 vote was passed, but unfortunately yesterday we
>>>>>uncovered a serious issue that is going to block it's release
>>>>>(security issue).
>>>>>
>>>>> I'm afraid the 0.5 Rave release will have to go without Wookie
>>>>> integration. Is it possible to exclude the Wookie module from the
>>>>> build or do you want me to roll back the wookie commits in order to
>>>>> remove the snapshot dependency?
>>>>
>>>> A third option would be for us to use svn:external to pull in the
>>>> necessary connector code from the tagged 0.9.1 release of Wookie.
>>>> Doing this we would not bundle the Wookie server with Rave 0.5, the
>>>> Oxford server is pretty stable and should be OK for a month of an
>>>> undocumented feature.
>>>>
>>>
>>> This is an option for local development, but if we do that would that mean
>>> - if you want to use Rave 0.5 you have to build the project yourself
>>> instead of having all the artifacts in the central maven repository?
>>> - Rave pushes a Wookie artifact into the central repository?
>>
>> Wookie provides a connector framework. In 0.9 it was not released as a
>> separate artifact, in 0.9.1 it will be but I have been forced to vote
>> -1 on the release today.
>>
>> If we use svn:external the necessary code will be checked out from a
>> release tag onto the local development machine. When the module is
>> built by the release manager it would be compiled as if it were a part
>> of the rave-wookie module and deployed to Maven as part of that jar.
>>
>> The code in question is just a few classes found at
>> http://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.0-incubating/connector/java/src/
>>
>> Ross
>>
>>>
>>>
>>>> Ross
>>>>
>>>>>
>>>>> Ross
>>>>>
>>>>>
>>>>>
>>>>> On 31 October 2011 10:40, Jasha Joachimsthal
>>>>> <j....@onehippo.com> wrote:
>>>>>> On 30 October 2011 17:53, Franklin, Matthew B.<mf...@mitre.org>
>>>> wrote:
>>>>>>
>>>>>>> In order to get the release out before ApacheCon, I need to start the
>>>>>>> process tomorrow afternoon. Please make sure any last minute tweaks
>>>> are in
>>>>>>> by 4:00 pm eastern.
>>>>>>>
>>>>>>> -Matt
>>>>>>>
>>>>>>> Sent via a mobile device. Please excuse typos or brevity.
>>>>>>>
>>>>>>
>>>>>> There's still a snapshot dependency on Wookie. @Ross or @Scott can you
>>>> fix
>>>>>> this?
>>>>>>
>>>>>> Jasha Joachimsthal
>>>>>>
>>>>>> Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522
>>>> 4466
>>>>>> US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll
>>>> free)
>>>>>>
>>>>>> www.onehippo.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ross Gardler (@rgardler)
>>>>> Programme Leader (Open Development)
>>>>> OpenDirective http://opendirective.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ross Gardler (@rgardler)
>>>> Programme Leader (Open Development)
>>>> OpenDirective http://opendirective.com
>>>>
>>>
>>
>>
>>