I've checked in a (mostly) working updated blank-archetype to the maven
svn trunk.
There's a new archetypes doc page at [1], along with a more detailed
look at the blank archetype itself at [2] that talks a bit about Maven
and the blank app itself.
Caveats:
There are some archetype issues I'm a little fuzzy on, including but not
limited to the following issues I'd like to fix (or have fixed ;)
- I had to add a commons-logging dependency but I'm not sure why
- mvn package is including Spring/Mock/Junit in the WAR
- the index.html's refresh doesn't seem to work under Jetty
- I don't know how to deploy the artifact
Any info appreciated. I'll try to start on the starter-archetype at some
point, but the next few weeks are pretty stressed for a variety of
uninteresting reasons. (Except that I get to use JRoR in my new day job,
which I'm hoping will have some nice synergies.)
[ ] 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.
The vote will remain open for at least 72 hours, longer upon request.
A vote can be amended at any time to upgrade or downgrade the quality
of the release based on future experience. If an initial vote
designates the build as "Beta", the release will be submitted for
mirroring and announced to the user list. Once released as a public
beta, subsequent quality votes on a build may be held on the user
list.
As always, the act of voting carries certain obligations. A binding
vote not only states an opinion, but means that the voter is agreeing
to help do the work
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
