maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wayne Fay <>
Subject Re: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
Date Thu, 13 Jan 2011 18:51:58 GMT
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on
> project svnkit: Error assembling JAR: Failed to read filesystem
> attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed
> to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad
> /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing
> process. Child creation error: no such file or directory -> [Help 1]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.

Well, what does it look like when you run with -e or -X? Don't send
the full output back to the list -- post it at and send
us a link, unless you can chop it down to the bare minimum of info

> How can java catch file system attributes better?
> Why do we use a Unix shell command to create a child prozess
> (sub-process in openvms) by Java just to catch a file system attribute?

You'd have to ask the JDK folks these questions. What JDK are you
using, and from what vendor?

> But it seems that on my OpenVMS with default DCL command language, the
> maven version 3 under java and a JVM attempts to place a command which
> should create a child process just to execute a ls command used to
> retrieve a file attribute.

Most likely the Java code written by the Maven team (or Java code
being used in Maven that is actually from plexus-utils or another
library) is simply leveraging standard Java file io routines which
happen to use the child process to execute ls etc. If there was a
better way to get this information, I'd expect it would have been
implemented, or perhaps OpenVMS is just not very well supported by the
Java platform? Maybe you could dig deep into the code (debug Maven,
plexus, and the jdk itself in Netbeans or something), find where this
child process thing is coming from, and offer up a patch to the
appropriate party?

> I call it a style break, we should not do it from Java and not assume
> Unix or the like shells avail,
> or we are at risk that over time fewer system will support what maven
> attempts to do.

This has very little to do with Maven, and is primarily the "fault" of
the JDK on OpenVMS. I would assume that a better approach to finding
the file attributes is available, but no one cares enough about
OpenVMS to implement it or pay for it? You are literally the only
person I've seen post questions on this list about OpenVMS (Nabble
archives reveal 1 other person has posted about it minimally) so it
seems to be a pretty low-use OS, at least as far as Maven is


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message