Hi Olivier,
No, the maven deploy goal is not executed twice if I launch it directly.
It only happens with therelease:perform goal (which has a deploy goal
configured)
org.apache.maven.plugins
maven-release-plugin
3.0.0
d to deploy artifacts: Could not
> transfer artifact temp.mectagcore:mectagcore:pom:1.0.0 from/to
> maven-artifacts (https://xxx.jfrog.io/artifactory/maven-artifacts): status
> code: 403, reason phrase: (403)
>
> If we disable the build-cache during release targets, we see
usual release plugin configuration is:
org.apache.maven.plugins
maven-release-plugin
3.0.0
* -DskipEnforceSnapshots -DskipITs -DskipTests
-DskipUTs
deploy
* SemVerVersionPolicy
GithubReleaseStrategy
@{prefix} Prepare release
The Apache Maven team is pleased to announce the release of the Apache
Maven Release Plugin, version 3.0.1
https://maven.apache.org/maven-release/maven-release-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-release-plugin
Hi,
The vote has passed with the following result:
+1: Herve Boutemy, Sylwester Lachiewicz, Maarten Mulders, Tamás Cservenák,
Guillaume Nodet, Olivier Lamy, Karl Heinz Marbaise
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the
Hi,
+1 from me,
Kind regards
Karl Heinz Marbaisew
On 30.05.23 23:34, Slawomir Jaranowski wrote:
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
There are still a couple of issues left in JIRA:
+1
On Wed, 31 May 2023 at 07:35, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
+1
Le mar. 30 mai 2023 à 23:35, Slawomir Jaranowski a
écrit :
> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
>
lopers List
Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1
FYI, there seem to be some issues with dependabot configs. It's useful
when it fires, but it doesn't always, and sometimes it closes update
PRs for no valid reason I can discern.
And of course there are the more c
iotte Rusty Harold
> Sent: Wednesday, May 31, 2023 7:09:22 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1
>
> One minor dependency update to maven-scm:
> https://na01.safelinks.protection.outlook.com/?url=http
Outlook for Android<https://aka.ms/AAb9ysg>
From: Elliotte Rusty Harold
Sent: Wednesday, May 31, 2023 7:09:22 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1
One minor dependency update to maven-scm:
https:
One minor dependency update to maven-scm:
https://github.com/apache/maven-release/pull/192
Otherwise, looks good.
On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
>
+1
On Tue, May 30, 2023 at 11:35 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
>
+1 - tested on macOS using Maven 3.9.2 with a custom release strategy.
Maarten
On 30/05/2023 23:34, Slawomir Jaranowski wrote:
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
There are still a couple of issues left in JIRA:
+1
wt., 30 maj 2023, 23:35 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
>
+1
Reproducible Builds ok: reference build done with JDK 17 on *nix
Regards,
Hervé
On 2023/05/30 21:34:37 Slawomir Jaranowski wrote:
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
Staging repo:
Hi,
Reopened. PR are welcome.
pt., 17 cze 2022 o 18:08 Pablo Caraballo Llorente
napisał(a):
> Hello.
>
> As a user of the maven-release-plugin, I find that the issue MRELEASE-282
> <https://issues.apache.org/jira/browse/MRELEASE-282> is an improvement
> that
> wo
Hello.
As a user of the maven-release-plugin, I find that the issue MRELEASE-282
<https://issues.apache.org/jira/browse/MRELEASE-282> is an improvement that
would be useful to improve the configuration of the prepare and perform
goals.
In my specific case, I cannot configure different arg
Guys,
let me know when you are done with all issues for M6, I will happily do
the release for the community.
M
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/upgrade.html
would be nice
yes, let's focus and do the release soon
Le vendredi 6 mai 2022, 04:05:15 CEST Olivier Lamy a écrit :
> Nice it looks like the call for release suddenly generates a lot of
> activity for this
>>> It looks there is a plan for early (ish) next week
> >>>
> >>> cheers
> >>> Olivier
> >>>
> >>> On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud <
> s...@leberrigaud.org>
> >>>
> >>> wrote:
> >>&
an idea of when a potential 3.0.0-M6 of the
maven-release-plugin might happen.
I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
quick PR & merge. And now, obviously, I would love to be able to use a
regular build of the plugin.
Thanks for your help,
SaM
(1) h
my wrote:
> > Hi
> > It looks there is a plan for early (ish) next week
> >
> > cheers
> > Olivier
> >
> > On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud
> >
> > wrote:
> > > Hello devs,
> > >
> > > I'd just like to get
next week
>
> cheers
> Olivier
>
> On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud
> wrote:
>
> > Hello devs,
> >
> > I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > maven-release-plugin might happen.
> >
> &
s it an alpha release? A beta
> > version? Is it production ready? Does it depend on the plugin (please say
> > no)?
> >
> > Gary
> >
> > On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud
> >
> > wrote:
> > > Hello devs,
> > >
> >
Am 2022-04-26 um 21:14 schrieb Jeff Jensen:
M is for Milestone, an incremental release towards the eventual final
release considered early production ready but incomplete for full planned
features and implementation.
To the point!
ase? A beta
> version? Is it production ready? Does it depend on the plugin (please say
> no)?
>
> Gary
>
> On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud
> wrote:
>
> > Hello devs,
> >
> > I'd just like to get an idea of when a potential 3.0.0-M6
3.0.0-M6 of the
> maven-release-plugin might happen.
>
> I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> quick PR & merge. And now, obviously, I would love to be able to use a
> regular build of the plugin.
>
> Thanks for your help,
> SaM
>
>
Hi
It looks there is a plan for early (ish) next week
cheers
Olivier
On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud
wrote:
> Hello devs,
>
> I'd just like to get an idea of when a potential 3.0.0-M6 of the
> maven-release-plugin might happen.
>
> I've managed to co
Hello devs,
I'd just like to get an idea of when a potential 3.0.0-M6 of the
maven-release-plugin might happen.
I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
quick PR & merge. And now, obviously, I would love to be able to use a
regular build of the plugin.
Th
. The default rules assume the tag
to be just the version (i.e. "1.2.3") and the patterns to follow my
understanding of https://www.conventionalcommits.org/en/v1.0.0/
A "full" example (copied from the IT test I created):
org.apache.maven.plugins
maven-release-plugin
@project.
> the maven-release-plugin.
>
> Since this is not yet a part of the current version of the release plugin I
> decided to give it a go myself.
>
> So far I have succeeded in creating a new VersionPolicy that does this and
> I'm wondering if the committers would consider includin
Hi,
I would like to use the ideas from the Conventional Commits to
automatically determine the next version for my release when releasing with
the maven-release-plugin.
Since this is not yet a part of the current version of the release plugin I
decided to give it a go myself.
So far I have
Hi,
The vote has passed with the following result:
+1 : Tibor Digana, Hervé BOUTEMY, Olivier Lamy, Sylwester Lachiewicz, Arnaud
Héritier, Robert Scholte
PMC quorum: reached
I will promote the artifacts to the central repo.
On 12-4-2021 19:31:13, Robert Scholte wrote:
Hi,
We solved 5
.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/examples/rollback-release.html
>
> Le jeudi 15 avril 2021, 22:38:05 CEST Rémy Sanlaville a écrit :
> > Hi Hervé,
> >
> > PR created (cf. https://github.com/apache/maven-release/pulls)
> >
> > Re
thank you Remi
PR merged and current release HTML tweaked [1] to benefit from the
documentation just now
Regards,
Hervé
https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/examples/rollback-release.html
Le jeudi 15 avril 2021, 22:38:05 CEST Rémy
aware to edit the page as you asked me
> >
> > > There's an edit-button on the page (upper left in nav bar) that links
> to
> > >
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > > -release-plugin/src/site/apt/examples/
+1
On 12-4-2021 19:31:13, Robert Scholte wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
There are still a couple of issues left in JIRA:
+1
On Thu, Apr 15, 2021 at 10:36 AM Sylwester Lachiewicz
wrote:
> +1
> Sylwester
>
> czw., 15 kwi 2021, 10:22 użytkownik Olivier Lamy
> napisał:
>
> > +1
> >
> > On Tue, 13 Apr 2021 at 3:31 am, Robert Scholte
> > wrote:
> >
> > > Hi,
> > >
> > > We solved 5 issues:
> > >
> > >
> >
>
+1
Sylwester
czw., 15 kwi 2021, 10:22 użytkownik Olivier Lamy napisał:
> +1
>
> On Tue, 13 Apr 2021 at 3:31 am, Robert Scholte
> wrote:
>
> > Hi,
> >
> > We solved 5 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
> >
> > There are
+1
On Tue, 13 Apr 2021 at 3:31 am, Robert Scholte wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
>
+1
checked that the build was reproducible: ok with JDK 8 on Windows
regards,
Hervé
Le lundi 12 avril 2021, 19:31:13 CEST Robert Scholte a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824
> rsion=12348079=Text
>
> There are
I wasn't aware about
> https://github.com/apache/maven-release/pulls
>
> I was just aware to edit the page as you asked me
>
> > There's an edit-button on the page (upper left in nav bar) that links to
> > https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/m
+1
On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
>
/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
Rémy
On Tue, Apr 13, 2021 at
Hi Rémy
I don't see it as PR under https://github.com/apache/maven-release/pulls
I did a quick scan over this list and the open Jira issues and decided not to
add more to this milestone release.
Robert
On 13-4-2021 09:09:21, Rémy Sanlaville wrote:
Hi Robert,
What about
Hi Robert,
What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?
Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
There are still a couple of issues left in JIRA:
nks to
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> thanks,
> Robert
>
>
There's an edit-button on the page (upper left in nav bar) that links to
https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
Would be great if you could help updating this page.
thanks,
Robert
On 17-6-2020 13:45:09
Hello,
FYI, it seems that the page rollback-release.html
<https://maven.apache.org/maven-release/maven-release-plugin/examples/rollback-release.html>
was not updated with the release 3.0.0-M1:
- RELEASE-229 <http://jira.codehaus.org/browse/MRELEASE-229> was fixed by
3.0.
Cancelled due to MRELEASE-1042[1]
I'll drop this release
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MRELEASE-1042
On 7-4-2020 20:48:42, Robert Scholte wrote:
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348049=Text
There
While I confirm MRELEASE-1038 fixed it seems that there is another problem
related to it : https://issues.apache.org/jira/browse/MRELEASE-1042
For now -1
On Tue, Apr 7, 2020 at 8:48 PM Robert Scholte wrote:
> Hi,
>
> We solved 8 issues:
>
>
Tested with a custom release strategy, no findings.
+1 from me.
Maarten
On 07/04/2020 20:48, Robert Scholte wrote:
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348049=Text
>
> There are still a couple of issues left in JIRA:
>
I see this in the pom.xml:
maven-source-plugin
3.2.0
The parent plugin is now 34. I'm not sure exactly what this refers to.
The version numbers of the plugins perhaps? Or the
maven-source-plugin? Or all the following plugins?
On Tue, Apr 7, 2020 at 2:48 PM Robert Scholte wrote:
>
> Hi,
>
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348049=Text
There are still a couple of issues left in JIRA:
://bernd.eckenfels.net
Von: Eric Lilja
Gesendet: Tuesday, February 4, 2020 7:35:01 PM
An: Maven Developers List
Betreff: Re: Prevent maven-release-plugin from reformatting attributes on
project element
Sure! Today I did a release in a single module project
An: Maven Developers List
Betreff: Re: Prevent maven-release-plugin from reformatting attributes on
project element
Ah, yes, I do remember the changed indentation of the tag element in the
past, put I don't recall seeing that lately. Have to check tomorrow when I
get to the office.
Bernd: Which
Ah, yes, I do remember the changed indentation of the tag element in the
past, put I don't recall seeing that lately. Have to check tomorrow when I
get to the office.
Bernd: Which version of the maven-release-plugin did you use?
- Eric L
On Tue, Feb 4, 2020 at 8:30 PM Bernd Eckenfels
wrote
://bernd.eckenfels.net
Von: Eric Lilja
Gesendet: Tuesday, February 4, 2020 3:21:51 PM
An: Maven Developers List
Betreff: Prevent maven-release-plugin from reformatting attributes on project
element
Hi, we noticed that maven-release-plugin changes formatting of the project
t; > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pretty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> &g
tty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> > - Eric L
> >
> > > Enrico
> > >
> > > [1]
> > >
> http://maven.apache.org/mav
.
> > If you have some tool that pretty prints XML according to your
> > comporate rules you could invoke it in completionGoals [1]
>
> That could be a workaround for now. Thanks!
>
> - Eric L
>
> > Enrico
> >
> > [1]
> > http://maven.apach
en.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals
>
aware of any such feature.
If you have some tool that pretty prints XML according to your
comporate rules you could invoke it in completionGoals [1]
Enrico
[1]
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals
>
> - Eric L
>
> On Tue, Feb 4, 2020 at
t; As far as it creates a valid XML with the same meaning this should not be a
> problem
>
> Enrico
>
> Il Mar 4 Feb 2020, 15:22 Eric Lilja ha scritto:
>
> > Hi, we noticed that maven-release-plugin changes formatting of the
> project
> > element, it writes the elemen
Eric
What's your use case?
As far as it creates a valid XML with the same meaning this should not be a
problem
Enrico
Il Mar 4 Feb 2020, 15:22 Eric Lilja ha scritto:
> Hi, we noticed that maven-release-plugin changes formatting of the project
> element, it writes the element as a singl
Hi, we noticed that maven-release-plugin changes formatting of the project
element, it writes the element as a single line, removing existing line
breaks on attributes. Is it possible to make it preserve original
formatting?
We're using maven-release-plugin version 3.0.0-M1
- Eric L
, at 21:02, Hervé Boutemy wrote:
org.apache.maven.plugins
maven-release-plugin
3.0.0-M1
Him, updating my projects to use this and got:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on
project smx3.bill-of-materials: Execution default
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:
>
> org.apache.maven.plugins
> maven-release-plugin
> 3.0.0-M1
>
Him, updating my projects to use this and got:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) o
The Apache Maven team is pleased to announce the release of the Apache Maven
Release Plugin, version 3.0.0-M1.
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare and
perform.
https
as expected:
> > - sources.jar are all different, because of a different order of
> > META-INF/LICENSE DEPENDENCIES and NOTICE
> > - maven-release-plugin-3.0.0-M1.jar is different, just because I forgot to
> > upgrade maven-plugin-tools (using version 3.2 which puts a date in
Hi,
The vote has passed with the following result:
+1 : Enrico Olivelli, Olivier Lamy, Robert Scholte, Hervé Boutemy
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail:
different order of
> META-INF/LICENSE DEPENDENCIES and NOTICE
> - maven-release-plugin-3.0.0-M1.jar is different, just because I forgot to
> upgrade maven-plugin-tools (using version 3.2 which puts a date in
> generated xml)
> - maven-release-manager-3.0.0-M1.jar is different becaus
Here is my +1
On reproducibility test, I took time to install a JDK 7 on my Mac and test, and
the results are not as good as expected:
- sources.jar are all different, because of a different order of
META-INF/LICENSE DEPENDENCIES and NOTICE
- maven-release-plugin-3.0.0-M1.jar is different, just
:
e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853
Staging site:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
https://maven.apache.org/maven-release-archives/maven-release-LATEST/
Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html
In addition
.. SUCCESS [ 3.639
s]
[INFO] Maven Release APIs . SUCCESS [ 2.492
s]
[INFO] Maven Release Manager .. SUCCESS [01:38
min]
[INFO] Maven Release Plugin ... SUCCESS [04:36
min
dc86a661e767074315a1f0ac0b8e4633b853
>
> Staging site:
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/
>
> Guide to testing staged releases:
> https://maven.
-release-archives/maven-release-LATEST/maven-release-plugin/
https://maven.apache.org/maven-release-archives/maven-release-LATEST/
Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html
In addition to these instructions, I'd like voters to check
about throwing in MRELEASE-229 as well?
Regards
Clemens
Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
Hi,
I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property
I'd like to release maven-release-plugin.
But there are a few open Jira issues
> > > how about throwing in MRELEASE-229 as well?
> > >
> > > Regards
> > >
> > > Clemens
> > >
> > > Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
> > > > Hi,
> > > >
> > > > I fixed MRELEASE-102
écrit :
> > Hi,
> >
> > how about throwing in MRELEASE-229 as well?
> >
> > Regards
> >
> > Clemens
> >
> > Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
> > > Hi,
> > >
> > > I fixed MRELEASE-1029 [1] for Reproducible B
of
> > project.build.outputTimestamp property
> >
> > I'd like to release maven-release-plugin.
> >
> > But there are a few open Jira issues assigned to the release:
> > MRELEASE-973,
> > MRELEASE-955, MRELEASE-980, MRELEASE-993
> >
> >
Hi,
how about throwing in MRELEASE-229 as well?
Regards
Clemens
Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
Hi,
I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property
I'd like to release maven-release-plugin.
But there are a few open
Hi,
I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property
I'd like to release maven-release-plugin.
But there are a few open Jira issues assigned to the release: MRELEASE-973,
MRELEASE-955, MRELEASE-980, MRELEASE-993
Can everyone check
Hi all,
just a quick question. I have a project that I'm releasing using the
maven-release-plugin, but every time I call release:prepare the build fails
with OutofMemoryError. I tried setting the MAVEN_OPTS to "-Xmx2G" but
honestly I don't think it has any effect because after the bu
to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-parent.git
>
> commit 9782eabad3cc07473924723d9ecfdc8b821b01a9
> Author: Hervé Boutemy
> AuthorDate: Sun Nov 11 20:36:40 2018 +0100
>
> [maven-release-plugin] rollback the release of maven-
Hello there,
I have a question regarding maven release plugin. We use codehaus
native-plugin to build jni, I want to pass the cflags during release phase.
However I see that I am unable to pass any of the arguments through release
plugin. Any experience or pointers would help
this is mvn command
with determining what kind
of project every pom is.
It hasn't been released yet, but it was written to help the
maven-release-plugin
I hope this makes sense,
Robert
[1] http://svn.apache.org/repos/asf/maven/shared/trunk/maven-project-utils/
On Tue, 21 Nov 2017 10:31:07 +0100, Petar Tahchiev
inish first, maven-release-plugin is not
> one of them right now.
>
> thanks,
> Robert
>
>
> On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev <paranoia...@gmail.com>
> wrote:
>
> Hi Robert,
>>
>> any updates on the release-aggregator? Is there
Hi Petar,
would be great if you could pick this up.
There's enough work I want to finish first, maven-release-plugin is not
one of them right now.
thanks,
Robert
On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev <paranoia...@gmail.com>
wrote:
Hi Robert,
any updates on the r
Hi Robert,
any updates on the release-aggregator? Is there anything I can do to help?
2017-06-27 22:43 GMT+03:00 Robert Scholte :
> Hi Petar,
>
> This is a clear sign that ${project} should not be used to resolve this.
> Instead the pom should be analyzed again and if
tended via commandline argument, you
need to do this:
-Dkey=value ${arguments}
Thanks for your explanations...
So that means the configuration for the maven-release-plugin must be
done before to support expanding the arguments like I expected..
So on the other hand the maven-r
}
Thanks for your explanations...
So that means the configuration for the maven-release-plugin must be
done before to support expanding the arguments like I expected..
So on the other hand the maven-release-plugin documentation for the
arguments property:
http://maven.apache.org/maven-release
hought the gpg.keyname property will be given to the called maven
process which will run the part in prepare...but based on my tests it
looks like it is not the case...cause the given "arguments" not
transfered or added to the Maven sub process...(Ok I though might be
caused by an older maven-r
to the called maven
process which will run the part in prepare...but based on my tests it
looks like it is not the case...cause the given "arguments" not
transfered or added to the Maven sub process...(Ok I though might be
caused by an older maven-release-plugin so I tested the same with the
ne
Hi Petar,
This is a clear sign that ${project} should not be used to resolve this.
Instead the pom should be analyzed again and if there's a system property
matching the parent, it should be replaced before loading the parent.
That'll require quite some new lines of code :)
The suggested
Petar Tahchiev wrote:
> Hey guys,
>
> my pull-request worked fine to not show the prompt to specify a version.
> However, it fails to update snapshot dependency versions when you resolve
> the parent to a concrete version.
> Particularly in my case:
>
>
> [BOM]
>
Hey guys,
my pull-request worked fine to not show the prompt to specify a version.
However, it fails to update snapshot dependency versions when you resolve
the parent to a concrete version.
Particularly in my case:
[BOM]
/\
1 - 100 of 743 matches
Mail list logo