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: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Thu, 27 Mar 2014 05:49:31 -0700 (PDT)
From: mkarg <karg@quipsy.de>
To: users@maven.apache.org
Message-ID: <1395924571582-5789696.post@n5.nabble.com>
In-Reply-To: 
 <CAEayHEMCboe7TbMuENpNFwo95k1KhU_4SeYX12jHL3jmEmL55g@mail.gmail.com>
References: <1395650439461-5789365.post@n5.nabble.com>
 <CAEayHEOGgV-7ZzoqTg7udryhk_by_Y8dADpwNNa9MxBXJHGQsA@mail.gmail.com>
 <1395909138436-5789681.post@n5.nabble.com>
 <CAEayHEMCboe7TbMuENpNFwo95k1KhU_4SeYX12jHL3jmEmL55g@mail.gmail.com>
Subject: Re: multi-module phases sequence
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I understand the issues, but I do not see why we should all just sit back and
say "Maven is broken by design, so all is good, just keep it as it is.". I
do not see that it is unfixable wrt the original question, as only thing I
asked for is that Maven accepts that if Module A needs Module B then it is
obvious that Module B must exist. In the end it is just a need for partial
serialization. I mean, I can even fix it by hand (merging two poms in one
and all works fine, as the executions run top to bottom), so it MUST be
possible to do just this partial fix in Maven core.


--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-phases-sequence-tp5789365p5789696.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org