Created a Jira Item for the tag problem:
https://issues.apache.org/jira/browse/ESME-353

D.

On Thu, Jul 28, 2011 at 7:27 PM, Vladimir Ivanov <[email protected]> wrote:
> Thank you for the testing and issue with tags that you've found! Hope I (or
> other guys) will be able to look into it this night.
>
> 2011/7/28 Jack Park <[email protected]>
>
>> Thanks!
>> And thanks to Vladimir for the other explanation.
>> I confess, I'm new to Scala/Lift, just coming off years of Java servlets. I
>> expect to make a few changes to ESME as I become more fluent with
>> Scala/Lift, given there are a few things I'd like it to do that don't appear
>> in any of the plans.
>>
>> Now watching for the next release.
>> Jack
>>
>>
>> On 7/28/2011 10:14 AM, Richard Hirsch wrote:
>>
>>> @Jack - just checked the stax instance where the RC is deployed. Looks
>>> you are right - tags appear to be broken. :-<
>>>
>>> D.
>>>
>>> On Thu, Jul 28, 2011 at 6:29 PM, Jack Park<[email protected]>
>>>  wrote:
>>>
>>>> While compiling the release, I got this (not sure what it means):
>>>> [WARNING]
>>>> C:\projects\SCALA-Projects\**ESME\svx1.3\server\src\main\**
>>>> scala\org\apache\esme\model\**UserAuth.scala:468:
>>>> warning: match is not exhaustive!
>>>> [WARNING] missing combination        Failure
>>>> [WARNING] missing combination   ParamFailure
>>>> [WARNING]
>>>> [WARNING]               user<- UserAuth.find(By(UserAuth.**
>>>> authKey,name),
>>>> [WARNING]                    ^
>>>> [WARNING] warning: there were unchecked warnings; re-run with-unchecked
>>>> for
>>>> details
>>>>
>>>> I notice that, unlike 1.2, in 1.3, tags do not appear to be displayed.
>>>>
>>>> Jack
>>>>
>>>> On 7/28/2011 12:52 AM, Ethan Jewett wrote:
>>>>
>>>>>
>>>>> Hi Dick,
>>>>>
>>>>> Ok, that sounds perfect. I'll go through some testing tomorrow morning.
>>>>>
>>>>> Cheers,
>>>>> Ethan
>>>>>
>>>>> On Thu, Jul 28, 2011 at 9:23 AM, Richard Hirsch<[email protected]>
>>>>>  wrote:
>>>>>
>>>>>>
>>>>>> @Ethan I was going to close the vote tomorrow. So go ahead and test it.
>>>>>>
>>>>>> Ill be leaving on vacation on Saturday and I wanted to put the new
>>>>>> release in the download area tomorrow afternoon.
>>>>>>
>>>>>> D.
>>>>>>
>>>>>> On Thu, Jul 28, 2011 at 9:16 AM, Ethan Jewett<[email protected]>
>>>>>>  wrote:
>>>>>>
>>>>>>>
>>>>>>> Unfortunately I haven't been able to test this release candidate at
>>>>>>> all. If we want to keep the vote open a bit longer, I should be able
>>>>>>> to do some basic testing tomorrow. Otherwise, go for it!
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ethan
>>>>>>>
>>>>>>> On Mon, Jul 25, 2011 at 7:02 PM, Vladimir Ivanov<
>>>>>>> [email protected]>
>>>>>>>  wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> My two cents: +1
>>>>>>>>
>>>>>>>> Vladimir
>>>>>>>>
>>>>>>>> 2011/7/25 Richard Hirsch<[email protected]>
>>>>>>>>
>>>>>>>>  Hi,
>>>>>>>>>
>>>>>>>>> I have posted our candidate for the 1.3 release for Apache ESME.
>>>>>>>>>
>>>>>>>>> The candidate can be found at
>>>>>>>>> http://people.apache.org/~**rhirsch/esme/<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
>>>>>>>>> http://svn.apache.org/repos/**asf/esme/tags/apache-esme-1.**3RC1/<http://svn.apache.org/repos/asf/esme/tags/apache-esme-1.3RC1/>
>>>>>>>>>
>>>>>>>>> The MD5 checksum of the apache-esme-1.3.src.tar.gz release package
>>>>>>>>> is
>>>>>>>>> 9B FF 83 5D 1E 1C D6 BD  22 9A C9 6C 3D C5 4D 37
>>>>>>>>>
>>>>>>>>> Please vote on releasing this package as Apache ESME 1.3.
>>>>>>>>>
>>>>>>>>> The vote is open for the next 72 hours and passes if
>>>>>>>>> a majority of at least three +1 ESME PMC votes is reached.
>>>>>>>>>
>>>>>>>>> [ ] +1 Release this package as Apache ESME 1.3
>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>
>>>>>>>>> Here's my +1.
>>>>>>>>>
>>>>>>>>> Dick
>>>>>>>>> Apache ESME Chair
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,
>>>>>>>> Vladimir Ivanov
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>
>
> --
> Best Regards,
> Vladimir Ivanov
>

Reply via email to