---- "Sochor Zdeněk" <[EMAIL PROTECTED]> schrieb: > Hi all, > > Sochor Zdeněk napsal(a): > > Hi all, > > today i tried to build whole MyFaces 1.1 + Tomahawk after ages. > > I started by new SVN checkout (myfaces-current), but something is > > going wrong :( > > Using JDK 1.4 + Maven2 on Win XP, clean install goals. > > > > [INFO] Failed to resolve artifact. > > > > Missing: > > ---------- > > 1) org.apache.tiles:tiles-api:jar:2.4.1 > > (last tiles-api version is 2.0.5)
Works fine for me with maven2.0.8 + java 1.6. And running mvn dependency:tree gives +- org.apache.tiles:tiles-core:jar:2.0.5:compile +- org.apache.tiles:tiles-api:jar:2.0.5:compile \- commons-logging:commons-logging-api:jar:1.1:compile which is correct. > > > After manual change in dependency i found few errors when using real > Java 1.4 (not -target) to build Tomahawk > > Automatic d/l of needed libraries: > tiles-core 2.0.5 > tiles-api-2.0.5 > - both are Java 5, for Java 1.4 tiles-core-2.0.5-j4.jar, > tiles-api-2.0.5-j4.jar are needed > > Java 5 method in source: > tomahawk\core\src\main\java\org\apache\myfaces\custom\schedule\AbstractScheduleRenderer.java:[237,33] > - replace(char,char) in java.lang.String cannot be applied to > (java.lang.String,java.lang.String) > > Should i file JIRA issues for this (Compiling Tomahawk + Java 1.4)? If there is java 1.5 code in tomahawk, this is definitely an issue. And yes we should add a classifier to the tiles dependency for the j4 version. The problem with being unable to build with maven looks more like a maven issue. But I suppose tomahawk needs a workaround for it, so yes why not file that too. Adding a direct dependency from the tomahawk pom to tiles-api should override the indirect dependency.. Thanks for reporting this. Regards, Simon
