date:20070225


Bob,

I see some interesting similarities to other projects. Tapestry has an 
@Inject annotation, and Spring has a @Required annotation. I guess my 
question is why would someone prefer Guice support over Spring? I read 
the "Why Guice?" section, but I didn't see this question.


Paul

Bob Lee wrote:

Guice has come along way since we copied the source over into XWork. If
anyone would like to try out Guice with Struts 2.0.6, we've included a
plugin jar in the latest distribution:
http://google-guice.googlecode.com/files/guice-1.0rc2.zip

And instructions for using Guice with Struts 2 in the users' guide:
http://docs.google.com/Doc?id=dd2fhx4z_5df5hw8

The users' guide is in dire need of help, we know. Kevin B. is working on a
complete rewrite. Let us know if you'd like to help!

You can find the latest Javadocs in the aforementioned zip or online here:
http://google-guice.googlecode.com/svn/trunk/javadoc/index.html

Thanks for checking this out. Let me know if you have any problems. We hope
you enjoy it, and we appreciate any feedback.

Also, the site may be public, and the implementation is pretty much
complete, but we are trying to stay under the radar until will have all our
ducks in a row, i.e. better documentation.

Thanks,
Bob



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Guice 1.0rc2

2007-02-25 Thread Bob Lee


Guice has come along way since we copied the source over into XWork. If
anyone would like to try out Guice with Struts 2.0.6, we've included a
plugin jar in the latest distribution:
http://google-guice.googlecode.com/files/guice-1.0rc2.zip

And instructions for using Guice with Struts 2 in the users' guide:
http://docs.google.com/Doc?id=dd2fhx4z_5df5hw8

The users' guide is in dire need of help, we know. Kevin B. is working on a
complete rewrite. Let us know if you'd like to help!

You can find the latest Javadocs in the aforementioned zip or online here:
http://google-guice.googlecode.com/svn/trunk/javadoc/index.html

Thanks for checking this out. Let me know if you have any problems. We hope
you enjoy it, and we appreciate any feedback.

Also, the site may be public, and the implementation is pretty much
complete, but we are trying to stay under the radar until will have all our
ducks in a row, i.e. better documentation.

Thanks,
Bob

Re: Struts 2 jars are missing signatures in the Maven repo

It should be noted, Wendy was kind enough after 1.3.6 to add a "release" 
profile to run the GPG plugin. But I forgot about it and did the 1.3.7 
deployment of the signing by hand :-) Silly me for not remembering!


Paul

Wendy Smoak wrote:

On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:


Could you specify the exact steps that we should be following then?


I added a TODO to review steps 5 and 6 on the wiki page.  You
mentioned March 4th for Struts 2.0.7, so that gives me a few days.

(I'd like to see Struts start using the release plugin, but I need to
spend some time with it and make sure everything is in place before I
suggest changing the release process, which is working well enough.
Maven releases should be easier than this!)

I use Cygwin exclusively, so I'm not having the back-and-forth issues
that you describe... and that's going to be difficult to troubleshoot
remotely. :(  How about creating a ssh key with Cygwin, and appending
it to to your authorized_keys on people.a.o?

Paul,  it sounds like the Struts 1 process is having a similar
problem, because 'mvn deploy' with the gpg plugin configured should
upload the signatures automatically along with the jars and poms.

Thanks again to our release managers!  I don't have time to take it on
again right now, but I will make time to help if anyone else would
like to learn the process.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:


Could you specify the exact steps that we should be following then?


I added a TODO to review steps 5 and 6 on the wiki page.  You
mentioned March 4th for Struts 2.0.7, so that gives me a few days.

(I'd like to see Struts start using the release plugin, but I need to
spend some time with it and make sure everything is in place before I
suggest changing the release process, which is working well enough.
Maven releases should be easier than this!)

I use Cygwin exclusively, so I'm not having the back-and-forth issues
that you describe... and that's going to be difficult to troubleshoot
remotely. :(  How about creating a ssh key with Cygwin, and appending
it to to your authorized_keys on people.a.o?

Paul,  it sounds like the Struts 1 process is having a similar
problem, because 'mvn deploy' with the gpg plugin configured should
upload the signatures automatically along with the jars and poms.

Thanks again to our release managers!  I don't have time to take it on
again right now, but I will make time to help if anyone else would
like to learn the process.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo

On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> Actually, I do have the asc files in my local repository, with a
> timestamp that indicates taht they were created when I released and
> deployed the Maven artifacts. So the question is why where only these
> files left behind?

That would happen if you did 'mvn install' rather than rather than 'mvn deploy'.

Looking at [1] I think steps 5 and 6 need to be adjusted.  The release
profile and the passphrase need to be used with 'deploy'.  (Step 5 is
doing 'install' which is the default.)

[1] http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html

Could you specify the exact steps that we should be following then?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:

Actually, I do have the asc files in my local repository, with a
timestamp that indicates taht they were created when I released and
deployed the Maven artifacts. So the question is why where only these
files left behind?


That would happen if you did 'mvn install' rather than rather than 'mvn deploy'.

Looking at [1] I think steps 5 and 6 need to be adjusted.  The release
profile and the passphrase need to be used with 'deploy'.  (Step 5 is
doing 'install' which is the default.)

[1] http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

When you have time, please post a message with the error you get about
ssh keys so we can try to sort it out.


There's no error. It just prompts me for a password, but PuTTY doesn't.

I have the .ssh directory and known hosts file in my XP home directory.

Cygwin probably can't find or use my SSH key, which I probably created
with PuTTY.

As it stands, I do some things with Cygwin and others from the XP
command line, because nothing works all in one place for me :(

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


Ted,

From my personal deployment experience, the ASC files never get 
deployed automatically. I always have to FTP them over. It's a little 
bit of a hassle to do it for 9 sub-projects, but 2.x has much much more. 
I'd like to find a way to upload them all with a command.


Paul

Ted Husted wrote:

On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

Well, _that_ was certainly not my intent!  You shouldn't have to sign
them "by hand" -- there are far too many of them to make that a
reasonable requirement.


Actually, I do have the asc files in my local repository, with a
timestamp that indicates taht they were created when I released and
deployed the Maven artifacts. So the question is why where only these
files left behind?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

Well, _that_ was certainly not my intent!  You shouldn't have to sign
them "by hand" -- there are far too many of them to make that a
reasonable requirement.


Actually, I do have the asc files in my local repository, with a
timestamp that indicates taht they were created when I released and
deployed the Maven artifacts. So the question is why where only these
files left behind?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


It's a great script. I highly recommend it.

Wendy Smoak wrote:

On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:


I think I might have to step away from the release manager role. Or,
at least the deployment of the Maven artifacts. I have a lot of
trouble getting the Maven signing plugins or scripts to work.  Signing
all these Maven artifacts by hand is not something I can do on a
regular basis. I'll fix 2.0.6, but, otherwise, this might have to be
my last Maven distribution.


Well, _that_ was certainly not my intent!  You shouldn't have to sign
them "by hand" -- there are far too many of them to make that a
reasonable requirement.

Prior to the gpg plugin being available I used a script to recursively
sign the jars in my local repo, and then upload the signatures.  I
think Paul just used it for the Struts 1.3.7 signatures.  It's a bash
shell script (I use Cygwin), but surely we have enough talent around
here to convert it to a script that will work on Windows...

Here's the signature part...

# Recursively pgp sign files in a directory structure
# Adapted from: http://gleamynode.net/wordpress/archives/129

echo -n "PGP Key Password: "
stty -echo
read PASSWORD
stty echo
echo ""

for FILE in $(find . -name "*.jar" -or -name "*.pom"); do

  echo -n "Signing: $FILE ... "

  echo "$PASSWORD" | gpg --default-key "$DEFAULT_KEY" --detach-sign
--armor --no-tty --yes --passphrase-fd 0 "$FILE" && echo done.

done

Unfortunately, this isn't something another committer can volunteer
for, the signatures really need to come from the person who built the
jars.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:


Prior to the gpg plugin being available I used a script to recursively
sign the jars in my local repo, and then upload the signatures.  I
think Paul just used it for the Struts 1.3.7 signatures.  It's a bash
shell script (I use Cygwin), but surely we have enough talent around
here to convert it to a script that will work on Windows...


Oh, wait, I just noticed you mentioned Cygwin. :)

When you have time, please post a message with the error you get about
ssh keys so we can try to sort it out.

I wonder if it's the "need to manually create a .ssh directory" which
is described here:
http://wiki.apache.org/struts/StrutsMaintenanceMaven#head-a50fcaa2d24d2668845a79e9371d91c30a320a39

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

for, the signatures really need to come from the person who built the
jars.


Statements like that never made sense to me. The bits should be
deterministic. If we build from the same tag, we should get the same
binaries. Why can't any other committer with a signature on file check
out the tag and post the Maven distribution.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo


On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:


I think I might have to step away from the release manager role. Or,
at least the deployment of the Maven artifacts. I have a lot of
trouble getting the Maven signing plugins or scripts to work.  Signing
all these Maven artifacts by hand is not something I can do on a
regular basis. I'll fix 2.0.6, but, otherwise, this might have to be
my last Maven distribution.


Well, _that_ was certainly not my intent!  You shouldn't have to sign
them "by hand" -- there are far too many of them to make that a
reasonable requirement.

Prior to the gpg plugin being available I used a script to recursively
sign the jars in my local repo, and then upload the signatures.  I
think Paul just used it for the Struts 1.3.7 signatures.  It's a bash
shell script (I use Cygwin), but surely we have enough talent around
here to convert it to a script that will work on Windows...

Here's the signature part...

# Recursively pgp sign files in a directory structure
# Adapted from: http://gleamynode.net/wordpress/archives/129

echo -n "PGP Key Password: "
stty -echo
read PASSWORD
stty echo
echo ""

for FILE in $(find . -name "*.jar" -or -name "*.pom"); do

  echo -n "Signing: $FILE ... "

  echo "$PASSWORD" | gpg --default-key "$DEFAULT_KEY" --detach-sign
--armor --no-tty --yes --passphrase-fd 0 "$FILE" && echo done.

done

Unfortunately, this isn't something another committer can volunteer
for, the signatures really need to come from the person who built the
jars.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo

2007-02-25 Thread Dave Newton

--- Ted Husted <[EMAIL PROTECTED]> wrote:
> I signed the struts2-core-2.0.6.jar by hand and
> uploaded it.
>
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/struts2-core/2.0.6/
> 
> If someone could verify that this is correct, that
> would be helpful.

The 2.0.6 JAR MD5 sig is correct, anyway.

> I think I might have to step away from the release
> manager role.

Your little jest escapes me ;) (Am I, btw, the only
person that loves "Murder by Death?"... "A room filled
with empty people!")

d.

Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Struts 2 jars are missing signatures in the Maven repo

The step by step that is being followed is here,

* http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html

which includes using the release profile. I don't know why it isn't
working for me.

My PuTTY SSL setup is fine now, but there is still something wrong
with Cygwin, since it can't find or use my private key. But that
should not have affected the gpg signatures.

I signed the struts2-core-2.0.6.jar by hand and uploaded it.

*
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/struts2-core/2.0.6/

If someone could verify that this is correct, that would be helpful.

I think I might have to step away from the release manager role. Or,
at least the deployment of the Maven artifacts. I have a lot of
trouble getting the Maven signing plugins or scripts to work. Signing
all these Maven artifacts by hand is not something I can do on a
regular basis. I'll fix 2.0.6, but, otherwise, this might have to be
my last Maven distribution.

-Ted.

On 2/25/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:

There seems to be a step missing in the Struts 2 release process. The
jars in the rsynced Maven repo are missing pgp/gpg signatures, for
example:

http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/struts2-core/2.0.5/

All the jars for both the 2.0.5 and 2.0.6 releases need to be signed.

For future builds, there is a 'release' profile in the struts2-parent
pom that will use maven-gpg-plugin to sign all the artifacts when they
are deployed to the staging repo. Or it can be done by signing the
jars in your local repo, and uploading the signatures.

Thanks,
--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Struts 1.3.7 Quality


The Struts 1.3.7 test build is now available.

Release notes:
* http://struts.apache.org/1.x/userGuide/release-notes.html

Distribution:
* http://people.apache.org/builds/struts/1.3.7/

Maven 2 staging repository:
* http://people.apache.org/builds/struts/1.3.7/m2-staging-repository/

If you have had a chance to review the test build, please respond with
a vote on its quality:

[  ] Leave at test build
[  ] Alpha
[  ] Beta
[  ] General Availability (GA)

Everyone who has tested the build is invited to vote. Votes by PMC
members are considered binding. A vote passes if there are at least
three binding +1s and more +1s than -1s.

Please remember that a *binding* +1 for GA implies that you intend to
support the release by applying patches and responding to posts to the
user and dev lists.

The vote will remain open for at least 72 hours, longer upon request.

Thank you,
Paul Benedict

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Struts 2 jars are missing signatures in the Maven repo


There seems to be a step missing in the Struts 2 release process.  The
jars in the rsynced Maven repo are missing pgp/gpg signatures, for
example:

http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/struts2-core/2.0.5/

All the jars for both the 2.0.5 and 2.0.6 releases need to be signed.

For future builds, there is a 'release' profile in the struts2-parent
pom that will use maven-gpg-plugin to sign all the artifacts when they
are deployed to the staging repo.  Or it can be done by signing the
jars in your local repo, and uploading the signatures.

Thanks,
--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nightly build script needs updating

2007-02-25 Thread Tom Schneider

The nightly scripts seem to be out of date for struts2.  The 2.0.x build 
is currently building trunk and there is no nightly build for 2.0.x:

http://svn.apache.org/repos/asf/struts/maven/trunk/scripts/nightly/nightly-2.0.x.sh

I'd be happy to update the scripts if someone could enlighten me on the 
proper procedure.  (Modifying the svn isn't the correct procedure 
according to the README.txt)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: s2 wiki font size

2007-02-25 Thread Musachy Barroso


to be much more difficult to read and not aligned

with the core site.




me too!


Paul


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

s2 wiki font size

I've always noticed the difference in font between the official Struts 
site and the S2 wiki. If someone will change the wiki's font size to 
point 12, you will then have matching font sizes. I find the current 
smaller font (11pt) to be much more difficult to read and not aligned 
with the core site.


Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [s2] Development Infrastructure (Re: [s2] Struts 2.0.7 Status)

2007-02-25 Thread Tom Schneider




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 like GC is on the right track, so
it's going to remain my own independent open source host of choice for
now. I'm no fan of moin-moin, but it will be interesting to see what
happens with this notion of storing wiki pages under SVN.
I agree that the issue tracking leaves much to be desired compared to 
JIRA, but since my projects aren't real active, I've only had to deal 
with 5 issues total so far.  :-)

Meanwhile, for our next battle, what do we need to do to get a
JiveForum setup for the Struts list somewhere. In the past, the best
way to get something into the ASF infrastructure is to vote with our
feet and host it somewhere else first. Then, we can point and say "Yet
it moves!".

For the dev list, there's already something setup at opensymphony:

http://forums.opensymphony.com/forum.jspa?forumID=34

I think it would be trivial to setup the user list.  Then it's just a 
matter of moving it over to an apache server.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[s2] Development Infrastructure (Re: [s2] Struts 2.0.7 Status)


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
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 like GC is on the right track, so
it's going to remain my own independent open source host of choice for
now. I'm no fan of moin-moin, but it will be interesting to see what
happens with this notion of storing wiki pages under SVN.

The "best of breed" approach we use at the ASF sometimes creates more
maintenance than the integrated approaches, like GC and SF, but it is
nice to be able to use the best tool for the job. (Leaving one to
wonder how long it will be before GC is the best tool for the job.)

Meanwhile, for our next battle, what do we need to do to get a
JiveForum setup for the Struts list somewhere. In the past, the best
way to get something into the ASF infrastructure is to vote with our
feet and host it somewhere else first. Then, we can point and say "Yet
it moves!".

You know, back in the day, I believe Pier setup an experimental Jive
instance for us, but it was not as cool as it is today. Or maybe that
was a different Jive.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [s2] Struts 2.0.7 Status

2007-02-25 Thread Tom Schneider




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 them loose.  The only question in my mind 
is: if we cut them loose, can we still include them in the core?  
There's probably quite a few plugins that should be included even if we 
cut them loose.  Also, there's probably some projects, like tabletags, 
that is replacing core functionality that should be included in the 
struts distribution itself.  (Once we feel it is of sufficient quality 
of course)


I'm glad everyone is following my trend to use googlecode for external 
projects.  :)  It's actually a really good fit for this kind of stuff 
compared to sourceforge.  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.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[s2] Struts 2.0.7 Status


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 keep each new GA milestone compatible
with the last GA, but we never make any guarantees beyond that,
meaning that 1.2.4 might not be binary compatible with 1.2.9 in some
respects.

Or, rather than tinker much with 2.0.x, we could just push anything
that smells like a new feature into 2.1.x, minimize cross-commits, and
get on with the 2.1.x release series.

For the 2.0.x series, one exception to the "new features" policy might
be items that are already part of the latest WebWork (e.g. WW-1678
"Cooke Interceptor"), and other items that speak to compatibility with
Struts 1 ((WW-1350 "Autofocus").

I'm not sure about WW-1704 (ParameterFilterInterceptor). Unless this
is part of WW2, it seems like something that we could push into
S2.1.x.

I silently moved 14 issues from 2.0.x to 2.0.7 (WW-1624, WW-1560,
WW-1600, WW-1654, WW-1672, SS-1619, WW-1719, WW-1717, WW-1350,
WW-1622, WW-1625, WW-1643, WW-1533), set them all to "minor" priority,
and removed the 2.0.x meta-version. If we do not resolve these issues
in 2.0.7, I'm thinking that we can push them to 2.0.8, 2.1.0, or the
2.x Future meta-version.


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".


Commit Logs - Nice Work.

Looking over the commit logs, we're doing a good job in referencing
each commit with a JIRA ticket and summarizing the substance of a
commit.

Keep in mind that the logs are available through the release notes
that JIRA generates, and they are available to posterity through the
SVN web interface. Don't be shy about including details or summarizing
any development discussions that lead up to the commit. Back in the
day, Craig was known to post 500 word commit logs, and skip the dev
list post altogether :)

Also note that when resolving or closing cross-posted issues, we can
select multiple versions (2.1.0, 2.0.7). Try not to select a "meta
version" like "2.1.x" or "Future" when resolving or closing issues.
(So anything logged against 2.1.x right now, if resolved or closed,
should be a fix for 2.1.0 (even if "not a problem"). Likewise the
"raised against" value should be a concrete release. If unsure, use
the earliest in the series.


Snippets rock!

Now that we have a working macro (thanks Don!), the snippet approach
to single-sourcing the documentation also seems to be working well. We
need a few more glue pages like the "Creating Interceptor" page, but
it looks to me like the current approach is creating a very helpful
set of online docs that we can actually keep up to date!

The beauty of snippets is that they encourage us to create better
JavaDocs, and "top-shelf" JavaDocs have always been a Struts hallmark.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r511291 - omnibus ticket.