It's now enforced in the build. That should solve problems w/ someone
upgrading Ant on a build machine and things going haywire. We can
adjust this requirement as needed in the future, but for now there is
no reason to allow any other version of Ant because frankly it just
causes inconsistencies, as Marek stated.
-Dan
On Wed, Nov 26, 2008 at 11:11 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
That explains why I couldn't reproduce it. I use Ant 1.7.0.
-Dan
On Wed, Nov 26, 2008 at 4:57 AM, Shane Bryzak <shane.bryzak(a)jboss.com> wrote:
> Thanks Marek, I downgraded to 1.7.0 and now it compiles correctly every
> time. Do we document the Ant version requirements somewhere?
>
> Marek Novotny wrote:
>>
>> Yes, don't use ant 1.7.1 for Seam 2.x. Only 1.7.0 is the right version for
>> Seam.
>>
>> It was discovered by me firstly in building Seam Feature Pack. I still
>> don't understand why they don't provide patch for this.
>>
>> Shane Bryzak napsal(a):
>>>
>>> After some further investigation, it looks like this is possibly a bug in
>>> ant - it seems there were some changes made for 1.7.1 which broke the
>>> compiling of package-info.java in some configurations.
>>>
>>>
https://issues.apache.org/bugzilla/show_bug.cgi?id=43114
>>>
>>>
>>>
>>> Shane Bryzak wrote:
>>>>
>>>> Still no luck, I have a fresh install of JB4.2.3.jdk6, and latest seam
>>>> svn trunk. The only modifications I've made are updating the
richfaces
>>>> version in root.pom.xml, and some minor changes to some examples (not
>>>> numberguess). I guess I'll have to start digging a little deeper.
>>>>
>>>> Shane Bryzak wrote:
>>>>>
>>>>> I'm on JBoss 4 with JDK 6, I'll clean everything and do a
fresh build
>>>>> and try again.
>>>>>
>>>>> Dan Allen wrote:
>>>>>>
>>>>>> I can't seem to reproduce the problem. I tested w/ JBoss 4
and 5 on
>>>>>> JDK 5 and 6.
>>>>>>
>>>>>> -Dan
>>>>>>
>>>>>> On Tue, Nov 25, 2008 at 9:16 PM, Shane Bryzak
<shane.bryzak(a)jboss.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> Has anyone made any changes to our Jbpm integration of late?
Both the
>>>>>>> dvdstore and numberguess examples are throwing this exception
upon
>>>>>>> deploy:
>>>>>>>
>>>>>>> Caused by: java.lang.RuntimeException: Error loading element
Jbpm
>>>>>>> with
>>>>>>> component name null and component class null
>>>>>>> at
>>>>>>>
>>>>>>>
org.jboss.seam.init.Initialization.installComponentsFromXmlElements(Initialization.java:351)
>>>>>>> at
>>>>>>>
>>>>>>>
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:226)
>>>>>>> ... 92 more
>>>>>>> _______________________________________________
>>>>>>> seam-dev mailing list
>>>>>>> seam-dev(a)lists.jboss.org
>>>>>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> seam-dev mailing list
>>>>> seam-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>> _______________________________________________
>>> 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://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but 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.
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but 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.