I added a comment on ww-1747 :
https://issues.apache.org/struts/browse/WW-1747
but it is still mark as fixed.
May I add comment on a fixed issue or do I have to open a new one ?
Is there a JIRA howto ??
Mike
-
To unsubscribe,
On 3/5/07, Mike Baroukh <[EMAIL PROTECTED]> wrote:
I added a comment on ww-1747 :
https://issues.apache.org/struts/browse/WW-1747
but it is still mark as fixed.
May I add comment on a fixed issue or do I have to open a new one ?
Is there a JIRA howto ??
Afaik, no - but feel free to reopen an
Thanks for your reply ..
>I would file an optimization request
It's not an optimization : it's a bug !
In fact, I added 2 comments on it at the end : the last one is an
optimization but the previous on is a bug I had to correct on my project
to make it work ...
That's why I post this messag
On 3/5/07, Mike Baroukh <[EMAIL PROTECTED]> wrote:
Thanks for your reply ..
>I would file an optimization request
It's not an optimization : it's a bug !
Ah, my mistake - I thought it was working correctly, and you only
wanted an optimization. In that case, just reopen the issue.
In fact,
We had set yesterday as a tag date for 2.0.7, so the release process
has begun. The release process for 2.0.x will likely be ongoing for
some time yet.
Depending on how much there is to do, I was going to tag and roll it
today. The amount of time I have to spend is finite, so at some point
we hav
On 3/5/07, Ted Husted <[EMAIL PROTECTED]> wrote:
We had set yesterday as a tag date for 2.0.7, so the release process
has begun. The release process for 2.0.x will likely be ongoing for
some time yet.
Apologies - I've been quite busy, so I missed that announcement. I saw
Tom updated a lot of is
If there's a particular issue that one of us believes simply must be
in the next milestone, then we should mark it as a "blocker". Anything
else is fair game for the next milestone.
The text of the bylaws talks about "showstoppers" and the "status
file". In practice, JIRA is our working status fi
As it stands, we have two spaces under Confluence. One is used to
create the "official" documentation (WW) that we bundle with the
release, the other is used as a conventional wiki (S2WIKI).
Since a snapshot of the WW space is distributed as part of the
release, a volunteer must first file a Cont
Ted Husted wrote:
I'll print and fax a CLA immediately.
Will I have to do anything more but sit back and wait until certain
rights have been granted to me in Confluence?
As I understand it, you say that it's possible to leave comments on the
(but not edit) WW pages without having signed the
I enabled comments on for the WW cwiki space.
I'll be able to see when the CLA goes on file, and when it does, then
we would be able to grant write access to the WW space.
In the meantime, it would be helpful to leave editing notes as comments.
-Ted.
On 3/5/07, Jan Normann Nielsen <[EMAIL PROT
* http://struts.apache.org/2.x/docs/action-configuration.html
underscore notation will cause problems with the generated
javascript for certain tags and themes
Do we have a better idea of which tags and which themes?
We had been presenting underscores in names as a recommended practice
when u
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
Well, since it was me who added the note ..
Pretty long time ago, I encountered some weird behaviour doing some
work on the (client side) validation, on a now discarded WW project.
From that moment on I always used either camelcase naming style, or
Unfortuneatly, I have no easy way of retrievin
:) Now that we are running Bamboo as a continuous integration server,
we might want to start observing the reports :)
Evidentially,
* http://opensource.bamboo.atlassian.com/browse/STRUTS-MAIN-186
revision r510958 and r510959 broke the build.
-Ted.
On 2/23/07, [EMAIL PROTECTED] <[EMAIL PROTEC
The project Struts 2 SVN - Main Build has the following 2 changes by 1 author:
*musachy* made the following changes at 07:11 PM, 05 March 2007
Comment:
Move classes to "dojo" package so they don't conflict with the ones from core
> /struts/struts2/trunk/plugins/dojo/src/test/java/org/apache/stru
Musachy, *please* learn to use 'svn move'! This should have been an 'svn
move' to retain history, and then an edit later. Yet again, we're losing the
history here, and you've made it much harder for us to verify that nothing
was inadvertently changed / broken in the process.
--
Martin Cooper
On
Sorry to spoil it, but I *did use svn move*:
http://svn.apache.org/viewvc?view=rev&revision=514940
musachy
On 3/5/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
Musachy, *please* learn to use 'svn move'! This should have been an 'svn
move' to retain history, and then an edit later. Yet again, w
On 3/5/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Sorry to spoil it, but I *did use svn move*:
http://svn.apache.org/viewvc?view=rev&revision=514940
If it was simply a move, there shouldn't have been any "diffs", just
the list of files.
Many of the files were "copied, changed from r51493
18 matches
Mail list logo
