Ooops, thanks Dan!
Please apply once the branch is unfrozen.
On 2 Apr 2008, at 15:56, Dan Allen wrote:
I also urge that you consider fixing the following issue:
http://jira.jboss.org/jira/browse/JBSEAM-2812
The Groovy hot redeployment strategy is not properly detecting Java
classes. Simple fix.
Sorry, I have been so strapped with the editing process that I have
overlooked submitting critical issues such as this.
-Dan
On Wed, Apr 2, 2008 at 7:50 AM, Jay Balunas <tech4j(a)gmail.com> wrote:
> Thanks Dan - I verify in the CR2 or GA builds.
>
> -Jay
>
>
>
>
> On Wed, Apr 2, 2008 at 3:04 AM, Dan Allen <dan.j.allen(a)gmail.com>
> wrote:
>> I already tracked down this problem, though the solution sits in a
>> different issue.
>>
>>
http://jira.jboss.org/jira/browse/JBSEAM-2319
>>
>> It is a compatibility problem with Ant 1.7.
>>
>> -Dan
>>
>>
>> On Tue, Apr 1, 2008 at 5:04 PM, Emmanuel Bernard
>> <emmanuel(a)hibernate.org>
> wrote:
>>
>>
>>
>>> I have finished
>>> I uncovered a bug in seam-gen + groovy though
>>>
http://jira.jboss.com/jira/browse/JBSEAM-2810
>>>
>>> We will fix that latter
>>>
>>>
>>>
>>> On Apr 1, 2008, at 15:12, Jay Balunas wrote:
>>>> So whats the plan with the tagging? Should I do it, or wait?
>>>>
>>>> Emmanuel Bernard wrote:
>>>>> Looking at it right now. It should be jsut a matter of switching
>>>>> the jar and testing the 2 demos
>>>>>
>>>>> On Apr 1, 2008, at 12:58, Pete Muir wrote:
>>>>>> Does it need to be in 2.0? How quick can you be?
>>>>>>
>>>>>> On 1 Apr 2008, at 17:49, Jay Balunas wrote:
>>>>>>> I have not put down the tag yet - but I'll leave it Pete
and
>>>>>>> others ;)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Emmanuel Bernard wrote:
>>>>>>>> Humm
>>>>>>>> I wanted to put Groovy 1.5.x in it and give it a test
>>>>>>>> Let me know if I can
>>>>>>>>
>>>>>>>> On Apr 1, 2008, at 09:57, Pete Muir wrote:
>>>>>>>>> Norman, Jay
>>>>>>>>>
>>>>>>>>> We're ready to start releasing 2.0.2.CR1 unless
there are any
>>>>>>>>> objections. Please work your magic ;-)
>>>>>>>>>
>>>>>>>>> Everyone, please don't commit to the 2.0 branch
without
>>>>>>>>> checking first until Norman/Jay give the all clear.
>>>>>>>>>
>>>>>>>>> In general, the 2.0 branch of development is now
frozen
>>>>>>>>> except
>>>>>>>>> for critical fixes and documentation.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> P
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Pete Muir
>>>>>>>>>
http://www.seamframework.org
>>>>>>>>>
http://in.relation.to/Bloggers/Pete
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> seam-dev mailing list
>>>>>>>>> seam-dev(a)lists.jboss.org
>>>>>>>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Pete Muir
>>>>>>
http://www.seamframework.org
>>>>>>
http://in.relation.to/Bloggers/Pete
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>
>>
>>
>> --
>> Dan Allen
>> Software consultant | Author of Seam in Action
>>
>>
http://www.mojavelinux.com
>>
http://manning.com/dallen
>>
>> NOTE: While I make a strong effort to keep up with my email on a
>> daily
>> basis, life and work come first and, at times, keep me away from
>> my mail
>> for a while. If you contact me, then don't hear back for more
>> than a week,
>> it is very likely that I am excessively backlogged or the message
>> was
>> caught in the spam filters. Please don't hesitate to resend a
>> message if
>> you feel that it did not reach my attention.
>>
>>
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
--
Dan Allen
Software consultant | Author of Seam in Action
http://www.mojavelinux.com
http://manning.com/dallen
NOTE: While I make a strong effort to keep up with my email on a daily
basis, life and work come first and, at times, keep me away from my
mail
for a while. If you contact me, then don't hear back for more than
a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a
message if
you feel that it did not reach my attention.