On 29/03/2010, sebb <seb...@gmail.com> wrote: > On 29/03/2010, Brett Randall <javabr...@gmail.com> wrote: > > Hi, > > > > Does someone here have access to > > /srv/gump/public/workspace/jakarta-bsf3/gump_mvn_settings.xml (or is > > it publicly available), referred to in the daily Gump build failure > > for BSF: > > > > > http://vmgump.apache.org/gump/public/jakarta-bsf3/jakarta-bsf3/gump_work/build_jakarta-bsf3_jakarta-bsf3.html > > > I think it is a temporary work file, which is deleted after the run completes. > > > > It seems possible that the local repository settings are out of > > alignment, or some other problem causes > > org.apache.bsf:bsf-engines:jar:3.0-SNAPSHOT to not be found. It may > > also be a collision with the module's POM, which declares > > pom-packaging, when we are attaching a JAR. Works on my local repo. > > Gump output has enough of a hint that maybe the Gump local repo has > > moved for the build and we may be installing to an old location in > > > /home/gump/.m2/repository/org/apache/bsf/bsf-engines/3.0-SNAPSHOT/bsf-engines-3.0-SNAPSHOT.jar > > (as opposed to > /srv/gump/public/workspace/mvnlocalrepo/org/apache/bsf/bsf-engines/3.0-SNAPSHOT/...). > > Guesswork without reviewing the Gump settings. > > > Could try asking on the Gump or Builds lists. >
Another possibility might be to remove the install from the Ant build file, and change the pom to <packaging>jar</packaging>, as Gump seems to handle Maven installs OK. This would need some other changes to the pom to ensure the jar was (re)created correctly. Not sure how easy that would be. > > Brett > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: bsf-dev-unsubscr...@jakarta.apache.org > > For additional commands, e-mail: bsf-dev-h...@jakarta.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: bsf-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: bsf-dev-h...@jakarta.apache.org
