Re: Bindingness of votes Was: Move Commons Proxy to Proper...

2007-09-28 Thread Ben Speakmon
And I'll be more careful about vote-counting in the future. Being American, you'd think I'd watch that stuff more carefully :) On 9/28/07, Henri Yandell <[EMAIL PROTECTED]> wrote: > > On 9/28/07, sebb <[EMAIL PROTECTED]> wrote: > > On 29/09/2007, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > On 9

Re: Bindingness of votes Was: Move Commons Proxy to Proper...

2007-09-28 Thread Henri Yandell
On 9/28/07, sebb <[EMAIL PROTECTED]> wrote: > On 29/09/2007, Henri Yandell <[EMAIL PROTECTED]> wrote: > > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > > > > I do not know which of these votes are binding/non-binding. > > > > To figure it out, cross reference with the committee-info.txt f

Re: Bindingness of votes Was: Move Commons Proxy to Proper...

2007-09-28 Thread sebb
On 29/09/2007, Henri Yandell <[EMAIL PROTECTED]> wrote: > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > > I do not know which of these votes are binding/non-binding. > > To figure it out, cross reference with the committee-info.txt file in > svn-private:committers/board/ In which case, m

Bindingness of votes Was: Move Commons Proxy to Proper...

2007-09-28 Thread Henri Yandell
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > I do not know which of these votes are binding/non-binding. To figure it out, cross reference with the committee-info.txt file in svn-private:committers/board/ Though all you really need to do is show that there are 3 binding votes there when

Re: [proxy] Cutting a release...

2007-09-28 Thread James Carman
Ok, then I'll change mine to optional. Thanks for the clarification, Dennis. On 9/28/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Optional means that you can use the product without these dependencies > present. Take commons-logging as an example. It has optional > dependencies on log4j and t

Re: [proxy] Cutting a release...

2007-09-28 Thread Dennis Lundberg
Here's a page with more details: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Dennis Lundberg wrote: Optional means that you can use the product without these dependencies present. Take commons-logging as an example. It has optional dependencies on log4

Re: [proxy] Cutting a release...

2007-09-28 Thread Dennis Lundberg
Optional means that you can use the product without these dependencies present. Take commons-logging as an example. It has optional dependencies on log4j and the other logging implementations. In the real world though it will only use one of these. So they are optional. Provided means that tha

Re: [VOTE] Move Commons Proxy to Proper...

2007-09-28 Thread Jörg Schaible
James Carman wrote: > All, > > I believe it is time to move Commons Proxy out of the sandbox and into > Commons Proper. It appears to be very close to a 1.0 release. This > vote will be left open until 10/05/2007 18:00 EDT (that's my timezone > :). So far, the votes are: > > Niall Pemberton:

[VOTE] Move Commons Proxy to Proper...

2007-09-28 Thread James Carman
All, I believe it is time to move Commons Proxy out of the sandbox and into Commons Proper. It appears to be very close to a 1.0 release. This vote will be left open until 10/05/2007 18:00 EDT (that's my timezone :). So far, the votes are: Niall Pemberton: +1 Paul Benedict: +1 Ben Speakmon: +1

Re: [proxy] Cutting a release...

2007-09-28 Thread James Carman
The dependencies are truly optional. I marked them as provided so that they wouldn't get picked up transitively (as you stated) by client projects. If they want to use the pieces of commons-proxy that need those extra libs, then they can explicitly add them to their POM. So, does that mean I sho

Re: [proxy] Cutting a release...

2007-09-28 Thread Ben Speakmon
Using provided doesn't tell maven to ignore the dependency, it just means that it's expected that the user will install it into his local repository himself or that it will be on the same classloader as the application when it's running. maven will still complain if it can't find it. Optional depe

Re: [proxy] Cutting a release...

2007-09-28 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Carman wrote: > All, Hi James, > > It's been a while since Commons Proxy has had any attention, but I > have received two emails in the past two days about it. So, I would > like to cut a 1.0 release for it. A 1.0 would be excellent. I am also

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Henri Yandell
Yeah; though personally I think you can start the vote with any of the +1s here as presumed votes. ie) We don't have to revote - just list them in the vote email. Hen On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > What will be the process here? This is merely a proposal, so I guess > we n

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread James Carman
I think I have it down now. I reorganized everything this morning. It looks like it's building correctly now. On 9/28/07, Joerg Hohwiller <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > James Carman wrote: > > All, > Hi James, > > > > How does the maven 2 build pi

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Carman wrote: > All, Hi James, > > How does the maven 2 build pick up the files in the xdocs directory? > I'm moving stuff around in commons proxy and I thought that the maven > 2 build would not pick up my site stuff from the xdocs directory, b

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread James Carman
What will be the process here? This is merely a proposal, so I guess we need an official vote thread started after this. Should I go ahead and start that now? On 9/28/07, Luc Maisonobe <[EMAIL PROTECTED]> wrote: > +1 > > Henri Yandell wrote: > > +1 too. > > > > On 9/28/07, Ben Speakmon <[EMAIL P

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Luc Maisonobe
+1 Henri Yandell wrote: +1 too. On 9/28/07, Ben Speakmon <[EMAIL PROTECTED]> wrote: +1 nonbinding. On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: +1 On 9/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote: +1 - To unsub

Re: [ANNOUNCEMENT] Commons Email 1.1 released

2007-09-28 Thread Henri Yandell
I think they're an old convenience that people have kept because that's what people do with things that are not obviously broken. I'm +1 to getting rid of them, I don't think they buy us anything, and if they're a mirror issue then the sooner the better. Anyone against rm'ing them? It should be p

Re: [ANNOUNCEMENT] Commons Email 1.1 released

2007-09-28 Thread sebb
On 28/09/2007, Ben Speakmon <[EMAIL PROTECTED]> wrote: > Are the current links touched by any scripts that generate sites, or are > they merely a convenience? I have no problem removing them if it won't hurt > anything. Sorry, no idea. But I removed the JMeter ones a while back, and have not been

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Henri Yandell
+1 too. On 9/28/07, Ben Speakmon <[EMAIL PROTECTED]> wrote: > +1 nonbinding. > > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > > > +1 > > > > On 9/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > > +1 > > > > > > > -

Re: [ANNOUNCEMENT] Commons Email 1.1 released

2007-09-28 Thread Ben Speakmon
Are the current links touched by any scripts that generate sites, or are they merely a convenience? I have no problem removing them if it won't hurt anything. Also, I was working from the release docs -- we should update them with stuff like this. On 9/28/07, sebb <[EMAIL PROTECTED]> wrote: > > I

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Ben Speakmon
+1 nonbinding. On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > +1 > > On 9/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > +1 > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EM

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread Ben Speakmon
If you do stick with the xdocs/ directory, though, you'll have to override the location of the site.xml (at least I did for maven 2 in the email 1.1release). On 9/28/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > So, do I just copy my old

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread James Carman
+1 On 9/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > +1 > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread Niall Pemberton
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > So, do I just copy my old xdocs into the src/site directory and it'll > pick it up as usual? Yes - except navigation.xml - AFAIK maven2 uses site.xml - which is similar Niall > On 9/28/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > On 9/2

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread James Carman
So, do I just copy my old xdocs into the src/site directory and it'll pick it up as usual? On 9/28/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > > All, > > > > How does the maven 2 build pick up the files in the xdocs directory? > > I believ

Re: [ALL] Which license-header.txt File?

2007-09-28 Thread Niall Pemberton
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > What license header file should we be using? The one Commons Proxy > currently has looks like this: > > /* > * Licensed to the Apache Software Foundation (ASF) under one > * or more contributor license agreements. See the NOTICE file > * di

Re: [ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread Niall Pemberton
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > All, > > How does the maven 2 build pick up the files in the xdocs directory? I believe its maven2 magic - to make moving from maven1 as painless as possible. > I'm moving stuff around in commons proxy and I thought that the maven > 2 build wo

[ALL] Which license-header.txt File?

2007-09-28 Thread James Carman
What license header file should we be using? The one Commons Proxy currently has looks like this: /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Paul Benedict
+1

[ALL] Maven 2 Build and xdocs directory...

2007-09-28 Thread James Carman
All, How does the maven 2 build pick up the files in the xdocs directory? I'm moving stuff around in commons proxy and I thought that the maven 2 build would not pick up my site stuff from the xdocs directory, but it does. I'd rather the xdocs stuff be placed in the src/site directory instead (to

Re: [continuum] BUILD FAILURE: Commons Proxy (Sandbox)

2007-09-28 Thread James Carman
Sorry, folks. I'm moving some stuff around so that it's a more standard, mavenized layout. I'll have this fixed shortly. On 9/28/07, [EMAIL PROTECTED] wrote: > Online report : > http://vmbuild.apache.org/continuum/buildResult.action?buildId=8609&projectId=188 > > Build statistics: > State: F

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-09-28 Thread commons-jelly-tags-jaxme development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

[continuum] BUILD FAILURE: Commons Proxy (Sandbox)

2007-09-28 Thread [EMAIL PROTECTED]
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=8609&projectId=188 Build statistics: State: Failed Previous State: Ok Started at: Fri 28 Sep 2007 04:33:21 -0700 Finished at: Fri 28 Sep 2007 04:34:00 -0700 Total time: 39s Build Trigger: Schedule Build Number:

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-09-28 Thread commons-jelly-tags-jsl development
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. Th

Re: [PROPOSAL] Move Commons Proxy to Proper

2007-09-28 Thread Niall Pemberton
On 4/14/06, James Carman <[EMAIL PROTECTED]> wrote: > Outside projects (currently my Syringe project and the "Crispy" project > at sourceforge) are beginning to want to use Commons Proxy, but are finding > it difficult since it's in the sandbox and no releases are available. I > believe Proxy's AP

Re: [proxy] Cutting a release...

2007-09-28 Thread Niall Pemberton
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote: > All, > > It's been a while since Commons Proxy has had any attention, but I > have received two emails in the past two days about it. So, I would > like to cut a 1.0 release for it. I know I need to do a little work, > since the site is a bit

Re: [ANNOUNCEMENT] Commons Email 1.1 released

2007-09-28 Thread sebb
I discovered recently that the "current" links in the parent directory don't work properly on mirrors. I suggest that these are removed. E.g. at present all the current links on http://mirror.public-internet.co.uk/apache/commons/email/ are copies of the 1.0 files. I've not checked any other mi

[proxy] Cutting a release...

2007-09-28 Thread James Carman
All, It's been a while since Commons Proxy has had any attention, but I have received two emails in the past two days about it. So, I would like to cut a 1.0 release for it. I know I need to do a little work, since the site is a bit out-dated (the SVN links are incorrect) from the TLP move. Wer

[EMAIL PROTECTED]: Project commons-email (in module apache-commons) failed

2007-09-28 Thread dIon Gillard
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue affect