Return-Path: Delivered-To: apmail-ws-scout-dev-archive@www.apache.org Received: (qmail 8276 invoked from network); 7 Jan 2007 05:32:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jan 2007 05:32:22 -0000 Received: (qmail 21532 invoked by uid 500); 7 Jan 2007 05:32:29 -0000 Delivered-To: apmail-ws-scout-dev-archive@ws.apache.org Received: (qmail 21511 invoked by uid 500); 7 Jan 2007 05:32:29 -0000 Mailing-List: contact scout-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: scout-dev@ws.apache.org List-Id: Delivered-To: mailing list scout-dev@ws.apache.org Received: (qmail 21500 invoked by uid 99); 7 Jan 2007 05:32:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jan 2007 21:32:28 -0800 X-ASF-Spam-Status: No, hits=4.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [206.190.48.107] (HELO web52104.mail.yahoo.com) (206.190.48.107) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 06 Jan 2007 21:32:17 -0800 Received: (qmail 73886 invoked by uid 60001); 7 Jan 2007 05:31:55 -0000 Message-ID: <20070107053155.73880.qmail@web52104.mail.yahoo.com> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=nzJczu1QX22KTDYhWkdhkX3DzRKsjndtlI2XNfYAHBrPS7Oo/yN30hEIZ+xWi0dNG1KRzqaJJAEX7pZg6OX9dcmx29kLGs7U1hWFWWh3bObHfPTmfRSDijujDT9uLhhzClM9pp7gT00ideEOospxEaseIR8COVKEW172KjWIcqA=; X-YMail-OSG: zCzXIdEVM1ndDSwZ2hA0Z29_iwwE5bwhQhenbG5vZO072Y9Wa1bgMqchyzGm6mNsp.OALSXZXTiR8y9DITHQNNZonw._JUVWyhnNeBXcOfF2Dum1dUg0yR6TNHPpFcur7nT.V7GGtX7OcFt4YF28Tm5daULyzsCIDDK0wycWA2RbMEXeaZB_9Bly Received: from [67.176.193.213] by web52104.mail.yahoo.com via HTTP; Sat, 06 Jan 2007 21:31:55 PST Date: Sat, 6 Jan 2007 21:31:55 -0800 (PST) From: Anil Saldhana Subject: Re: replacing the trunk with branch-v0.7rc3 To: scout-dev@ws.apache.org In-Reply-To: <459FCD73.3070505@redhat.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-193244186-1168147915=:69016" Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org --0-193244186-1168147915=:69016 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit The question of uddi types arose due to plain uddi types (which juddi provided us). But someone had issues with having a dependence on juddi due to classloading issues. So brought in xmlbeans to generate the uddiv2 types. In the long run, since the uddi types are static and will not change, scout can create its own uddi types. Then there is no dependence on juddi or xmlbeans for that. Kurt T Stam wrote: I actually have been working with the trunk code and in fact *like* that it does not depend on the juddi jar (other then for testing). What is the issue with xmlbeans? It seems to do the trick just fine. After looking at the v0.7rc3 code base and understanding the background I think we should keep the trunk code, and *merge* in the branch fixes.I'm sorry for flip flopping here.. My 2 cents --Kurt Anil Saldhana wrote: Ok, here is the background. I asked Kurt to take care of synchronizing rc3 to trunk yesterday and I was supposed to open a VOTE for it today. But because he works in a timezone earlier than me, he broached the topic on the list. The reason the trunk has gone stale is because it contains the xmlbeans related refactoring done last year, which really did not make it to any of the releases. Geir cut the v0.5 release - I made a v0.7rc1 branch out of it and released v0.7rc1 (after a vote ofcourse). Then another branch v0.7rc2 was cut from v0.7rc1 to include bug fixes and released. So yesterday I made a copy of trunk in archives. After a vote, the branch v0.7rc2/rc3 was supposed to be synched up with trunk. Finally, once we are ready - we can do a v0.7 release that takes care of JEE1.4 JAXR requirements(UDDI/Capability level 0 ). Immediate items: a) Sync trunk and active development happens there. b) Release Scout into maven repos. ( I think I did this for v0.7rc2) Also, I want to introduce Kurt as someone who will take juddi and Scout to the next level because he has a lot of ideas. "Geir Magnusson Jr." wrote: Again, who asked you to do this? geir On Jan 4, 2007, at 8:49 AM, Kurt T Stam wrote: > No a vote was not done, I guess the prevailing wisdom is that the most > recent development was done on the branches and not on the trunk. > > --Kurt > > Davanum Srinivas wrote: >> "was asked" - By Who? >> >> Please start a VOTE for doing this. (or was there a vote done >> already?) >> >> thanks, >> dims >> >> On 1/4/07, Kurt T Stam wrote: >>> Hi guys, >>> >>> I was asked to *replace* the trunk with the code in the v0.7rc3 >>> branch. >>> The trunk was archived yesterday afternoon, but before I do this >>> I want >>> to make sure there are no objections to this. The idea is to have >>> the >>> trunk contain the latest code again. Note that this would be a >>> replace, >>> not a merge. >>> >>> I will send out another email before starting the work, but I'd >>> like to >>> it today. >>> >>> Thank you, >>> >>> --Kurt >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org >>> For additional commands, e-mail: scout-dev-help@ws.apache.org >>> >>> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: scout-dev-help@ws.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org For additional commands, e-mail: scout-dev-help@ws.apache.org __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-193244186-1168147915=:69016 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit The question of uddi types arose due to plain uddi types (which juddi provided us). But someone had issues with having a dependence on juddi due to classloading issues. So brought in xmlbeans to generate the uddiv2 types.

In the long run, since the uddi types are static and will not change, scout can create its own uddi types. Then there is no dependence on juddi or xmlbeans for that.

Kurt T Stam <kstam@redhat.com> wrote:
I actually have been working with the trunk code and in fact *like* that it does not depend on the juddi jar (other then for testing). What is the issue with xmlbeans? It seems to do the trick just fine.

After looking at the v0.7rc3 code base and understanding the background I think we should keep the trunk code, and *merge* in the branch fixes.I'm sorry for flip flopping here..

My 2 cents

--Kurt

Anil Saldhana wrote:
Ok, here is the background.

I asked Kurt to take care of synchronizing rc3 to trunk yesterday and I was supposed to open a VOTE for it today. But because he works in a timezone earlier than me, he broached the topic on the list.

The reason the trunk has gone stale is because it contains the xmlbeans related refactoring done last year, which really did not make it to any of the releases.

Geir cut the v0.5 release - I made a v0.7rc1 branch out of it and released v0.7rc1 (after a vote ofcourse). Then another branch v0.7rc2 was cut from v0.7rc1 to include bug fixes and released.

So yesterday I made a copy of trunk in archives. After a vote, the branch v0.7rc2/rc3 was supposed to be synched up with trunk.

Finally, once we are ready - we can do a v0.7 release that takes care of JEE1.4 JAXR requirements(UDDI/Capability level 0 ).

Immediate items:
a) Sync trunk and active development happens there.
b) Release Scout into maven repos. ( I think I did this for v0.7rc2)

Also, I want to introduce Kurt as someone who will take juddi and Scout to the next level because he has a lot of ideas.

"Geir Magnusson Jr." <geir@pobox.com> wrote:
Again, who asked you to do this?

geir

On Jan 4, 2007, at 8:49 AM, Kurt T Stam wrote:

> No a vote was not done, I guess the prevailing wisdom is that the most
> recent development was done on the branches and not on the trunk.
>
> --Kurt
>
> Davanum Srinivas wrote:
>> "was asked" - By Who?
>>
>> Please start a VOTE for doing this. (or was there a vote done
>> already?)
>>
>> thanks,
>> dims
>>
>> On 1/4/07, Kurt T Stam wrote:
>>> Hi guys,
>>>
>>> I was asked to *replace* the trunk with the code in the v0.7rc3
>>> branch.
>>> The trunk was archived yesterday afternoon, but before I do this
>>> I want
>>> to make sure there are no objections to this. The idea is to have
>>> the
>>> trunk contain the latest code again. Note that this would be a
>>> replace,
>>> not a merge.
>>>
>>> I will send out another email before starting the work, but I'd
>>> like to
>>> it today.
>>>
>>> Thank you,
>>>
>>> --Kurt
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-193244186-1168147915=:69016--