Problem building Lenya 1.4-dev

Andreas Hartmann wrote:
> Michael Wechner wrote:
>> Andreas Hartmann wrote:
>>> Michael Wechner wrote:
>>>> Hi
>>>>
>>>> I just did an update of Lenya 1.4-dev
revision 417200
>>>>
>>>> BUILD FAILED
>>>> java.lang.UnsupportedClassVersionError: 
>>>>
org/apache/lenya/cms/ant/CopyJavaSourcesTask (Unsupported 
>>>> major.minor version 49.0)
>>>>
>>>> any idea what might be wrong?
>>>
>>> http://issues.apache.org/bugzilla/show_bug.cgi?id=39893
>>
>> does that mean we have switched now to Java 1.5?
>
> No, I've compiled the classes with Java 1.5. I thought
that the
> target VM would be 1.4, but apparently something
didn't work as
> expected :(
>
> Maybe the compile-build-tasks target needs special
properties.

ok. I have separated the sources from the classes within
tools/anttasks
and will create a lib. Please test it. It's working now
again for Java 
1.4 and should
also work for 1.5 
>
>
>>> http://marc.theaimsgroup.com/?l=lenya-dev
&m=115131052428302&w=2
>>
>> well, if classes are handled as tools, then I think
it makes perfect 
>> sense to ship classes,
>> for instance see the configure libs/classes. The
CopyJavaSourcesTask 
>> is a tool for
>> the build process. Just think about it as a
third-party product.
>>
>> Or would you rather like to add the java sources of
ant and then 
>> build ant before you actually build Lenya?!
>
> Well, Ant is a separate product and we use a released
version.
> But our specific build tasks are directly related to
the Lenya
> codebase, therefore I think it makes sense to compile
them
> on the fly.

I think it depends. For instance tools/config can be used
outside of 
Lenya, since
it's rather generic and I think tools/anttasks could also
be used 
outside, but I guess
would need to be refactored 

On the other hand if we want to compile them on the fly then
I think we 
should move them
from tools into the core or a module, I think as it was once


Michi
>
> -- Andreas
>
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
michael.wechnerwyona.com                        michiapache.org
+41 44 272 91 61


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Michael Wechner wrote:
> Andreas Hartmann wrote:
>> Michael Wechner wrote:
>>> Andreas Hartmann wrote:
>>>> Michael Wechner wrote:
>>>>> Hi
>>>>>
>>>>> I just did an update of Lenya 1.4-dev
revision 417200
>>>>>
>>>>> BUILD FAILED
>>>>> java.lang.UnsupportedClassVersionError:

>>>>>
org/apache/lenya/cms/ant/CopyJavaSourcesTask (Unsupported 
>>>>> major.minor version 49.0)
>>>>>
>>>>> any idea what might be wrong?
>>>>
>>>> http://issues.apache.org/bugzilla/show_bug.cgi?id=39893
>>>
>>> does that mean we have switched now to Java
1.5?
>>
>> No, I've compiled the classes with Java 1.5. I
thought that the
>> target VM would be 1.4, but apparently something
didn't work as
>> expected :(
>>
>> Maybe the compile-build-tasks target needs special
properties.
> 
> ok. I have separated the sources from the classes
within tools/anttasks
> and will create a lib. Please test it. It's working
now again for Java 
> 1.4 and should
> also work for 1.5 

Yes, it works for me with 1.5.
Thanks a lot!


>>>> http://marc.theaimsgroup.com/?l=lenya-dev
&m=115131052428302&w=2
>>>
>>> well, if classes are handled as tools, then I
think it makes perfect 
>>> sense to ship classes,
>>> for instance see the configure libs/classes.
The CopyJavaSourcesTask 
>>> is a tool for
>>> the build process. Just think about it as a
third-party product.
>>>
>>> Or would you rather like to add the java
sources of ant and then 
>>> build ant before you actually build Lenya?!
>>
>> Well, Ant is a separate product and we use a
released version.
>> But our specific build tasks are directly related
to the Lenya
>> codebase, therefore I think it makes sense to
compile them
>> on the fly.
> 
> I think it depends. For instance tools/config can be
used outside of 
> Lenya, since
> it's rather generic and I think tools/anttasks could
also be used 
> outside, but I guess
> would need to be refactored 
> 
> On the other hand if we want to compile them on the fly
then I think we 
> should move them
> from tools into the core or a module, I think as it was
once 

OK, maybe we should just leave it like it is 

-- Andreas


-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
andreas.hartmannwyona.com                     andreasapache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org