[VOTE] Move JSON plugin to trunk
I think the JSON plugin is ready to be moved to trunk, here is my +1. musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [VOTE] Move JSON plugin to trunk
+1 On Wed, Aug 5, 2009 at 10:40 AM, Musachy Barroso wrote: > I think the JSON plugin is ready to be moved to trunk, here is my +1. > > > musachy > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
Re: [VOTE] Move JSON plugin to trunk
+1 On Wed, Aug 5, 2009 at 12:40 PM, Musachy Barroso wrote: > I think the JSON plugin is ready to be moved to trunk, here is my +1. > > > musachy > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
Re: [VOTE] Move JSON plugin to trunk
Musachy Barroso wrote: I think the JSON plugin is ready to be moved to trunk, here is my +1. (non-committer's non-binding) +1 -Dale - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
It looks like also the Struts StrutsTestCase depends on the same class
in wrong location, should I move that class also?
Regards
--
Lukasz
http://www.lenart.org.pl/
http://dailylog.lenart.org.pl/
2009/8/5 Atlassian Open Source Bamboo :
> STRUTS-MAINJ6-911 failed.
> This build occured because it is a dependant of XWORK-MAIN-396.
> No failed tests found, a possible compilation error.
> Code Changes
> This build does not have any commits.
> Error Summary See full build log
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[32,30]
> cannot find symbol
> symbol : class TestNGXWorkTestCase
> location: package com.opensymphony.xwork2
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[38,36]
> cannot find symbol
> symbol: class TestNGXWorkTestCase
> public class StrutsTestCase extends TestNGXWorkTestCase {
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[42,8]
> cannot find symbol
> symbol : variable super
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[48,8]
> cannot find symbol
> symbol : variable configurationManager
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[49,8]
> cannot find symbol
> symbol : variable configuration
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[49,24]
> cannot find symbol
> symbol : variable configurationManager
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[50,8]
> cannot find symbol
> symbol : variable container
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[50,20]
> cannot find symbol
> symbol : variable configuration
> location: class org.apache.struts2.StrutsTestCase
>
> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[56,8]
> cannot find symbol
> symbol : variable super
> location: class org.apache.struts2.StrutsTestCase
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
>
> Email generated by Atlassian Bamboo - if you wish to stop receiving these
> emails edit your user profile or notify your administrator
> Want this information in your IDE?
> Actions
> View Online
> Add Comments
> View Artifacts
> Download Logs
>
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
is that a class in core? or the one in the junit plugin ?
On Wed, Aug 5, 2009 at 11:55 AM, Lukasz
Lenart wrote:
> It looks like also the Struts StrutsTestCase depends on the same class
> in wrong location, should I move that class also?
>
>
> Regards
> --
> Lukasz
> http://www.lenart.org.pl/
> http://dailylog.lenart.org.pl/
>
> 2009/8/5 Atlassian Open Source Bamboo :
>> STRUTS-MAINJ6-911 failed.
>> This build occured because it is a dependant of XWORK-MAIN-396.
>> No failed tests found, a possible compilation error.
>> Code Changes
>> This build does not have any commits.
>> Error Summary See full build log
>> [INFO]
>>
>> [ERROR] BUILD FAILURE
>> [INFO]
>>
>> [INFO] Compilation failure
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[32,30]
>> cannot find symbol
>> symbol : class TestNGXWorkTestCase
>> location: package com.opensymphony.xwork2
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[38,36]
>> cannot find symbol
>> symbol: class TestNGXWorkTestCase
>> public class StrutsTestCase extends TestNGXWorkTestCase {
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[42,8]
>> cannot find symbol
>> symbol : variable super
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[48,8]
>> cannot find symbol
>> symbol : variable configurationManager
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[49,8]
>> cannot find symbol
>> symbol : variable configuration
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[49,24]
>> cannot find symbol
>> symbol : variable configurationManager
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[50,8]
>> cannot find symbol
>> symbol : variable container
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[50,20]
>> cannot find symbol
>> symbol : variable configuration
>> location: class org.apache.struts2.StrutsTestCase
>>
>> /opt/j2ee/domains/bamboo.atlassian.com/opensource/home/xml-data/build-dir/STRUTS-MAINJ6/plugins/testng/src/main/java/org/apache/struts2/StrutsTestCase.java:[56,8]
>> cannot find symbol
>> symbol : variable super
>> location: class org.apache.struts2.StrutsTestCase
>>
>>
>> [INFO]
>>
>> [INFO] For more information, run Maven with the -e switch
>>
>> Email generated by Atlassian Bamboo - if you wish to stop receiving these
>> emails edit your user profile or notify your administrator
>> Want this information in your IDE?
>> Actions
>> View Online
>> Add Comments
>> View Artifacts
>> Download Logs
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > is that a class in core? or the one in the junit plugin ? It's from core. Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
yeah you can move that one around if needed. On Wed, Aug 5, 2009 at 12:08 PM, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> is that a class in core? or the one in the junit plugin ? > > It's from core. > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > yeah you can move that one around if needed. My mistake, it's in testng-plugin Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
if you move it it will break for people who are using it On Wed, Aug 5, 2009 at 12:24 PM, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> yeah you can move that one around if needed. > > My mistake, it's in testng-plugin > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
the problem is that those are not real tests, in the sense that they dont test anything, like StrutsTestCase, they are extended by users to create their own tests, so the code has to be under src/java/main instead of "test". musachy On Wed, Aug 5, 2009 at 12:32 PM, Musachy Barroso wrote: > if you move it it will break for people who are using it > > On Wed, Aug 5, 2009 at 12:24 PM, Lukasz > Lenart wrote: >> 2009/8/5 Musachy Barroso : >>> yeah you can move that one around if needed. >> >> My mistake, it's in testng-plugin >> >> >> Regards >> -- >> Lukasz >> http://www.lenart.org.pl/ >> http://dailylog.lenart.org.pl/ >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > if you move it it will break for people who are using it So then I have to rollback changes I made to Xwork and move back ;-( Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
fun fun :) On Wed, Aug 5, 2009 at 12:36 PM, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> if you move it it will break for people who are using it > > So then I have to rollback changes I made to Xwork and move back ;-( > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > the problem is that those are not real tests, in the sense that they > dont test anything, like StrutsTestCase, they are extended by users to > create their own tests, so the code has to be under src/java/main > instead of "test". Ok, that's why I opened that case as Jira ticket in Xwork - nobody was complaining :-( Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
If you have questions, drop an email here or ping someone(Wes is the on-call this week) over IM, it is less frustrating than using jira. On Wed, Aug 5, 2009 at 12:42 PM, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> the problem is that those are not real tests, in the sense that they >> dont test anything, like StrutsTestCase, they are extended by users to >> create their own tests, so the code has to be under src/java/main >> instead of "test". > > Ok, that's why I opened that case as Jira ticket in Xwork - nobody was > complaining :-( > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > If you have questions, drop an email here or ping someone(Wes is the > on-call this week) over IM, it is less frustrating than using jira. Ok, I'll remember. What kind of IM do you use? Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
musa...@gmail.com in gtalk On Wed, Aug 5, 2009 at 12:50 PM, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> If you have questions, drop an email here or ping someone(Wes is the >> on-call this week) over IM, it is less frustrating than using jira. > > Ok, I'll remember. What kind of IM do you use? > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
2009/8/5 Musachy Barroso : > musa...@gmail.com in gtalk Ok, thanks, I see you on GTalk but didn't see Wes ;-) Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Sam Huynh is out of the office (08/05 - 08/07)
I will be out of the office starting 08/05/2009 and will not return until 08/10/2009. I will respond to your message when I return. For customers coverage: O&M : Ghosh WP: Cindy Edwards: Hai Kongsberg: Hai Best Regards, Sam Huynh IBM AoD - SAP Basis shu...@us.ibm.com cell - 832-235-5108
2.1.8 release?
What's keeping it from being released? -- Andreas Joseph Krogh Senior Software Developer / CTO +-+ OfficeNet AS| The most difficult thing in the world is to | Rosenholmveien 25 | know how to do a thing and to watch | 1414 Trollåsen | somebody else doing it wrong, without | NORWAY | comment.| | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: 2.1.8 release?
Free time on Rainer's hands, when xwork gets released then 2.1.8 can be released. musachy On Wed, Aug 5, 2009 at 3:35 PM, Andreas Joseph Krogh wrote: > What's keeping it from being released? > > -- > Andreas Joseph Krogh > Senior Software Developer / CTO > +-+ > OfficeNet AS | The most difficult thing in the world is to | > Rosenholmveien 25 | know how to do a thing and to watch | > 1414 Trollåsen | somebody else doing it wrong, without | > NORWAY | comment. | > | | > Tlf: +47 24 15 38 90 | | > Fax: +47 24 15 38 91 | | > Mobile: +47 909 56 963 | | > +-+ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
I am on as w...@wantii.com, but I'm eastern time, so you have to catch me between nine and six est After that I check email but usually don't log in to im. On 8/5/09, Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : >> musa...@gmail.com in gtalk > > Ok, thanks, I see you on GTalk but didn't see Wes ;-) > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
documentation CSS
after the auto export adventures, the documentation in 2.x is pointing to a missing css file: @import url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); these dirs do not not exists under /www/struts.apache.org, are the css files configured for the export somewhere? or we need to create that dir in p.a.o? I can't create dirs anyway, but it is an option. musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
can I get admin rights to cwiki? musachy On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso wrote: > after the auto export adventures, the documentation in 2.x is pointing > to a missing css file: > > > @import > url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); > > > these dirs do not not exists under /www/struts.apache.org, are the css > files configured for the export somewhere? or we need to create that > dir in p.a.o? I can't create dirs anyway, but it is an option. > > musachy > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
On Wed, Aug 5, 2009 at 5:25 PM, Musachy Barroso wrote: > can I get admin rights to cwiki? Done. -- Martin Cooper > > musachy > > On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso wrote: > > after the auto export adventures, the documentation in 2.x is pointing > > to a missing css file: > > > > > > @import > url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); > > > > > > these dirs do not not exists under /www/struts.apache.org, are the css > > files configured for the export somewhere? or we need to create that > > dir in p.a.o? I can't create dirs anyway, but it is an option. > > > > musachy > > -- > > "Hey you! Would you help me to carry the stone?" Pink Floyd > > > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
Re: documentation CSS
thanks On Wed, Aug 5, 2009 at 5:28 PM, Martin Cooper wrote: > On Wed, Aug 5, 2009 at 5:25 PM, Musachy Barroso wrote: > >> can I get admin rights to cwiki? > > > Done. > > -- > Martin Cooper > > > >> >> musachy >> >> On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso wrote: >> > after the auto export adventures, the documentation in 2.x is pointing >> > to a missing css file: >> > >> > >> > @import >> url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); >> > >> > >> > these dirs do not not exists under /www/struts.apache.org, are the css >> > files configured for the export somewhere? or we need to create that >> > dir in p.a.o? I can't create dirs anyway, but it is an option. >> > >> > musachy >> > -- >> > "Hey you! Would you help me to carry the stone?" Pink Floyd >> > >> >> >> >> -- >> "Hey you! Would you help me to carry the stone?" Pink Floyd >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: 2.1.8 release?
Ok, why aren't we bringing xwork into Struts 2 again? Don On Thu, Aug 6, 2009 at 8:44 AM, Musachy Barroso wrote: > Free time on Rainer's hands, when xwork gets released then 2.1.8 can > be released. > > musachy > > On Wed, Aug 5, 2009 at 3:35 PM, Andreas Joseph > Krogh wrote: >> What's keeping it from being released? >> >> -- >> Andreas Joseph Krogh >> Senior Software Developer / CTO >> +-+ >> OfficeNet AS | The most difficult thing in the world is to | >> Rosenholmveien 25 | know how to do a thing and to watch | >> 1414 Trollåsen | somebody else doing it wrong, without | >> NORWAY | comment. | >> | | >> Tlf: +47 24 15 38 90 | | >> Fax: +47 24 15 38 91 | | >> Mobile: +47 909 56 963 | | >> +-+ >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: 2.1.8 release?
On Wednesday 05 August 2009 09:17:03 pm Don Brown wrote: > Ok, why aren't we bringing xwork into Struts 2 again? > > Don > I hate to be a nay-sayer here, but I, for one am using XWork outside of struts and think it has some really serious potential as a command-pattern framework outside of Struts. I just started using it recently and to be honest, I had to jump through some hoops to get it working because it seems like we made some compromises for struts (removing all of the bean definitions from xwork- default.xml). I actually have some plans for xwork as soon as I get my current project released. That being said, I don't think I'd mind if we moved it into apache-space... I think it would benefit from apache's infrastructure. If we made it a top-level project maybe in the asf repo, next to struts1 and struts2 that would be cool because all struts committers would have easy access to it, but it could retain it's identity and I could keep running it in a back-end (read: non-web- app) context. -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [OSS Bamboo] Struts 2 SVN - Main Build (Java 6) build 911 has FAILED (0 tests failed)
On Wednesday 05 August 2009 04:16:45 pm Lukasz Lenart wrote: > 2009/8/5 Musachy Barroso : > > musa...@gmail.com in gtalk > > Ok, thanks, I see you on GTalk but didn't see Wes ;-) > > > Regards Sorry, I forgot to say earlier, I'm on *gtalk* as well as w...@wantii.com (not sure if that part was clear). -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: 2.1.8 release?
> > I hate to be a nay-sayer here, but I, for one am using XWork outside of struts > and think it has some really serious potential as a command-pattern framework > outside of Struts. I just started using it recently and to be honest, I had to > jump through some hoops to get it working because it seems like we made some > compromises for struts (removing all of the bean definitions from xwork- > default.xml). I actually have some plans for xwork as soon as I get my current > project released. > I was going to ask if anyone was using it outside struts, but that doesn't prevent us from making it it's own artifact. > That being said, I don't think I'd mind if we moved it into apache-space... I > think it would benefit from apache's infrastructure. If we made it a top-level > project maybe in the asf repo, next to struts1 and struts2 that would be cool > because all struts committers would have easy access to it, but it could > retain it's identity and I could keep running it in a back-end (read: non-web- > app) context. I don't think this would fix the problem, which is the duplicated effort on the builds. A good compromise would be to keep it under its own artifact under struts, just like core, that way we would need just one release and it could still be used independently. I haven't cared much before, but if it will make our releases easier/smoother, then I am +1 for it. musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [VOTE] Move JSON plugin to trunk
On Wednesday 05 August 2009 12:40:40 pm Musachy Barroso wrote: > I think the JSON plugin is ready to be moved to trunk, here is my +1. > > > musachy I am having trouble getting the build to complete right now, but AFAICT, this should be a mostly harmless move since none of the reference apps are using it, so once the build is working again, we should just add it into showcase and see what happens. That being said, I'd like to get this into core as a built-in result type. I'm sure if we did a poll, we'll find more people using it than say the xsl result. I am pretty sure that this is the eventual plan, I just want to voice my support so that if anyone is against it, we can start arguing^H^H^H^H^H^H^H discussing now :) -W (In case I wasn't clear, I'm not +1'ing yet, need to test still, but should get it shortly) -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
fixed On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso wrote: > after the auto export adventures, the documentation in 2.x is pointing > to a missing css file: > > > @import > url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); > > > these dirs do not not exists under /www/struts.apache.org, are the css > files configured for the export somewhere? or we need to create that > dir in p.a.o? I can't create dirs anyway, but it is an option. > > musachy > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [VOTE] Move JSON plugin to trunk
Although I understand it is quite used, I am not sure why you want it in core, having it as plugin works just as well, and it is out of the way of people that do not use it. musachy On Wed, Aug 5, 2009 at 6:47 PM, Wes Wannemacher wrote: > On Wednesday 05 August 2009 12:40:40 pm Musachy Barroso wrote: >> I think the JSON plugin is ready to be moved to trunk, here is my +1. >> >> >> musachy > > I am having trouble getting the build to complete right now, but AFAICT, this > should be a mostly harmless move since none of the reference apps are using > it, so once the build is working again, we should just add it into showcase > and see what happens. > > That being said, I'd like to get this into core as a built-in result type. I'm > sure if we did a poll, we'll find more people using it than say the xsl > result. > I am pretty sure that this is the eventual plan, I just want to voice my > support so that if anyone is against it, we can start arguing^H^H^H^H^H^H^H > discussing now :) > > -W > > (In case I wasn't clear, I'm not +1'ing yet, need to test still, but should > get it shortly) > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: 2.1.8 release?
On Wednesday 05 August 2009 09:44:45 pm Musachy Barroso wrote: [snip] > > I was going to ask if anyone was using it outside struts, but that > doesn't prevent us from making it it's own artifact. > [snip] > > I don't think this would fix the problem, which is the duplicated > effort on the builds. A good compromise would be to keep it under its > own artifact under struts, just like core, that way we would need just > one release and it could still be used independently. I haven't cared > much before, but if it will make our releases easier/smoother, then I > am +1 for it. > being its own artifact makes more sense, it would make releasing the two much easier, on second thought I agree with this. My only real concern is that I can get to it w/o struts. The context I am working with now doesn't fit well with struts, and adding struts means I would have to do even more work getting a base configuration so that xwork can run actions. One example that sticks out in my mind is that when I run actions, each action execution gets its own thread and one of the results I built for this project launches from 1 to infinite more actions. Obviously it wouldn't make sense to chain to multiple actions in a web-app and since a view is rendered in struts, having actions run in a separate thread wouldn't work well in a web-app. -W -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [VOTE] Move JSON plugin to trunk
On Wednesday 05 August 2009 09:54:41 pm Musachy Barroso wrote: > Although I understand it is quite used, I am not sure why you want it > in core, having it as plugin works just as well, and it is out of the > way of people that do not use it. > The main reason is that if it is part of core, building an ajax plugin that doesn't depend on another plugin will be much easier. We have avoided, in the past, building plugins that depend on other plugins. I think it'd be easier to go forward with the jquery plugin we've talked about if "json" is a built-in result type. -W -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
anyone knows what happened to the title of the "code" sections? none of them are showing. musachy On Wed, Aug 5, 2009 at 6:47 PM, Musachy Barroso wrote: > fixed > > On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso wrote: >> after the auto export adventures, the documentation in 2.x is pointing >> to a missing css file: >> >> >> @import >> url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); >> >> >> these dirs do not not exists under /www/struts.apache.org, are the css >> files configured for the export somewhere? or we need to create that >> dir in p.a.o? I can't create dirs anyway, but it is an option. >> >> musachy >> -- >> "Hey you! Would you help me to carry the stone?" Pink Floyd >> > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
On Wed, Aug 5, 2009 at 8:04 PM, Musachy Barroso wrote: > anyone knows what happened to the title of the "code" sections? none > of them are showing. There are two macros enabled - "Code Macro" and "New Code Macro" - that both claim to provide the 'code' macro. No doubt one does what you want and the other does not, but I have no idea how to determine which one is active or how to make the other one active. -- Martin Cooper > musachy > > On Wed, Aug 5, 2009 at 6:47 PM, Musachy Barroso wrote: > > fixed > > > > On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso > wrote: > >> after the auto export adventures, the documentation in 2.x is pointing > >> to a missing css file: > >> > >> > >> @import > url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); > >> > >> > >> these dirs do not not exists under /www/struts.apache.org, are the css > >> files configured for the export somewhere? or we need to create that > >> dir in p.a.o? I can't create dirs anyway, but it is an option. > >> > >> musachy > >> -- > >> "Hey you! Would you help me to carry the stone?" Pink Floyd > >> > > > > > > > > -- > > "Hey you! Would you help me to carry the stone?" Pink Floyd > > > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
Re: documentation CSS
hum..I will try to figure that one later. Another question..where are the snippet variables defined? there seem to be a bunch of broken snippets. On Wed, Aug 5, 2009 at 8:09 PM, Martin Cooper wrote: > On Wed, Aug 5, 2009 at 8:04 PM, Musachy Barroso wrote: > >> anyone knows what happened to the title of the "code" sections? none >> of them are showing. > > > There are two macros enabled - "Code Macro" and "New Code Macro" - that both > claim to provide the 'code' macro. No doubt one does what you want and the > other does not, but I have no idea how to determine which one is active or > how to make the other one active. > > -- > Martin Cooper > > > >> musachy >> >> On Wed, Aug 5, 2009 at 6:47 PM, Musachy Barroso wrote: >> > fixed >> > >> > On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso >> wrote: >> >> after the auto export adventures, the documentation in 2.x is pointing >> >> to a missing css file: >> >> >> >> >> >> @import >> url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); >> >> >> >> >> >> these dirs do not not exists under /www/struts.apache.org, are the css >> >> files configured for the export somewhere? or we need to create that >> >> dir in p.a.o? I can't create dirs anyway, but it is an option. >> >> >> >> musachy >> >> -- >> >> "Hey you! Would you help me to carry the stone?" Pink Floyd >> >> >> > >> > >> > >> > -- >> > "Hey you! Would you help me to carry the stone?" Pink Floyd >> > >> >> >> >> -- >> "Hey you! Would you help me to carry the stone?" Pink Floyd >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: documentation CSS
found it On Wed, Aug 5, 2009 at 8:35 PM, Musachy Barroso wrote: > hum..I will try to figure that one later. Another question..where are > the snippet variables defined? there seem to be a bunch of broken > snippets. > > On Wed, Aug 5, 2009 at 8:09 PM, Martin Cooper wrote: >> On Wed, Aug 5, 2009 at 8:04 PM, Musachy Barroso wrote: >> >>> anyone knows what happened to the title of the "code" sections? none >>> of them are showing. >> >> >> There are two macros enabled - "Code Macro" and "New Code Macro" - that both >> claim to provide the 'code' macro. No doubt one does what you want and the >> other does not, but I have no idea how to determine which one is active or >> how to make the other one active. >> >> -- >> Martin Cooper >> >> >> >>> musachy >>> >>> On Wed, Aug 5, 2009 at 6:47 PM, Musachy Barroso wrote: >>> > fixed >>> > >>> > On Wed, Aug 5, 2009 at 5:08 PM, Musachy Barroso >>> wrote: >>> >> after the auto export adventures, the documentation in 2.x is pointing >>> >> to a missing css file: >>> >> >>> >> >>> >> @import >>> url(/confluence/download/resources/confluence.ext.code:code/shStyles.css); >>> >> >>> >> >>> >> these dirs do not not exists under /www/struts.apache.org, are the css >>> >> files configured for the export somewhere? or we need to create that >>> >> dir in p.a.o? I can't create dirs anyway, but it is an option. >>> >> >>> >> musachy >>> >> -- >>> >> "Hey you! Would you help me to carry the stone?" Pink Floyd >>> >> >>> > >>> > >>> > >>> > -- >>> > "Hey you! Would you help me to carry the stone?" Pink Floyd >>> > >>> >>> >>> >>> -- >>> "Hey you! Would you help me to carry the stone?" Pink Floyd >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>> For additional commands, e-mail: dev-h...@struts.apache.org >>> >>> >> > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Let's kill xwork (was Re: 2.1.8 release?)
XWork was left at OpenSymphony, because at the time, there were a number of WebWork developers still around and we wanted to continue to work together. Today, WebWork activity seems all but dead, leaving us with no advantages having the code hosted over there. Furthermore, having critical code in different packages is really confusing for developers of the framework and its apps with no apparent benefit. Ideally, I'd like to bring xwork trunk into the core jar and be done with the theoretically useful yet practically painful split. However, that would break Struts 2 apps without tedious backwards-compatibility code, but getting the code bases integrated is the first step. Maybe at first, we keep two artifacts, but I think we should think about a serious migration to just one. XWork itself will always be around, but trying to put a framework at our core that is meant for ambiguous theoretical users brings unnecessary complexity and problems to all parties. Can I start planning the funeral? :) Don On Thu, Aug 6, 2009 at 11:55 AM, Wes Wannemacher wrote: > On Wednesday 05 August 2009 09:44:45 pm Musachy Barroso wrote: > [snip] >> >> I was going to ask if anyone was using it outside struts, but that >> doesn't prevent us from making it it's own artifact. >> > [snip] >> >> I don't think this would fix the problem, which is the duplicated >> effort on the builds. A good compromise would be to keep it under its >> own artifact under struts, just like core, that way we would need just >> one release and it could still be used independently. I haven't cared >> much before, but if it will make our releases easier/smoother, then I >> am +1 for it. >> > > being its own artifact makes more sense, it would make releasing the two much > easier, on second thought I agree with this. My only real concern is that I > can get to it w/o struts. The context I am working with now doesn't fit well > with struts, and adding struts means I would have to do even more work getting > a base configuration so that xwork can run actions. One example that sticks > out > in my mind is that when I run actions, each action execution gets its own > thread and one of the results I built for this project launches from 1 to > infinite more actions. Obviously it wouldn't make sense to chain to multiple > actions in a web-app and since a view is rendered in struts, having actions > run in a separate thread wouldn't work well in a web-app. > > -W > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Let's kill xwork (was Re: 2.1.8 release?)
Sounds reasonable to me. Couple of question to fuel discussion: What would be the target version? Do we need to go through incubation, etc? (I have never known much about the ASF legal process) musachy On Wed, Aug 5, 2009 at 10:12 PM, Don Brown wrote: > XWork was left at OpenSymphony, because at the time, there were a > number of WebWork developers still around and we wanted to continue to > work together. Today, WebWork activity seems all but dead, leaving us > with no advantages having the code hosted over there. Furthermore, > having critical code in different packages is really confusing for > developers of the framework and its apps with no apparent benefit. > > Ideally, I'd like to bring xwork trunk into the core jar and be done > with the theoretically useful yet practically painful split. However, > that would break Struts 2 apps without tedious backwards-compatibility > code, but getting the code bases integrated is the first step. Maybe > at first, we keep two artifacts, but I think we should think about a > serious migration to just one. XWork itself will always be around, > but trying to put a framework at our core that is meant for ambiguous > theoretical users brings unnecessary complexity and problems to all > parties. > > Can I start planning the funeral? :) > > Don > > On Thu, Aug 6, 2009 at 11:55 AM, Wes Wannemacher wrote: >> On Wednesday 05 August 2009 09:44:45 pm Musachy Barroso wrote: >> [snip] >>> >>> I was going to ask if anyone was using it outside struts, but that >>> doesn't prevent us from making it it's own artifact. >>> >> [snip] >>> >>> I don't think this would fix the problem, which is the duplicated >>> effort on the builds. A good compromise would be to keep it under its >>> own artifact under struts, just like core, that way we would need just >>> one release and it could still be used independently. I haven't cared >>> much before, but if it will make our releases easier/smoother, then I >>> am +1 for it. >>> >> >> being its own artifact makes more sense, it would make releasing the two much >> easier, on second thought I agree with this. My only real concern is that I >> can get to it w/o struts. The context I am working with now doesn't fit well >> with struts, and adding struts means I would have to do even more work >> getting >> a base configuration so that xwork can run actions. One example that sticks >> out >> in my mind is that when I run actions, each action execution gets its own >> thread and one of the results I built for this project launches from 1 to >> infinite more actions. Obviously it wouldn't make sense to chain to multiple >> actions in a web-app and since a view is rendered in struts, having actions >> run in a separate thread wouldn't work well in a web-app. >> >> -W >> >> -- >> Wes Wannemacher >> >> Head Engineer, WanTii, Inc. >> Need Training? Struts, Spring, Maven, Tomcat... >> Ask me for a quote! >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Let's kill xwork (was Re: 2.1.8 release?)
On Thu, Aug 6, 2009 at 4:22 PM, Musachy Barroso wrote: > Sounds reasonable to me. Couple of question to fuel discussion: > > What would be the target version? > Do we need to go through incubation, etc? (I have never known much > about the ASF legal process) The code would definitely have to go through an IP clearance step, which I'd be happy to help with. The target version will just be the Struts version - no need for a separate release cycle. Don > > musachy > > On Wed, Aug 5, 2009 at 10:12 PM, Don Brown wrote: >> XWork was left at OpenSymphony, because at the time, there were a >> number of WebWork developers still around and we wanted to continue to >> work together. Today, WebWork activity seems all but dead, leaving us >> with no advantages having the code hosted over there. Furthermore, >> having critical code in different packages is really confusing for >> developers of the framework and its apps with no apparent benefit. >> >> Ideally, I'd like to bring xwork trunk into the core jar and be done >> with the theoretically useful yet practically painful split. However, >> that would break Struts 2 apps without tedious backwards-compatibility >> code, but getting the code bases integrated is the first step. Maybe >> at first, we keep two artifacts, but I think we should think about a >> serious migration to just one. XWork itself will always be around, >> but trying to put a framework at our core that is meant for ambiguous >> theoretical users brings unnecessary complexity and problems to all >> parties. >> >> Can I start planning the funeral? :) >> >> Don >> >> On Thu, Aug 6, 2009 at 11:55 AM, Wes Wannemacher wrote: >>> On Wednesday 05 August 2009 09:44:45 pm Musachy Barroso wrote: >>> [snip] I was going to ask if anyone was using it outside struts, but that doesn't prevent us from making it it's own artifact. >>> [snip] I don't think this would fix the problem, which is the duplicated effort on the builds. A good compromise would be to keep it under its own artifact under struts, just like core, that way we would need just one release and it could still be used independently. I haven't cared much before, but if it will make our releases easier/smoother, then I am +1 for it. >>> >>> being its own artifact makes more sense, it would make releasing the two >>> much >>> easier, on second thought I agree with this. My only real concern is that I >>> can get to it w/o struts. The context I am working with now doesn't fit well >>> with struts, and adding struts means I would have to do even more work >>> getting >>> a base configuration so that xwork can run actions. One example that sticks >>> out >>> in my mind is that when I run actions, each action execution gets its own >>> thread and one of the results I built for this project launches from 1 to >>> infinite more actions. Obviously it wouldn't make sense to chain to multiple >>> actions in a web-app and since a view is rendered in struts, having actions >>> run in a separate thread wouldn't work well in a web-app. >>> >>> -W >>> >>> -- >>> Wes Wannemacher >>> >>> Head Engineer, WanTii, Inc. >>> Need Training? Struts, Spring, Maven, Tomcat... >>> Ask me for a quote! >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>> For additional commands, e-mail: dev-h...@struts.apache.org >>> >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Struts2 on FishEye / Cruicible
2009/7/31 Wes Wannemacher : > I don't know how much we'll use it, but IMO, the sandbox is a good > candidate for code-reviewy kind of stuff. Especially if we pick back > up on the JQuery stuff we were discussing previously. Done, sandbox also added, it's here: http://fisheye6.atlassian.com/browse/strutssandbox Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
