On 19/06/2010, Phil Steitz <p...@steitz.com> wrote: > sebb wrote: > > [Third time lucky?] > > > > Please review and vote on the BSF 3.1 release. > > > > The artifacts are available at: > > > > http://people.apache.org/~sebb/bsf-3.1-RC3/ > > > > The Maven artifacts are at: > > > > https://repository.apache.org/content/repositories/orgapachebsf-004/ > > > > The SVN tag is at: > > > > http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.1-RC3 > > > > This will be renamed following a successful vote. > > > > Keys are here: > > http://www.apache.org/dist/jakarta/bsf/KEYS > > > > Vote will remain open for at least 72 hours. > > > > [ ] +1 I support this release. > > [ ] -1 I am against releasing the packages (must include a reason). > > > > Thanks in advance! > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org > > For additional commands, e-mail: general-h...@jakarta.apache.org > > > > > Sigs and hashes are good. All else looks good; but I got this error > when I tried "mvn clean test" from the source distro (JDK 1.6): > > [INFO] Unable to find resource 'org.apache.bsf:bsf-engines:jar:3.1' > in repository central (http://repo1.maven.org/maven2) > Downloading: > > http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-impl/1.2.2/axiom-impl-1.2.2.jar > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve dependencies for one or more projects in > the reactor. Reason: Missing: > ---------- > 1) org.apache.bsf:bsf-engines:jar:3.1 > > > When I later did just "mvn" it seems to have downloaded / installed > everything it needs, so "mvn clean test" subsequently succeeds. I > don't know if this is a real problem or not.
This seems to be a general problem with multi-module maven testing. The command: mvn package works OK, and performs tests, even if the jars have not been installed locally yet. However mvn test does not work unless you do a prior install. I think that is a bug (or at the very least a sub-optimal design feature) in Maven. > Might be good to add > something to the BUILDING doc to indicate what you have to do first. This does already say to start by running: mvn The default goal is install, so this will ensure that subsequent "mvn test" commands do succeed. > Phil > > > Phil > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org > For additional commands, e-mail: general-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org