Well they are susceptible to Sun's hype at least. :-)

I just tried the 3.0.3 branch and got the very same problem - very
strange. I'm guessing this is something about my environment? I also
noticed this warning before the actual failure message:

WARN info.magnolia.cms.beans.config.ContentRepository
ContentRepository.java(getRepositoryMapping:564) 04.04.2007 10:20:40 no
mapping for the repository [website]

This seems really suspicious. Note this is only a problem with I try to
build the entire project. I can build /magnolia itself OK. My ultimate
goal, however, is to build the entire project, import it into Eclipse,
customize it, and hopefully ultimately contribute useful bits of that
effort back.



-Michael

 

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] 
Sent: April 4, 2007 4:53 AM
To: [email protected]
Subject: Re: [magnolia-dev] 3.0.2 build failure

Hmmm..... IT likes the bleeding edge, huh?

I haven't attempted to build the 3.0.2 tag, so I can't help you on that
one.  You might want to consider posting to the user list instead for a
response.  This list is for magnolia internal development.  I lurk here
to keep an eye on magnolia future development and the bug reports.

--David

Michael Beaty wrote:

>Hi David.
>
>I'm building with Maven 2.0.5. I have also tried the latest 2.0.6 with 
>the same result.
>
>JDK is 1.5.0_11.
>
>Thanks for the head's up on JDK1.6. IT has been pushing me down that 
>path and I had a feeling it would just confuse things at this point.
>
>-Michael
> 
>
>-----Original Message-----
>From: [email protected] [mailto:[EMAIL PROTECTED]
>Sent: April 3, 2007 4:20 PM
>To: [email protected]
>Subject: Re: [magnolia-dev] 3.0.2 build failure
>
>Couple of quick questions ...
>
>1. Are you building with Maven 2.0.5 or version 2.0.4?
>
>2. What JDK are you using.  I've found building with Java 1.6 (aka 6.0)

>to be prone to errors.
>
>FWIW, I'm building 3.0 branch (3.0.3-SNAPSHOT) with out issue using 
>Maven 2.0.5 and Sun JDK 1.5.0_11.
>
>--David
>
>Michael Beaty wrote:
>  
>
>>I'm trying to update my 3.0.1 installation to 3.0.2. First I tried 
>>updating from SVN, but noticed some build errors afterwards. Since 
>>then I've deleted my downloaded source and Maven repository, 
>>re-downloaded the source from SVN (3.0.2 tag), but still have the same
>>    
>>
>
>  
>
>>problem. The issue seems to be when magnolia-core is being built.
>>
>>Here are the test failure messages:
>>Failed tests:
>> 
>>testGetModuleRootJar(info.magnolia.cms.beans.config.ModuleRegistration
>>Te
>>st)
>> 
>>testGetModuleRootJarWIthDot(info.magnolia.cms.beans.config.ModuleRegis
>>tr
>>ationTest)
>> 
>>testGetModuleRootDirectory(info.magonlia.cms.beans.config.ModuleRegist
>>ra
>>tionTest)
>>Tests in error:
>>  testParseAndFormat(info.magnolia.cms.core.ie.DataTransporterTest)
>>
>>Am I the only one encountering this problem? Is it a known issue?
>>
>>For the time being, I've been able to successfully build 3.0.2 based 
>>on the SourceForge-hosted version of the source.
>>
>>-Michael Beaty
>>Senior Software Engineer
>>LeapFrog Enterprises
>>
>>----------------------------------------------------------------
>>for list details see
>>http://www.magnolia.info/en/developer.html
>>----------------------------------------------------------------
>>  
>>    
>>
>
>
>----------------------------------------------------------------
>for list details see
>http://www.magnolia.info/en/developer.html
>----------------------------------------------------------------
>
>----------------------------------------------------------------
>for list details see
>http://www.magnolia.info/en/developer.html
>----------------------------------------------------------------
>  
>


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------

Reply via email to