Re: [VOTE] Struts 2.1.3 Quality

+1 GA On Fri, Dec 26, 2008 at 11:47 AM, Musachy Barroso wrote: > The Struts 2.1.3 test build is now available. > > Release notes: > * [http://struts.apache.org/2.x/docs/version-notes-213.html] > > Distribution: > * [http://people.apache.org/builds/struts/2.1.3/] > > Maven 2 staging repository: >

Re: [VOTE] Struts 2.1.3 Quality

I d/l and tested the apps here - http://code.google.com/p/struts2inpractice/ I've been working on a book (as some of you might know) and I have been working off of trunk, so I updated my local poms and ran / tested locally and they all worked. Of course, they don't use all of Struts2 functionali

Re: deleting pages in the wiki

thanks musachy On Fri, Dec 26, 2008 at 3:20 PM, Martin Cooper wrote: > On Fri, Dec 26, 2008 at 12:08 PM, Musachy Barroso wrote: > >> Any of you have rights to delete pages from the wiki? I am trying to >> delete >> http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Struts+2.1.

Re: deleting pages in the wiki

On Fri, Dec 26, 2008 at 12:08 PM, Musachy Barroso wrote: > Any of you have rights to delete pages from the wiki? I am trying to > delete > http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Struts+2.1.x+Distribution+(New)

deleting pages in the wiki

Any of you have rights to delete pages from the wiki? I am trying to delete http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Struts+2.1.x+Distribution+(New), and I get: You do not have permission to view this page. You have to be a member of all the following groups to access

Re: [VOTE] Struts 2.1.3 Quality

I've now his an exception in the ssl plugin which comes from Google code. I'm going to have more time to debug this a bit more tomorrow, but thanks for the pointers. Al. Musachy Barroso wrote: add this to your struts.xml: does it work after that? musachy On Fri, Dec 26, 2008 at 12:51

Re: [VOTE] Struts 2.1.3 Quality

add this to your struts.xml: does it work after that? musachy On Fri, Dec 26, 2008 at 12:51 PM, Musachy Barroso wrote: > As Codebehind was deprecated REST should build on top of Convention, > you might want to start a new thread for this (maybe we broke > something in REST?). > > musachy >

Re: [VOTE] Struts 2.1.3 Quality

As Codebehind was deprecated REST should build on top of Convention, you might want to start a new thread for this (maybe we broke something in REST?). musachy On Fri, Dec 26, 2008 at 12:46 PM, Al Sutton wrote: > I've just dropped the 2.1.3 jars into an app which was working with 2.1.2 > and the

Re: [VOTE] Struts 2.1.3 Quality

I've just dropped the 2.1.3 jars into an app which was working with 2.1.2 and the rest URLs appear to no longer work. Previously / fired off Controller.index() in my actions package. Now I just get; "T here is no Action mapped for namespace / and action name . - [unknown location]" I've tr

2.1.3 Release

Just done a quick check of the libs and noticed that 1.3.10 contains some more recent libs that then 2.1.3 release. Namely; commons-beatutils (1.8.0 in s1.3.10, .1.7.0 in s2.1.3) commons-chain(1.2 in S1, 1.1 in S2) It might be worth syncing these two for the next release :). Al. -- == Fun

[VOTE] Struts 2.1.3 Quality

The Struts 2.1.3 test build is now available. Release notes: * [http://struts.apache.org/2.x/docs/version-notes-213.html] Distribution: * [http://people.apache.org/builds/struts/2.1.3/] Maven 2 staging repository: * [http://people.apache.org/builds/struts/2.1.3/m2-staging-repository/] Once you

Re: [OT] Archetypes: Maven v. classpath

On Fri, Dec 26, 2008 at 8:18 AM, Dave Newton wrote: > The resources, at least; for example I'm working on struts2-blank-archetype. > The Java code is moved, the resources aren't, so the tests fail because the > package.properties isn't in the correct location. That (the ability to 'package' no

Re: [OT] Archetypes: Maven v. classpath

> Can you be more specific about what's not going into the right place? The resources, at least; for example I'm working on struts2-blank-archetype. The Java code is moved, the resources aren't, so the tests fail because the package.properties isn't in the correct location. In the Java code the

Re: [OT] Archetypes: Maven v. classpath

On Fri, Dec 26, 2008 at 6:17 AM, Dave Newton wrote: > I think this is a documented archetype issue, but it makes archetypes a > little less useful: if I'm creating a project from an archetype and give it a > groupId (package) how come it only puts *some* of the stuff in the > appropriate classp

[OT] Archetypes: Maven v. classpath

I think this is a documented archetype issue, but it makes archetypes a little less useful: if I'm creating a project from an archetype and give it a groupId (package) how come it only puts *some* of the stuff in the appropriate classpath? And do I really not have access to the groupId etc. in