Build Failure - org.commonjava.aprox:aprox-api:jar:0.8.3-SNAPSHOT about indy HOT 9 CLOSED

Did you happen to rebuild galley from master as well? It looks like you haven't built the latest, which is 0.3.0-SNAPSHOT and includes the httpclient transport.

from indy.

Also, if you update aprox master from my GH repo again, you'll need to rebuilt weft from master as well. I've added the ability to override threadpool size/priority using a configuration section in /etc/aprox/main.conf.

from indy.

The repo script should take care of that and I can confirm the following...
[sbadakhc@localhost galley]$ git remote -v
origin https://github.com/sbadakhc/galley.git (fetch)
origin https://github.com/sbadakhc/galley.git (push)
upstream https://github.com/jdcasey/galley.git (fetch)
upstream https://github.com/jdcasey/galley.git (push)
[sbadakhc@localhost galley]$ git tag
galley-0.1.0
galley-0.2.0
[sbadakhc@localhost galley]$ git branch

• master
  [sbadakhc@localhost galley]$ git rev-parse HEAD
  d581bf109b7438a5f8fec3efe247a61d174c1b62

I will clone your repos directly rather than using my forks to make sure!

from indy.

Confirmed galley build failure using cloned upstream repos and not my forks. Will investigate and get back to you.

from indy.

Looks like the test expects a connection to be made...will skip tests for now and report back.

Expected: null
got: <org.commonjava.maven.galley.TransferException: Repository remote request failed for: http://localhost:9514/list-basic/nexus-switchyard/index.html. Reason: Connection to http://localhost:9514 refused>

Tests run: 12, Failures: 7, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Galley :: Parent .................................. SUCCESS [0.925s]
[INFO] Galley :: API ..................................... SUCCESS [1.932s]
[INFO] Galley :: Caches :: Parent ........................ SUCCESS [0.032s]
[INFO] Galley :: Cache :: TCK ............................ SUCCESS [0.139s]
[INFO] Galley :: Test-Harness :: Parent .................. SUCCESS [0.016s]
[INFO] Galley :: Test Harness for API Implementations .... SUCCESS [0.318s]
[INFO] Galley :: Core API ................................ SUCCESS [1.397s]
[INFO] Galley :: Transports :: Parent .................... SUCCESS [0.034s]
[INFO] Galley :: Transports :: HttpClient Transport ...... FAILURE [2.222s]
[INFO] Galley :: Transports :: File and Archive Transport SKIPPED
[INFO] Galley :: Test Harness for Core Classes ........... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.834s
[INFO] Finished at: Sun Sep 08 22:31:32 CEST 2013
[INFO] Final Memory: 634M/3925M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project galley-transport-httpclient: There are test failures.

from indy.

OK so confirmed build success for atlas, galley and cartographer using repo clones and not forks and skipping tests but still get a Aprox build failure. I suspect my forks are ok now as well but will confirm with skip tests.

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] AProx :: Parent POM ............................... SUCCESS [0.708s]
[INFO] AProx :: API ...................................... SUCCESS [7.334s]
[INFO] AProx :: Test-Harness Parent ...................... SUCCESS [0.024s]
[INFO] AProx :: Database TCK ............................. SUCCESS [0.254s]
[INFO] AProx :: Databases Parent ......................... SUCCESS [0.039s]
[INFO] AProx :: In-Memory Database ....................... SUCCESS [0.406s]
[INFO] AProx :: File-Managers Parent ..................... SUCCESS [0.017s]
[INFO] AProx :: Default File Manager ..................... SUCCESS [0.112s]
[INFO] AProx :: Subsystems Parent ........................ SUCCESS [0.021s]
[INFO] AProx :: HTTP Client Subsystem .................... SUCCESS [0.155s]
[INFO] AProx :: Core ..................................... FAILURE [53.683s]
[INFO] AProx :: Flat-File Subsystem ...................... SKIPPED
[INFO] AProx :: Maven Component Subsystem ................ SKIPPED
[INFO] AProx :: Flat-File Database ....................... SKIPPED
[INFO] AProx :: Filer TCK ................................ SKIPPED
[INFO] AProx :: Build-Time Tooling ....................... SKIPPED
[INFO] AProx :: Assemblies ............................... SKIPPED
[INFO] AProx :: Add-Ons .................................. SKIPPED
[INFO] AProx :: Auto-Proxy Add-On ........................ SKIPPED
[INFO] AProx :: DepGraph (Cartographer Integration) ...... SKIPPED
[INFO] AProx :: Dot-Maven (.m2 WebDAV) Add-On ............ SKIPPED
[INFO] AProx :: Index Merger ............................. SKIPPED
[INFO] AProx :: WARs ..................................... SKIPPED
[INFO] AProx :: Minimal REST WAR ......................... SKIPPED
[INFO] AProx :: UIs ...................................... SKIPPED
[INFO] AProx :: Monorail UI Overlay (WAR) ................ SKIPPED
[INFO] AProx :: Basic WAR ................................ SKIPPED
[INFO] AProx :: Savant ................................... SKIPPED
[INFO] AProx :: EasyProx ................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:04.311s
[INFO] Finished at: Sun Sep 08 22:37:44 CEST 2013
[INFO] Final Memory: 484M/3925M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project aprox-core: Could not resolve dependencies for project org.commonjava.aprox:aprox-core:jar:0.8.3-SNAPSHOT: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project aprox-core: Could not resolve dependencies for project org.commonjava.aprox:aprox-core:jar:0.8.3-SNAPSHOT: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.commonjava.aprox:aprox-core:jar:0.8.3-SNAPSHOT: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.commonjava.cdi.util:weft:jar:0.3-SNAPSHOT
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
... 26 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :aprox-core

from indy.

That's because I shifted aprox to depend on weft 0.3-SNAPSHOT, which is required to allow overrides of thread pool sizing/priority via configuration. Unfortunately, weft is now in the build list (you can build from master) for a short time, until I'm sure it's stabilized enough to release 0.3.

As far as the galley tests are concerned, I'm not sure whether you managed to get them running or not, but those http transport tests should be standing up a Vert.x server instance, running test downloads against it, and shutting it down again. You shouldn't need any external infrastructure for that.

from indy.

No prob! will revert to master as advised. Still having to skip tests, connection to localhost is refused which suggests there is no listener...will investigate and feedback.

Cheers!

from indy.

Reverted to 0.8.2 for the time being.

from indy.