Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of mgainty@hotmail.com designates
 65.55.116.28 as permitted sender)
Message-ID: <BLU172-W383B28FC160753F33F517CAE9A0@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_1c68725e-6be2-4de3-8de7-b7570c9960e5_"
From: Martin Gainty <mgainty@hotmail.com>
To: "users@maven.apache.org" <users@maven.apache.org>
Subject: RE: Why does Maven fail to compile my project occasionally?
Date: Wed, 19 Feb 2014 21:48:44 -0500
Importance: Normal
In-Reply-To: <1392861493863-5785441.post@n5.nabble.com>
References: 
 <CAPg65qhXj4b9VsK2eKd4VTpf3ghWMn603GWz_JFQX4C0HSPPww@mail.gmail.com>
 <52FE29B7.20407@artifact-software.com>
 <1392392192345-5784856.post@n5.nabble.com>
 <52FE659D.1000809@artifact-software.com>
 <1392437696526-5784947.post@n5.nabble.com>
 <CA+nPnMw10XjXqb4Y7-uuG13tptPKh40mPpiWkO53GQtmFr4R8g@mail.gmail.com>
 <CAPg65qjd50aQ7Z62Gbv7A-Q6kTT7S0H8rfSuj=dy-KVh5Fu9Jw@mail.gmail.com>
 <CALy+7UmOyvYLxHQk-v9q9P+LQrtUcCa9BruRmk_W-bMkDuUXGQ@mail.gmail.com>,<1392861493863-5785441.post@n5.nabble.com>
MIME-Version: 1.0

--_1c68725e-6be2-4de3-8de7-b7570c9960e5_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 =20


> Date: Wed=2C 19 Feb 2014 17:58:13 -0800
> From: levskiweng@gmail.com
> To: users@maven.apache.org
> Subject: Re: Why does Maven fail to compile my project occasionally?
>=20
> Wayne Fay wrote
> > Maven calls out to your system JDK to do the compilation step. With
> > the [ERROR] lines you provided previously=2C Maven is simply passing
> > along the error that was reported by javac. I bet=2C if you constructed
> > the proper javac call (which can be seen in Maven's logs if you use -X
> > for debug mode)=2C you would see the same error produced without
> > involving Maven (or Jenkins) at all.
> >=20
> > IIRC you had some "cannot find symbol" errors. What do you expect
> > Maven to do about code defects reported by the Java compiler? Why are
> > you blaming Maven for this?
>=20
> After digging into the dependency tree described in each module's pom.xml
> for several days=2C I found that you're right. It's my fault=2C not Maven=
's.
> It's because my code depends some other modules which I didn't put it int=
o
> pom.xml explicitly. And I'm adding them into the corresponding pom.xml.
> Thank you for directing me back to the right track!
>=20
> However=2C I'm curious that I succeed to compile the project after severa=
l
> compilation failure. How does it happen? I've passed the parameter 'clean
> install -Dmaven.test.skip=3Dtrue --update-snapshots --batch-mode --fail-f=
ast
> --debug -Dmaven.compiler.forceJavacCompilerUse=3Dtrue
> -Dmaven.compiler.verbose=3Dtrue' to Maven=2C but it doesn't get the same =
error
> when I compile the project the second time.
=20
MG>be specific about the supposed error(s) you say you are seeing
MG>display pom.xml

MG>what is execution string first time around?
MG>Display Results for First Iteration

MG>what is execution string second time around?
MG>Display Results for Second Iteration

> =3B-)
>=20
> Could anyone explain the somewhat weird behavior of Maven? Thanks.
>=20
>=20
>=20
> --
> View this message in context: http://maven.40175.n5.nabble.com/Why-does-M=
aven-fail-to-compile-my-project-occasionally-tp5784849p5785441.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>=20
> ---------------------------------------------------------------------
> To unsubscribe=2C e-mail: users-unsubscribe@maven.apache.org
> For additional commands=2C e-mail: users-help@maven.apache.org
>=20
 		 	   		  =

--_1c68725e-6be2-4de3-8de7-b7570c9960e5_--