Our parent pom is using the configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.2</version>
<configuration>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Papache-release ${arguments}</arguments>
</configuration>
</plugin>
we are specifying
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<!-- see http://jira.codehaus.org/browse/MRELEASE-812 -->
<version>2.4.2</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9</version>
</dependency>
</dependencies>
<configuration>
<localCheckout>true</localCheckout>
<pushChanges>true</pushChanges>
<tagNameFormat>@{project.artifactId}-@
{project.version}</tagNameFormat>
<useReleaseProfile>false</useReleaseProfile>
<preparationGoals>clean install</preparationGoals>
<goals>deploy</goals>
<!-- The profile we want to use when doing the release -->
<arguments>-Prelease,enable-schemagen,apt,sourcecheck,hibernate</arguments>
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>
I'm wondering why we have to enable the "release" profile explicitly,
because we already configured it in our pom...
Best,
Christian
On Sun, Oct 18, 2015 at 10:10 AM, Willem Jiang <willem.ji...@gmail.com>
wrote:
> Hi Gregor，
>
> The "-Prelease" profile can help you to update the version of those
> integration test projects.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Oct 18, 2015 at 3:35 PM, Gregor Zurowski <gre...@list.zurowski.org
> >
> wrote:
>
> > Unfortunately, I need to cancel this vote, as I realized that the
> > versions of four integration test projects (camel-itest-performance,
> > camel-itest-karaf, camel-performance and camel-itest-osgi) were not
> > updated properly. I won't be able to prepare a new release candidate
> > today, so I need to postpone it to some time later this week.
> >
> > Thanks,
> > Gregor
> >
> > On Sun, Oct 18, 2015 at 7:24 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> > wrote:
> > > +1 (binding)
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 10/17/2015 11:40 PM, Gregor Zurowski wrote:
> > >>
> > >> Hi Everyone:
> > >>
> > >> This is a vote to release Apache Camel 2.15.4 that has over 40 fixes
> > >> and improvements. As recently discussed on the dev mailing list, we
> > >> want to get this patch release out as it also includes some important
> > >> bug fixes for camel-test-blueprint.
> > >>
> > >> Release notes:
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12333271
> > >>
> > >> Staging repository:
> > >>
> https://repository.apache.org/content/repositories/orgapachecamel-1039/
> > >>
> > >> Tarballs:
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1039/org/apache/camel/apache-camel/2.15.4/
> > >>
> > >> Tag:
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=2de23e3bc6f566ecae8c7c6e115246235e78e0d5
> > >>
> > >> Please test this release candidate and cast your vote.
> > >> [ ] +1 Release the binary as Apache Camel 2.15.4
> > >> [ ] -1 Veto the release (provide specific comments)
> > >>
> > >> The vote is open for at least 72 hours.
> > >>
> > >> Thanks,
> > >> Gregor
> > >>
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> >
>
