On 6/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Old site plugin? Try -U on the command line to make it update, or
rm -rf $M2_REPO/org/apache/maven/plugins/maven-site-plugin
so it will download again.
The -U switch worked. Hmm,
Hi all,
I'm running with struts 1.1 and I tried to migrate to 1.2.9 this
morning. My biggest problem is that I needed to change the code base of
my 1.1 to put new feature I needeed. One of them is that I introduced
new scope like: window scope So I have
ApplicationScope
SessionScope
Toby, it looks like the revision history is getting lost for the files
being moved to 'resources' From the commit messages, and svn logs, it
looks like they're being deleted and re-added as new files. Is that
what you're doing? If so, the 'svn mv' command (or 'svn cp' and 'svn
rm' ) will
Actually they are being deleted and re-added.
What should be done now? Should I revert them back and move them.
Sorry about the lost of history, this is the first time I learn about svn cp.
:-) Should have read the svn manual early on.
regards
- Original Message
From: Wendy Smoak
I think i could revert them back and them move them over as Wendy suggested.
This could preserved the history. I'll get this done asap.
- Original Message
From: tm jee [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org
Sent: Sunday, 11 June, 2006 10:56:25 PM
Subject:
On 6/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
Several notes and a mystery below.
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
You can also stage the entire site locally with:
'mvn site:stage'
It defaults to
On 6/11/06, tm jee [EMAIL PROTECTED] wrote:
I think i could revert them back and them move them over as Wendy suggested.
This could preserved the history. I'll get this done asap.
Unless someone else speaks up, I think it's probably okay to leave
these. IIRC we didn't bring over history
On Jun 11, 2006, at 2:14 AM, Wendy Smoak wrote:
On 6/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 6/10/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Old site plugin? Try -U on the command line to make it update, or
rm -rf $M2_REPO/org/apache/maven/plugins/maven-site-plugin
so it
On 6/11/06, James Mitchell [EMAIL PROTECTED] wrote:
I thought you were still building nightlies from the trunk, but yes,
the assembly is next. We can't do much about the aggregation anyway
(unless James wants to go work on Maven plugins... ;) )
Already looking at it, albeit with what
I was looking into how to provide better aggregation. It's been a
while since I looked at that code, so please don't wait for me to
provide a fix in the short term. Between the day job and the kids
(since school is out), I hardly have time to just keep up with
mailing list traffic.
Go
On 6/11/06, James Mitchell [EMAIL PROTECTED] wrote:
I guess what I'm looking for is something like this:
http://wiki.apache.org/struts/Shale/BuildingWithMaven2
With something like the above, all the great hints and tricks you
guys keep throwing around in the threads won't get lost.
Not sure
The snapshots of Struts Action 1.3.5 were updated on Friday. See the
release plan for more information and a link to the distribution
snapshot:
* http://wiki.apache.org/struts/StrutsActionRelease135
This includes the fix for STR-2855, adding the equivalent of
With XWork now supporting wildcards in xwork.xml, I think it is time to
remove the explicit support for the fooAction!barMethod.action syntax.
From a reading of our tickets, the legacy support for that syntax is
affecting the framework in strange ways, and now that we have wildcards,
they can
Yes, as to Action1, the vast majority of the style errors are a fair
cop and reflect things we shouldn't be doing.
Of course, as far as Action 1 is concerned, it's a fair question of
whether the checkstyle report adds any value. No one appears
interested in fixing the errors, and so there are
I finally understand wildcards! Can you give an example of using more
than one wildcard in an action name?
Bob
On 6/11/06, Don Brown [EMAIL PROTECTED] wrote:
With XWork now supporting wildcards in xwork.xml, I think it is time to
remove the explicit support for the fooAction!barMethod.action
Sure... Building on the last example...
action name=*!*.* class=foo.bar.{1}Action method={2}
param name=id{3}/param
...
result name=success/{1}.jsp/result
/action
Eventually, I'd like to get to the point where we define a couple of
generic patterns, and make xwork.xml optional. Then, you
Yippie, we got the history back for all action2 webapp resources relocation.
- Original Message
From: Wendy Smoak [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org; tm jee [EMAIL PROTECTED]
Sent: Sunday, 11 June, 2006 11:19:16 PM
Subject: Re: svn commit: r413422 -
17 matches
Mail list logo
