[VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

Hi,

I have posted our candidate for the first Apache release developed
within the ESME podling.

The candidate can be found at

 http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>

See the CHANGES.txt file for details on release contents. The release
candidate is a tar archive of the sources in
https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/<https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating>

The MD5 checksum of the apache-esme-incubating-1.0-
src.tar.gz release package is

8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C


Please vote on releasing this package as Apache ESME 1.0-incubating.
The vote is open for the next 72 hours and passes if
a majority of at least three +1  ESME PPMC votes is reached. Assuming
the vote passes, I will ask the Incubator PMC to approve the release.

  [ ] +1 Release this package as Apache ESME 1.0-incubating
  [ ] -1 Do not release this package because...

Here's my +1.

Since the last release attempt, the following changes have been made
* Updated README to indicate that ESME currently just supports JDK 1.6
* Removed license reference from the README
* Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks
Ethan)
  Perform "mvn site" to see the current dependencies. The only dependencies
  only license information are the com.twitter.* jars and I was unabled to
find
  licensing info. Although newer versions in github are licensed with Apache

  License
* Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
* Changed version in pom.xml to
<version>apache-esme-1.0-incubating</version>
* removed svn files from release
* directory created by release is no longer called "trunk"
* Checked SHA signature on signed release but this should be a diff between
SHA1
  and SHA512


Dick Hirsch

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ah, forgot, the /server/compass-index folder magically appeared agin
of course :)

S

On 20 February 2010 20:54, Sig Rinde <si...@gmail.com> wrote:
> When I found the prob on my side the ESME webinterface funcionalry was
> normal. It was through the API the prob occurred but with the
> default.props change according to Dick it now works as it should.
>
> Sig
>
> Sent from my iPhone somewhere in the world, bad spelling due to funny
> keyboard, apologies for that...
> sig@rinde.com
> +33 (0)6 8887 9944
> Skype: sigurd.rinde
> Twitter: sig
>
> On 20 Feb 2010, at 20:28, Richard Hirsch <hi...@gmail.com> wrote:
>
>> OK.
>>
>> The question is this issue a "show-stopper?" Any opinions?
>>
>> My tests with "mvn jetty:run" didn't show any problems. Of course, I
>> didn't try to log-off and log-on again.
>>
>> If this problems leads to behavior as Sig suggested that the
>> application doesn't work correctly - posting messages, etc - then we
>> have to cut a new release.
>>
>> I won't be able to test the app until Monday. Can some other people
>> test the app in Jetty and Tomcat. Logging on and then off to see if
>> the application without the change in default.props functions
>> correctly - with the exception of search.
>>
>> D.
>>
>> On Sat, Feb 20, 2010 at 8:21 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Yay, that did the trick on my side at least! Works now.
>>>
>>> Good work folks... say when if you make more changes ;)
>>>
>>> Sig
>>>
>>> On 20 February 2010 20:10, Richard Hirsch <hi...@gmail.com>
>>> wrote:
>>>> The problem appears to be in the default.props file:
>>>> compass_config_file=/props/compass.jdbc.cfg.xml
>>>>
>>>> If you change it to "compass.filesystem.cfg.xml", it should be fine.
>>>>
>>>> D.
>>>>
>>>>
>>>> On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com>
>>>> wrote:
>>>>> Based on Sig's email I did some testing and it looks to me like
>>>>> search
>>>>> is broken in this build when using the "mvn jetty:run" command to
>>>>> launch the server. Can anyone else verify?
>>>>>
>>>>> Until we can figure out what the problem is, I'm changing my vote
>>>>> to -1
>>>>>
>>>>> Looking into it now....
>>>>>
>>>>> Ethan
>>>>>
>>>>> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>> > wrote:
>>>>>> @Gianugo  did you forget to vote on the release? I didn't see a
>>>>>> "+1"
>>>>>> or a "-1" in your two posts. Or would you rather vote for the
>>>>>> release
>>>>>> when it gets to the "general" mailing list?
>>>>>>
>>>>>> D.
>>>>>>
>>>>>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>>>>>> <g....@sourcesense.com> wrote:
>>>>>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>>>> > wrote:
>>>>>>>> can you try a "mvn site" to see what it is coming from...
>>>>>>>>
>>>>>>>> I tried with a empty repository and it worked :-<
>>>>>>>
>>>>>>> False alarm - I had some weird settings left in settings.xml.
>>>>>>> Nuked
>>>>>>> that one as well, it worked.
>>>>>>>
>>>>>>> Sorry for the fuss,
>>>>>>>
>>>>>>> --
>>>>>>> Gianugo Rabellino
>>>>>>> M: +44 779 5364 932 / +39 389 44 26 846
>>>>>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@gmail.com>]

When I found the prob on my side the ESME webinterface funcionalry was
normal. It was through the API the prob occurred but with the
default.props change according to Dick it now works as it should.

Sig

Sent from my iPhone somewhere in the world, bad spelling due to funny
keyboard, apologies for that...
sig@rinde.com
+33 (0)6 8887 9944
Skype: sigurd.rinde
Twitter: sig

On 20 Feb 2010, at 20:28, Richard Hirsch <hi...@gmail.com> wrote:

> OK.
>
> The question is this issue a "show-stopper?" Any opinions?
>
> My tests with "mvn jetty:run" didn't show any problems. Of course, I
> didn't try to log-off and log-on again.
>
> If this problems leads to behavior as Sig suggested that the
> application doesn't work correctly - posting messages, etc - then we
> have to cut a new release.
>
> I won't be able to test the app until Monday. Can some other people
> test the app in Jetty and Tomcat. Logging on and then off to see if
> the application without the change in default.props functions
> correctly - with the exception of search.
>
> D.
>
> On Sat, Feb 20, 2010 at 8:21 PM, Sig Rinde <si...@rinde.com> wrote:
>> Yay, that did the trick on my side at least! Works now.
>>
>> Good work folks... say when if you make more changes ;)
>>
>> Sig
>>
>> On 20 February 2010 20:10, Richard Hirsch <hi...@gmail.com>
>> wrote:
>>> The problem appears to be in the default.props file:
>>> compass_config_file=/props/compass.jdbc.cfg.xml
>>>
>>> If you change it to "compass.filesystem.cfg.xml", it should be fine.
>>>
>>> D.
>>>
>>>
>>> On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com>
>>> wrote:
>>>> Based on Sig's email I did some testing and it looks to me like
>>>> search
>>>> is broken in this build when using the "mvn jetty:run" command to
>>>> launch the server. Can anyone else verify?
>>>>
>>>> Until we can figure out what the problem is, I'm changing my vote
>>>> to -1
>>>>
>>>> Looking into it now....
>>>>
>>>> Ethan
>>>>
>>>> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>> > wrote:
>>>>> @Gianugo  did you forget to vote on the release? I didn't see a
>>>>> "+1"
>>>>> or a "-1" in your two posts. Or would you rather vote for the
>>>>> release
>>>>> when it gets to the "general" mailing list?
>>>>>
>>>>> D.
>>>>>
>>>>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>>>>> <g....@sourcesense.com> wrote:
>>>>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>>> > wrote:
>>>>>>> can you try a "mvn site" to see what it is coming from...
>>>>>>>
>>>>>>> I tried with a empty repository and it worked :-<
>>>>>>
>>>>>> False alarm - I had some weird settings left in settings.xml.
>>>>>> Nuked
>>>>>> that one as well, it worked.
>>>>>>
>>>>>> Sorry for the fuss,
>>>>>>
>>>>>> --
>>>>>> Gianugo Rabellino
>>>>>> M: +44 779 5364 932 / +39 389 44 26 846
>>>>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>>>>
>>>>>
>>>>
>>>
>>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

We can't do a release with "role.api_test=integration-admin" either,
so that has to go as well.

It is a huge security hole: No api_test user is delivered with the
software, so if someone unwittingly deploys with this setting, the
first user to create an account with the username "api_test" will have
the ability to add accounts and manage tokens for all users via the
API. In other words, they will be able to gain access any account via
the API.

Ethan

On Sat, Feb 20, 2010 at 2:07 PM, Sig Rinde <si...@rinde.com> wrote:
>> Maybe making this two-line change to one file is small enough that we
>> don't have to revote. I'm not sure. Maybe the mentors can weigh in.
>
> Two lines?
>
> I only changed "jdbc" to "filesystem" and it worked (for me)
>
> Anything I missed?
>
> S
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

> Maybe making this two-line change to one file is small enough that we
> don't have to revote. I'm not sure. Maybe the mentors can weigh in.

Two lines?

I only changed "jdbc" to "filesystem" and it worked (for me)

Anything I missed?

S

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Vassil Dichev <vd...@apache.org>]

We should by all means do String.trim on input values- from properties
or otherwise.


On Tue, Feb 23, 2010 at 9:36 AM, Sig Rinde <si...@rinde.com> wrote:
> Ethan / Dick
>
> Noticed that the default.props file that was included in today's RC
> indeed had much trailing characters (spaces) so even if I used vi to
> add the role.api_test line to it I had to clean it up first.
>
> Unless you're aware of the issue that I stumbled into last you'll walk
> into the trap. Space characters are not easy to see unless you poke
> around looking for them...
>
> Suggest you clean up that file so it's free of that easy-to-fall-into-trap.
>
> Sig
>
> On 22 February 2010 14:37, Ethan Jewett <es...@gmail.com> wrote:
>> Whew, that's a relief :-)
>>
>> On Mon, Feb 22, 2010 at 1:10 AM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan,
>>>
>>> you were right! So much easier to find errors when one knows where to look :)
>>>
>>> A single tailing space character after the rol.api_test line, sneaky
>>> little invisible character...
>>>
>>> My fault, used copy past using textmate. Next time vi only...
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Just to be sure:

Downloaded again the apache-esme-1.0-RC1-incubating.src.tar.gz from
http://people.apache.org/~rhirsch/esme/

md5 is correct

tar -xzvf locally

Used vi to inspect server/src/main/resources/props/default.props:

(851 k BTW - is 804 k when sorted out without any trailing spaces but
one line after the */)

Exactly same as I found last time:

32 spaces after the end */
14 spaces on the next line

Sig


On 23 February 2010 09:53, Richard Hirsch <hi...@gmail.com> wrote:
> @sig:  Are you sure?
>
> I checked the file and didn't see anything.
>
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-RC1-incubating/server/src/main/resources/props/default.props
>
> On Tue, Feb 23, 2010 at 8:36 AM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan / Dick
>>
>> Noticed that the default.props file that was included in today's RC
>> indeed had much trailing characters (spaces) so even if I used vi to
>> add the role.api_test line to it I had to clean it up first.
>>
>> Unless you're aware of the issue that I stumbled into last you'll walk
>> into the trap. Space characters are not easy to see unless you poke
>> around looking for them...
>>
>> Suggest you clean up that file so it's free of that easy-to-fall-into-trap.
>>
>> Sig
>>
>> On 22 February 2010 14:37, Ethan Jewett <es...@gmail.com> wrote:
>>> Whew, that's a relief :-)
>>>
>>> On Mon, Feb 22, 2010 at 1:10 AM, Sig Rinde <si...@rinde.com> wrote:
>>>> Ethan,
>>>>
>>>> you were right! So much easier to find errors when one knows where to look :)
>>>>
>>>> A single tailing space character after the rol.api_test line, sneaky
>>>> little invisible character...
>>>>
>>>> My fault, used copy past using textmate. Next time vi only...
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

@sig:  Are you sure?

I checked the file and didn't see anything.

https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-RC1-incubating/server/src/main/resources/props/default.props

On Tue, Feb 23, 2010 at 8:36 AM, Sig Rinde <si...@rinde.com> wrote:
> Ethan / Dick
>
> Noticed that the default.props file that was included in today's RC
> indeed had much trailing characters (spaces) so even if I used vi to
> add the role.api_test line to it I had to clean it up first.
>
> Unless you're aware of the issue that I stumbled into last you'll walk
> into the trap. Space characters are not easy to see unless you poke
> around looking for them...
>
> Suggest you clean up that file so it's free of that easy-to-fall-into-trap.
>
> Sig
>
> On 22 February 2010 14:37, Ethan Jewett <es...@gmail.com> wrote:
>> Whew, that's a relief :-)
>>
>> On Mon, Feb 22, 2010 at 1:10 AM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan,
>>>
>>> you were right! So much easier to find errors when one knows where to look :)
>>>
>>> A single tailing space character after the rol.api_test line, sneaky
>>> little invisible character...
>>>
>>> My fault, used copy past using textmate. Next time vi only...
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ethan / Dick

Noticed that the default.props file that was included in today's RC
indeed had much trailing characters (spaces) so even if I used vi to
add the role.api_test line to it I had to clean it up first.

Unless you're aware of the issue that I stumbled into last you'll walk
into the trap. Space characters are not easy to see unless you poke
around looking for them...

Suggest you clean up that file so it's free of that easy-to-fall-into-trap.

Sig

On 22 February 2010 14:37, Ethan Jewett <es...@gmail.com> wrote:
> Whew, that's a relief :-)
>
> On Mon, Feb 22, 2010 at 1:10 AM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan,
>>
>> you were right! So much easier to find errors when one knows where to look :)
>>
>> A single tailing space character after the rol.api_test line, sneaky
>> little invisible character...
>>
>> My fault, used copy past using textmate. Next time vi only...

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Whew, that's a relief :-)

On Mon, Feb 22, 2010 at 1:10 AM, Sig Rinde <si...@rinde.com> wrote:
> Ethan,
>
> you were right! So much easier to find errors when one knows where to look :)
>
> A single tailing space character after the rol.api_test line, sneaky
> little invisible character...
>
> My fault, used copy past using textmate. Next time vi only...
>
> Sorry for confusion.
>
> S
>
> On 22 February 2010 00:35, Ethan Jewett <es...@gmail.com> wrote:
>> Hi Sig,
>>
>> I'm guessing that there is something wrong with your default.props
>> file. I say this because pool creation does not require the
>> integration-admin role and is working. User creation does require the
>> integration-admin role and is not working. This indicates to me that
>> either the api_test user is not set up as an integration-admin or the
>> token you are using for your API calls from Thingamy belongs to a
>> different user.
>>
>> If you could also send the contents of the default.props file in your
>> server/src/main/resources/props and server/target/classes/props/
>> folders, that would be helpful. If the two are different, then you may
>> need to do a "mvn clean install" in order to pick up the changes
>> you've made.
>>
>> If *that* doesn't work, can you tell me the exact call you are making
>> to "api2/users" and then what the response code is?
>>
>> Ethan
>>
>> On Sun, Feb 21, 2010 at 3:14 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan,
>>>
>>> and sorry for me confusing :)
>>>
>>> The test_api line was/is in the default.props file, same as always.
>>>
>>> WIthout that I guess I could not have connected which it did, creating
>>> a pool as always. So far all as normal.
>>>
>>> It's when I want to add the other users and asking for a token in
>>> return nothing happens. Our side recieves nothing and the user I'm
>>> trying to add does not show as a user in ESME web interface.
>>>
>>> S
>>>
>>> On 21 February 2010 22:04, Ethan Jewett <es...@gmail.com> wrote:
>>>> Hi Sig,
>>>>
>>>> Yes, sorry for the confusion, you definitely need to add the api_test
>>>> line to default.props (you can just copy from test.default.props)
>>>> because you are using ESME in an integration scenario and making use
>>>> of the API methods that require the integration-admin role.
>>>>
>>>> Once you do this and create your api_test user (and token), you should
>>>> be able to go ahead. As far as I know, the only change since the last
>>>> release candidate is the change I made to default.props.
>>>>
>>>> Please let us know if you continue to have problems after doing this.
>>>>
>>>> Please also note, that there is no particular reason that you need to
>>>> have this user be called "api_test", but my understanding is that that
>>>> is the username you are using for Thingamy/ESME integration. If it is
>>>> actually a different user, please adjust the contexts of
>>>> test.default.props accordingly.
>>>>
>>>> Thanks,
>>>> Ethan
>>>>
>>>> On Sun, Feb 21, 2010 at 1:36 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>> Ethan, used the second option and it started up fine:
>>>>>
>>>>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>>>>>
>>>>> Added the api_test line to default.props, connecting to ESME using
>>>>> token worked, it created a pool as planned.
>>>>>
>>>>> Nothing to be seen in terminal stream from ESME server, on my side
>>>>> it's waiting for ESME token.
>>>>>
>>>>> What are the changes since the last that could affect my side?
>>>>>
>>>>> Same copy of same thingamy template, all same here.
>>>>>
>>>>> Sig
>>>>>
>>>>> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> Ha! Ok, let's see if I can figure out how to do this :-)
>>>>>>
>>>>>> In order to check out this tag into a folder called "esme_test", you
>>>>>> need to run the command: "svn checkout
>>>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>>>> esme_test"
>>>>>>
>>>>>> If you are not interested in a source-controlled copy of ESME, you can
>>>>>> just use the command: "svn export
>>>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>>>> esme_test"
>>>>>>
>>>>>> Ethan
>>>>>>
>>>>>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>> Ethan,
>>>>>>>
>>>>>>> remember I'm a geek-in-training!
>>>>>>>
>>>>>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>>>>>
>>>>>>> Eh?
>>>>>>>
>>>>>>> Please, something expanded and specific! :-)
>>>>>>>
>>>>>>> Sig
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ethan,

you were right! So much easier to find errors when one knows where to look :)

A single tailing space character after the rol.api_test line, sneaky
little invisible character...

My fault, used copy past using textmate. Next time vi only...

Sorry for confusion.

S

On 22 February 2010 00:35, Ethan Jewett <es...@gmail.com> wrote:
> Hi Sig,
>
> I'm guessing that there is something wrong with your default.props
> file. I say this because pool creation does not require the
> integration-admin role and is working. User creation does require the
> integration-admin role and is not working. This indicates to me that
> either the api_test user is not set up as an integration-admin or the
> token you are using for your API calls from Thingamy belongs to a
> different user.
>
> If you could also send the contents of the default.props file in your
> server/src/main/resources/props and server/target/classes/props/
> folders, that would be helpful. If the two are different, then you may
> need to do a "mvn clean install" in order to pick up the changes
> you've made.
>
> If *that* doesn't work, can you tell me the exact call you are making
> to "api2/users" and then what the response code is?
>
> Ethan
>
> On Sun, Feb 21, 2010 at 3:14 PM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan,
>>
>> and sorry for me confusing :)
>>
>> The test_api line was/is in the default.props file, same as always.
>>
>> WIthout that I guess I could not have connected which it did, creating
>> a pool as always. So far all as normal.
>>
>> It's when I want to add the other users and asking for a token in
>> return nothing happens. Our side recieves nothing and the user I'm
>> trying to add does not show as a user in ESME web interface.
>>
>> S
>>
>> On 21 February 2010 22:04, Ethan Jewett <es...@gmail.com> wrote:
>>> Hi Sig,
>>>
>>> Yes, sorry for the confusion, you definitely need to add the api_test
>>> line to default.props (you can just copy from test.default.props)
>>> because you are using ESME in an integration scenario and making use
>>> of the API methods that require the integration-admin role.
>>>
>>> Once you do this and create your api_test user (and token), you should
>>> be able to go ahead. As far as I know, the only change since the last
>>> release candidate is the change I made to default.props.
>>>
>>> Please let us know if you continue to have problems after doing this.
>>>
>>> Please also note, that there is no particular reason that you need to
>>> have this user be called "api_test", but my understanding is that that
>>> is the username you are using for Thingamy/ESME integration. If it is
>>> actually a different user, please adjust the contexts of
>>> test.default.props accordingly.
>>>
>>> Thanks,
>>> Ethan
>>>
>>> On Sun, Feb 21, 2010 at 1:36 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> Ethan, used the second option and it started up fine:
>>>>
>>>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>>>>
>>>> Added the api_test line to default.props, connecting to ESME using
>>>> token worked, it created a pool as planned.
>>>>
>>>> Nothing to be seen in terminal stream from ESME server, on my side
>>>> it's waiting for ESME token.
>>>>
>>>> What are the changes since the last that could affect my side?
>>>>
>>>> Same copy of same thingamy template, all same here.
>>>>
>>>> Sig
>>>>
>>>> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>>>>> Ha! Ok, let's see if I can figure out how to do this :-)
>>>>>
>>>>> In order to check out this tag into a folder called "esme_test", you
>>>>> need to run the command: "svn checkout
>>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>>> esme_test"
>>>>>
>>>>> If you are not interested in a source-controlled copy of ESME, you can
>>>>> just use the command: "svn export
>>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>>> esme_test"
>>>>>
>>>>> Ethan
>>>>>
>>>>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>> Ethan,
>>>>>>
>>>>>> remember I'm a geek-in-training!
>>>>>>
>>>>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>>>>
>>>>>> Eh?
>>>>>>
>>>>>> Please, something expanded and specific! :-)
>>>>>>
>>>>>> Sig
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Hi Sig,

I'm guessing that there is something wrong with your default.props
file. I say this because pool creation does not require the
integration-admin role and is working. User creation does require the
integration-admin role and is not working. This indicates to me that
either the api_test user is not set up as an integration-admin or the
token you are using for your API calls from Thingamy belongs to a
different user.

If you could also send the contents of the default.props file in your
server/src/main/resources/props and server/target/classes/props/
folders, that would be helpful. If the two are different, then you may
need to do a "mvn clean install" in order to pick up the changes
you've made.

If *that* doesn't work, can you tell me the exact call you are making
to "api2/users" and then what the response code is?

Ethan

On Sun, Feb 21, 2010 at 3:14 PM, Sig Rinde <si...@rinde.com> wrote:
> Ethan,
>
> and sorry for me confusing :)
>
> The test_api line was/is in the default.props file, same as always.
>
> WIthout that I guess I could not have connected which it did, creating
> a pool as always. So far all as normal.
>
> It's when I want to add the other users and asking for a token in
> return nothing happens. Our side recieves nothing and the user I'm
> trying to add does not show as a user in ESME web interface.
>
> S
>
> On 21 February 2010 22:04, Ethan Jewett <es...@gmail.com> wrote:
>> Hi Sig,
>>
>> Yes, sorry for the confusion, you definitely need to add the api_test
>> line to default.props (you can just copy from test.default.props)
>> because you are using ESME in an integration scenario and making use
>> of the API methods that require the integration-admin role.
>>
>> Once you do this and create your api_test user (and token), you should
>> be able to go ahead. As far as I know, the only change since the last
>> release candidate is the change I made to default.props.
>>
>> Please let us know if you continue to have problems after doing this.
>>
>> Please also note, that there is no particular reason that you need to
>> have this user be called "api_test", but my understanding is that that
>> is the username you are using for Thingamy/ESME integration. If it is
>> actually a different user, please adjust the contexts of
>> test.default.props accordingly.
>>
>> Thanks,
>> Ethan
>>
>> On Sun, Feb 21, 2010 at 1:36 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan, used the second option and it started up fine:
>>>
>>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>>>
>>> Added the api_test line to default.props, connecting to ESME using
>>> token worked, it created a pool as planned.
>>>
>>> Nothing to be seen in terminal stream from ESME server, on my side
>>> it's waiting for ESME token.
>>>
>>> What are the changes since the last that could affect my side?
>>>
>>> Same copy of same thingamy template, all same here.
>>>
>>> Sig
>>>
>>> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>>>> Ha! Ok, let's see if I can figure out how to do this :-)
>>>>
>>>> In order to check out this tag into a folder called "esme_test", you
>>>> need to run the command: "svn checkout
>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>> esme_test"
>>>>
>>>> If you are not interested in a source-controlled copy of ESME, you can
>>>> just use the command: "svn export
>>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>>> esme_test"
>>>>
>>>> Ethan
>>>>
>>>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>> Ethan,
>>>>>
>>>>> remember I'm a geek-in-training!
>>>>>
>>>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>>>
>>>>> Eh?
>>>>>
>>>>> Please, something expanded and specific! :-)
>>>>>
>>>>> Sig
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ethan,

and sorry for me confusing :)

The test_api line was/is in the default.props file, same as always.

WIthout that I guess I could not have connected which it did, creating
a pool as always. So far all as normal.

It's when I want to add the other users and asking for a token in
return nothing happens. Our side recieves nothing and the user I'm
trying to add does not show as a user in ESME web interface.

S

On 21 February 2010 22:04, Ethan Jewett <es...@gmail.com> wrote:
> Hi Sig,
>
> Yes, sorry for the confusion, you definitely need to add the api_test
> line to default.props (you can just copy from test.default.props)
> because you are using ESME in an integration scenario and making use
> of the API methods that require the integration-admin role.
>
> Once you do this and create your api_test user (and token), you should
> be able to go ahead. As far as I know, the only change since the last
> release candidate is the change I made to default.props.
>
> Please let us know if you continue to have problems after doing this.
>
> Please also note, that there is no particular reason that you need to
> have this user be called "api_test", but my understanding is that that
> is the username you are using for Thingamy/ESME integration. If it is
> actually a different user, please adjust the contexts of
> test.default.props accordingly.
>
> Thanks,
> Ethan
>
> On Sun, Feb 21, 2010 at 1:36 PM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan, used the second option and it started up fine:
>>
>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>>
>> Added the api_test line to default.props, connecting to ESME using
>> token worked, it created a pool as planned.
>>
>> Nothing to be seen in terminal stream from ESME server, on my side
>> it's waiting for ESME token.
>>
>> What are the changes since the last that could affect my side?
>>
>> Same copy of same thingamy template, all same here.
>>
>> Sig
>>
>> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>>> Ha! Ok, let's see if I can figure out how to do this :-)
>>>
>>> In order to check out this tag into a folder called "esme_test", you
>>> need to run the command: "svn checkout
>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>> esme_test"
>>>
>>> If you are not interested in a source-controlled copy of ESME, you can
>>> just use the command: "svn export
>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>> esme_test"
>>>
>>> Ethan
>>>
>>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> Ethan,
>>>>
>>>> remember I'm a geek-in-training!
>>>>
>>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>>
>>>> Eh?
>>>>
>>>> Please, something expanded and specific! :-)
>>>>
>>>> Sig
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Hi Sig,

Yes, sorry for the confusion, you definitely need to add the api_test
line to default.props (you can just copy from test.default.props)
because you are using ESME in an integration scenario and making use
of the API methods that require the integration-admin role.

Once you do this and create your api_test user (and token), you should
be able to go ahead. As far as I know, the only change since the last
release candidate is the change I made to default.props.

Please let us know if you continue to have problems after doing this.

Please also note, that there is no particular reason that you need to
have this user be called "api_test", but my understanding is that that
is the username you are using for Thingamy/ESME integration. If it is
actually a different user, please adjust the contexts of
test.default.props accordingly.

Thanks,
Ethan

On Sun, Feb 21, 2010 at 1:36 PM, Sig Rinde <si...@rinde.com> wrote:
> Ethan, used the second option and it started up fine:
>
> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>
> Added the api_test line to default.props, connecting to ESME using
> token worked, it created a pool as planned.
>
> Nothing to be seen in terminal stream from ESME server, on my side
> it's waiting for ESME token.
>
> What are the changes since the last that could affect my side?
>
> Same copy of same thingamy template, all same here.
>
> Sig
>
> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>> Ha! Ok, let's see if I can figure out how to do this :-)
>>
>> In order to check out this tag into a folder called "esme_test", you
>> need to run the command: "svn checkout
>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>> esme_test"
>>
>> If you are not interested in a source-controlled copy of ESME, you can
>> just use the command: "svn export
>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>> esme_test"
>>
>> Ethan
>>
>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan,
>>>
>>> remember I'm a geek-in-training!
>>>
>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>
>>> Eh?
>>>
>>> Please, something expanded and specific! :-)
>>>
>>> Sig
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Sun, Feb 21, 2010 at 10:05 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>>
>> Is it just the function to create tokens or does the function creating
>> users fail as well?
>
> User creation fails, none can be seen in the ESME web interface, hence
> (I guess) no token sent back.
>
>>>
>>> Added the api_test line to default.props, connecting to ESME using
>>> token worked, it created a pool as planned.
>>
>> I'm confused. Does it work or not after adding the line to default.props?
>
> Sorry: It does not work. That line should affect the first step,
> connecting the system which creates a pool - which I can see in ESME
> web interface having been created.
>
> In other words, user creation does not work. Which it did in the last
> RC using same setup.

Was this the last RC that is still available here:
http://people.apache.org/~rhirsch/esme/ ?

The only change was Ethan's change of the default.props

>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>
> Is it just the function to create tokens or does the function creating
> users fail as well?

User creation fails, none can be seen in the ESME web interface, hence
(I guess) no token sent back.

>>
>> Added the api_test line to default.props, connecting to ESME using
>> token worked, it created a pool as planned.
>
> I'm confused. Does it work or not after adding the line to default.props?

Sorry: It does not work. That line should affect the first step,
connecting the system which creates a pool - which I can see in ESME
web interface having been created.

In other words, user creation does not work. Which it did in the last
RC using same setup.

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

Do the API2 tests work correctly?

try "mvn test"

On Sun, Feb 21, 2010 at 9:54 PM, Richard Hirsch <hi...@gmail.com> wrote:
> On Sun, Feb 21, 2010 at 8:36 PM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan, used the second option and it started up fine:
>>
>> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.
>
> Is it just the function to create tokens or does the function creating
> users fail as well?
>
>>
>> Added the api_test line to default.props, connecting to ESME using
>> token worked, it created a pool as planned.
>
> I'm confused. Does it work or not after adding the line to default.props?
>
>>
>> Nothing to be seen in terminal stream from ESME server, on my side
>> it's waiting for ESME token.
>>
>> What are the changes since the last that could affect my side?
>>
>> Same copy of same thingamy template, all same here.
>>
>> Sig
>>
>> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>>> Ha! Ok, let's see if I can figure out how to do this :-)
>>>
>>> In order to check out this tag into a folder called "esme_test", you
>>> need to run the command: "svn checkout
>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>> esme_test"
>>>
>>> If you are not interested in a source-controlled copy of ESME, you can
>>> just use the command: "svn export
>>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>>> esme_test"
>>>
>>> Ethan
>>>
>>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> Ethan,
>>>>
>>>> remember I'm a geek-in-training!
>>>>
>>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>>
>>>> Eh?
>>>>
>>>> Please, something expanded and specific! :-)
>>>>
>>>> Sig
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Sun, Feb 21, 2010 at 8:36 PM, Sig Rinde <si...@rinde.com> wrote:
> Ethan, used the second option and it started up fine:
>
> Now I suddenly cannot create tokens for users in Thingamy any more... hmm.

Is it just the function to create tokens or does the function creating
users fail as well?

>
> Added the api_test line to default.props, connecting to ESME using
> token worked, it created a pool as planned.

I'm confused. Does it work or not after adding the line to default.props?

>
> Nothing to be seen in terminal stream from ESME server, on my side
> it's waiting for ESME token.
>
> What are the changes since the last that could affect my side?
>
> Same copy of same thingamy template, all same here.
>
> Sig
>
> On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
>> Ha! Ok, let's see if I can figure out how to do this :-)
>>
>> In order to check out this tag into a folder called "esme_test", you
>> need to run the command: "svn checkout
>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>> esme_test"
>>
>> If you are not interested in a source-controlled copy of ESME, you can
>> just use the command: "svn export
>> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
>> esme_test"
>>
>> Ethan
>>
>> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Ethan,
>>>
>>> remember I'm a geek-in-training!
>>>
>>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>>
>>> Eh?
>>>
>>> Please, something expanded and specific! :-)
>>>
>>> Sig
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ethan, used the second option and it started up fine:

Now I suddenly cannot create tokens for users in Thingamy any more... hmm.

Added the api_test line to default.props, connecting to ESME using
token worked, it created a pool as planned.

Nothing to be seen in terminal stream from ESME server, on my side
it's waiting for ESME token.

What are the changes since the last that could affect my side?

Same copy of same thingamy template, all same here.

Sig

On 21 February 2010 20:04, Ethan Jewett <es...@gmail.com> wrote:
> Ha! Ok, let's see if I can figure out how to do this :-)
>
> In order to check out this tag into a folder called "esme_test", you
> need to run the command: "svn checkout
> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
> esme_test"
>
> If you are not interested in a source-controlled copy of ESME, you can
> just use the command: "svn export
> http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
> esme_test"
>
> Ethan
>
> On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
>> Ethan,
>>
>> remember I'm a geek-in-training!
>>
>>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>>
>> Eh?
>>
>> Please, something expanded and specific! :-)
>>
>> Sig
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Ha! Ok, let's see if I can figure out how to do this :-)

In order to check out this tag into a folder called "esme_test", you
need to run the command: "svn checkout
http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
esme_test"

If you are not interested in a source-controlled copy of ESME, you can
just use the command: "svn export
http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating
esme_test"

Ethan

On Sun, Feb 21, 2010 at 12:30 PM, Sig Rinde <si...@rinde.com> wrote:
> Ethan,
>
> remember I'm a geek-in-training!
>
>> Just the usual SVN process, but grab the tag instead of the trunk :-)
>
> Eh?
>
> Please, something expanded and specific! :-)
>
> Sig
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Ethan,

remember I'm a geek-in-training!

> Just the usual SVN process, but grab the tag instead of the trunk :-)

Eh?

Please, something expanded and specific! :-)

Sig

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Hi Sig,

Just the usual SVN process, but grab the tag instead of the trunk :-)

ESME is set up to default to the file system store for compass
("/props/compass.cfg.xml" actually) so there is no need to define a
configuration file in your default.props unless you want something
different. Search is working for me with the current tag, so I hope it
works for you too!

Ethan

On Sun, Feb 21, 2010 at 12:07 PM, Sig Rinde <si...@rinde.com> wrote:
> Got a tar file or shall I do the usual svn?
>
> Noticed that the default.props file do not have
> "compass_config_file=/props/compass.filesystem.cfg.xml" anymore.
> Compass/search etc still working now? :)
>
>
> On 21 February 2010 18:59, Richard Hirsch <hi...@gmail.com> wrote:
>> @sig - thanks for finding the bugs - the more bugs found, the higher
>> quality of ESME - and then everyone wins.
>>
>> If you want to get a head start on testing the new RC - just take a
>> look here: https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>
>> I'll do some tests tomorrow during the day and then start a vote in the evening.
>>
>> D.
>>
>> On Sun, Feb 21, 2010 at 6:22 PM, Sig Rinde <si...@rinde.com> wrote:
>>> Great work folks, interesting process to follow I must say
>>
>> I also find it interesting - especially comparing the release process
>> in a "community-based" / ASF project to releases in the corporate
>> world.
>>
>>>
>>> And sorry for messing up, keep in mind for next time I'm really good
>>> at stumbling over bugs, i.e. mess up, so set me to test work early =)
>>>
>>> Sig
>>>
>>> On 21 February 2010 17:55, Ethan Jewett <es...@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> Thanks for humoring my concerns, and again for all the work you're doing Dick.
>>>>
>>>> I've checked out the new tag and tested it. It passes all unit tests,
>>>> search is working out of the box, and the security hole is closed.
>>>> From my point of view, we're ready for a vote.
>>>>
>>>> Thanks,
>>>> Ethan
>>>>
>>>> On Sun, Feb 21, 2010 at 10:08 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> OK.
>>>>>
>>>>> I've tagged a new Release Candidate:
>>>>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>>>>
>>>>> This means that we have to vote again (sigh!) -.
>>>>>
>>>>> This time I suggest we test the tagged RC before we do a vote.
>>>>>
>>>>> D.
>>>>>
>>>>> On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> For the original issue, where doing nothing simply results in a loss
>>>>>> of functionality, I would agree. However, I think this is a major
>>>>>> security hole that requires that the person deploying the software to
>>>>>> take a specific action. If they don't take this action, then their
>>>>>> deployment is vulnerable. I'm not comfortable putting the ESME stamp
>>>>>> on a release that we know has this kind of issue. I think it's worth
>>>>>> spending the extra time to address this issue and set the precedent
>>>>>> that we don't release software with known security holes.
>>>>>>
>>>>>> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
>>>>>> even know if I can :-), so if a majority have voted for release after
>>>>>> 72 hours (which I think is the case), then feel free to go ahead.
>>>>>>
>>>>>> Ethan
>>>>>>
>>>>>> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>> I agree with Bertrand.
>>>>>>>
>>>>>>> I'd like to get this release out and then do a another release soon to
>>>>>>> fix the errors.
>>>>>>>
>>>>>>> Right now, there are the two issues that have to be changed and Ethan
>>>>>>> has already changed them in SVN.
>>>>>>>
>>>>>>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>>>>>>confuse people.
>>>>>>> The fact that search doesn't work is IMHO the lesser of the two
>>>>>>> errors. Does the API2 not work at all or is the problem more the
>>>>>>> security one associated with the "role.api_test=integration-admin"
>>>>>>> setting?
>>>>>>>
>>>>>>> I'm reluctant to cut a new release , because then we'd have to start
>>>>>>> over again. Like I've said, I see this first release as a learning
>>>>>>> experience. No release will be perfect and will always include a few
>>>>>>> bugs. I'd rather get this release out and then do another release in 2
>>>>>>> weeks time with the bug fixes.  Now that we know how to do create
>>>>>>> releases it will be easier the next time.  We should get used to
>>>>>>>
>>>>>>> I'd rather describe the two changes that have to made in the resource
>>>>>>> files in a blog post or on the wiki and then push for a new release.
>>>>>>>
>>>>>>> Anyone else have thoughts on this
>>>>>>>
>>>>>>> D.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>>>>>>> <bd...@apache.org> wrote:
>>>>>>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>>>> ...Maybe making this two-line change to one file is small enough that we
>>>>>>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>>>>>>
>>>>>>>> Anything that changes the release artifacts needs a new vote.
>>>>>>>>
>>>>>>>> On the other hand, if there's a workaround (IIUC people can change
>>>>>>>> something manually to get things to work?) I suggest releasing as is.
>>>>>>>>
>>>>>>>> Nothing prevents you from making another release soon, if needed.
>>>>>>>> Getting used to releasing is good progress towards graduation ;-)
>>>>>>>>
>>>>>>>> -Bertrand
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Got a tar file or shall I do the usual svn?

Noticed that the default.props file do not have
"compass_config_file=/props/compass.filesystem.cfg.xml" anymore.
Compass/search etc still working now? :)


On 21 February 2010 18:59, Richard Hirsch <hi...@gmail.com> wrote:
> @sig - thanks for finding the bugs - the more bugs found, the higher
> quality of ESME - and then everyone wins.
>
> If you want to get a head start on testing the new RC - just take a
> look here: https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>
> I'll do some tests tomorrow during the day and then start a vote in the evening.
>
> D.
>
> On Sun, Feb 21, 2010 at 6:22 PM, Sig Rinde <si...@rinde.com> wrote:
>> Great work folks, interesting process to follow I must say
>
> I also find it interesting - especially comparing the release process
> in a "community-based" / ASF project to releases in the corporate
> world.
>
>>
>> And sorry for messing up, keep in mind for next time I'm really good
>> at stumbling over bugs, i.e. mess up, so set me to test work early =)
>>
>> Sig
>>
>> On 21 February 2010 17:55, Ethan Jewett <es...@gmail.com> wrote:
>>> Hi,
>>>
>>> Thanks for humoring my concerns, and again for all the work you're doing Dick.
>>>
>>> I've checked out the new tag and tested it. It passes all unit tests,
>>> search is working out of the box, and the security hole is closed.
>>> From my point of view, we're ready for a vote.
>>>
>>> Thanks,
>>> Ethan
>>>
>>> On Sun, Feb 21, 2010 at 10:08 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> OK.
>>>>
>>>> I've tagged a new Release Candidate:
>>>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>>>
>>>> This means that we have to vote again (sigh!) -.
>>>>
>>>> This time I suggest we test the tagged RC before we do a vote.
>>>>
>>>> D.
>>>>
>>>> On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>>> Hi all,
>>>>>
>>>>> For the original issue, where doing nothing simply results in a loss
>>>>> of functionality, I would agree. However, I think this is a major
>>>>> security hole that requires that the person deploying the software to
>>>>> take a specific action. If they don't take this action, then their
>>>>> deployment is vulnerable. I'm not comfortable putting the ESME stamp
>>>>> on a release that we know has this kind of issue. I think it's worth
>>>>> spending the extra time to address this issue and set the precedent
>>>>> that we don't release software with known security holes.
>>>>>
>>>>> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
>>>>> even know if I can :-), so if a majority have voted for release after
>>>>> 72 hours (which I think is the case), then feel free to go ahead.
>>>>>
>>>>> Ethan
>>>>>
>>>>> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>> I agree with Bertrand.
>>>>>>
>>>>>> I'd like to get this release out and then do a another release soon to
>>>>>> fix the errors.
>>>>>>
>>>>>> Right now, there are the two issues that have to be changed and Ethan
>>>>>> has already changed them in SVN.
>>>>>>
>>>>>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>>>>>confuse people.
>>>>>> The fact that search doesn't work is IMHO the lesser of the two
>>>>>> errors. Does the API2 not work at all or is the problem more the
>>>>>> security one associated with the "role.api_test=integration-admin"
>>>>>> setting?
>>>>>>
>>>>>> I'm reluctant to cut a new release , because then we'd have to start
>>>>>> over again. Like I've said, I see this first release as a learning
>>>>>> experience. No release will be perfect and will always include a few
>>>>>> bugs. I'd rather get this release out and then do another release in 2
>>>>>> weeks time with the bug fixes.  Now that we know how to do create
>>>>>> releases it will be easier the next time.  We should get used to
>>>>>>
>>>>>> I'd rather describe the two changes that have to made in the resource
>>>>>> files in a blog post or on the wiki and then push for a new release.
>>>>>>
>>>>>> Anyone else have thoughts on this
>>>>>>
>>>>>> D.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>>>>>> <bd...@apache.org> wrote:
>>>>>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>>> ...Maybe making this two-line change to one file is small enough that we
>>>>>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>>>>>
>>>>>>> Anything that changes the release artifacts needs a new vote.
>>>>>>>
>>>>>>> On the other hand, if there's a workaround (IIUC people can change
>>>>>>> something manually to get things to work?) I suggest releasing as is.
>>>>>>>
>>>>>>> Nothing prevents you from making another release soon, if needed.
>>>>>>> Getting used to releasing is good progress towards graduation ;-)
>>>>>>>
>>>>>>> -Bertrand
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

@sig - thanks for finding the bugs - the more bugs found, the higher
quality of ESME - and then everyone wins.

If you want to get a head start on testing the new RC - just take a
look here: https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/

I'll do some tests tomorrow during the day and then start a vote in the evening.

D.

On Sun, Feb 21, 2010 at 6:22 PM, Sig Rinde <si...@rinde.com> wrote:
> Great work folks, interesting process to follow I must say

I also find it interesting - especially comparing the release process
in a "community-based" / ASF project to releases in the corporate
world.

>
> And sorry for messing up, keep in mind for next time I'm really good
> at stumbling over bugs, i.e. mess up, so set me to test work early =)
>
> Sig
>
> On 21 February 2010 17:55, Ethan Jewett <es...@gmail.com> wrote:
>> Hi,
>>
>> Thanks for humoring my concerns, and again for all the work you're doing Dick.
>>
>> I've checked out the new tag and tested it. It passes all unit tests,
>> search is working out of the box, and the security hole is closed.
>> From my point of view, we're ready for a vote.
>>
>> Thanks,
>> Ethan
>>
>> On Sun, Feb 21, 2010 at 10:08 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> OK.
>>>
>>> I've tagged a new Release Candidate:
>>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>>
>>> This means that we have to vote again (sigh!) -.
>>>
>>> This time I suggest we test the tagged RC before we do a vote.
>>>
>>> D.
>>>
>>> On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
>>>> Hi all,
>>>>
>>>> For the original issue, where doing nothing simply results in a loss
>>>> of functionality, I would agree. However, I think this is a major
>>>> security hole that requires that the person deploying the software to
>>>> take a specific action. If they don't take this action, then their
>>>> deployment is vulnerable. I'm not comfortable putting the ESME stamp
>>>> on a release that we know has this kind of issue. I think it's worth
>>>> spending the extra time to address this issue and set the precedent
>>>> that we don't release software with known security holes.
>>>>
>>>> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
>>>> even know if I can :-), so if a majority have voted for release after
>>>> 72 hours (which I think is the case), then feel free to go ahead.
>>>>
>>>> Ethan
>>>>
>>>> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> I agree with Bertrand.
>>>>>
>>>>> I'd like to get this release out and then do a another release soon to
>>>>> fix the errors.
>>>>>
>>>>> Right now, there are the two issues that have to be changed and Ethan
>>>>> has already changed them in SVN.
>>>>>
>>>>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>>>>confuse people.
>>>>> The fact that search doesn't work is IMHO the lesser of the two
>>>>> errors. Does the API2 not work at all or is the problem more the
>>>>> security one associated with the "role.api_test=integration-admin"
>>>>> setting?
>>>>>
>>>>> I'm reluctant to cut a new release , because then we'd have to start
>>>>> over again. Like I've said, I see this first release as a learning
>>>>> experience. No release will be perfect and will always include a few
>>>>> bugs. I'd rather get this release out and then do another release in 2
>>>>> weeks time with the bug fixes.  Now that we know how to do create
>>>>> releases it will be easier the next time.  We should get used to
>>>>>
>>>>> I'd rather describe the two changes that have to made in the resource
>>>>> files in a blog post or on the wiki and then push for a new release.
>>>>>
>>>>> Anyone else have thoughts on this
>>>>>
>>>>> D.
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>>>>> <bd...@apache.org> wrote:
>>>>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>>> ...Maybe making this two-line change to one file is small enough that we
>>>>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>>>>
>>>>>> Anything that changes the release artifacts needs a new vote.
>>>>>>
>>>>>> On the other hand, if there's a workaround (IIUC people can change
>>>>>> something manually to get things to work?) I suggest releasing as is.
>>>>>>
>>>>>> Nothing prevents you from making another release soon, if needed.
>>>>>> Getting used to releasing is good progress towards graduation ;-)
>>>>>>
>>>>>> -Bertrand
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Great work folks, interesting process to follow I must say!

And sorry for messing up, keep in mind for next time I'm really good
at stumbling over bugs, i.e. mess up, so set me to test work early =)

Sig

On 21 February 2010 17:55, Ethan Jewett <es...@gmail.com> wrote:
> Hi,
>
> Thanks for humoring my concerns, and again for all the work you're doing Dick.
>
> I've checked out the new tag and tested it. It passes all unit tests,
> search is working out of the box, and the security hole is closed.
> From my point of view, we're ready for a vote.
>
> Thanks,
> Ethan
>
> On Sun, Feb 21, 2010 at 10:08 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> OK.
>>
>> I've tagged a new Release Candidate:
>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>
>> This means that we have to vote again (sigh!) -.
>>
>> This time I suggest we test the tagged RC before we do a vote.
>>
>> D.
>>
>> On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
>>> Hi all,
>>>
>>> For the original issue, where doing nothing simply results in a loss
>>> of functionality, I would agree. However, I think this is a major
>>> security hole that requires that the person deploying the software to
>>> take a specific action. If they don't take this action, then their
>>> deployment is vulnerable. I'm not comfortable putting the ESME stamp
>>> on a release that we know has this kind of issue. I think it's worth
>>> spending the extra time to address this issue and set the precedent
>>> that we don't release software with known security holes.
>>>
>>> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
>>> even know if I can :-), so if a majority have voted for release after
>>> 72 hours (which I think is the case), then feel free to go ahead.
>>>
>>> Ethan
>>>
>>> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> I agree with Bertrand.
>>>>
>>>> I'd like to get this release out and then do a another release soon to
>>>> fix the errors.
>>>>
>>>> Right now, there are the two issues that have to be changed and Ethan
>>>> has already changed them in SVN.
>>>>
>>>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>>>confuse people.
>>>> The fact that search doesn't work is IMHO the lesser of the two
>>>> errors. Does the API2 not work at all or is the problem more the
>>>> security one associated with the "role.api_test=integration-admin"
>>>> setting?
>>>>
>>>> I'm reluctant to cut a new release , because then we'd have to start
>>>> over again. Like I've said, I see this first release as a learning
>>>> experience. No release will be perfect and will always include a few
>>>> bugs. I'd rather get this release out and then do another release in 2
>>>> weeks time with the bug fixes.  Now that we know how to do create
>>>> releases it will be easier the next time.  We should get used to
>>>>
>>>> I'd rather describe the two changes that have to made in the resource
>>>> files in a blog post or on the wiki and then push for a new release.
>>>>
>>>> Anyone else have thoughts on this
>>>>
>>>> D.
>>>>
>>>>
>>>>
>>>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>>>> <bd...@apache.org> wrote:
>>>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>>>> ...Maybe making this two-line change to one file is small enough that we
>>>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>>>
>>>>> Anything that changes the release artifacts needs a new vote.
>>>>>
>>>>> On the other hand, if there's a workaround (IIUC people can change
>>>>> something manually to get things to work?) I suggest releasing as is.
>>>>>
>>>>> Nothing prevents you from making another release soon, if needed.
>>>>> Getting used to releasing is good progress towards graduation ;-)
>>>>>
>>>>> -Bertrand
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Hi,

Thanks for humoring my concerns, and again for all the work you're doing Dick.

I've checked out the new tag and tested it. It passes all unit tests,
search is working out of the box, and the security hole is closed.
>From my point of view, we're ready for a vote.

Thanks,
Ethan

On Sun, Feb 21, 2010 at 10:08 AM, Richard Hirsch <hi...@gmail.com> wrote:
> OK.
>
> I've tagged a new Release Candidate:
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>
> This means that we have to vote again (sigh!) -.
>
> This time I suggest we test the tagged RC before we do a vote.
>
> D.
>
> On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
>> Hi all,
>>
>> For the original issue, where doing nothing simply results in a loss
>> of functionality, I would agree. However, I think this is a major
>> security hole that requires that the person deploying the software to
>> take a specific action. If they don't take this action, then their
>> deployment is vulnerable. I'm not comfortable putting the ESME stamp
>> on a release that we know has this kind of issue. I think it's worth
>> spending the extra time to address this issue and set the precedent
>> that we don't release software with known security holes.
>>
>> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
>> even know if I can :-), so if a majority have voted for release after
>> 72 hours (which I think is the case), then feel free to go ahead.
>>
>> Ethan
>>
>> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> I agree with Bertrand.
>>>
>>> I'd like to get this release out and then do a another release soon to
>>> fix the errors.
>>>
>>> Right now, there are the two issues that have to be changed and Ethan
>>> has already changed them in SVN.
>>>
>>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>>confuse people.
>>> The fact that search doesn't work is IMHO the lesser of the two
>>> errors. Does the API2 not work at all or is the problem more the
>>> security one associated with the "role.api_test=integration-admin"
>>> setting?
>>>
>>> I'm reluctant to cut a new release , because then we'd have to start
>>> over again. Like I've said, I see this first release as a learning
>>> experience. No release will be perfect and will always include a few
>>> bugs. I'd rather get this release out and then do another release in 2
>>> weeks time with the bug fixes.  Now that we know how to do create
>>> releases it will be easier the next time.  We should get used to
>>>
>>> I'd rather describe the two changes that have to made in the resource
>>> files in a blog post or on the wiki and then push for a new release.
>>>
>>> Anyone else have thoughts on this
>>>
>>> D.
>>>
>>>
>>>
>>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>>> <bd...@apache.org> wrote:
>>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>>> ...Maybe making this two-line change to one file is small enough that we
>>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>>
>>>> Anything that changes the release artifacts needs a new vote.
>>>>
>>>> On the other hand, if there's a workaround (IIUC people can change
>>>> something manually to get things to work?) I suggest releasing as is.
>>>>
>>>> Nothing prevents you from making another release soon, if needed.
>>>> Getting used to releasing is good progress towards graduation ;-)
>>>>
>>>> -Bertrand
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Sun, Feb 21, 2010 at 7:15 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Sun, Feb 21, 2010 at 5:08 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> OK.
>>
>> I've tagged a new Release Candidate:
>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>>
>> This means that we have to vote again (sigh!) -.
>>
>> This time I suggest we test the tagged RC before we do a vote.
>
> While at it, may I suggest the release to be explicitly labeled
> 1.0RC1? There seem to be some rough edges in the process at least and
> possibly somewhere in the code - maybe it would be best to seed a
> release candidate or two in short cycles and gather additional peer
> review rather than slapping an overpromising 1.0 on the release name?

Excellent idea. Will do.

Can I use the same tag or should I create a new SVN tag as well.
Ideally, I could use the existing tag and just rename the tar file for
the release.

> Plain 1.0 might generate expectations, whilst RCs are generally
> believed to be workable enough, yet still have some i's to dot.
>
> For one, I'd be more comfortable in +1'ing releases - I held back mine
> as I wanted to so some tests when this bug report came in.
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Gianugo Rabellino <g....@sourcesense.com>]

On Sun, Feb 21, 2010 at 5:08 PM, Richard Hirsch <hi...@gmail.com> wrote:
> OK.
>
> I've tagged a new Release Candidate:
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/
>
> This means that we have to vote again (sigh!) -.
>
> This time I suggest we test the tagged RC before we do a vote.

While at it, may I suggest the release to be explicitly labeled
1.0RC1? There seem to be some rough edges in the process at least and
possibly somewhere in the code - maybe it would be best to seed a
release candidate or two in short cycles and gather additional peer
review rather than slapping an overpromising 1.0 on the release name?
Plain 1.0 might generate expectations, whilst RCs are generally
believed to be workable enough, yet still have some i's to dot.

For one, I'd be more comfortable in +1'ing releases - I held back mine
as I wanted to so some tests when this bug report came in.

-- 
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

OK.

I've tagged a new Release Candidate:
https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/

This means that we have to vote again (sigh!) -.

This time I suggest we test the tagged RC before we do a vote.

D.

On Sun, Feb 21, 2010 at 12:49 AM, Ethan Jewett <es...@gmail.com> wrote:
> Hi all,
>
> For the original issue, where doing nothing simply results in a loss
> of functionality, I would agree. However, I think this is a major
> security hole that requires that the person deploying the software to
> take a specific action. If they don't take this action, then their
> deployment is vulnerable. I'm not comfortable putting the ESME stamp
> on a release that we know has this kind of issue. I think it's worth
> spending the extra time to address this issue and set the precedent
> that we don't release software with known security holes.
>
> I'm sticking with my -1 at this point. I'm not trying to veto (I don't
> even know if I can :-), so if a majority have voted for release after
> 72 hours (which I think is the case), then feel free to go ahead.
>
> Ethan
>
> On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> I agree with Bertrand.
>>
>> I'd like to get this release out and then do a another release soon to
>> fix the errors.
>>
>> Right now, there are the two issues that have to be changed and Ethan
>> has already changed them in SVN.
>>
>>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>>confuse people.
>> The fact that search doesn't work is IMHO the lesser of the two
>> errors. Does the API2 not work at all or is the problem more the
>> security one associated with the "role.api_test=integration-admin"
>> setting?
>>
>> I'm reluctant to cut a new release , because then we'd have to start
>> over again. Like I've said, I see this first release as a learning
>> experience. No release will be perfect and will always include a few
>> bugs. I'd rather get this release out and then do another release in 2
>> weeks time with the bug fixes.  Now that we know how to do create
>> releases it will be easier the next time.  We should get used to
>>
>> I'd rather describe the two changes that have to made in the resource
>> files in a blog post or on the wiki and then push for a new release.
>>
>> Anyone else have thoughts on this
>>
>> D.
>>
>>
>>
>> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
>> <bd...@apache.org> wrote:
>>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>> ...Maybe making this two-line change to one file is small enough that we
>>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>>
>>> Anything that changes the release artifacts needs a new vote.
>>>
>>> On the other hand, if there's a workaround (IIUC people can change
>>> something manually to get things to work?) I suggest releasing as is.
>>>
>>> Nothing prevents you from making another release soon, if needed.
>>> Getting used to releasing is good progress towards graduation ;-)
>>>
>>> -Bertrand
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Hi all,

For the original issue, where doing nothing simply results in a loss
of functionality, I would agree. However, I think this is a major
security hole that requires that the person deploying the software to
take a specific action. If they don't take this action, then their
deployment is vulnerable. I'm not comfortable putting the ESME stamp
on a release that we know has this kind of issue. I think it's worth
spending the extra time to address this issue and set the precedent
that we don't release software with known security holes.

I'm sticking with my -1 at this point. I'm not trying to veto (I don't
even know if I can :-), so if a majority have voted for release after
72 hours (which I think is the case), then feel free to go ahead.

Ethan

On Sat, Feb 20, 2010 at 3:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
> I agree with Bertrand.
>
> I'd like to get this release out and then do a another release soon to
> fix the errors.
>
> Right now, there are the two issues that have to be changed and Ethan
> has already changed them in SVN.
>
>>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>>confuse people.
> The fact that search doesn't work is IMHO the lesser of the two
> errors. Does the API2 not work at all or is the problem more the
> security one associated with the "role.api_test=integration-admin"
> setting?
>
> I'm reluctant to cut a new release , because then we'd have to start
> over again. Like I've said, I see this first release as a learning
> experience. No release will be perfect and will always include a few
> bugs. I'd rather get this release out and then do another release in 2
> weeks time with the bug fixes.  Now that we know how to do create
> releases it will be easier the next time.  We should get used to
>
> I'd rather describe the two changes that have to made in the resource
> files in a blog post or on the wiki and then push for a new release.
>
> Anyone else have thoughts on this
>
> D.
>
>
>
> On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>>> ...Maybe making this two-line change to one file is small enough that we
>>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>>
>> Anything that changes the release artifacts needs a new vote.
>>
>> On the other hand, if there's a workaround (IIUC people can change
>> something manually to get things to work?) I suggest releasing as is.
>>
>> Nothing prevents you from making another release soon, if needed.
>> Getting used to releasing is good progress towards graduation ;-)
>>
>> -Bertrand
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

I agree with Bertrand.

I'd like to get this release out and then do a another release soon to
fix the errors.

Right now, there are the two issues that have to be changed and Ethan
has already changed them in SVN.

>I believe that this will happen on any system and I think the fact that search and the API2 doesn't work out of the box will really
>confuse people.
The fact that search doesn't work is IMHO the lesser of the two
errors. Does the API2 not work at all or is the problem more the
security one associated with the "role.api_test=integration-admin"
setting?

I'm reluctant to cut a new release , because then we'd have to start
over again. Like I've said, I see this first release as a learning
experience. No release will be perfect and will always include a few
bugs. I'd rather get this release out and then do another release in 2
weeks time with the bug fixes.  Now that we know how to do create
releases it will be easier the next time.  We should get used to

I'd rather describe the two changes that have to made in the resource
files in a blog post or on the wiki and then push for a new release.

Anyone else have thoughts on this

D.



On Sat, Feb 20, 2010 at 10:10 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
>> ...Maybe making this two-line change to one file is small enough that we
>> don't have to revote. I'm not sure. Maybe the mentors can weigh in....
>
> Anything that changes the release artifacts needs a new vote.
>
> On the other hand, if there's a workaround (IIUC people can change
> something manually to get things to work?) I suggest releasing as is.
>
> Nothing prevents you from making another release soon, if needed.
> Getting used to releasing is good progress towards graduation ;-)
>
> -Bertrand
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Bertrand Delacretaz <bd...@apache.org>]

On Sat, Feb 20, 2010 at 9:03 PM, Ethan Jewett <es...@gmail.com> wrote:
> ...Maybe making this two-line change to one file is small enough that we
> don't have to revote. I'm not sure. Maybe the mentors can weigh in....

Anything that changes the release artifacts needs a new vote.

On the other hand, if there's a workaround (IIUC people can change
something manually to get things to work?) I suggest releasing as is.

Nothing prevents you from making another release soon, if needed.
Getting used to releasing is good progress towards graduation ;-)

-Bertrand

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

I believe it is a show-stopper. Posting messages works fine, but the
search functionality is broken out of the box.

On my Mac (OS X 10.6), building the release candidate runs fine with
mvn jetty:run, but when I try to use the search functionality I get an
error:

Message: java.lang.IllegalArgumentException: Could not load JDBC
driver class [com.example.jdbc.Driver]

This is happening because Compass is attempting to use the
configuration in the compass.jdbc.cfg.xml file that comes with the
release, which points to a non-existent driver
(com.example.jdbc.Driver).

http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/resources/props/compass.jdbc.cfg.xml?view=markup&pathrev=906917

I believe that this will happen on any system and I think the fact
that search and the API2 doesn't work out of the box will really
confuse people. So, unfortunately, I think we have to go through this
one more time with a blank default.props file :-(

Maybe making this two-line change to one file is small enough that we
don't have to revote. I'm not sure. Maybe the mentors can weigh in.

Ethan

On Sat, Feb 20, 2010 at 1:28 PM, Richard Hirsch <hi...@gmail.com> wrote:
> OK.
>
> The question is this issue a "show-stopper?" Any opinions?
>
>  My tests with "mvn jetty:run" didn't show any problems. Of course, I
> didn't try to log-off and log-on again.
>
> If this problems leads to behavior as Sig suggested that the
> application doesn't work correctly - posting messages, etc - then we
> have to cut a new release.
>
> I won't be able to test the app until Monday. Can some other people
> test the app in Jetty and Tomcat. Logging on and then off to see if
> the application without the change in default.props functions
> correctly - with the exception of search.
>
> D.
>
> On Sat, Feb 20, 2010 at 8:21 PM, Sig Rinde <si...@rinde.com> wrote:
>> Yay, that did the trick on my side at least! Works now.
>>
>> Good work folks... say when if you make more changes ;)
>>
>> Sig
>>
>> On 20 February 2010 20:10, Richard Hirsch <hi...@gmail.com> wrote:
>>> The problem appears to be in the default.props file:
>>> compass_config_file=/props/compass.jdbc.cfg.xml
>>>
>>> If you change it to "compass.filesystem.cfg.xml", it should be fine.
>>>
>>> D.
>>>
>>>
>>> On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com> wrote:
>>>> Based on Sig's email I did some testing and it looks to me like search
>>>> is broken in this build when using the "mvn jetty:run" command to
>>>> launch the server. Can anyone else verify?
>>>>
>>>> Until we can figure out what the problem is, I'm changing my vote to -1
>>>>
>>>> Looking into it now....
>>>>
>>>> Ethan
>>>>
>>>> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> @Gianugo  did you forget to vote on the release? I didn't see a "+1"
>>>>> or a "-1" in your two posts. Or would you rather vote for the release
>>>>> when it gets to the "general" mailing list?
>>>>>
>>>>> D.
>>>>>
>>>>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>>>>> <g....@sourcesense.com> wrote:
>>>>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>> can you try a "mvn site" to see what it is coming from...
>>>>>>>
>>>>>>> I tried with a empty repository and it worked :-<
>>>>>>
>>>>>> False alarm - I had some weird settings left in settings.xml. Nuked
>>>>>> that one as well, it worked.
>>>>>>
>>>>>> Sorry for the fuss,
>>>>>>
>>>>>> --
>>>>>> Gianugo Rabellino
>>>>>> M: +44 779 5364 932 / +39 389 44 26 846
>>>>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

OK.

The question is this issue a "show-stopper?" Any opinions?

 My tests with "mvn jetty:run" didn't show any problems. Of course, I
didn't try to log-off and log-on again.

If this problems leads to behavior as Sig suggested that the
application doesn't work correctly - posting messages, etc - then we
have to cut a new release.

I won't be able to test the app until Monday. Can some other people
test the app in Jetty and Tomcat. Logging on and then off to see if
the application without the change in default.props functions
correctly - with the exception of search.

D.

On Sat, Feb 20, 2010 at 8:21 PM, Sig Rinde <si...@rinde.com> wrote:
> Yay, that did the trick on my side at least! Works now.
>
> Good work folks... say when if you make more changes ;)
>
> Sig
>
> On 20 February 2010 20:10, Richard Hirsch <hi...@gmail.com> wrote:
>> The problem appears to be in the default.props file:
>> compass_config_file=/props/compass.jdbc.cfg.xml
>>
>> If you change it to "compass.filesystem.cfg.xml", it should be fine.
>>
>> D.
>>
>>
>> On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com> wrote:
>>> Based on Sig's email I did some testing and it looks to me like search
>>> is broken in this build when using the "mvn jetty:run" command to
>>> launch the server. Can anyone else verify?
>>>
>>> Until we can figure out what the problem is, I'm changing my vote to -1
>>>
>>> Looking into it now....
>>>
>>> Ethan
>>>
>>> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> @Gianugo  did you forget to vote on the release? I didn't see a "+1"
>>>> or a "-1" in your two posts. Or would you rather vote for the release
>>>> when it gets to the "general" mailing list?
>>>>
>>>> D.
>>>>
>>>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>>>> <g....@sourcesense.com> wrote:
>>>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>> can you try a "mvn site" to see what it is coming from...
>>>>>>
>>>>>> I tried with a empty repository and it worked :-<
>>>>>
>>>>> False alarm - I had some weird settings left in settings.xml. Nuked
>>>>> that one as well, it worked.
>>>>>
>>>>> Sorry for the fuss,
>>>>>
>>>>> --
>>>>> Gianugo Rabellino
>>>>> M: +44 779 5364 932 / +39 389 44 26 846
>>>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>>>
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Sig Rinde <si...@rinde.com>]

Yay, that did the trick on my side at least! Works now.

Good work folks... say when if you make more changes ;)

Sig

On 20 February 2010 20:10, Richard Hirsch <hi...@gmail.com> wrote:
> The problem appears to be in the default.props file:
> compass_config_file=/props/compass.jdbc.cfg.xml
>
> If you change it to "compass.filesystem.cfg.xml", it should be fine.
>
> D.
>
>
> On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com> wrote:
>> Based on Sig's email I did some testing and it looks to me like search
>> is broken in this build when using the "mvn jetty:run" command to
>> launch the server. Can anyone else verify?
>>
>> Until we can figure out what the problem is, I'm changing my vote to -1
>>
>> Looking into it now....
>>
>> Ethan
>>
>> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> @Gianugo  did you forget to vote on the release? I didn't see a "+1"
>>> or a "-1" in your two posts. Or would you rather vote for the release
>>> when it gets to the "general" mailing list?
>>>
>>> D.
>>>
>>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>>> <g....@sourcesense.com> wrote:
>>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> can you try a "mvn site" to see what it is coming from...
>>>>>
>>>>> I tried with a empty repository and it worked :-<
>>>>
>>>> False alarm - I had some weird settings left in settings.xml. Nuked
>>>> that one as well, it worked.
>>>>
>>>> Sorry for the fuss,
>>>>
>>>> --
>>>> Gianugo Rabellino
>>>> M: +44 779 5364 932 / +39 389 44 26 846
>>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>>
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

The problem appears to be in the default.props file:
compass_config_file=/props/compass.jdbc.cfg.xml

If you change it to "compass.filesystem.cfg.xml", it should be fine.

D.


On Sat, Feb 20, 2010 at 7:42 PM, Ethan Jewett <es...@gmail.com> wrote:
> Based on Sig's email I did some testing and it looks to me like search
> is broken in this build when using the "mvn jetty:run" command to
> launch the server. Can anyone else verify?
>
> Until we can figure out what the problem is, I'm changing my vote to -1
>
> Looking into it now....
>
> Ethan
>
> On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> @Gianugo  did you forget to vote on the release? I didn't see a "+1"
>> or a "-1" in your two posts. Or would you rather vote for the release
>> when it gets to the "general" mailing list?
>>
>> D.
>>
>> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
>> <g....@sourcesense.com> wrote:
>>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> can you try a "mvn site" to see what it is coming from...
>>>>
>>>> I tried with a empty repository and it worked :-<
>>>
>>> False alarm - I had some weird settings left in settings.xml. Nuked
>>> that one as well, it worked.
>>>
>>> Sorry for the fuss,
>>>
>>> --
>>> Gianugo Rabellino
>>> M: +44 779 5364 932 / +39 389 44 26 846
>>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>>
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

Based on Sig's email I did some testing and it looks to me like search
is broken in this build when using the "mvn jetty:run" command to
launch the server. Can anyone else verify?

Until we can figure out what the problem is, I'm changing my vote to -1

Looking into it now....

Ethan

On Fri, Feb 19, 2010 at 10:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
> @Gianugo  did you forget to vote on the release? I didn't see a "+1"
> or a "-1" in your two posts. Or would you rather vote for the release
> when it gets to the "general" mailing list?
>
> D.
>
> On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
> <g....@sourcesense.com> wrote:
>> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> can you try a "mvn site" to see what it is coming from...
>>>
>>> I tried with a empty repository and it worked :-<
>>
>> False alarm - I had some weird settings left in settings.xml. Nuked
>> that one as well, it worked.
>>
>> Sorry for the fuss,
>>
>> --
>> Gianugo Rabellino
>> M: +44 779 5364 932 / +39 389 44 26 846
>> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

@Gianugo  did you forget to vote on the release? I didn't see a "+1"
or a "-1" in your two posts. Or would you rather vote for the release
when it gets to the "general" mailing list?

D.

On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> can you try a "mvn site" to see what it is coming from...
>>
>> I tried with a empty repository and it worked :-<
>
> False alarm - I had some weird settings left in settings.xml. Nuked
> that one as well, it worked.
>
> Sorry for the fuss,
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

Cool - I was getting worried ...

D.

On Fri, Feb 19, 2010 at 7:02 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> can you try a "mvn site" to see what it is coming from...
>>
>> I tried with a empty repository and it worked :-<
>
> False alarm - I had some weird settings left in settings.xml. Nuked
> that one as well, it worked.
>
> Sorry for the fuss,
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Gianugo Rabellino <g....@sourcesense.com>]

On Fri, Feb 19, 2010 at 6:46 PM, Richard Hirsch <hi...@gmail.com> wrote:
> can you try a "mvn site" to see what it is coming from...
>
> I tried with a empty repository and it worked :-<

False alarm - I had some weird settings left in settings.xml. Nuked
that one as well, it worked.

Sorry for the fuss,

-- 
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

can you try a "mvn site" to see what it is coming from...

I tried with a empty repository and it worked :-<

D.

On Fri, Feb 19, 2010 at 6:23 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> Hi,
>>
>> I have posted our candidate for the first Apache release developed
>> within the ESME podling.
>
> As it happens, I had to nuke my dev stuff so I started fresh with the
> newest maven and a clean repository on my machine. Unfortunately, I
> seem to be stuck on a lift dependency, that is
> javax.mail:mail:jar:1.4.3-rc1. Anything obvious I'm missing?
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

what JDK are you using?

D.

On Fri, Feb 19, 2010 at 6:23 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> Hi,
>>
>> I have posted our candidate for the first Apache release developed
>> within the ESME podling.
>
> As it happens, I had to nuke my dev stuff so I started fresh with the
> newest maven and a clean repository on my machine. Unfortunately, I
> seem to be stuck on a lift dependency, that is
> javax.mail:mail:jar:1.4.3-rc1. Anything obvious I'm missing?
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

Working on next release and I noticed that I'm having the same problem
that Gianugo  describes below. The only pom.xml change is when I add a
new repository.

            <repository>
               <id>repository.jboss.org</id>

<url>http://repository.jboss.org/maven2/org/jboss/netty/netty</url>
                <snapshots>
                  <enabled>false</enabled>
                </snapshots>
             </repository>

The problem must be related to wrong libraries being taken during the
build process. Might be useful for dealing with later bugs.

D.

On Fri, Feb 19, 2010 at 6:23 PM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> Hi,
>>
>> I have posted our candidate for the first Apache release developed
>> within the ESME podling.
>
> As it happens, I had to nuke my dev stuff so I started fresh with the
> newest maven and a clean repository on my machine. Unfortunately, I
> seem to be stuck on a lift dependency, that is
> javax.mail:mail:jar:1.4.3-rc1. Anything obvious I'm missing?
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Gianugo Rabellino <g....@sourcesense.com>]

On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Hi,
>
> I have posted our candidate for the first Apache release developed
> within the ESME podling.

As it happens, I had to nuke my dev stuff so I started fresh with the
newest maven and a clean repository on my machine. Unfortunately, I
seem to be stuck on a lift dependency, that is
javax.mail:mail:jar:1.4.3-rc1. Anything obvious I'm missing?

-- 
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Mrinal Wadhwa <mr...@gmail.com>]

+1 from me too ... thank you Dick for all the hard work in getting this
ready

Cheers,
Mrinal

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

Thanks.

I'll check it out....

On Fri, Feb 19, 2010 at 3:31 PM, Uday Subbarayan
<ud...@yahoo.com> wrote:
> I ran mvn package and I see missing jar errors in the surefire-reports. Here is the error descriptions:
>
> Test set: org.apache.esme.api.RestTest
> -------------------------------------------------------------------------------
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.368 sec <<< FAILURE!
> testStatus(org.apache.esme.api.RestTest)  Time elapsed: 0.189 sec  <<< ERROR!
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
>     at org.apache.commons.httpclient.HttpClient.<clinit>(HttpClient.java:66)
>     at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
>     at org.apache.esme.api.RestTest.testStatus(RestTest.java:45)
> Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>     ... 29 more
>
> testSendMsg(org.apache.esme.api.RestTest)  Time elapsed: 0.014 sec  <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
>     at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
>     at org.apache.esme.api.RestTest.testSendMsg(RestTest.java:68)
>
> testGetMessages(org.apache.esme.api.RestTest)  Time elapsed: 0.002 sec  <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
>     at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
>     at org.apache.esme.api.RestTest.testGetMessages(RestTest.java:89)
>
> testWaitForMessages(org.apache.esme.api.RestTest)  Time elapsed: 0.002 sec  <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
>     at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
>     at org.apache.esme.api.RestTest.testWaitForMessages(RestTest.java:110)
>
> -Uday.
>
> -------------------------
>
> I do not blog but e-write:
>
> http://uds-web.blogspot.com
>
> --- On Fri, 2/19/10, Richard Hirsch <hi...@gmail.com> wrote:
>
> From: Richard Hirsch <hi...@gmail.com>
> Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
> To: esme-dev@incubator.apache.org
> Date: Friday, February 19, 2010, 4:34 AM
>
> The ESME java client is provided in this release more as a code sample
> that people should use a starting point for their own work.
>
> We were thinking of removing it from future releases or updating it to
> the use the new API.
>
> Out of curiousity, what is failing?
>
> D.
>
> On Fri, Feb 19, 2010 at 5:28 AM, Uday Subbarayan
> <ud...@yahoo.com> wrote:
>> Congratulations for the 1.0.
>>
>> I also tried the java client and is failing. Is there a sample java client to post messages using API?
>>
>> Thanks,
>> Uday.
>>
>> -------------------------
>>
>> I do not blog but e-write:
>>
>> http://uds-web.blogspot.com
>>
>> --- On Thu, 2/18/10, Richard Hirsch <hi...@gmail.com> wrote:
>>
>> From: Richard Hirsch <hi...@gmail.com>
>> Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
>> To: esme-dev@incubator.apache.org
>> Date: Thursday, February 18, 2010, 12:43 PM
>>
>> On Thu, Feb 18, 2010 at 1:41 PM, Bertrand Delacretaz
>> <bd...@apache.org> wrote:
>>> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> ...The candidate can be found at
>>>>
>>>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>>>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>>>> src.tar.gz release package is
>>>>
>>>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...
>>>
>>> +1 to the release, thanks!
>>>
>>> Checked the rat report, mvn dependency:tree of the server module,
>>> which builds and starts.
>>>
>>> Tests still fail for me when building esme-java-client, haven't
>>> investigated, not a blocker for the release.
>>>
>>
>> We included the esme-java-client more as a example of an esme client.
>> It will probably disappear in the next release
>> but I wanted to include it in our first release.
>>
>>> -Bertrand
>>>
>>
>>
>>
>>
>
>
>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Uday Subbarayan <ud...@yahoo.com>]

I ran mvn package and I see missing jar errors in the surefire-reports. Here is the error descriptions:

Test set: org.apache.esme.api.RestTest
-------------------------------------------------------------------------------
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.368 sec <<< FAILURE!
testStatus(org.apache.esme.api.RestTest)  Time elapsed: 0.189 sec  <<< ERROR!
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    at org.apache.commons.httpclient.HttpClient.<clinit>(HttpClient.java:66)
    at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
    at org.apache.esme.api.RestTest.testStatus(RestTest.java:45)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    ... 29 more

testSendMsg(org.apache.esme.api.RestTest)  Time elapsed: 0.014 sec  <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
    at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
    at org.apache.esme.api.RestTest.testSendMsg(RestTest.java:68)

testGetMessages(org.apache.esme.api.RestTest)  Time elapsed: 0.002 sec  <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
    at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
    at org.apache.esme.api.RestTest.testGetMessages(RestTest.java:89)

testWaitForMessages(org.apache.esme.api.RestTest)  Time elapsed: 0.002 sec  <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.httpclient.HttpClient
    at org.apache.esme.api.EsmeRestApi.<init>(EsmeRestApi.java:53)
    at org.apache.esme.api.RestTest.testWaitForMessages(RestTest.java:110)

-Uday.

-------------------------

I do not blog but e-write:

http://uds-web.blogspot.com

--- On Fri, 2/19/10, Richard Hirsch <hi...@gmail.com> wrote:

From: Richard Hirsch <hi...@gmail.com>
Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
To: esme-dev@incubator.apache.org
Date: Friday, February 19, 2010, 4:34 AM

The ESME java client is provided in this release more as a code sample
that people should use a starting point for their own work.

We were thinking of removing it from future releases or updating it to
the use the new API.

Out of curiousity, what is failing?

D.

On Fri, Feb 19, 2010 at 5:28 AM, Uday Subbarayan
<ud...@yahoo.com> wrote:
> Congratulations for the 1.0.
>
> I also tried the java client and is failing. Is there a sample java client to post messages using API?
>
> Thanks,
> Uday.
>
> -------------------------
>
> I do not blog but e-write:
>
> http://uds-web.blogspot.com
>
> --- On Thu, 2/18/10, Richard Hirsch <hi...@gmail.com> wrote:
>
> From: Richard Hirsch <hi...@gmail.com>
> Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
> To: esme-dev@incubator.apache.org
> Date: Thursday, February 18, 2010, 12:43 PM
>
> On Thu, Feb 18, 2010 at 1:41 PM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> ...The candidate can be found at
>>>
>>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>>> src.tar.gz release package is
>>>
>>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...
>>
>> +1 to the release, thanks!
>>
>> Checked the rat report, mvn dependency:tree of the server module,
>> which builds and starts.
>>
>> Tests still fail for me when building esme-java-client, haven't
>> investigated, not a blocker for the release.
>>
>
> We included the esme-java-client more as a example of an esme client.
> It will probably disappear in the next release
> but I wanted to include it in our first release.
>
>> -Bertrand
>>
>
>
>
>



      

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

The ESME java client is provided in this release more as a code sample
that people should use a starting point for their own work.

We were thinking of removing it from future releases or updating it to
the use the new API.

Out of curiousity, what is failing?

D.

On Fri, Feb 19, 2010 at 5:28 AM, Uday Subbarayan
<ud...@yahoo.com> wrote:
> Congratulations for the 1.0.
>
> I also tried the java client and is failing. Is there a sample java client to post messages using API?
>
> Thanks,
> Uday.
>
> -------------------------
>
> I do not blog but e-write:
>
> http://uds-web.blogspot.com
>
> --- On Thu, 2/18/10, Richard Hirsch <hi...@gmail.com> wrote:
>
> From: Richard Hirsch <hi...@gmail.com>
> Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
> To: esme-dev@incubator.apache.org
> Date: Thursday, February 18, 2010, 12:43 PM
>
> On Thu, Feb 18, 2010 at 1:41 PM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> ...The candidate can be found at
>>>
>>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>>> src.tar.gz release package is
>>>
>>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...
>>
>> +1 to the release, thanks!
>>
>> Checked the rat report, mvn dependency:tree of the server module,
>> which builds and starts.
>>
>> Tests still fail for me when building esme-java-client, haven't
>> investigated, not a blocker for the release.
>>
>
> We included the esme-java-client more as a example of an esme client.
> It will probably disappear in the next release
> but I wanted to include it in our first release.
>
>> -Bertrand
>>
>
>
>
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Uday Subbarayan <ud...@yahoo.com>]

Congratulations for the 1.0.

I also tried the java client and is failing. Is there a sample java client to post messages using API?

Thanks,
Uday.

-------------------------

I do not blog but e-write:

http://uds-web.blogspot.com

--- On Thu, 2/18/10, Richard Hirsch <hi...@gmail.com> wrote:

From: Richard Hirsch <hi...@gmail.com>
Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes  Again :->)
To: esme-dev@incubator.apache.org
Date: Thursday, February 18, 2010, 12:43 PM

On Thu, Feb 18, 2010 at 1:41 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> ...The candidate can be found at
>>
>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>> src.tar.gz release package is
>>
>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...
>
> +1 to the release, thanks!
>
> Checked the rat report, mvn dependency:tree of the server module,
> which builds and starts.
>
> Tests still fail for me when building esme-java-client, haven't
> investigated, not a blocker for the release.
>

We included the esme-java-client more as a example of an esme client.
It will probably disappear in the next release
but I wanted to include it in our first release.

> -Bertrand
>



      

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Thu, Feb 18, 2010 at 1:41 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> ...The candidate can be found at
>>
>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>> src.tar.gz release package is
>>
>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...
>
> +1 to the release, thanks!
>
> Checked the rat report, mvn dependency:tree of the server module,
> which builds and starts.
>
> Tests still fail for me when building esme-java-client, haven't
> investigated, not a blocker for the release.
>

We included the esme-java-client more as a example of an esme client.
It will probably disappear in the next release
but I wanted to include it in our first release.

> -Bertrand
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Bertrand Delacretaz <bd...@apache.org>]

On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
> ...The candidate can be found at
>
>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
> ...The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
>
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C ...

+1 to the release, thanks!

Checked the rat report, mvn dependency:tree of the server module,
which builds and starts.

Tests still fail for me when building esme-java-client, haven't
investigated, not a blocker for the release.

-Bertrand

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Anne Kathrine Petterøe <yo...@gmail.com>]

It displayed correctly on my machine...


On 17. feb. 2010, at 20.14, Richard Hirsch wrote:

> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> 
>> Hi,
>> 
>> I have posted our candidate for the first Apache release developed
>> within the ESME podling.
>> 
>> The candidate can be found at
>> 
>>  http://people.apache.org/~rhirsch/esme/
>> 
>> See the CHANGES.txt file for details on release contents. The release
>> candidate is a tar archive of the sources in
>> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/
> 
> The URL behind this element is incorrect if displayed in rich
> formatting: it should be
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/
> . Another reason to use text-only when writing emails.
>> 
>> The MD5 checksum of the apache-esme-incubating-1.0-
>> src.tar.gz release package is
>> 
>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
>> 
>> Please vote on releasing this package as Apache ESME 1.0-incubating.
>> The vote is open for the next 72 hours and passes if
>> a majority of at least three +1  ESME PPMC votes is reached. Assuming
>> the vote passes, I will ask the Incubator PMC to approve the release.
>> 
>>   [ ] +1 Release this package as Apache ESME 1.0-incubating
>>   [ ] -1 Do not release this package because...
>> 
>> Here's my +1.
>> 
>> Since the last release attempt, the following changes have been made
>> * Updated README to indicate that ESME currently just supports JDK 1.6
>> * Removed license reference from the README
>> * Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks Ethan)
>>   Perform "mvn site" to see the current dependencies. The only dependencies
>>   only license information are the com.twitter.* jars and I was unabled to find
>>   licensing info. Although newer versions in github are licensed with Apache
>>   License
>> * Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
>> * Changed version in pom.xml to <version>apache-esme-1.0-incubating</version>
>> * removed svn files from release
>> * directory created by release is no longer called "trunk"
>> * Checked SHA signature on signed release but this should be a diff between SHA1
>>   and SHA512
>> 
>> 
>> Dick Hirsch

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>
> Hi,
>
> I have posted our candidate for the first Apache release developed
> within the ESME podling.
>
> The candidate can be found at
>
>  http://people.apache.org/~rhirsch/esme/
>
> See the CHANGES.txt file for details on release contents. The release
> candidate is a tar archive of the sources in
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/

The URL behind this element is incorrect if displayed in rich
formatting: it should be
https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/
. Another reason to use text-only when writing emails.
>
> The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
>
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
>
> Please vote on releasing this package as Apache ESME 1.0-incubating.
> The vote is open for the next 72 hours and passes if
> a majority of at least three +1  ESME PPMC votes is reached. Assuming
> the vote passes, I will ask the Incubator PMC to approve the release.
>
>   [ ] +1 Release this package as Apache ESME 1.0-incubating
>   [ ] -1 Do not release this package because...
>
> Here's my +1.
>
> Since the last release attempt, the following changes have been made
> * Updated README to indicate that ESME currently just supports JDK 1.6
> * Removed license reference from the README
> * Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks Ethan)
>   Perform "mvn site" to see the current dependencies. The only dependencies
>   only license information are the com.twitter.* jars and I was unabled to find
>   licensing info. Although newer versions in github are licensed with Apache
>   License
> * Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
> * Changed version in pom.xml to <version>apache-esme-1.0-incubating</version>
> * removed svn files from release
> * directory created by release is no longer called "trunk"
> * Checked SHA signature on signed release but this should be a diff between SHA1
>   and SHA512
>
>
> Dick Hirsch

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Anne Kathrine Petterøe <yo...@gmail.com>]

All good things are three :-D

+1


On 17. feb. 2010, at 20.03, Richard Hirsch wrote:

> Hi,
> 
> I have posted our candidate for the first Apache release developed
> within the ESME podling.
> 
> The candidate can be found at
> 
> http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
> 
> See the CHANGES.txt file for details on release contents. The release
> candidate is a tar archive of the sources in
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/<https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating>
> 
> The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
> 
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
> 
> 
> Please vote on releasing this package as Apache ESME 1.0-incubating.
> The vote is open for the next 72 hours and passes if
> a majority of at least three +1  ESME PPMC votes is reached. Assuming
> the vote passes, I will ask the Incubator PMC to approve the release.
> 
>  [ ] +1 Release this package as Apache ESME 1.0-incubating
>  [ ] -1 Do not release this package because...
> 
> Here's my +1.
> 
> Since the last release attempt, the following changes have been made
> * Updated README to indicate that ESME currently just supports JDK 1.6
> * Removed license reference from the README
> * Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks
> Ethan)
>  Perform "mvn site" to see the current dependencies. The only dependencies
>  only license information are the com.twitter.* jars and I was unabled to
> find
>  licensing info. Although newer versions in github are licensed with Apache
> 
>  License
> * Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
> * Changed version in pom.xml to
> <version>apache-esme-1.0-incubating</version>
> * removed svn files from release
> * directory created by release is no longer called "trunk"
> * Checked SHA signature on signed release but this should be a diff between
> SHA1
>  and SHA512
> 
> 
> Dick Hirsch

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Daniel Kulp <dk...@apache.org>]

+1 (binding, IPMC)

Great job everyone on the last minute cleanup stuff.

Dan


On Wed February 17 2010 2:03:03 pm Richard Hirsch wrote:
> Hi,
> 
> I have posted our candidate for the first Apache release developed
> within the ESME podling.
> 
> The candidate can be found at
> 
>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsc
> h/esme/>
> 
> See the CHANGES.txt file for details on release contents. The release
> candidate is a tar archive of the sources in
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incu
> bating/<https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.
> 0-incubating>
> 
> The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
> 
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
> 
> 
> Please vote on releasing this package as Apache ESME 1.0-incubating.
> The vote is open for the next 72 hours and passes if
> a majority of at least three +1  ESME PPMC votes is reached. Assuming
> the vote passes, I will ask the Incubator PMC to approve the release.
> 
>   [ ] +1 Release this package as Apache ESME 1.0-incubating
>   [ ] -1 Do not release this package because...
> 
> Here's my +1.
> 
> Since the last release attempt, the following changes have been made
> * Updated README to indicate that ESME currently just supports JDK 1.6
> * Removed license reference from the README
> * Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks
> Ethan)
>   Perform "mvn site" to see the current dependencies. The only dependencies
>   only license information are the com.twitter.* jars and I was unabled to
> find
>   licensing info. Although newer versions in github are licensed with
> Apache
> 
>   License
> * Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
> * Changed version in pom.xml to
> <version>apache-esme-1.0-incubating</version>
> * removed svn files from release
> * directory created by release is no longer called "trunk"
> * Checked SHA signature on signed release but this should be a diff between
> SHA1
>   and SHA512
> 
> 
> Dick Hirsch

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Ethan Jewett <es...@gmail.com>]

+1

Thanks again Dick!

On Wed, Feb 17, 2010 at 1:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Hi,
>
> I have posted our candidate for the first Apache release developed
> within the ESME podling.
>
> The candidate can be found at
>
>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>
> See the CHANGES.txt file for details on release contents. The release
> candidate is a tar archive of the sources in
> https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1-0-0-incubating/<https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating>
>
> The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
>
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
>
>
> Please vote on releasing this package as Apache ESME 1.0-incubating.
> The vote is open for the next 72 hours and passes if
> a majority of at least three +1  ESME PPMC votes is reached. Assuming
> the vote passes, I will ask the Incubator PMC to approve the release.
>
>  [ ] +1 Release this package as Apache ESME 1.0-incubating
>  [ ] -1 Do not release this package because...
>
> Here's my +1.
>
> Since the last release attempt, the following changes have been made
> * Updated README to indicate that ESME currently just supports JDK 1.6
> * Removed license reference from the README
> * Removed GPL-licensed and other unused dependencies from pom.xml.  (Thanks
> Ethan)
>  Perform "mvn site" to see the current dependencies. The only dependencies
>  only license information are the com.twitter.* jars and I was unabled to
> find
>  licensing info. Although newer versions in github are licensed with Apache
>
>  License
> * Pom.xml no longer refers to lift snapshot but to the "1.1-M8" version
> * Changed version in pom.xml to
> <version>apache-esme-1.0-incubating</version>
> * removed svn files from release
> * directory created by release is no longer called "trunk"
> * Checked SHA signature on signed release but this should be a diff between
> SHA1
>  and SHA512
>
>
> Dick Hirsch
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Richard Hirsch <hi...@gmail.com>]

On Thu, Feb 18, 2010 at 12:31 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> ...The candidate can be found at
>>
>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>> src.tar.gz release package is
>>
>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
>
> I'm ready to give my +1, just one thing needs to be clarified IMO:
>
>> ...com.twitter.* jars and I was unabled to find  licensing info.
>> Although newer versions in github are licensed with Apache...
>
> Could you document here where that Apache-licensed version is found?

Found the version we need: http://github.com/stevej/scala-stats

Apache License is here: http://github.com/stevej/scala-stats/blob/master/LICENSE

For example, http://github.com/stevej/scala-stats/tree/master/src/main/scala/com/twitter/stats/
shows the Stats class that we use in Boot.scala.

>
> I also looked at net.lag:configgy which is a transient dependency of
> that com.twitter.starts thing, and according to
> http://www.lag.net/configgy/README.html it's Apache license, all good
> here.
>
> Note also that  mvn dependency:analyze still shows some unused
> declared dependencies, but that's not a problem for the release.
>
> -Bertrand
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Vassil Dichev <vd...@apache.org>]

+1 for the release, very good! and +1 for text-only emails ;-)


On Thu, Feb 18, 2010 at 1:31 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> ...The candidate can be found at
>>
>>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
>> ...The MD5 checksum of the apache-esme-incubating-1.0-
>> src.tar.gz release package is
>>
>> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C
>
> I'm ready to give my +1, just one thing needs to be clarified IMO:
>
>> ...com.twitter.* jars and I was unabled to find  licensing info.
>> Although newer versions in github are licensed with Apache...
>
> Could you document here where that Apache-licensed version is found?
>
> I also looked at net.lag:configgy which is a transient dependency of
> that com.twitter.starts thing, and according to
> http://www.lag.net/configgy/README.html it's Apache license, all good
> here.
>
> Note also that  mvn dependency:analyze still shows some unused
> declared dependencies, but that's not a problem for the release.
>
> -Bertrand
>

Re: [VOTE] Approve the release of apache-esme-incubating-1.0 - (Yes Again :->)

[Bertrand Delacretaz <bd...@apache.org>]

Hi,

On Wed, Feb 17, 2010 at 8:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
> ...The candidate can be found at
>
>  http://people.apache.org/~rhirsch/esme/<http://people.apache.org/%7Erhirsch/esme/>
> ...The MD5 checksum of the apache-esme-incubating-1.0-
> src.tar.gz release package is
>
> 8E 43 0D DF F8 FE 15 9B  22 47 C2 C0 CC 30 21 2C

I'm ready to give my +1, just one thing needs to be clarified IMO:

> ...com.twitter.* jars and I was unabled to find  licensing info.
> Although newer versions in github are licensed with Apache...

Could you document here where that Apache-licensed version is found?

I also looked at net.lag:configgy which is a transient dependency of
that com.twitter.starts thing, and according to
http://www.lag.net/configgy/README.html it's Apache license, all good
here.

Note also that  mvn dependency:analyze still shows some unused
declared dependencies, but that's not a problem for the release.

-Bertrand