[
https://issues.apache.org/jira/browse/HADOOP-8924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559313#comment-13559313
]
Colin Patrick McCabe commented on HADOOP-8924:
----------------------------------------------
It seems like this broke {{mvn eclipse:eclipse}}.
I get this output:
{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.478s
[INFO] Finished at: Mon Jan 21 18:30:18 PST 2013
[INFO] Final Memory: 33M/661M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT or one of
its dependencies could not be resolved: Could not find artifact
org.apache.hadoop:hadoop-maven-plugins:jar:3.0.0-SNAPSHOT -> [Help 1]
org.apache.maven.plugin.PluginResolutionException: Plugin
org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.apache.hadoop:hadoop-maven-plugins:jar:3.0.0-SNAPSHOT
at
org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:140)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.
java:142)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:
261)
at
org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
at
org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.
calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:280)
at
org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.
calculateForkedLifecycle(DefaultLifecycleExecutionPlanCalculator.java:520)
{code}
The underlying issue seems to be that {{generate-resources}} is broken, and
maven-eclipse-plugin "Invokes the execution of the lifecycle phase
generate-resources prior to executing itself." (As described here:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html )
You can see that this command also fails with the same error: {{mvn
generate-resources}}. In fact, a lot of the early phases of the default
lifecycle seem to fail: {{validate}}, {{initialize}}, {{generate-sources}}.
For some reason {{mvn site}} works, though, despite the fact that it should be
implicitly calling those earlier build phases.
> Add maven plugin alternative to shell script to save package-info.java
> ----------------------------------------------------------------------
>
> Key: HADOOP-8924
> URL: https://issues.apache.org/jira/browse/HADOOP-8924
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: trunk-win
>
> Attachments: HADOOP-8924.2.patch, HADOOP-8924.3.patch,
> HADOOP-8924.3.patch, HADOOP-8924.4.patch, HADOOP-8924.5.patch,
> HADOOP-8924.6.patch, HADOOP-8924.7.patch, HADOOP-8924-branch-2.7.patch,
> HADOOP-8924-branch-trunk-win.2.patch, HADOOP-8924-branch-trunk-win.3.patch,
> HADOOP-8924-branch-trunk-win.4.patch, HADOOP-8924-branch-trunk-win.5.patch,
> HADOOP-8924-branch-trunk-win.6.patch, HADOOP-8924-branch-trunk-win.7.patch,
> HADOOP-8924-branch-trunk-win.patch, HADOOP-8924.patch
>
>
> Currently, the build process relies on saveVersion.sh to generate
> package-info.java with a version annotation. The sh binary may not be
> available on all developers' machines (e.g. Windows without Cygwin). This
> issue tracks removal of that dependency in Hadoop Common.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
