On 17/03/2009, sebb <seb...@gmail.com> wrote:
> On 17/03/2009, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> > Actually, the tests are (correctly) run many times. VFS uses an interesting
>  > mechanism to run the tests once for each provider type. It took me quite a
>  > while to figure out what it was doing. Some providers, such as webdav, http
>  > and ftp have to be run manually. I've put instructions in the doc on how to
>  > do that, but you can only read it if you build the site.
>
>
> I think there is a problem with the implementation, as it looks like
>  the same names are used for the surefire-reports files for different
>  providers.
>
>  If a test for one provider fails, the failure details will be lost
>  when another provider runs the same test.

Duh - ignore that - the provider name is in the file.

>
>  >  As for the test jar, yes Sandbox has a dependency on it. It has to be 
> built
>  > and available for the Sandbox build to run. Maven won't do that with just
>  > mvn test.
>  >
>  >  Ralph
>  >
>  >
>  >  On Mar 17, 2009, at 5:55 AM, sebb wrote:
>  >
>  >
>  > > On 17/03/2009, sebb <seb...@gmail.com> wrote:
>  > >
>  > > > On 17/03/2009, Siegfried Goeschl <siegfried.goes...@it20one.at> wrote:
>  > > >
>  > > > > Hi Ralph,
>  > > > >
>  > > > > +) I'm unable to run "mvn test" on commons-vfs (see below) SVN trunk
>  > > > > +) you can deploy a SNAPSHOT using "mvn -Pci deploy"
>  > > > >
>  > > >
>  > > >
>  > > > Surely you just have to run
>  > > >
>  > > > mvn install
>  > > >
>  > > > to deploy it to your local repo?
>  > > >
>  > > >
>  > >
>  > > That worked for me.
>  > >
>  > > However, the test takes quite a long time, and produces lots of output.
>  > > It looks as though some (most) of the tests are being run twice.
>  > >
>  > > The Surefire settings perhaps need to be tweaked.
>  > > And/or remove any package suites.
>  > >
>  > >
>  > >
>  > > >
>  > > > > Cheers,
>  > > > >
>  > > > > Siegfried Goeschl
>  > > > >
>  > > > > === START ===
>  > > > >
>  > > > > Downloading:
>  > > > >
>  > 
> http://people.apache.org/repo/m2-snapshot-repository//org/apache/commons/commons-vfs/2.0-SNAPSHOT/commons-vfs-2.0-SNAPSHOT-tests.jar
>  > > > > Downloading:
>  > > > >
>  > 
> http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/jars/commons-vfs-2.0-SNAPSHOT-tests.jar
>  > > > > [INFO]
>  > > > >
>  > ------------------------------------------------------------------------
>  > > > > [ERROR] BUILD ERROR
>  > > > > [INFO]
>  > > > >
>  > ------------------------------------------------------------------------
>  > > > > [INFO] Failed to resolve artifact.
>  > > > >
>  > > > > Missing:
>  > > > > ----------
>  > > > > 1)
>  > org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>  > > > >
>  > > > >  Try downloading the file manually from the project website.
>  > > > >
>  > > > >  Then, install it using the command:
>  > > > >     mvn install:install-file -DgroupId=org.apache.commons
>  > > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
>  > > > > -Dpackaging=test-jar -Dfile=/path/to/file
>  > > > >
>  > > > >  Alternatively, if you host your own repository you can deploy the
>  > file
>  > > > > there:
>  > > > >     mvn deploy:deploy-file -DgroupId=org.apache.commons
>  > > > > -DartifactId=commons-vfs -Dversion=2.0-SNAPSHOT -Dclassifier=tests
>  > > > > -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url]
>  > -DrepositoryId=[id]
>  > > > >
>  > > > >  Path to dependency:
>  > > > >       1)
>  > org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
>  > > > >       2)
>  > org.apache.commons:commons-vfs:test-jar:tests:2.0-SNAPSHOT
>  > > > >
>  > > > > ----------
>  > > > > 1 required artifact is missing.
>  > > > >
>  > > > > for artifact:
>  > > > >
>  > org.apache.commons:commons-vfs-sandbox:jar:2.0-SNAPSHOT
>  > > > >
>  > > > > from the specified remote repositories:
>  > > > >  central (http://repo1.maven.org/maven2),
>  > > > >  apache.m1
>  > (http://people.apache.org/repo/m1-snapshot-repository/),
>  > > > >  apache.snapshots
>  > (http://people.apache.org/repo/m2-snapshot-repository/)
>  > > > >
>  > > > > === END ===
>  > > > >
>  > > > >
>  > > > > Ralph Goers wrote:
>  > > > >
>  > > > > >
>  > > > > > On Mar 16, 2009, at 3:31 PM, Jörg Schaible wrote:
>  > > > > >
>  > > > > >
>  > > > > > > Hi Ralph,
>  > > > > > >
>  > > > > > > Ralph Goers wrote:
>  > > > > > >
>  > > > > > >
>  > > > > > > > I have finished the work to implement webdav versioning support
>  > in VFS
>  > > > > > > > trunk. I would like to take advantage of this in Commons
>  > Configuration
>  > > > > > > > (that code is also complete) but to do so I need a release of
>  > VFS 2.0.
>  > > > > > > > What must be done to accomplish this? FWIW I don't yet have a
>  > PGP key
>  > > > > > > > so I kind of get stuck at that spot in the "creating releases"
>  > > > > > > > instructions.
>  > > > > > > >
>  > > > > > >
>  > > > > > > I'd like to fix VFS-169 first. I have a complete different
>  > approach than
>  > > > > > > Frank. If you don't mind, I'll commit it directly as soon as
>  > possible.
>  > > > > > >
>  > > > > > >
>  > > > > >
>  > > > > > That's fine. Also, while you do this you might want to review the
>  > > > > > project and make sure it has everything for a proper release. I 
> will
>  > > > > > be doing the same?
>  > > > > >
>  > > > > > Also, is there a way to release a SNAPSHOT so that I can commit my
>  > > > > > Commons Configuration enhancements?
>  > > > > >
>  > > > > > Ralph
>  > > > > >
>  > ---------------------------------------------------------------------
>  > > > > > 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
>  > >
>  > >
>  >
>  >
>  > ---------------------------------------------------------------------
>  >  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

Reply via email to