> The pom.xml in the log4j 1.2 branch is used to describe the project > in the Maven repository, but is not used to build the project.
ok, if i would have looked into the pom i would have seen that no dependencies are defined... > It would be good to revisit the pom.xml in both log4j 1.2 and log4j > 1.3. There are a couple of open bugs on the log4j 1.3 pom. At > least, should put comments in the pom.xml indicate that they aren't > for building if that is the case. that would be great. unfortunately i just started with maven and can't offer my help. > Since the poms were written it has been reported that more of the > dependencies have been added to Maven repo, so we may be approaching > the point where maven could collect all the necessary dependencies. that's true, the sun dependencies are available directly from sun https://maven-repository.dev.java.net/nonav/ so you would just have to add the following to your pom: <repository> <id>java.net</id> <url>https://maven-repository.dev.java.net/nonav/repository</url> <layout>legacy</layout> </repository> with this i guess it should be possible to have a maven build which is working from scratch... -- View this message in context: http://www.nabble.com/maven-build-tf3219983.html#a8946285 Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
