I have another update on this...note I can't be 100% sure of my conclusions
as it's somewhat random but here goes.
clean install - succeeds
-PciBuild clean install - fails
-X -PciBuild clean install - succeeds at least some times
However if I remove the aggregate-jar goal from ciBuild profile t
Regarding the reactor build order/issue okay/yes that is what we expected
that it builds each to the final phase. However if I step back and
describe what I see in the build behavior...I see that although each module
does build to final stage (e.g. expected generated artifacts are in target
folder
Hi David,
On 23/01/17 00:54, David Hoffer wrote:
I will try all of these things the best I can, see my comments inline below.
In addition to my comments below I have a question about how Maven
handles plugin phases in a multi module build. Once the reactor module
build order is established doe
I will try all of these things the best I can, see my comments inline below.
In addition to my comments below I have a question about how Maven handles
plugin phases in a multi module build. Once the reactor module build order
is established does it build each module all the way to the final phas
Hi David,
the first thing I strongly recommend to make a build of your project
where you first clean the local cache ($HOME/.m2/repository) completely
and just run your build via:
mvn package -DskipTests=true
(No usage of install!)..
This should work without any issue...If it does not than
Any input on this? This is killing us right now...we don't have a way to
get past this and builds are failing. We have no idea what to try to fix
this.
Any input is greatly appreciated.
-Dave
On Sat, Jan 21, 2017 at 7:18 AM, David Hoffer wrote:
> Maven home: C:\Programs\Apache\Maven\apache-m
Maven home: C:\Programs\Apache\Maven\apache-maven-3.3.9
Java version: 1.8.0_102, vendor: Oracle Corporation
Java home: C:\Programs\Java\jdk1.8.0_102\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
Command line: mvn clean insta
Hi,
how is Maven called ? Which Maven Version do you use? Are you using "-T"
option?
What looks a little bit strnage to me is that a parent:
"[00:34:50] : [Step 2/3] [INFO] JMS: Parent (POM)
.. SUCCESS [22:08 min]"
shows a time of 22 minutes ? Is this really
Okay I finally have debug build log information. Note this is for the two
unpack-dependencies. The first finds and unpacks, the second does not.
Note there are no errors here as the error is later when the missing file
is referenced.
Let me know if any other debug log info is needed.
[INFO] ---
With -X added to the command line it succeeded. I will try it again. That
is how this problem has been going...sometimes it works but mostly it does
not. At times I make a small change and it works thinking that maybe the
issue is fixed but only to find that subsequent builds fail.
Can you tell
Here is some build and log messages when run in normal mode...I will get
debug logs. Note it's the unpack-JMS-WS-Eventing step that is skipped
below...so the expected file is not found.
[00:34:49] : [Step 2/3] [INFO]
[00:34:49] : [Step 2/3] [INFO]
Hi,
On 20/01/17 17:07, Bernd Eckenfels wrote:
Any logs (on debug level)?
yes and a concrete error message and of course (as Bernd already
mentioned log output)...
Just a note: Have you correctly defined a dependency to the module which
creates the zip/tar/jar from your module which uses
m
I'll run that right now...
-Dave
On Fri, Jan 20, 2017 at 9:07 AM, Bernd Eckenfels
wrote:
> Any logs (on debug level)?
>
> Am Fri, 20 Jan 2017 08:55:44 -0700
> schrieb David Hoffer :
>
> > We have a large multi-module build where occasionally (often) the
> > maven-dependency-plugin's unpack and
Any logs (on debug level)?
Am Fri, 20 Jan 2017 08:55:44 -0700
schrieb David Hoffer :
> We have a large multi-module build where occasionally (often) the
> maven-dependency-plugin's unpack and unpack-dependencies goal will
> skip their work. E.g. The specified artifact is not unzipped.
-
We have a large multi-module build where occasionally (often) the
maven-dependency-plugin's unpack and unpack-dependencies goal will skip
their work. E.g. The specified artifact is not unzipped.
I have not been able to get a handle on what is causing this failure. This
has been an ongoing issue
15 matches
Mail list logo
