You don't need these:
- Code: Select all
$ mvn install:install-file -DgroupId=info.codesaway -DartifactId=regexplus -Dversion=2010-04-16 -Dpackaging=jar -Dfile=/home/y/git/pmsencoder-deps/RegExPlus.jar
$ mvn install:install-file -DgroupId=com.google.code -DartifactId=ps3mediaserver -Dversion=1.20.412 -Dpackaging=jar -Dfile=/home/y/git/ps3mediaserver-read-only/ps3mediaserver/pms.jar
my setup is
- Sun Java jdk1.6.0_21
Thanks. I can reproduce this on Maven 3.0.
For now, stick with your workaround or use Maven 2.x. I'm not planning to change the repo: the "virtual
" name (plugins-releases &c.) is meant to work like a symlink, shielding users from the underlying location (plugins-releases-local), which may be subject to change.
Maven 3.0 worked for me with a clean local repository last time I checked (only a week or two ago), so it's probably a transient bug in one of the dependencies that'll shake itself out shortly.