2.2.0 distribution download contains no WAR and won't build?! about oozie

[rvs]

Brian,

you're correct we stopped publishing binary distributions of Oozie (QuickStart needs to be corrected) so there's tarball that would have oozie.war.

Now, I suspect that your build issue comes from the lack of ydoxia plugin. You might want to do the following before proceeding with the maven build:

$ git checkout ydoxia
$ mvn install

After that the following seems to generate the binary distribution for me just fine:

$ mvn clean package assembly:single -DskipTests

I'm tempted to close this issue, unless I hear from you otherwise

Thanks,
Roman.

[briantm]

The build failure was caused by an ambiguous version dependency on the build-helper-maven-plugin. The fix was to add in the core/pom.xml for:

            <groupId>org.codehaus.mojo</groupId>
            <artifactId>build-helper-maven-plugin</artifactId>
            <version>1.5</version>

[angeloh]

What version of maven are you using for the build?

[briantm]

I had just upgraded to the latest: Apache Maven 2.2.1

You know, however, that the plugin above is not part of the maven distribution itself. So, depending on what repositories users are configured to access either locally or remotely, they may not get the version of the plugin you're assuming. That is apparently what happened to me and why specifying an explicit version removes the problem.

[angeloh]

Could you try Apache Maven 2.2.0 this version without the above dependency in pom.xml and let us know if you still see the same errors or not? Please remember to remove the dependency from you local maven repo (~/.m2).
http://archive.apache.org/dist/maven/binaries/apache-maven-2.2.0-bin.tar.gz

[briantm]

Probably would work. But as I had upgraded from maven 2.0.9 specifically in order to build oozie, and since I already had an earlier version of the build-helper-maven-plugin in my repo, and since the pom does not requiest a particular version, my 2.2.x maven used the existing, old plugin version. I assume this would happen for anyone like me who upgrades an older maven install and has used an earlier build-helper-maven-plugin before, as opposed to people doing a fresh install with no repository.

[briantm]

In other words, the problem is probably not the maven version, but the existence of an older build-helper-maven-plugin in the local repo, as you allude to.

[tucu00]

would you try doing a build using the HEAD of master?

make sure you trash your ~/.m2/repository as it may be corrupted thanks to to the java.net repository (which now is not used anymore)