Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-15 Thread Glen Daniels
Seems to work fine, although you should perhaps make super-clear in the next version's README that you require JDK 1.6 (I was on 1.5 and had build problems). +1 from me for the release. Thanks, --Glen On 2/15/2010 10:05 AM, Richard Hirsch wrote: > The ESME community has voted on and approved the

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-15 Thread Richard Hirsch
@Glen: Thanks for the tip. I've updated the README for the next release. D. On Mon, Feb 15, 2010 at 9:34 PM, Glen Daniels wrote: > Seems to work fine, although you should perhaps make super-clear in the > next > version's README that you require JDK 1.6 (I was on 1.5 and had build > problems).

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Daniel Kulp
+1 (mentor and IPMC binding) Some thoughts, but nothing that I would consider a "show stopper" since this is a source only release (aka: not providing a prebuilt war type thing or deploying it to Maven central): 1) The README mentions a "Collective work: Copyright 2007", but the NOTICE start

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Mattmann, Chris A (388J)
Hi guys, On 2/16/10 8:22 AM, "Daniel Kulp" wrote: >> What would be better in the pom.xml: >> apache-esme-1.0? > > No, just 1.0-incubator or similar. If this is the 1.0 release, the version > number should be 1.0. The 1.1 release would have a version of 1.1. According to: http://incubator.

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Bertrand Delacretaz
Hi, On Mon, Feb 15, 2010 at 4:05 PM, Richard Hirsch wrote: > ...The candidate can be found at: >  http://people.apache.org/~rhirsch/esme/ Unfortunately I'm -1 on the release, I have a few issues including a GPL dependency. 1) jwebunit dependency is GPL The server module depends on net.sourcefo

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Joe Schaefer
- Original Message > From: Bertrand Delacretaz > To: esme-...@incubator.apache.org > Cc: general@incubator.apache.org > Sent: Tue, February 16, 2010 11:28:22 AM > Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 > > Hi, > > On Mon, Feb 1

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Richard Hirsch
Like I said - I'm seeing this first release as a learning experience (grin, grin) On Tue, Feb 16, 2010 at 5:28 PM, Bertrand Delacretaz wrote: > Hi, > > On Mon, Feb 15, 2010 at 4:05 PM, Richard Hirsch > wrote: > > ...The candidate can be found at: > > > > http://people.apache.org/~rhirsch/esme

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-16 Thread Bertrand Delacretaz
On Tue, Feb 16, 2010 at 6:11 PM, Joe Schaefer wrote: > - Original Message > >> From: Bertrand Delacretaz >> ...Unfortunately I'm -1 on the release, I have a few issues including a >> GPL dependency. >> >> 1) jwebunit dependency is GPL >> The server module depends on >> >> net.sourceforge

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-17 Thread Bertrand Delacretaz
Hi, On Tue, Feb 16, 2010 at 8:12 PM, Richard Hirsch wrote: > On Tue, Feb 16, 2010 at 5:28 PM, Bertrand Delacretaz > wrote: >>... 4) When trying to build esme-java-client with "mvn clean install" I >> get "Embedded error: Error while executing the external compiler" if >> JAVA_HOME is not set. >>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-17 Thread Ethan Jewett
Thanks Joe and Bertrand. Point taken. Better to be safe and respectful than sorry. I'll continue the discussion on the ESME list alone. Ethan On Tue, Feb 16, 2010 at 5:17 PM, Bertrand Delacretaz wrote: > On Tue, Feb 16, 2010 at 6:11 PM, Joe Schaefer wrote: >> - Original Message >> >>>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0

2010-02-17 Thread Ethan Jewett
Thanks Joe and Bertrand. Point taken. Better to be safe and respectful than sorry. I'll try to spend some time looking at it. On the surface, it looks like it's imported into my API2 tests but is not really used. I'll try removing it from the tests in general, not just API2. It looks like it real