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)
Message-ID: <528B8BF2.9050002@artifact-software.com>
Date: Tue, 19 Nov 2013 11:04:02 -0500
From: Ron Wheeler <rwheeler@artifact-software.com>
Reply-To: rwheeler@artifact-software.com
Organization: Artifact Software
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Russell Gold <russell.gold@oracle.com>,
 Maven Users List <users@maven.apache.org>
Subject: Re: Is it possible to release a child module that isn't listed in
 the parent's list of modules?
References: <1384811062108-5775784.post@n5.nabble.com>
 <528A8FF4.7040709@artifact-software.com>
 <1384815615843-5775797.post@n5.nabble.com>
 <CAKDUN1sjoCYz0F=DuvV1EbQ3KVnF1tAje-ZdLBdU3=-1uc-niA@mail.gmail.com>
 <1384873757093-5775848.post@n5.nabble.com>
 <528B8582.4080807@artifact-software.com>
 <478CF980-2765-460E-B4F4-78E4D28C4022@oracle.com>
In-Reply-To: <478CF980-2765-460E-B4F4-78E4D28C4022@oracle.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 19/11/2013 10:50 AM, Russell Gold wrote:
> The release plugin does an awful lot more than deploy. The usual case is that during development, your version is set to a snapshot - the plugin changes it to a release version, commits the change to CM and tags it, among other things. Deploy won�t do any of that.

Exactly but I think that all he wants to do it to deploy a single module 
as a "RELEASE"  that is not part of a part of the project (not a child 
of the parent) but is related to it in some way. It appears that the 
rest of the project is not ready for release yet but this module is.
My point is that for a single module, that is out of step with the rest 
of the project, it make not be worthwhile fighting with the release 
plug-in to save 30 seconds of CM work and 30 seconds of POM editing.

>
> That said, your point about the versions is a good one. It makes no sense to set the snapshot back to match the version just released.
I hope that this discussion of releases gets him back on track.
  I do wonder if there was some confusion about the function of the 
release-plug-in and the actual deploy of a release.
Your comments will go a long way to making this clearer.
> Regards,
> Russ
>
> On Nov 19, 2013, at 10:36 AM, Ron Wheeler <rwheeler@artifact-software.com> wrote:
>
>> I never us the release plug-in so you can take my comments with a grain of salt.
>>
>>  From reading the docs I am not sure that these are right.
>>
>> -DdevelopmentVersion=52.0.0-SNAPSHOT -DreleaseVersion=52.0.0
>>
>>
>> My interpretation is that you are trying to get maven to go backwards.
>> You are saying to release 52.0.0 and make a new snapshot of 52.0.0-SNAPSHOT which is not right.
>>
>> -DdevelopmentVersion=52.0.1-SNAPSHOT -DreleaseVersion=52.0.0
>>
>> seems to be the right arguments.
>>
>> I am not sure why you are even using the release plug-in at all. If you just want to deploy a release of one module just use the deploy command.
>> Release wants to do a some magic to your project to get it setup for the next development cycle and I am not sure that you really want to do all this at this time.
>>
>> If you just want to deploy the current release and start working on 52.0.1-SNAPSHOT for one module, you can just deploy and change the pom to point the 52.0.1-SNAPSHOT parent and you are ready for the next development cycle. - Not worth wrestling with the release plug-in.
>>
>> Ron
>>
>>
>> On 19/11/2013 10:09 AM, laredotornado-3 wrote:
>>> I hadn't specified a Maven release version anywhere, so I assume you meant
>>> like this
>>>
>>>      mvn -B -DdevelopmentVersion=52.0.0-SNAPSHOT -DreleaseVersion=52.0.0
>>> -Dusername=***** -Dtag=myprojectt-52.0.0 -DskipTests -P prod -Dresume=false
>>> -DdryRun=true org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
>>>
>>> However, I get the same errors, whether I specify the project version like
>>> this:
>>>
>>>          <parent>
>>>                  <artifactId>subco</artifactId>
>>>                  <groupId>org.mainco.subco</groupId>
>>>                  <version>52.0.0</version>
>>>          </parent>
>>>
>>> or like this
>>>
>>>          <parent>
>>>                  <artifactId>subco</artifactId>
>>>                  <groupId>org.mainco.subco</groupId>
>>>                  <version>52.0.0-SNAPSHOT</version>
>>>          </parent>
>>>
>>> Was there something more I needed to do? -
>>>
>>>
>>>
>>> --
>>> View this message in context: http://maven.40175.n5.nabble.com/Is-it-possible-to-release-a-child-module-that-isn-t-listed-in-the-parent-s-list-of-modules-tp5775784p5775848.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
>>>
>>>
>>
>> -- 
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


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