* No zip file for the -src.
* The tar.gz doesn't open into *-src/ directory.
* Unable to find your key so I can verify the pgp.
--
MD5s good.
Ant, Maven and Maven2 all work from the src tar.gz.
Jars were built by Plexus, so does that mean this is a Maven2 release?
Do we have a plan for how we'll do that?
I'm thinking:
* Change group id?
* How do we build a 2.0 release and vote on that rather than voting on
the release manager's ability to do a release? Is there a way to
deploy known files to an m2 repository rather than having to rebuild?
* How much of the release code can be shared - I can see stuff in the
pom.xml, can that stuff be in the parent pom?
Hen
On 2/1/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
Hi,
after IO 1.3 is out, I've made a second release candidate available
for review on
http://people.apache.org/~jochen/commons-fileupload/dist
The proposed site can be viewed at
http://people.apache.org/~jochen/commons-fileupload/site
The site includes clirr and checkstyle reports, a rat report is at
http://people.apache.org/~jochen/commons-fileupload/dist/rat.txt
(This report was created by using the rat-maven-plugin, btw.)
Please cast your vote:
[ ] +1
[ ] =0
[ ] -1
I'll keep the vote open until saturday, if noone else intervenes.
Jochen
--
How fast can a year go? As fast as your childs first year.
---------------------------------------------------------------------
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]
