Glase, Stefan schrieb: > > since those changes my applications compiles with the following errors: > > > > [WARNING] POM for 'org.apache.myfaces.tomahawk:tomahawk:pom:1.1.7-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project org.apache.myfaces.tomahawk:tomahawk at Artifact [org.apache.myfaces.tomahawk:tomahawk:pom:1.1.7-SNAPSHOT:compile] > > [WARNING] POM for 'org.apache.myfaces.tomahawk:tomahawk-sandbox:pom:1.1.7-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project org.apache.myfaces.tomahawk:tomahawk-sandbox at Artifact [org.apache.myfaces.tomahawk:tomahawk-sandbox:pom:1.1.7-SNAPSHOT:compile] > > > > After that dependencies for tomahawk will not be resolved and result in missing commons-fileupload and commons-lang, so I have to add them manually to my dependencies. > > > > Any suggestions what to do or ideas what is wrong since the last changes with tomahawk?
The problem is that a dependency on "jsf-facelets" was added recently, so that facelets taglibs can be supported. The parent tomahawk pom defines the version of facelets used, but the "core" pom omits the version in its dependency declaration. All would normally be well, as the child pom will inherit the version set in the parent pom. But the parent pom has not yet been deployed to the snapshot repo. So the child pom now has a dependency on facelets, but no version is specified. Of course it all works fine for people who have built tomahawk locally, as their local repo has the latest parent pom. It's only having an old parent pom plus a new child pom that is the problem. Leonardo, can you please either add a version number to the child pom for the facelets dependency, or push the tomahawk parent pom to the snapshot repo? Regards, Simon
