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 <e...@zusammenkunft.net>
wrote:
> Am Wed, 13 May 2015 22:47:15 -0700
> schrieb Dan Tran <dant...@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-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
