You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dan Tran <da...@gmail.com> on 2015/05/14 07:47:15 UTC
deployAtEnd really works?
Hi
I am using this feature the first time and it does not seem to work
mvn clean deploy -DdeployAtEnd=true
Each module displays this string at deploy phase
[INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ xxxxx*
[INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
Once the whole build is done, no deploy activity
Am I missing any thing?
Thanks
-Dan
Re: deployAtEnd really works?
Posted by Robert Scholte <rf...@apache.org>.
deployAtEnd works for most projects, not all. Hence, it is 'false' by
default.
Improvements need to be made in Maven Core itself[1]
It seems like Jason wants to fix this for the next release.
[1] https://issues.apache.org/jira/browse/MNG-5666
Op Thu, 14 May 2015 10:21:19 +0200 schreef Karl Heinz Marbaise
<kh...@gmx.de>:
> Hi Dan,
>
> On 5/14/15 8:12 AM, Dan Tran wrote:
>> Hi Bernd ,
>>
>> I dont configure or execute any maven-deploy-plugin at my top level
>> parent
>> pom.
>>
>> The only thing that I have which may not be very conventional:
>>
>> all of my modules are conditional activated by profile looking for
>> existing
>> existing pom
>>
>> <profile>
>> <id>enable-compX</id>
>> <activation>
>> <file>
>> <exists>components/compX/pom.xml</exists>
>> </file>
>> </activation>
>> <modules>
>> <module>components/compX</module>
>> </modules>
>> </profile>
>>
>>
>> I am using Maven 3.2.3
>
> What's the reason having a module activating via profile...
>
> http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: deployAtEnd really works?
Posted by Dan Tran <da...@gmail.com>.
I hit the same usecase discussed at your blog, and have to orchestrate
maven to activate all modules at release time ( maven -B release:prepare
release:perform -Dmy-release together with additional profile activation
at release plugin configuration.
For the currently setup, it will not go thru release plugin, it is a way
for me to create a single maven build by combine a bunch of independent
component sources thru Perforce mapping
-D
On Thu, May 14, 2015 at 1:21 AM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi Dan,
>
> On 5/14/15 8:12 AM, Dan Tran wrote:
>
>> Hi Bernd ,
>>
>> I dont configure or execute any maven-deploy-plugin at my top level parent
>> pom.
>>
>> The only thing that I have which may not be very conventional:
>>
>> all of my modules are conditional activated by profile looking for
>> existing
>> existing pom
>>
>> <profile>
>> <id>enable-compX</id>
>> <activation>
>> <file>
>> <exists>components/compX/pom.xml</exists>
>> </file>
>> </activation>
>> <modules>
>> <module>components/compX</module>
>> </modules>
>> </profile>
>>
>>
>> I am using Maven 3.2.3
>>
>
> What's the reason having a module activating via profile...
>
>
> http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
>
> Kind regards
> Karl Heinz Marbaise
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: deployAtEnd really works?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Dan,
On 5/14/15 8:12 AM, Dan Tran wrote:
> Hi Bernd ,
>
> I dont configure or execute any maven-deploy-plugin at my top level parent
> pom.
>
> The only thing that I have which may not be very conventional:
>
> all of my modules are conditional activated by profile looking for existing
> existing pom
>
> <profile>
> <id>enable-compX</id>
> <activation>
> <file>
> <exists>components/compX/pom.xml</exists>
> </file>
> </activation>
> <modules>
> <module>components/compX</module>
> </modules>
> </profile>
>
>
> I am using Maven 3.2.3
What's the reason having a module activating via profile...
http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: deployAtEnd really works?
Posted by domi <do...@fortysix.ch>.
I think to remember that I had the same problem when a module was included via profile, deployAtEnd seems not to work in that case
Domi
> Am 14.05.2015 um 09:01 schrieb Cintia Del Rio <mi...@gmail.com>:
>
> I was able to achieve similar results using this plugin:
>
> https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
>
> It's possible to disable the 'remote' staging and use only local staging -
> it's called 'Deferred deploy'. Effectively it's the same as deployAtEnd.
>
>
> The nexus staging plugin works with files to keep the state, so it's not
> affected by the customised lifecycles.
>
>> On 14 May 2015 at 16:48, Dan Tran <da...@gmail.com> wrote:
>>
>> Darn, I am using rpm-maven-plugin, and it has its own build lifecycle.
>>
>> what a bug. It is a very good feature
>>
>> Thanks
>>
>> -Dan
>>
>> On Wed, May 13, 2015 at 11:19 PM, Cintia Del Rio <mi...@gmail.com>
>> wrote:
>>
>>> Do you have a customised lifecycle plugin in your reactor?
>>>
>>> https://jira.codehaus.org/browse/MDEPLOY-176
>>>
>>>
>>>> On 14 May 2015 at 16:12, Dan Tran <da...@gmail.com> wrote:
>>>>
>>>> Hi Bernd ,
>>>>
>>>> I dont configure or execute any maven-deploy-plugin at my top level
>>> parent
>>>> pom.
>>>>
>>>> The only thing that I have which may not be very conventional:
>>>>
>>>> all of my modules are conditional activated by profile looking for
>>> existing
>>>> existing pom
>>>>
>>>> <profile>
>>>> <id>enable-compX</id>
>>>> <activation>
>>>> <file>
>>>> <exists>components/compX/pom.xml</exists>
>>>> </file>
>>>> </activation>
>>>> <modules>
>>>> <module>components/compX</module>
>>>> </modules>
>>>> </profile>
>>>>
>>>>
>>>> I am using Maven 3.2.3
>>>>
>>>> -Dan
>>>>
>>>>
>>>> On Wed, May 13, 2015 at 10:56 PM, Bernd Eckenfels <
>>> ecki@zusammenkunft.net>
>>>> wrote:
>>>>
>>>>> Am Wed, 13 May 2015 22:47:15 -0700
>>>>> schrieb Dan Tran <da...@gmail.com>:
>>>>>
>>>>>> I am using this feature the first time and it does not seem to work
>>>>>>
>>>>>> mvn clean deploy -DdeployAtEnd=true
>>>>>>
>>>>>> Each module displays this string at deploy phase
>>>>>>
>>>>>> [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
>>>>>> xxxxx*
>>>>>>
>>>>>> [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
>>>>>>
>>>>>>
>>>>>> Once the whole build is done, no deploy activity
>>>>>>
>>>>>>
>>>>>> Am I missing any thing?
>>>>>
>>>>> Do you have a deploy plugin invocation in the aggregator pom?
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>> --
>>> -------
>>> Sent from TARDIS. Typos might be a timey whyney thingy.
>>> Enviado da TARDIS, podem existir erros devido à diferenças de
>> espaço-tempo.
>>>
>>> Cintia Del Rio
>
>
>
> --
> -------
> Sent from TARDIS. Typos might be a timey whyney thingy.
> Enviado da TARDIS, podem existir erros devido à diferenças de espaço-tempo.
>
> Cintia Del Rio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: deployAtEnd really works?
Posted by Cintia Del Rio <mi...@gmail.com>.
I was able to achieve similar results using this plugin:
https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
It's possible to disable the 'remote' staging and use only local staging -
it's called 'Deferred deploy'. Effectively it's the same as deployAtEnd.
The nexus staging plugin works with files to keep the state, so it's not
affected by the customised lifecycles.
On 14 May 2015 at 16:48, Dan Tran <da...@gmail.com> wrote:
> Darn, I am using rpm-maven-plugin, and it has its own build lifecycle.
>
> what a bug. It is a very good feature
>
> Thanks
>
> -Dan
>
> On Wed, May 13, 2015 at 11:19 PM, Cintia Del Rio <mi...@gmail.com>
> wrote:
>
> > Do you have a customised lifecycle plugin in your reactor?
> >
> > https://jira.codehaus.org/browse/MDEPLOY-176
> >
> >
> > On 14 May 2015 at 16:12, Dan Tran <da...@gmail.com> wrote:
> >
> > > Hi Bernd ,
> > >
> > > I dont configure or execute any maven-deploy-plugin at my top level
> > parent
> > > pom.
> > >
> > > The only thing that I have which may not be very conventional:
> > >
> > > all of my modules are conditional activated by profile looking for
> > existing
> > > existing pom
> > >
> > > <profile>
> > > <id>enable-compX</id>
> > > <activation>
> > > <file>
> > > <exists>components/compX/pom.xml</exists>
> > > </file>
> > > </activation>
> > > <modules>
> > > <module>components/compX</module>
> > > </modules>
> > > </profile>
> > >
> > >
> > > I am using Maven 3.2.3
> > >
> > > -Dan
> > >
> > >
> > > On Wed, May 13, 2015 at 10:56 PM, Bernd Eckenfels <
> > ecki@zusammenkunft.net>
> > > wrote:
> > >
> > > > Am Wed, 13 May 2015 22:47:15 -0700
> > > > schrieb Dan Tran <da...@gmail.com>:
> > > >
> > > > > I am using this feature the first time and it does not seem to work
> > > > >
> > > > > mvn clean deploy -DdeployAtEnd=true
> > > > >
> > > > > Each module displays this string at deploy phase
> > > > >
> > > > > [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> > > > > xxxxx*
> > > > >
> > > > > [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
> > > > >
> > > > >
> > > > > Once the whole build is done, no deploy activity
> > > > >
> > > > >
> > > > > Am I missing any thing?
> > > >
> > > > Do you have a deploy plugin invocation in the aggregator pom?
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > -------
> > Sent from TARDIS. Typos might be a timey whyney thingy.
> > Enviado da TARDIS, podem existir erros devido à diferenças de
> espaço-tempo.
> >
> > Cintia Del Rio
> >
>
--
-------
Sent from TARDIS. Typos might be a timey whyney thingy.
Enviado da TARDIS, podem existir erros devido à diferenças de espaço-tempo.
Cintia Del Rio
Re: deployAtEnd really works?
Posted by Dan Tran <da...@gmail.com>.
Darn, I am using rpm-maven-plugin, and it has its own build lifecycle.
what a bug. It is a very good feature
Thanks
-Dan
On Wed, May 13, 2015 at 11:19 PM, Cintia Del Rio <mi...@gmail.com>
wrote:
> Do you have a customised lifecycle plugin in your reactor?
>
> https://jira.codehaus.org/browse/MDEPLOY-176
>
>
> On 14 May 2015 at 16:12, Dan Tran <da...@gmail.com> wrote:
>
> > Hi Bernd ,
> >
> > I dont configure or execute any maven-deploy-plugin at my top level
> parent
> > pom.
> >
> > The only thing that I have which may not be very conventional:
> >
> > all of my modules are conditional activated by profile looking for
> existing
> > existing pom
> >
> > <profile>
> > <id>enable-compX</id>
> > <activation>
> > <file>
> > <exists>components/compX/pom.xml</exists>
> > </file>
> > </activation>
> > <modules>
> > <module>components/compX</module>
> > </modules>
> > </profile>
> >
> >
> > I am using Maven 3.2.3
> >
> > -Dan
> >
> >
> > On Wed, May 13, 2015 at 10:56 PM, Bernd Eckenfels <
> ecki@zusammenkunft.net>
> > wrote:
> >
> > > Am Wed, 13 May 2015 22:47:15 -0700
> > > schrieb Dan Tran <da...@gmail.com>:
> > >
> > > > I am using this feature the first time and it does not seem to work
> > > >
> > > > mvn clean deploy -DdeployAtEnd=true
> > > >
> > > > Each module displays this string at deploy phase
> > > >
> > > > [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> > > > xxxxx*
> > > >
> > > > [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
> > > >
> > > >
> > > > Once the whole build is done, no deploy activity
> > > >
> > > >
> > > > Am I missing any thing?
> > >
> > > Do you have a deploy plugin invocation in the aggregator pom?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
>
>
> --
> -------
> Sent from TARDIS. Typos might be a timey whyney thingy.
> Enviado da TARDIS, podem existir erros devido à diferenças de espaço-tempo.
>
> Cintia Del Rio
>
Re: deployAtEnd really works?
Posted by Cintia Del Rio <mi...@gmail.com>.
Do you have a customised lifecycle plugin in your reactor?
https://jira.codehaus.org/browse/MDEPLOY-176
On 14 May 2015 at 16:12, Dan Tran <da...@gmail.com> wrote:
> Hi Bernd ,
>
> I dont configure or execute any maven-deploy-plugin at my top level parent
> pom.
>
> The only thing that I have which may not be very conventional:
>
> all of my modules are conditional activated by profile looking for existing
> existing pom
>
> <profile>
> <id>enable-compX</id>
> <activation>
> <file>
> <exists>components/compX/pom.xml</exists>
> </file>
> </activation>
> <modules>
> <module>components/compX</module>
> </modules>
> </profile>
>
>
> I am using Maven 3.2.3
>
> -Dan
>
>
> On Wed, May 13, 2015 at 10:56 PM, Bernd Eckenfels <ec...@zusammenkunft.net>
> wrote:
>
> > Am Wed, 13 May 2015 22:47:15 -0700
> > schrieb Dan Tran <da...@gmail.com>:
> >
> > > I am using this feature the first time and it does not seem to work
> > >
> > > mvn clean deploy -DdeployAtEnd=true
> > >
> > > Each module displays this string at deploy phase
> > >
> > > [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> > > xxxxx*
> > >
> > > [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
> > >
> > >
> > > Once the whole build is done, no deploy activity
> > >
> > >
> > > Am I missing any thing?
> >
> > Do you have a deploy plugin invocation in the aggregator pom?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
--
-------
Sent from TARDIS. Typos might be a timey whyney thingy.
Enviado da TARDIS, podem existir erros devido à diferenças de espaço-tempo.
Cintia Del Rio
Re: deployAtEnd really works?
Posted by Dan Tran <da...@gmail.com>.
Hi Bernd ,
I dont configure or execute any maven-deploy-plugin at my top level parent
pom.
The only thing that I have which may not be very conventional:
all of my modules are conditional activated by profile looking for existing
existing pom
<profile>
<id>enable-compX</id>
<activation>
<file>
<exists>components/compX/pom.xml</exists>
</file>
</activation>
<modules>
<module>components/compX</module>
</modules>
</profile>
I am using Maven 3.2.3
-Dan
On Wed, May 13, 2015 at 10:56 PM, Bernd Eckenfels <ec...@zusammenkunft.net>
wrote:
> Am Wed, 13 May 2015 22:47:15 -0700
> schrieb Dan Tran <da...@gmail.com>:
>
> > I am using this feature the first time and it does not seem to work
> >
> > mvn clean deploy -DdeployAtEnd=true
> >
> > Each module displays this string at deploy phase
> >
> > [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> > xxxxx*
> >
> > [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
> >
> >
> > Once the whole build is done, no deploy activity
> >
> >
> > Am I missing any thing?
>
> Do you have a deploy plugin invocation in the aggregator pom?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: deployAtEnd really works?
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Am Wed, 13 May 2015 22:47:15 -0700
schrieb Dan Tran <da...@gmail.com>:
> I am using this feature the first time and it does not seem to work
>
> mvn clean deploy -DdeployAtEnd=true
>
> Each module displays this string at deploy phase
>
> [INFO] *--- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> xxxxx*
>
> [INFO] Deploying xxxxx:0.0.1-SNAPSHOT at end
>
>
> Once the whole build is done, no deploy activity
>
>
> Am I missing any thing?
Do you have a deploy plugin invocation in the aggregator pom?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org