Re: [DISCUSS] DayTrader 2.1.3 release
Donald Woods wrote: Seems to be a maven problem, in that only one of the CARs is being published This will probably take a reorg of the source tree to fix, like moving the plugin builds into their own /plugins directory like the server builds and only building one plugin per subdirectory. Should I cancel the vote and spend time fixing this, or release what we have and fix it in trunk for DayTrader 2.2? I'm a bit undecided on this. I guess I'm ok with releasing this "as is" for 2.1.3. It's been a long time since we've had a Daytrader release and it seems that this is providing the primary functionality. And ... after all it is a sample ... so perhaps releasing what we have and fixing it in trunk for Daytrader 2.2 makes the most sense. Joe -Donald Joe Bohn wrote: Donald Woods wrote: I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
Sounds like a TODO for DayTrader 2.2. -Donald 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
Given the lack of interest of getting a DayTrader out for the 2.1 codebase, I'm going to move it to samples/trunk for 2.2 unless I get a lot of input and votes on 2.1.3 this week. -Donald Donald Woods 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
Re: [DISCUSS] DayTrader 2.1.3 release
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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 >>> >> > >
Re: [DISCUSS] DayTrader 2.1.3 release
Seems to be a maven problem, in that only one of the CARs is being published This will probably take a reorg of the source tree to fix, like moving the plugin builds into their own /plugins directory like the server builds and only building one plugin per subdirectory. Should I cancel the vote and spend time fixing this, or release what we have and fix it in trunk for DayTrader 2.2? -Donald Joe Bohn wrote: Donald Woods wrote: I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
Does anybody have any information on this? I'm a bit reluctant to vote +1 on this given that our released artifacts don't include everything produced by the build. Joe Joe Bohn wrote: Donald Woods wrote: I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
Donald Woods wrote: I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. 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 <[EMAIL PROTECTED]> 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
Re: [DISCUSS] DayTrader 2.1.3 release
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 <[EMAIL PROTECTED]> 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 >
Re: [DISCUSS] DayTrader 2.1.3 release
Release vote has started. -Donald Donald Woods 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
