Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Envelope-To: java-dev@axis.apache.org
Date: Sat, 9 Sep 2017 15:27:06 +0200
From: =?windows-1252?Q?Thorsten_Sch=F6ning?= <tschoening@am-soft.de>
Organization: AM-SoFT IT-Systeme
Message-ID: <1945397673.20170909152706@am-soft.de>
To: Martin Gainty <java-dev@axis.apache.org>
Subject: Re: [AXIS2] Some project builds fail if goal "clean" is not used
In-Reply-To: <BLUPR14MB02593AD59706D11C59CFFBF6AE6A0@BLUPR14MB0259.namprd14.prod.outlook.com>
References: <165709498.20170905111249@am-soft.de>
  <BLUPR14MB02595429BCB7DF5029860433AE6A0@BLUPR14MB0259.namprd14.prod.outlook.com>,<365974901.20170909122544@am-soft.de>
  <BLUPR14MB02593AD59706D11C59CFFBF6AE6A0@BLUPR14MB0259.namprd14.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 09 Sep 2017 13:27:13 -0000

Guten Tag Martin Gainty,
am Samstag, 9. September 2017 um 13:36 schrieben Sie:

MG>>maven-compiler-plugin (with incremental) overwrites most recent changed=
 classes inside target\classes and target\test-classes
MG>>maven-compiler-plugin (full compile) compiles and overwrites ALL classe=
s (changed or not)

MG>>as  you have already discovered default behaviour for mvn clean  is to =
delete ALL classes in target\classes and target\test-classes

You are getting it wrong: The problem is e.g. "mvn test" without(!)
"clean". In that case there is something which deletes totally
unchanged, formerly successfully compiled classes and only the class
files itself, not the parent directory or any other directory. And
that is bad because some builds depend on formerly
compiled/packaged/whatever results and those are not available anymore
sometimes, because they has been deleted.

Adding "clean" fixes that, because a complete rebuild is issued, but
that shouldn't be needed if I don't change things. Let me quote
myself:

> One example is with axis-metadata, were the following command fails
> after a former successful build:
>
> > mvn test --projects :axis2-metadata
>
> While the following one succeeds:
>
> > mvn clean test --projects :axis2-metadata

From=20my understanding, "mvn test ..." only shouldn't fail after a
successful former build, but it does. Instead it should simply execute
tests again, which it is doing, but it fails for some tests because
some of those depend on compiled Java classes which are not available
anymore.

So the question only is if "mvn test ..." should have deleted those
files or not.

Mit freundlichen Gr=FC=DFen,

Thorsten Sch=F6ning

--=20
Thorsten Sch=F6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Gesch=E4ftsf=FChrer: Andreas Muchow


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org