Yes this has fixed this issue, thank you!
-Dave
On Thu, Dec 6, 2012 at 5:13 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
ok, we got it:
see http://jira.codehaus.org/browse/MDEP-187
if you upgrade m-dependency-p to 2.6, you'll get a better error message
then you should probably try to mvn
Those last two lines make no sense to me as this happens on systems
with Admin/root permissions. There doesn't seem to be any way this
can be a permissions issue, so I assume that's an incorrect/misleading
message.
-Dave
On Wed, Dec 5, 2012 at 11:23 PM, Hervé BOUTEMY herve.bout...@free.fr
Disk full? Have you tried building from C:?
/Anders
On Thu, Dec 6, 2012 at 1:47 PM, David Hoffer dhoff...@gmail.com wrote:
Those last two lines make no sense to me as this happens on systems
with Admin/root permissions. There doesn't seem to be any way this
can be a permissions issue, so I
Most probably, it means that one of the file is used by another
application, thus cannot be deleted.
On Thu, Dec 6, 2012 at 1:47 PM, David Hoffer dhoff...@gmail.com wrote:
Those last two lines make no sense to me as this happens on systems
with Admin/root permissions. There doesn't seem to
This happens if I build locally and when built with our CI build
server. When I build locally it will use disk C and the disk is not
full. These folders are just the normal maven build folders so if
there is something using the file...it's a Maven process.
We are using Maven3...perhaps the site
Note that the copy-dependencies goal in the stand-alone module is not
really relevant/useful in the site build. Rather it's a key part of
the regular...clean, install, release phases...that module just copies
artifacts and builds an aggregate artifact (i.e. it does not have
source code). But I'm
if you run with mvn -X and give us the full stack trace, perhaps we can see
what's going wrong
Le jeudi 6 décembre 2012 06:34:52 David Hoffer a écrit :
Note that the copy-dependencies goal in the stand-alone module is not
really relevant/useful in the site build. Rather it's a key part of
Sure here is the build log from the site build (regular build works).
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.2:site (default-cli) on
project stand-alone: failed to get report for
org.apache.maven.plugins:maven-surefire-report-plugin: Failed to
execute goal
ok, we got it:
see http://jira.codehaus.org/browse/MDEP-187
if you upgrade m-dependency-p to 2.6, you'll get a better error message
then you should probably try to mvn package site, to have the package phase
executed before the site tries to use the result artifacts
Regards,
Hervé
Le jeudi 6
please read the last two lines
F:\work\7832e3bc4d2f257b\dashboard-core\target\classes (Access is
denied)
Le mercredi 5 décembre 2012 15:00:24 David Hoffer a écrit :
I have a multi-module maven build and can't get the site build to
work. It's currently failing with this error. The module its
10 matches
Mail list logo
