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 wsmoak@gmail.com designates
 209.85.161.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=gUm6GJliOWXgDO3iUJCtk96RP4SN4UN7/+vNlwZ+mQCA578Ny0X5olUWBl9gP74bDI
         z4rksegdN+3OL3pqK3w/hiefPe0XcWbYoohJwRdDFpj9WKu+fX7tq5GFWxzCaYfw71Qi
         qMs+LGBcbx51e6xXIbzJ0zTOXGBnDK5w7kThE=
MIME-Version: 1.0
In-Reply-To: <4D25CF2B.4000007@javactivity.org>
References: <4D25C56E.7040605@javactivity.org>
 <AANLkTina32nNYbLCaQhMorODc3_=mhErCCX49S0bs4eB@mail.gmail.com>
 <4D25CF2B.4000007@javactivity.org>
From: Wendy Smoak <wsmoak@gmail.com>
Date: Thu, 6 Jan 2011 09:31:55 -0500
Message-ID: <AANLkTikjf5DGiJk_W=RqA4_o1nJq5k4zuk1Qu8iGG8-_@mail.gmail.com>
Subject: Re: maven deploy module conditionally
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 6, 2011 at 9:18 AM, Steve Cohen <scohen@javactivity.org> wrote:
>> Set all your versions to end in -SNAPSHOT, that way you can leave them
>> in the aggregated build without the repository manager complaining on
>> deploy.
>>
>
> Yes, I suppose I could do that (which is pretty much what I did before), =
but
> it sort of defeats the whole purpose of what I'm trying to accomplish her=
e,
> which is, be a little more organized about what is release and what is in
> development.
>
>> If one of the modules is stable, do a release of it and have the other
>> modules depend on that released version (but you can still build the
>> next snapshot in your aggregator build.)
>
> Is what you are saying, then, that I need to "comment out" the stable
> modules as modules in the aggregator project? =A0That would pull them fro=
m the
> repo (they are then just dependencies, like third party jars)? =A0It woul=
d be
> nice not to have to mess with the POMs in this way. =A0That's what I'm lo=
oking
> for.

No commenting out.  I was trying to make the fewest changes to your
current setup as possible, since you said you didn't want to redesign
the build.

Following the Maven conventions, you never have a non-SNAPSHOT version
number checked in on a trunk or branch -- only on a tag.  (Or briefly
while a release is happening.)

It sounds like right now you are building an artifact with a
non-snapshot version number over and over.  That goes against the idea
that 'releases never change' -- releases should be built once, put in
the repository, and pulled from there when needed.

The version numbers make it clear what's under development and what's
not.  If module A depends on B-1.1-SNAPSHOT (being built in the
aggregated build,) then B is under development.  If A depends on
B-1.0, then you are using a stable version of B.

Maven does not currently have the concept of 'skip deployment if my
version number does not end in -SNAPSHOT'.  You'd probably have to put
the deploy plugin configured to with 'skip=3Dtrue' in a profile, and
patch the profile activation code to understand that concept.

--=20
Wendy

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