I've added Apache snapshots to my nexus "Public Repositories", but that didn't help. Jenkins has three failed builds in a row, so this isn't a transient thing for me. I'm not against using a SNAPSHOT build from another project in the sandbox. However, we should document that and make sure folks know that they're going to have to build BCEL locally or configure Maven to pull from somewhere else.
On Mon, Jun 4, 2012 at 12:54 AM, Matt Benson <gudnabr...@gmail.com> wrote: > Oddly, I had this problem, but on the second try the build worked. :| > > Matt > > On Sun, Jun 3, 2012 at 10:25 PM, James Carman > <jcar...@carmanconsulting.com> wrote: >> I pointed my local Jenkins/Sonar setup at classscan at: >> >> http://svn.apache.org/repos/asf/commons/sandbox/classscan/trunk >> >> It's failing on: >> >> Could not resolve dependencies for project >> org.apache.commons:classscan:jar:0.1-SNAPSHOT: Could not find artifact >> org.apache.bcel:bcel:jar:6.0-SNAPSHOT. >> >> Do I need to add Apache Snapshots to my nexus setup to get this to >> work? It won't work out-of-the-box with regular Maven. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
