Thanks Dragos, I've been using that plugin before, that will work on a developer's machine when you try to build and debug the project but I also need this to work with my automated build system. That's why I need maven to work.
"Change the version of log4j to 1.2.16. The metadata for 1.2.15 is bad, as you have discovered, because the dependencies are missing from the central repository. However, there is a policy of not changing artifacts or metadata in the central maven repository, because this can lead to builds being unrepeatable. That is, a build might behave differently if an artifact or its metadata changed." So edit the pom.xml and change the version for log4j from 1.2.15 to 1.2.16 (maybe somebody can fix it in the sbt configuration so we don't have to keep patching this by hand?)
Now mvm compile downloads all the dependencies but it doesn't build anything: ... [INFO] No sources to compile BUILD SUCCESSFUL
'mvm package' gives a similar warning - that the generated jar file will be empty. So it seems to me that the POM doesn't know anything about source code that it needs to compile. Maybe this is a quick fix for the engineer that created the sbt project file, I don't know.
BTW, after renaming the kafka_2.8.0-0.8.0-SNAPSHOT.pom to pom.xml, IDEA can open the project and it shows the sources in project view, but when I try to compile the project I get the same result as above (nothing happens).
Any help on this will be really appreciated.
On 6/12/13 10:45 AM, "Dragos Manolescu" <[EMAIL PROTECTED]> wrote:
Try downloading the file manually from the project website.
Then, install it using the command: mvn install:install-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency: 1) org.apache.kafka:kafka_2.8.0:jar:0.8.0-beta1 2) log4j:log4j:jar:1.2.15 3) com.sun.jmx:jmxri:jar:1.2.1
- I hand-edit the pom.xml and change the version of log4j from 1.2.15 to 1.2.16 (apparently this was still not fixed)
Now the "mvn package" command apparently succeeds but the generated jar is empty (only manifests in it):