Unfortunately all versions of the jruby jar have this offending property
setup and have been deployed to Maven central repo for quite some time, so
anyone who uses Maven 2.0.9 and has a project dependency on JRuby lists it
as a dependency is going to have this problem.
I narrowed this down to the
Hervé Boutemy wrote:
copy the files to new ones and remove old ones
Doh, I could have known: WAGON-19, MDEPLOY-28
I just did it on pmd plugin 2.4-SNAPSHOT: you can deploy the snapshot now
Thanks Hervé, deployment worked fine.
Benjamin
since the problem is with maven-metadata.xml* files, not parent directory,
there is a Unix trick to fix the permissions without waiting for the owner to
do it: copy the files to new ones and remove old ones
for f in maven-metadata.xml*; do mv $f $f~; cp $f~ $f; chmod g+w $f; rm -f
$f~; done
I
+1
--jason
On Apr 19, 2008, at 1:39 AM, Raphaël Piéroni wrote:
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&styleName=Html&version=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
http://maven.apache
I would hope that Maven wouldn't allow system properties to be overridden in
the POM :-) Maybe properties beginning with java.* have been blocked? Have
you tried to rename the property to something benign?
Paul
On Fri, Apr 18, 2008 at 7:30 PM, Chris Custine <[EMAIL PROTECTED]> wrote:
> It looks
