geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <joe.b...@earthlink.net>
Subject Re: [DISCUSS] DayTrader 2.1.3 release
Date Mon, 08 Dec 2008 18:43:23 GMT
Lin,

Thanks for the information.  IIUC then, the plugin catalog entries and 
lack of jetty client plugins seem to be independent issues from the 
tomcat client cars not being released.   So there are a few issues then. 
    Given that this is a sample they might not be show-stoppers.

Joe

Lin Sun wrote:
> Hi Joe/Donald,
> 
> Yes the tomcat client plugin is built when you do a local build and
> the car artifact can be installed as a plugin when you supply the .car
> file during the plugin installation.  The prob IIRC is that we don't
> have a way to automatically update the plugin catalog file yet, thus
> if you choose to select plugins from a repo, you won't be able to see
> this client plugin in the repo as it is not in the plugin catalog.
> 
> One apporach is to manually update the plugin catalog in the repo, by
> copying the content of the geronimo-plugin.xml inside of the client
> car artifact.    This worked well when I tested it.
> 
> For the jetty version, I think I forgot to work on them :-(   I think
> it would be nice to get it completed as well.
> 
> Lin
> 
> On Fri, Dec 5, 2008 at 12:05 PM, Joe Bohn <joe.bohn@earthlink.net> wrote:
> 
>> I'm confused by this.  The tomcat client plugins *are* built when you do a
>> local build (as the README mentions) ... and supposedly they can be
>> installed as plugins according to the README as well (I didn't try this).
>>
>> So why are these tomcat client car files not included in the staging-repo
>> content that we are voting on?
>>
>> We're voting on both the source and the artifacts ... so if the source when
>> built produces the artifacts it seems like we should be voting on those too.
>>
>> BTW, only the tomcat cars exist as an archive file ... there are jetty
>> versions but they only exist in an unpacked form.
>>
>> Here are the artifacts for the clients produced by the build:
>> ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car
>> ./daytrader-tomcat/target/daytrader-streamer-client-2.1.3.car
>> ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car
>> ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car
>> ./daytrader-tomcat/target/daytrader-ws-client-2.1.3.car
>> ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car
>>
>> Is there some strange build processing that is creating these which is not
>> honored by the mvn release plugin?
>>
>> Joe
>>
>>> Maybe we can get them setup as plugins in daytrader/trunk for the 2.2
>>> release.
>>>
>>>
>>> -Donald
>>>
>>>
>>> Lin Sun wrote:
>>>> Hi Donald,
>>>>
>>>> Thanks for getting this out for vote!
>>>>
>>>> Do we plan to allow users to install the app client as G plugin?  If
>>>> so, I think there is a manual work, that is to add the app client's
>>>> plugin.xml file to the plugin catalog (geronimo-plugins.xml).  I think
>>>> we've got code to pack the app client car file and copy it onto local
>>>> .m2 repo.
>>>>
>>>> Thanks
>>>>
>>>> Lin
>>>>
>>>> On Tue, Dec 2, 2008 at 5:03 PM, Donald Woods <dwoods@apache.org> wrote:
>>>>> I'm working on updating the daytrader/branches/2.1 for a 2.1.3 release
>>>>> (will
>>>>> rename it to branches/2.1.3 shortly.)  Once everything is ready, I'll
>>>>> put it
>>>>> up for a vote.
>>>>>
>>>>> BTW - I'm not creating a branches/2.1 for on-going maintenance, as if
it
>>>>> is
>>>>> ever needed, we can copy over the 2.1.3 tag to create it.  I'm just
>>>>> wanting
>>>>> to get this overdue Daytrader 2.1.x out so we can focus on the 2.2
>>>>> release.
>>>>>
>>>>>
>>>>> -Donald
>>>>>
>>
> 


Mime
View raw message