The problem turned out to be that the struts-staging stanza in my
settings.xml still had the replacement variables (yourid) set,
instead of my own.
So, the Maven artifacts are in the staging directory, but should we be
moving them over prior to a vote of the PMC? At this point, it's just
a
On 1/4/07, Ted Husted [EMAIL PROTECTED] wrote:
So, the Maven artifacts are in the staging directory, but should we be
moving them over prior to a vote of the PMC? At this point, it's just
a tagged test build; 2.0.2 is not a release.
(Ted, you own the files under m2-staging-repository, can you
I logged WW-1596 with a patch for DatePicker and TimePicker, it is a
trivial patch, at least they work now :)
musachy
Ted Husted wrote:
There are still several broken examples and tags., which I listed on
the Showcase index page, in the hope that they still might be fixed
for Struts 2.0.3
On 1/3/07, mraible [EMAIL PROTECTED] wrote:
Any chance of getting this deployed to Apache's Snapshot Maven repo?
http://people.apache.org/maven-snapshot-repository/org/apache/struts/struts2-core/
The automatic deploy tool didn't work for me, there's a problem with
my key, and I won't have a
On 1/3/07, Ted Husted [EMAIL PROTECTED] wrote:
On 1/3/07, mraible [EMAIL PROTECTED] wrote:
Any chance of getting this deployed to Apache's Snapshot Maven repo?
http://people.apache.org/maven-snapshot-repository/org/apache/struts/struts2-core/
We no longer stage tagged and numbered builds in
On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote:
OK, I'll get ready to roll another release then.
I've updated the release notes with the latest changes, and I'm
preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1.
-Ted.
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote:
OK, I'll get ready to roll another release then.
I've updated the release notes with the latest changes, and I'm
preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1.
Just FYI, the
I looked again at a clean checkout and found the reference. The
assembly POM in my usual working copy was missing the XWork stanza.
I'm not sure when I did that or why.
The other thing is why do we get the
Embedded error:
C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
I looked again at a clean checkout and found the reference. The
assembly POM in my usual working copy was missing the XWork stanza.
I'm not sure when I did that or why.
The other thing is why do we get the
Embedded error:
I can't even find the XWork reference in the POM assembly. :)
Why don't you go ahead and fix the parent POM, and then we'll tag it.
-Ted.
On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
On 12/30/06, Ted Husted [EMAIL PROTECTED] wrote:
OK,
I was leaving site out. Thanks!
-Ted.
On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
I looked again at a clean checkout and found the reference. The
assembly POM in my usual working copy was missing the XWork stanza.
I'm not sure when I
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
I was leaving site out. Thanks!
I'm having trouble with 'mvn install -Pall' (svn trunk, with the
version set at 2.0.2.)
The struts-all build is failing because it can't find
'struts2-config-browser-plugin'. To make it work, I dropped into
Yes, we decided that a combined struts-all.jar wasn't useful.
From clean checkout against a clean repository, I had to install the
plugins first, and then run the usual assembly commands, same as you.
I added a note to the wiki page.
-Ted.
On 12/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:
For now, I'll just delete it from the library before I sign it, to
avoid confusion. Then, we can take it out all together for Struts
2.0.3.
-Ted.
On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
Yes, we decided that a combined struts-all.jar wasn't useful.
From clean checkout against a clean
Ted,
Making XWork a more public project is not a problem - we just hadn't done so
up until now due to no need.
As for the names of the releases (RC, beta, 2.0.1.1.1.1, whatever you
want...)... that is really easy to fix: just ask Rainer or whoever is doing the
release :) OpenSymphony doesn't
[From Tag Reorganization thread]
On 12/30/06, Don Brown [EMAIL PROTECTED] wrote:
Quick update: The dojo separation is looking easier than I thought. I
plan to finish it tomorrow, however, it requires the latest xwork so
we should probably put it after 2.0.2. It is looking pretty good for
The change I made to xwork is a very minor, internal Guice improvement
that should have no impact on its GA release. I haven't checked with
Rainer lately, but I'd imagine XWork 2.0 could go final very soon.
As for branching for 2.1, yeah, we could do that. I was thinking of
doing the ajax
Don Brown wrote:
The change I made to xwork is a very minor, internal Guice improvement
that should have no impact on its GA release. I haven't checked with
Rainer lately, but I'd imagine XWork 2.0 could go final very soon.
I spoke with him at Javapolis, and I believe everything was ready to
On 12/30/06, Don Brown [EMAIL PROTECTED] wrote:
The change I made to xwork is a very minor, internal Guice improvement
that should have no impact on its GA release. I haven't checked with
Rainer lately, but I'd imagine XWork 2.0 could go final very soon.
As for branching for 2.1, yeah, we
It is an interesting idea, but the showstoppers for me are:
* All the bugs that have been fixed since then
* The documentation would be completely wrong as it is for 2.0.2
* XWork trunk might not even work with 2.0.1
I think we are 95% of the way to a GA release and really do think it
could be
I'm perfectly willing to backport the bugfixes, and the Struts
documentation is bundled with the release. We'd just have to patch the
release notes pages with any updates.
The XWork trunk does not work with the current release, so we would
have to branch XWork too, and increment its head as
Ted Husted wrote:
I'm perfectly willing to backport the bugfixes, and the Struts
documentation is bundled with the release. We'd just have to patch the
release notes pages with any updates.
Unfortunately, I don't believe that is possible, and really, it would be
counter-productive. There as
On 12/30/06, Don Brown [EMAIL PROTECTED] wrote:
I'd feel a lot better if XWork would move to the milestone release
that we use, and Tomcat uses, and HTTPD uses, and MySQL uses, to name
a few. This hand-over-hand approach, that continually dooms Struts
releases to beta status is a frustrating
Ted,
I just released XWork 2.0RC1. All required files are uploaded to the
OpenSymphony repos. Please crosscheck if everything works for you as
expected.
If you'd like to download the distribution bundles, go to
https://xwork.dev.java.net/servlets/ProjectDocumentList?folderID=6088
tia,
Rainer
After some more testing, it appears as though the javascript issues
associated with the optiontransferselect (WW-1559) are actually
effecting it's behavior. I think we should add this back to the 2.0.2 list.
I'm not all that familiar with dojo, but I'll start to look into it today.
David
Hi guys, I was out f town. About the problem with the autocompleter, it
is missing a css file, 'cause Don asked me to create another patch and
I had started to work on the big autocompleter ticket already so I
missed it. Please don't rollback anything, I will submit today a patch
for the
I attached the patch to WW-1562. It is a fairly long ticket, not
everything is fixed, but the most important stuff is:
* Add a way to hide the dropdown arrow
* Reload options on type, and be able to specify minimum text length for
reload
* Remember selected values is there is a validation
The problem is that we have a an issue report, but no suggestions as
to a resolution. If we have a patch to apply for 2.0.2, that would be
great. But, otherwise, we might want to keep it as a known issue to
fix as soon as we figure out how. A 2.0.2 release is not going to a a
GA candidate anyway
That's fine with me, just help me understand the difference between this
and the datetimepicker and action-redirect issues. . .what makes them
showstoppers?
not trying to be a pain, just trying to understand :)
David
Ted Husted wrote:
The problem is that we have a an issue report, but no
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get positive votes for a build with know defects.
AFAIK, the JavaScript error (WW-1559) doesn't impede functionality. It
might keep people from
Ted Husted wrote:
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get positive votes for a build with know defects.
AFAIK, the JavaScript error (WW-1559) doesn't impede functionality. It
I can give you a hand on that problem when I finish with the datepicker
stuff.
musachy
David H. DeWolf wrote:
Ted Husted wrote:
Both the datetimepicker and the action-redirect prefix worked in the
2.0.1 beta but don't work now. Both are outright bugs, and it's
unlikely we would get
We're down to a handful of problems, which are all reflected in the
Showcase examples, one way or the other. Some of these were also
present in Struts 2.0.1, and so may be a problem with the example
itself.
* https://issues.apache.org/struts/browse/WW-1538
The showstoppers are the
33 matches
Mail list logo
