On 3/21/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
> I was under the impression that I will be deploying my locally built
> artifacts.
Yes, it's just not clear to me whether deploy creates the artifacts.
It seems to be building and testing som
Yep, it's all done except for the voting.
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
So, is that it? What else can I do? Did all the files make it?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 8:48 PM, Ted Husted wrote:
> For some reason, t
So, is that it? What else can I do? Did all the files make it?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 8:48 PM, Ted Husted wrote:
For some reason, the rest of the folders didn't move over with
struts2-assembly, so I moved it back and tried again,
For some reason, the rest of the folders didn't move over with
struts2-assembly, so I moved it back and tried again, and it seems
fine now.
Thanks so much, James!
-Ted.
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
I'm trying to move forward on this and not sure what the next step
is.
I'm trying to move forward on this and not sure what the next step
is. I'm pretty sure that step #6 did not do what it was supposed to
do. When I compare what's under 2.0.6...
/home/jmitchell/apache_home/apache-tomcat-5.5.20/
I only see struts2-assemply/ and not all the other modules. May
Where is this failing for you? Step 4?
mvn clean install site -P all,alljars,pre-assembly
works fine for me when using the 2.0.7 tag.
James Mitchell wrote:
There's no api/ under STRUTS_2_0_X branch, so the assembly is failing.
I made a quick fix to remove those references () and trying aga
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
I was under the impression that I will be deploying my locally built
artifacts.
Yes, it's just not clear to me whether deploy creates the artifacts.
It seems to be building and testing something.
But, it probably wouldn't work clean anyway.
I was under the impression that I will be deploying my locally built
artifacts.
The trunk has api/, but the branch does not, so assembly would work
for trunk. I'm not sure why it's missing api/, you'd have to ask the
guy who did the branch ;)
--
James Mitchell
The Ruby Roundup
http://
There's no api/ under STRUTS_2_0_X branch, so the assembly is
failing. I made a quick fix to remove those references ()
and trying again.
I suppose I should commit this, unless we need the api as part of the
distribution. If so, which Jira should I reference?
--
James Mitchell
The Ruby
I don't know if you needed to do #4 or not, it seems to do some
building as it goes.
For an issue ticket, you could use WW-1834. We would probably need to
change the HEAD too.
-T.
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
There's no api/ under STRUTS_2_0_X branch, so the assembly i
Ok, I'll do it.
So, going from the below wiki page, there's a couple of steps that
I'll have to do prior to #6. I know I need to at least start at #4.
So I'll start there.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 12:43 PM, Ted Husted wrote:
Nope.
On 3/21/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Have you found a volunteer yet?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 8:22 AM, Ted Husted wrote:
> We need another volunteer to perform step #6 of the release gauntlet,
> which stages th
Have you found a volunteer yet?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 8:22 AM, Ted Husted wrote:
We need another volunteer to perform step #6 of the release gauntlet,
which stages the JARs as Maven artifacts
* http://struts.apache.org/2.x/docs/cr
We need another volunteer to perform step #6 of the release gauntlet,
which stages the JARs as Maven artifacts
* http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
My CygWin SSH setup is still muddled. I tried running it using
password authentication three times, but did
On 3/19/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Sure. I'll grab that as soon as I see it.
OK, 2.0.7 is tagged. Since we still don't have a full suite of
Selenium tests, we should do a thorough clickthru on the Showcase and
MailReader, to see if the patches upset anything obvious :)
If y
On Mar 19, 2007, at 10:32 PM, Ted Husted wrote:
I'm going to apply the rest of the patches now and then tag it. If
you'd like to check out the tag and help test the applications, that
would be great.
Sure. I'll grab that as soon as I see it.
If the porlet and Dojo plugins are ready, I'd al
I'm going to apply the rest of the patches now and then tag it. If
you'd like to check out the tag and help test the applications, that
would be great.
If the porlet and Dojo plugins are ready, I'd also like to start
thinking about a 2.1.0 build.
-T.
On 3/19/07, James Mitchell <[EMAIL PROTECTED
I've got a few hours tonight and tomorrow if you need help with
anything. If not, I'll look through Jira for something to do.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 19, 2007, at 6:54 PM, Ted Husted wrote:
OK, I have to step out for a couple of hours, but th
OK, I have to step out for a couple of hours, but then I'll finish up
the patches slated for 2.0.7, and Get-R-Tagged !.
-T.
On 3/19/07, Ted Husted <[EMAIL PROTECTED]> wrote:
OK, I've been through the unassigned issues, and I'm starting on a few
simple but worthy patches that came up over the we
OK, I've been through the unassigned issues, and I'm starting on a few
simple but worthy patches that came up over the week. Then, later
tonight, I'll at least tag the build, though I doubt that I'll be able
to finish the testing and uploading. But, I may be able get to that
late tomorrow.
-Ted.
These too would be helpful.
* https://issues.apache.org/struts/browse/WW-1560
* https://issues.apache.org/struts/browse/WW-1539
Or, as to the MailReader, a whole 'nother way to go would be to work
it up from scratch as a zero-config, maybe with a HSQLDB backend using
iBATIS or Cayenne. (since Hi
On 3/16/07, Don Brown <[EMAIL PROTECTED]> wrote:
In my opinion, you should avoid using custom interceptor stacks
whenever possible. That way, you can simplify your configuration and
make your application more consistent. If the mailreader always used
the default stack, the zero configuration co
In my opinion, you should avoid using custom interceptor stacks
whenever possible. That way, you can simplify your configuration and
make your application more consistent. If the mailreader always used
the default stack, the zero configuration conversion would be trivial.
Of course, another equ
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> If anyone is looking for something to do, a
> Zero-Configuration MailReader would make a world of
> difference right now.
I know I'm not a committer, but I have one more free
weekend before a new gig starts and I was all set to
volunteer...
But then
On 3/12/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Otherwise, I can put it down for the
17th, and we can call it a St Paddy's day celebration :)
I was looking at the wrong calendar when I said 17th. The time I have
aside is on Monday the 19th, so if there's anything people would like
to do over
I had some time to look into splitting the code out of core and
there's a lot more going on than I first thought. Right now I'm
still getting back into s2, so either someone else run with it or it
will have to wait a few weeks for me to get my head around it all.
Thanks
--
James Mitchell
I don't understand. Why would the refactoring have to happen
*before* any code was moved into a plugin?
Before vs after? I don't get that part.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 14, 2007, at 11:49 AM, Nils-Helge Garli wrote:
I was referring to some ea
I was referring to some earlier mail threads, "[s2] Pluggable URL
building proposal
(http://www.mail-archive.com/dev@struts.apache.org/msg26942.html)" and
"[S2] Experimental Features"
(http://www.mail-archive.com/dev@struts.apache.org/msg26342.html)
where some issues were discussed that need to be
What do you mean? I haven't changed any code yet, and the portlet
sample app runs fine. What code should be refactored and why?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 14, 2007, at 3:02 AM, Nils-Helge Garli wrote:
As long as the URL building has been refacto
To clarify, I can setup accounts on the zone and you can have root
access or whateverI hope you weren't thinking that I would do it ;)
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 14, 2007, at 8:59 AM, James Mitchell wrote:
I can give you whatever you need for t
I can give you whatever you need for the zone. Please make sure that
whatever you do is allowed (infra@).
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 13, 2007, at 11:49 PM, Patrick Lightbody wrote:
Probably wouldn't be a bad idea to get a standalone instance of
As long as the URL building has been refactored, or will be refactored
at the same time, as discussed earlier, there shouldn't be anything
stopping from extracting it as a plugin.
Nils-H
On 3/14/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Ok, I took the portlet app and added some pluto maven
Ok, I took the portlet app and added some pluto maven magic and
deployed it to pluto 1.1.0...works fine.
Now, I'd like to begin pulling the portlet code out into a plugin.
It seems pretty straight forward, however, since I've not messed with
the plugin architecture very much, are there any
Probably wouldn't be a bad idea to get a standalone instance of Forums 5.5
(coming out soon) set up for Struts. Email me if you want to get that going, or
if you can provide me instructions for setting it up (zone login info, etc).
-
Sounds cool Ted, marked as "fix for fure".
Cheers.
Ted Husted <[EMAIL PROTECTED]> wrote: We could just change the "Fix For" to
future, in case someone wants to
try later.
Ted.
On 3/12/07, tm jee wrote:
> Hi guys,
>
> > OK, we've now cleared out all the 2.0.7 patches from last week, save
> >
We could just change the "Fix For" to future, in case someone wants to
try later.
Ted.
On 3/12/07, tm jee <[EMAIL PROTECTED]> wrote:
Hi guys,
> OK, we've now cleared out all the 2.0.7 patches from last week, save
> one that might still be sitting on Toby's hard drive :)
The jira issue for th
forgotten to mention that the code is already in WebWork svn together with
documentation and a showcase example. Details could be found in the jira issue
itself.
cheers
tm jee <[EMAIL PROTECTED]> wrote: Hi guys,
> OK, we've now cleared out all the 2.0.7 patches from last week, save
> one tha
Hi guys,
> OK, we've now cleared out all the 2.0.7 patches from last week, save
> one that might still be sitting on Toby's hard drive :)
The jira issue for this is at [1]. Would it be possible to not migrate this to
Struts2, cause I am not really sure how to make it a plugin (part of the code
OK, we've now cleared out all the 2.0.7 patches from last week, save
one that might still be sitting on Toby's hard drive :)
Unfortunately, I won't be able to run through the release gauntlet
tonight, and the rest of the week is booked. If someone else is up for
rolling 2.0.7, please, feel free.
On 3/10/07, James Mitchell <[EMAIL PROTECTED]> wrote:
That said, I would look at the portlet support, but I'm probably the
least qualified to work on that. If you still have no one to
volunteer, I can look at it next week.
At this point, the next step is to migrate it to a plugin, as Musachy
h
On 3/10/07, James Mitchell <[EMAIL PROTECTED]> wrote:
After nearly a 1 year hiatus to work on a JSF gig, my client has
decided not to continue down the JSF route, and on a personal note, I
couldn't be happier. I really hope JSF 1.2 does for JSF what EJB3/
JPA did for EJB2. I have not been havin
I hope to be able to assist with the portlet plugin as well.
On 3/10/07, James Mitchell <[EMAIL PROTECTED]> wrote:
After nearly a 1 year hiatus to work on a JSF gig, my client has
decided not to continue down the JSF route, and on a personal note, I
couldn't be happier. I really hope JSF 1.2 do
After nearly a 1 year hiatus to work on a JSF gig, my client has
decided not to continue down the JSF route, and on a personal note, I
couldn't be happier. I really hope JSF 1.2 does for JSF what EJB3/
JPA did for EJB2. I have not been having fun.
On a positive note, my client has decided
I haven't done a clean checkout of the trunk, but the trunk build is
failing for me because of test failures. If I build the trunk without
the tests, it succeeds.
But, I do see that the 2_0_x branch is building just fine for me,
which means I can still try to tag and roll Struts 2.0.7 on Monday.
If you'd like to cast a non-binding vote for Struts 2.0.6 as to beta
quality, please feel free to do so. The quality votes never really
close, and if a serious problem were found, we could downgrade the
release. We make the best judgment we can based on the information we
have available at the tim
Hi Guys, we recently migrated our projects from WW2 to Struts2 (2.0.6) and
noticed some minor glitches and a fairly critical bug currently in XW 2.0.1
which affects struts 2:
http://forums.opensymphony.com/thread.jspa?threadID=67970&tstart=0
People starts wondering how Struts 2.0.6 could be tagg
I was in the midst of some issue surgery, when issues.apache.org went
down (at least from here) a moment ago. So, I thought I should whip
off a quick email about what I was doing.
So far, we've cleared 25+ issues for 2.0.7. I went through the
remaining issues, resolved a few stragglers, and pushe
There's a few parts of GoogleCode that are still quirky. I'm
disappointed that the Subversion alerts do not include the DIFFs.
We've had to resort to posting our own daily DIFFs. The immutable
issue descriptions is also awkward. But, the other sites also have
their own quirks too. It does seem l
On 2/25/07, Tom Schneider <[EMAIL PROTECTED]> wrote:
I've been using the plugin registry for all my
documentation since I like Confluence better than the google wiki. :) I
hope no one minds.
I'd say that no one will mind. :)
There's a few parts of GoogleCode that are still quirky. I'm
disapp
Core Plugins
This is more of a 2.1.x status item, but looking forward, do we want
to bundle so many plugins with the core, or do we want to try and cut
some of these loose somehow? Of course, there is also something to be
said for "letting sleeping dogs lie".
I think we should cut some of the
Tag Date
On the release notes, I've proposed a tag date of Sunday, 4 March
2007, if that works for everyone.
Issues / Roadmap
Traditionally, we have included new features in milestones so long as
changes were backwardly compatible with the immediately previous GA
API. We were just careful to k
51 matches
Mail list logo
