On Nov 13, 2006, at 5:07 AM, Marnie McCormack wrote:
fscontext has been removed from svn and the test disabled so we
shouldn't be
trying to auto download this one imho ?
Done. I've committed the change to client/pom.xml to remove the need
for these jars.
--steve
Marnie
On 11/13/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
On Nov 12, 2006, at 8:34 PM, Rafael Schloming wrote:
> Steve Vinoski wrote:
>> Under branches/mvn is a first cut at building and testing the java
>> code with maven. I would appreciate it if others could checkout
>> the branch and try it, especially on platforms other than OS X.
>> All feedback welcomed.
>> BTW, be sure to get "mvn" and not "maven" as the latter is an old
>> branch that doesn't work and needs to go away.
>
> This is what happens for me:
>
> [INFO]
>
---------------------------------------------------------------------
-
> --
> [ERROR] BUILD ERROR
> [INFO]
>
---------------------------------------------------------------------
-
> --
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) fscontext:fscontext:jar:1.2-beta3
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=fscontext -
> DartifactId=fscontext \
> -Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/path/to/file
Yes, fscontext is a current problem because there's no maven release
for it. I raised this as an issue on this list last week.
But as a temporary workaround, you can do exactly what the error
message says. If you download the fscontext zip file from Sun [1],
you can extract the fscontext and providerutil jars and install them
into your local repository just as the error message indicates:
mvn install:install-file -DgroupId=fscontext -DartifactId=fscontext \
-Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
fscontext-1.2-beta3.jar
mvn install:install-file -DgroupId=fscontext -
DartifactId=providerutil \
-Dversion=1.2-beta3 -Dpackaging=jar -Dfile=/your/path/to/
providerutil-1.2-beta3.jar
Another alternative, depending on whether we want the build to
require these jars or not, would be to remove their dependencies from
the pom files.
--steve
[1] <http://java.sun.com/products/jndi/downloads/index.html>
