mvn build failure due to missing snapshot

[GoogleCodeExporter]

The latset BridJ mvn build fails due to missing snapshot package:

[WARNING] repository metadata for: 'snapshot 
com.nativelibs4java:maven-velocity-plugin:0.6-SNAPSHOT' could not be retrieved 
from repository: blackpad-nexus due to an error: Error transferring file: 
Server returned HTTP response code: 503 for URL: 
http://www.blackpad.fr/nexus/content/groups/public/com/nativelibs4java/maven-vel
ocity-plugin/0.6-SNAPSHOT/maven-metadata.xml
[INFO] Repository 'blackpad-nexus' will be blacklisted

(similar warnings follow)

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Changing pom.xml to use older snapshot "fixes" it,

Index: pom.xml
===================================================================
--- pom.xml (リビジョン 2187)
+++ pom.xml (作業コピー)
@@ -21,7 +21,7 @@
   <parent>
      <groupId>com.nativelibs4java</groupId>
      <artifactId>nl4j-runtime-parent</artifactId>
-     <version>0.6-SNAPSHOT</version>
+     <version>0.5-SNAPSHOT</version>
      <relativePath>../Parent</relativePath>
   </parent>

... but I guess the appropriate fix would be to have newer snapshot uploaded 
somewhere.

Original issue reported on code.google.com by atsushi...@gmail.com on 6 Jul 2011 at 1:42

[GoogleCodeExporter]

Hello Atsushi,

Thanks for your report.

FYI, here are the official build instructions :
http://code.google.com/p/bridj/wiki/Build

You'll notice they imply that the whole NativeLibs4Java tree be compiled, which 
is a bit long but will have the added benefit of installing all the 
non-deployed artifacts that snapshots versions might need.

You can make the compilation faster by running "mvn install -DskipTests" in the 
Runtime sub-directory (parent to both BridJ and the velocity plugin).

I'm deploying these snapshot artifacts right now so compilation in the sole 
BridJ directory will work for a while, but the "issue" will happen virtually at 
each  new version :-)

Cheers
--
zOlive

Original comment by olivier.chafik@gmail.com on 6 Jul 2011 at 3:47

• Changed state: NotABug

[GoogleCodeExporter]

Bah, sorry I misunderstood that it should be done at libraries/Runtime/BridJ 
(as it always worked with that command line *there*).

But then the right command didn't work either. Actually I think I tried this 
couple of times at topdir. I guess, something still needs to be fixed?

atsushi@atsushi-Aspire-3820:~/svn/nativelibs4java$ mvn install 
-Dmaven.test.skip=true
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an existing 
pom.xml, but the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Thu Jul 07 03:02:10 JST 2011
[INFO] Final Memory: 4M/84M
[INFO] ------------------------------------------------------------------------

Original comment by atsushi...@gmail.com on 6 Jul 2011 at 6:05

[GoogleCodeExporter]

Oops sorry, thanks for checking, I'm reopening the issue then !
(which version of Maven are you using, btw ? I haven't moved to Maven 3.x yet)

Cheers

Original comment by olivier.chafik@gmail.com on 6 Jul 2011 at 10:49

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I was using 2.2.1 on Ubuntu. I tried 3.0.3 but resulted in the same failure.

Original comment by atsushi...@gmail.com on 7 Jul 2011 at 6:13

[GoogleCodeExporter]

Hi Atsushi,

I cannot seem to be reproducing this issue on MacOS X (deleted my 
~/.m2/repository, checked out a fresh local copy and went have a (dozen) 
coffees, it eventually built everything fine).
Have you made sure you don't have any local modifications in your 'pom.xml' 
files ? (and that you don't run 'mvn clean install' instead of just 'mvn 
install' ? Clean somehow needs the velocity plugin to be installed 
beforehand...).

Cheers
--
zOlive

Original comment by olivier.chafik@gmail.com on 7 Jul 2011 at 8:26

[GoogleCodeExporter]

Hmm, I believe I don't have blocking changes. I removed many extra changes and 
put my mvn build and other outputs here (still same build failure): 
https://gist.github.com/1073562

I deleted ~/m2/repository and retried, but resulted in the same error.

We wouldn't need top-level build so far (as I didn't) - setting priority less 
critical.

Original comment by atsushi...@gmail.com on 9 Jul 2011 at 4:41

• Added labels: Priority-Medium
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Ok, I see now !
You're actually one folder *above* the official top directory (the top maven 
directory is libraries, not trunk, which has no pom.xml file)

Original comment by olivier.chafik@gmail.com on 10 Jul 2011 at 9:27

[GoogleCodeExporter]

That's it. Now I can correctly build everything.

I have updated the wiki page to reflect this.

Original comment by atsushi...@gmail.com on 15 Jul 2011 at 4:51

• Changed state: Fixed