You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Nick Burch <ni...@torchbox.com> on 2007/06/08 15:38:23 UTC

[VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Hi All

Following Andy's -1 to the last release candidate, I have tweaked the ant 
build file. With RC2, we now have different maven artificats of poi, 
poi-contrib and poi-scratchpad, which all use the normal POI jars.

Otherwise, RC2 is much like RC1, only with a few more Apache Jakarta POI 
-> Apache POI changes from Yegor.

The release candidate is available to download from:
 	http://people.apache.org/~nick/POI-3.0.1-RC2/main/
 	http://people.apache.org/~nick/POI-3.0.1-RC2/maven/

Despite the file names, *these files are only a release candidate* (as the 
directory name indicates).


Could everyone give the files a check, especially:
* file and directory names are as expected
* things say Apache POI not Apache Jakarta POI / Jakarta POI
* the maven stuff doesn't break maven
* the maven stuff is structured in a way we're all happy with


Once you're done, it's time to vote:
  [ ] +1  I support the release
  [ ] +0  I don't care
  [ ] -1  I'm opposed to the release because...

Voting will close a week today (Friday 15th June)


As might be expected, I'm +1

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re[2]: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by Nick Burch <ni...@torchbox.com>.
On Fri, 8 Jun 2007, Yegor Kozlov wrote:
> What about a readme for Maven users? If they have troubles with the poms
> they can follow the instructions.

I've done some checking, and it does look like the poms for 3.0.1 RC2 are
what maven wants. I've also discovered that the directory structure used
on people.apache.org to accept artifacts for the ibiblio sync is quite
different to the directory structure used after the sync. So, it's not
actually very easy for maven users to test with.

With that in mind, I'm tempted to say that we should just vote on the main
release artifacts as before (I'm pretty sure this was Andy's position
too?).

(At the same time as generating the release candidate artificats, also run
the ant task to spit out the maven poms. After the vote, you can upload
the maven poms along with the main voted on artificats, and copy the voted
on jars over for maven too. However, if the release manager doesn't want
to do maven stuff, anyone else can do later, since it's all based on
voted-on files)


Since we don't have to worry about maven stuff any more, shall we re-start
the vote? We're voting to release 3.0.1 RC2, as found in
	http://people.apache.org/~nick/POI-3.0.1-RC2/main/
as 3.0.1-FINAL. The vote now ends on Friday 23rd June

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by Martin van den Bemt <ml...@mvdb.net>.
If you ask the maven people to help out, they tend to do that :)

Mvgr,
Martin

Yegor Kozlov wrote:
> What about a readme for Maven users? If they have troubles with the
> poms they can follow the instructions.
> P.S. I'm not a Maven user either, and not sure what we can put into this
> readme file. Any ideas?
> 
> Yegor
> 
>> On Fri, 8 Jun 2007, Andrew C. Oliver wrote:
>>> Right....what I'm saying is if Maven people (or you individually) want 
>>> to structure our stuff for maven, splendid.
> 
>> I'm not a maven user myself, I just want them to be happy and leave me
>> alone!
> 
>>> However the project should not create official artifacts strictly for 
>>> Maven or any other build system.  I'm +1 on the /main/ artifacts and I'm 
>>> -1 on anything in the /maven/ directory.
> 
>> OK, I've zapped the jars from under /maven/, and I'll just copy them over
>> from /main/ when I push files out to the repository
> 
>> /maven/ just contains the automatically generated poms, which maven users
>> will want to check out and confirm they're what they'd expect. I'm not
>> sure if we actually need them to be voted on or not, in the same way we do
>> for everything in /main/, but I am keen to get them looked at. If 
>> possible, they should be looked at by maven users _before_ release, so I
>> won't get another telling off from repository@ for invalid poms....
> 
>> Nick
> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re[2]: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by Yegor Kozlov <ye...@dinom.ru>.
What about a readme for Maven users? If they have troubles with the
poms they can follow the instructions.
P.S. I'm not a Maven user either, and not sure what we can put into this
readme file. Any ideas?

Yegor

> On Fri, 8 Jun 2007, Andrew C. Oliver wrote:
>> Right....what I'm saying is if Maven people (or you individually) want 
>> to structure our stuff for maven, splendid.

> I'm not a maven user myself, I just want them to be happy and leave me
> alone!

>> However the project should not create official artifacts strictly for 
>> Maven or any other build system.  I'm +1 on the /main/ artifacts and I'm 
>> -1 on anything in the /maven/ directory.

> OK, I've zapped the jars from under /maven/, and I'll just copy them over
> from /main/ when I push files out to the repository

> /maven/ just contains the automatically generated poms, which maven users
> will want to check out and confirm they're what they'd expect. I'm not
> sure if we actually need them to be voted on or not, in the same way we do
> for everything in /main/, but I am keen to get them looked at. If 
> possible, they should be looked at by maven users _before_ release, so I
> won't get another telling off from repository@ for invalid poms....

> Nick

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by Nick Burch <ni...@torchbox.com>.
On Fri, 8 Jun 2007, Andrew C. Oliver wrote:
> Right....what I'm saying is if Maven people (or you individually) want 
> to structure our stuff for maven, splendid.

I'm not a maven user myself, I just want them to be happy and leave me 
alone!

> However the project should not create official artifacts strictly for 
> Maven or any other build system.  I'm +1 on the /main/ artifacts and I'm 
> -1 on anything in the /maven/ directory.

OK, I've zapped the jars from under /maven/, and I'll just copy them over 
from /main/ when I push files out to the repository

/maven/ just contains the automatically generated poms, which maven users 
will want to check out and confirm they're what they'd expect. I'm not 
sure if we actually need them to be voted on or not, in the same way we do 
for everything in /main/, but I am keen to get them looked at. If 
possible, they should be looked at by maven users _before_ release, so I 
won't get another telling off from repository@ for invalid poms....

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by "Andrew C. Oliver" <ac...@buni.org>.
Right....what I'm saying is if Maven people (or you individually) want 
to structure our stuff for maven, splendid.  However the project should 
not create official artifacts strictly for Maven or any other build 
system.  I'm +1 on the /main/ artifacts and I'm -1 on anything in the 
/maven/ directory.

Nick Burch wrote:
> On Fri, 8 Jun 2007, Andrew C. Oliver wrote:
>> But there is still a separate set of Jars specifically for maven.....
> 
> They're the same ones as in /main/ :)
> 
> (I've just copied them into the maven directory too, so that it's one 
> less step during the release process.)
> 
> Nick
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org


-- 
Buni Meldware Communication Suite
http://buni.org
Multi-platform and extensible Email,
Calendaring (including freebusy),
Rich Webmail, Web-calendaring, ease
of installation/administration.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by Nick Burch <ni...@torchbox.com>.
On Fri, 8 Jun 2007, Andrew C. Oliver wrote:
> But there is still a separate set of Jars specifically for maven.....

They're the same ones as in /main/ :)

(I've just copied them into the maven directory too, so that it's one less 
step during the release process.)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by "Andrew C. Oliver" <ac...@buni.org>.
But there is still a separate set of Jars specifically for maven.....

Nick Burch wrote:
> Hi All
> 
> Following Andy's -1 to the last release candidate, I have tweaked the 
> ant build file. With RC2, we now have different maven artificats of poi, 
> poi-contrib and poi-scratchpad, which all use the normal POI jars.
> 
> Otherwise, RC2 is much like RC1, only with a few more Apache Jakarta POI 
> -> Apache POI changes from Yegor.
> 
> The release candidate is available to download from:
>     http://people.apache.org/~nick/POI-3.0.1-RC2/main/
>     http://people.apache.org/~nick/POI-3.0.1-RC2/maven/
> 
> Despite the file names, *these files are only a release candidate* (as 
> the directory name indicates).
> 
> 
> Could everyone give the files a check, especially:
> * file and directory names are as expected
> * things say Apache POI not Apache Jakarta POI / Jakarta POI
> * the maven stuff doesn't break maven
> * the maven stuff is structured in a way we're all happy with
> 
> 
> Once you're done, it's time to vote:
>  [ ] +1  I support the release
>  [ ] +0  I don't care
>  [ ] -1  I'm opposed to the release because...
> 
> Voting will close a week today (Friday 15th June)
> 
> 
> As might be expected, I'm +1
> 
> Nick
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org


-- 
Buni Meldware Communication Suite
http://buni.org
Multi-platform and extensible Email,
Calendaring (including freebusy),
Rich Webmail, Web-calendaring, ease
of installation/administration.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org


Re: [VOTE] Release 3.0.1 RC2 as 3.0.1 FINAL

Posted by "Rainer Klute (Rainer Klute IT-Consulting)" <kl...@rainer-klute.de>.
Nick Burch schrieb:
> Could everyone give the files a check, especially:
> * file and directory names are as expected
> * things say Apache POI not Apache Jakarta POI / Jakarta POI
> * the maven stuff doesn't break maven
> * the maven stuff is structured in a way we're all happy with

I presently don't have the time to fiddle around with POI, there I vote
as follows:

> Once you're done, it's time to vote:
>  [ ] +1  I support the release
>  [X] +0  I do abstain
>  [ ] -1  I'm opposed to the release because... 

Best regards
Rainer Klute

                           Rainer Klute IT-Consulting
  Dipl.-Inform.
  Rainer Klute             E-Mail: klute@rainer-klute.de
  Körner Grund 24          Phone:  +49 231 5349423
D-44143 Dortmund           Mobile: +49 172 2324824

OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E