urrent issue with the maven-release-plugin. I want
> to publish a multi-module project of mine to Maven Central, via
> oss.sonatype.org. When I'm executing mvn release:perform (mvn
> release:prepare works without problems), a NullPointerException occurs,
> with the following stacktrace
Hello everyone,
hopefully, someone on this mailing list can provide me with some hint
what is causing my current issue with the maven-release-plugin. I want
to publish a multi-module project of mine to Maven Central, via
oss.sonatype.org. When I'm executing mvn release:perform (mvn
onment, and we have seen strange behavior in several maven projects,
> when using the release plugin in conjunction with build-cache, which we have
> been able to reproduce both locally and in CI.
>
> Our usual release plugin configuration is:
>
>
> org.
Hi all,
We are starting to apply the build-cache maven extension in our local
and CI environment, and we have seen strange behavior in several maven
projects, when using the release plugin in conjunction with build-cache,
which we have been able to reproduce both locally and in CI.
Our
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
I have added a comment to the PR.
Robert also did and the contributor is waiting for Robert's feedback
Enrico
Il Mer 5 Ago 2020, 10:42 Konrad Windszus ha scritto:
> Hi,
> as the last release of the m-release-plugin (3.0.0-M2) failed due to
> https://issues.apache.org/jira/browse/MREL
Hi,
as the last release of the m-release-plugin (3.0.0-M2) failed due to
https://issues.apache.org/jira/browse/MRELEASE-1042
<https://issues.apache.org/jira/browse/MRELEASE-1042> and a PR has been
provided with a fix for quite some time now
(https://github.com/apache/maven-release/p
ite and the available artifact.
>
> https://maven.apache.org/maven-release/maven-release-plugin/index.html
> lists 3.0.0-M2 published 2020-04-07 as the current release, but it
> cannot be downloaded from eg.
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release->
There is a mismatch between the published site and the available artifact.
https://maven.apache.org/maven-release/maven-release-plugin/index.html
lists 3.0.0-M2 published 2020-04-07 as the current release, but it
cannot be downloaded from eg.
https://repo.maven.apache.org/maven2/org/apache
Hello, I am having trouble understanding remoteTagging.
I use Maven 3.5. 4, maven-release-plugin 3.0. 0-M1 and Subversion 1.8 to build
multimodule projects.
Sunbversion is a standard structure: trunk, branches, and tags.
trunk/
├ myProject/
│ ├ pom.xml (parent pom)
│ ：
├ sub1
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
Hi list,
I'm using the Maven Release Plugin together with Git for version
control. I would like to achieve the following. When I create a release
on master, say version 1.5.0, I would like to have both a tag and a new
branch - starting at that tag. The branch would be there to release
fix
Normally you need to use the -Darguments="-Dexec.skip=true" for the release
plugin to pass on options to the child invocations.
mvn -DdryRun -Dexec.skip=true -Darguments="..." release:prepare
Gruss
Bernd
--
http://bernd.eckenfels.net
Greetings.
I'm having trouble running a sentence like this:
"$> mvn release:prepare -DdryRun -Dexec.skip=true"
With this configuration:
"
...
org.apache.maven.plugins
maven-release-plugin
looks like there is WIP on that:
https://issues.apache.org/jira/browse/MRELEASE-980
Help welcome (testing, providing feedback, ...)
Regards,
Hervé
Le jeudi 31 octobre 2019, 02:31:47 CET Scott Rossillo a écrit :
> We're using the maven-release-plugin and all our tags end up looking l
don' t recall any commits like that, generally I see that the last commit
in a tag is "[maven-release-plugin] prepare release
<https://github.com/B3Partners/brmo/commit/bdcc63208bd4a8b521f3b82bd82d87148e9c2687>
..."
and in my master branch I see "[maven-release-plugin] p
We're using the maven-release-plugin and all our tags end up looking like:
vX.Y.Z copy for tag vX.Y.Z
With git "copy for tag" is pretty nonsensical. Preferably, the message
would be "Release X.Y.Z". I looked at the source code and see the actual
tagging is delegate
Hello,
We use Maven release plugin with Jazz repository for automated release. While
performing deliver operation below command is used.
"scm deliver --repository-uri --username --password *
--source --target --overwrite-uncommitted"
Internally we have configured commit ru
So I wrote a blog post on how we use the Maven Release Plugin with Jenkins
to do Continuous Delivery and Continuous Deployment in the DevOptics team
of CloudBees.
If you are interested it's at:
https://www.cloudbees.com/blog/apache-maven-continuous-deliverydeployment-devoptics-teams-approach
quot; already has quotes, so you need to escape the
> those.
>
> thanks,
> Robert
>
>
> On Thu, 17 May 2018 23:20:59 +0200, Naveen Swamy <mnnav...@gmail.com>
> wrote:
>
> Hello there,
>>
>> I have a question regarding maven release plugin. We use codehaus
&
quotes, so you need to escape the
those.
thanks,
Robert
On Thu, 17 May 2018 23:20:59 +0200, Naveen Swamy <mnnav...@gmail.com>
wrote:
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 rele
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
On 1 Mar 2018, at 23:18, Matthew Broadhead wrote:
> Thanks Mark. looks easy enough. i may try a maven plugin first though as i
> like the idea of maven controlling all the git pushes etc
I tend to NOT let maven do the git pushes, for the cases we're doing releases
on a hot fix, or a support
ster, develop, feature/*
branches). If
so, we use the jgitflow-maven-plugin instead of
maven-release-plugin, which
handles these transitions and the inherent conflicts caused by the
maven
versioning.
Unfortunately, the maintainer is no longer working on it (and says
he's not
even working in java
s
quite sweetly.
… and it is being actively maintained.
Cheers,
Steve C
On 1 Mar 2018, at 12:56 am, Ben Tatham <bentat...@nanometrics.ca> wrote:
Sounds like you're using gitflow (master, develop, feature/* branches). If
so, we use the jgitflow-maven-plugin instead of maven-release
/*
branches). If
so, we use the jgitflow-maven-plugin instead of
maven-release-plugin, which
handles these transitions and the inherent conflicts caused by the
maven
versioning.
Unfortunately, the maintainer is no longer working on it (and says
he's not
even working
cs.ca> wrote:
>
> Sounds like you're using gitflow (master, develop, feature/* branches). If
> so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which
> handles these transitions and the inherent conflicts caused by the maven
> versioning.
>
> Unfort
On 1 Mar 2018, at 2:56, Ben Tatham wrote:
> Sounds like you're using gitflow (master, develop, feature/* branches). If
> so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which
> handles these transitions and the inherent conflicts caused by the maven
>
thanks Ben that looks just the job
On 28/02/2018 14:56, Ben Tatham wrote:
Sounds like you're using gitflow (master, develop, feature/* branches). If
so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which
handles these transitions and the inherent conflicts caused
Sounds like you're using gitflow (master, develop, feature/* branches). If
so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which
handles these transitions and the inherent conflicts caused by the maven
versioning.
Unfortunately, the maintainer is no longer working
hi,
not sure if this is the correct place to ask questions about the maven
release plugin
i am trying to set my snapshots and releases properly
i am using git with a master branch and a development branch
how do i work in the snapshot on development and then tag the releases
to master?
if you
holte [mailto:rfscho...@apache.org]
Sent: Monday, November 27, 2017 03:11
To: Maven Users List <users@maven.apache.org>
Subject: Re: Commit message for release plugin
Hi Sander,
Messages are part of a "component"[1][2] And here is where the message is
created[3]
So yes, it is
Maven for build, but not
for release. For that it has a shell script that, among other things,
does a single commit (representing the release) which includes a mix of
manual and automated information in the commit message. I'm trying to
convert this over to using the Maven Release Plugin. I'
to convert this over to using the
Maven Release Plugin. I'm quite familiar with that plugin, so I know that it
doesn't typically work like this legacy script does. But in order to give the
consumers of this process less change to deal with, I'm wondering if there's
any workarounds to include a more
e.org/maven-ci-friendly.html
>
>> Cheers,
>> Steve C
>>> On 24 Oct 2017, at 8:27 pm, Pascal <pascal.gr...@gmail.com> wrote:
>>>
>>> For me it's hard to understand the problem you are having, it might help to
>>> specify the exact errors you
, at 8:27 pm, Pascal <pascal.gr...@gmail.com> wrote:
For me it's hard to understand the problem you are having, it might help to
specify the exact errors you are getting.
If you are willing to try something other than the release plugin, have a
look at https://axelfontaine.com/blo
Oct 2017, at 8:27 pm, Pascal <pascal.gr...@gmail.com> wrote:
>
> For me it's hard to understand the problem you are having, it might help to
> specify the exact errors you are getting.
>
> If you are willing to try something other than the release plugin, have a
> look at ht
[EXTERNAL] Re: how to use both buildnumber-maven-plugin
> and maven-release-plugin
>
> External Sender: Use caution with links/attachments.
>
>
>
> Hi,
>
> On 24/10/17 15:59, Justin Georgeson wrote:
> > I want to enforce in every build (not just release builds)
arguments="-Dmaven.buildNumber.doCheck=false"' but that just seems
hacky, so I was curious if there's a better way.
You know about the release:prepare goal what it is exactly doing ?
http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
Maybe I misunderstand your que
aven Users List <users@maven.apache.org>; Justin Georgeson
<justin.george...@halliburton.com>
Subject: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and
maven-release-plugin
External Sender: Use caution with links/attachments.
Hi,
the question is what the real problem is?
C
Hi,
the question is what the real problem is?
Can you have an example project which shows the problem? Or can you
describe more in detail what exactly does not work or not work like you
expect it..
Kind regards
Karl Heinz Marbaise
For me it's hard to understand the problem you are having, it might help to
specify the exact errors you are getting.
If you are willing to try something other than the release plugin, have a
look at https://axelfontaine.com/blog/dead-burried.html
Cheers,
Pascal
2017-10-23 18:40 GMT+02:00
The 'clean verify' invoked by release:prepare fails in buildnumber-maven-plugin
because pom.xml is modified. I can pass arguments to release:prepare have
buildnumber-maven-plugin skip the check for modifications, but that check is
one of the main motivations for using it in the first place.
n Github shows something:
https://github.com/Pr0methean/BetterRandom/commit/0ce146b58ab0f18da93d665e8604dfa15eebdf09
Revert "Merge coverage and post-Proguard testing into same run."
This reverts commit a7f1da8.
instead of the usual messages like:
"[maven-release-plugin] prepare rele
dom
>0.9.2.15-SNAPSHOT
>BetterRandom
>
>
> So in the end the parent is an aggregator...So my question if why are
> you trying to release a single module ? Why not the whole in one go?
>
> Furthermore you see the difference in the version ?
>
> BTW: I'm not sure but there
versions of maven-release-plugin (but I'm not sure if really support
releases of childs at the moment?)...
Kind regards
Karl Heinz Marbaise
On 10/09/17 20:52, Chris wrote:
I've been informed at https://issues.sonatype.org/browse/OSSRH-34445 that:
"The logs show that the build is t
I see that after you build the release version, you are then building the
snapshot version. It is the latter that is being uploaded:
>
> Uploaded:
>
I've been informed at https://issues.sonatype.org/browse/OSSRH-34445 that:
"The logs show that the build is trying to checkout the release branch, but
whatever it checks out probably still has 0.9.2.7-SNAPSHOT as the version
instead of 0.9.2.8
Once the build things it's building a SNAPSHOT
t; You don't put it in the URL.
> >>
> >> subdir/pom.xml
> >>
> >>
> >>
> >> On Fri, Jun 17, 2016 at 10:21 PM, Dan Tran <dant...@gmail.com> wrote:
> >> > Hi
> >> >
> >> > I would like to host multiple mult
-module maven projects, each project
>> has
>> > its own top level folder
>> > under same GIT repository
>> >
>> > is it possible to release each project using maven release plugin?, if
>> so,
>> > what would be SCM URL for each folder?
>>
subdir/pom.xml
>
>
>
> On Fri, Jun 17, 2016 at 10:21 PM, Dan Tran <dant...@gmail.com> wrote:
> > Hi
> >
> > I would like to host multiple multi-module maven projects, each project
> has
> > its own top level folder
> > under same GIT repository
> &g
it possible to release each project using maven release plugin?, if so,
> what would be SCM URL for each folder?
>
> Advice are greatly appreciated.
>
> -Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.or
elease each project using maven release plugin?, if
so,
what would be SCM URL for each folder?
Advice are greatly appreciated.
-Dan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Hi
I would like to host multiple multi-module maven projects, each project has
its own top level folder
under same GIT repository
is it possible to release each project using maven release plugin?, if so,
what would be SCM URL for each folder?
Advice are greatly appreciated.
-Dan
Hi Bernd,
you should make sure you are using a recent version of maven-release-plugin
(>=2.5). Older versions have compatibility issues because of the git scm
provider they depend on which is incompatible with current git versions.
Vincent
2015-10-05 22:26 GMT+02:00 Bernd Eckenfels
Hi,
I am trying to use the release plugin with a new project where I want the
entire project to use a single version number (vs. one version number per
module). I have the single version number part working like this:
1.)In my parent pom, I do the following:
test
snapshots
on
https://github.com/apache/maven-release. It is implementing the standard
versioning scheme to deal with this with maven.
Vincent
2015-10-06 22:01 GMT+02:00 Robert Patrick <robert.patr...@oracle.com>:
> Hi,
>
>
>
> I am trying to use the release plugin with a new
a JIRA as soon as I have the
results with multiple os, git and maven versions.
Bernd
--
http://bernd.eckenfels.net
-Original Message-
From: Vincent Latombe <vincent.lato...@gmail.com>
To: Maven Users List <users@maven.apache.org>
Sent: Di., 06 Okt. 2015 22:56
Subject: Re: [re
Unlike with a SVN workspace the release:prepare goal in a Git workspace
seems to not error-out when it sees untracked (git status results
in ??) files. I have seen this on windows.
In some cases it was not mentioning the files at all (they are shown in
-X debug output) in other cases it was
Hi,
I'm trying to use the release plugin (2.5.2 with maven 2.2.1) to perform a
delivery.
I did some tests using the release:perform goal.
In the current branch, it
- updates the pom with the release version,
- commit the modification,
- add a tag,
- updates the pom to next snapshot
Hi all,
not sure to be on the good ML but I would like to ask to one of the
maven-release-plugin leader/owner to update some help page about the plugin
version to use.
for example, this help page is up-to-date and refers to the latest plugin
vrersion : 2.5.2
http://maven.apache.org/maven
Hi Brice,
On 7/31/15 3:56 PM, Brice Vandeputte wrote:
Hi all,
not sure to be on the good ML but I would like to ask to one of the
maven-release-plugin leader/owner to update some help page about the plugin
version to use.
It is very good to get in contact with us to show there is something
-plugin:perform
-DconnectionUrl=scm:svn:https://svn.mycompany.com/repos/path/to/myproject/tags/myproject-1.2.3
as outlined at
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html.
But I did not find the correct syntax for GIT. In the end, I created
at
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html
.
But I did not find the correct syntax for GIT. In the end, I created a
release.properties with the content scm.tag=myproject-1.2.3 and could
run
mvn release-plugin:perform
-DconnectionUrl=scm:git:git
something like:
mvn release-plugin:perform
-DconnectionUrl=scm:svn:
https://svn.mycompany.com/repos/path/to/myproject/tags/myproject-1.2.3
as outlined at
http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html
.
But I did not find the correct
It appears as though the maven-release-plugin needs to be updated for Maven
3.3.1 (similar to the maven-invoker-plugin)?
I get this error trying a dry run:
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on
project parent: Failed
The Apache Maven team is pleased to announce the release of the Apache
Maven Release Plugin, version 2.5.2
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.
http://maven.apache.org
Hi,
a short solution could be
https://issues.apache.org/jira/browse/MRELEASE-902
after the new release of maven-release-plugin 2.5.2 is there you could
change to the new release which contains a fix for that...
Kind regards
Karl Heinz Marbaise
On 4/22/15 10:02 PM, cody.a.fy
That works for me.
Thanks!
Cody Fyler
Lending Grid Build Team
G=Lending Grid Builds
(515) – 441 - 0814
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Wednesday, April 22, 2015 3:11 PM
To: Maven Users List
Subject: Re: Issue with maven-release-plugin
the credentials from somewhere which is related
to the Active Directory / Kerberos ticket.
However this seems to fail if using the maven-release-plugin. However this may
relate to
https://jira.codehaus.org/browse/MRELEASE-892
as there is also an error message to use --force interactive to make
Hi Robert,
- I have looked at the Maven SCM project but do not get my problem solved or
more hints on it
- The maven-release-plugin is locked (with version 2.5, not 2.5.1)
- If running maven with -X according to console no credentials are provided
when accessing the SVN
- If running maven
Hi Sebastian,
since your issue has to do with svn, one needs to look at the Maven SCM
project.[1]
That's what the maven-release-plugin is using to the commits, tags and
checkouts.
First ensure you've locked the version of the maven-release-plugin,
preferably the lastest (i.e. 2.5.1
Hi Sebastian,
this is first of all more an svn commandline issue rather than a Maven /
maven-release-plugin issue.
For that reason you should start by calling svn directly from the
commandline. In the end, that's exactly what maven-release-plugin
(actually the scm-svn-provider) does. Once
Hello,
I have a problem with the maven-release-plugin using the SVN credentials
(details below). I always get an SVN authorization error. It seems that the
release plugin does not use the existing credentials. Unfortunately I'm even
not sure whether it is a problem of the maven-release-plugin
usage oft he
release plugin.
Chris
-Ursprüngliche Nachricht-
Von: Robert Scholte [mailto:rfscho...@apache.org]
Gesendet: Montag, 1. Dezember 2014 20:00
An: Maven Users List
Betreff: Re: AW: Problems with the release plugin
Just to be sure that we are on the same page:
Your request
-version plugin for Maven and Ant and start using this completely
dropping usage oft he release plugin.
I really think that you are better off releasing 'manually' in the
transition. I think you will discover that it is not so easy to change
the release plugin to 'just relax a constraint
Just to be sure that we are on the same page:
Your request is if the maven-release-plugin could be changed, so you can
specify versions for external (i.e. non reactor/multimodule) dependencies.
I won't allow this unless it can be automated, hence the introduction of
the VersionPolicy
stuff the release plugin does for you by default and
instead they try to hack around it... Your trick may work for you, but we
can't let people think it should work for everyone and every case)
Regards
Mirko
--
Sent from my mobile
On Nov 28, 2014 7:49 PM, alejandro.e...@grassvalley.com
from the tag). The point being that most people just
don't
see all the good stuff the release plugin does for you by default and
instead they try to hack around it... Your trick may work for you, but we
can't let people think it should work for everyone and every case)
Regards
Mirko
(https://github.com/chrisdutz/jenkins-release-plugin).
Also it sort of feels like I am doing Ant to Maven migration for the last few
years all the time ... for business, in other Apache Project (Mainly Apache
Flex) ... and every now and then I come to this point.
I still don't really see how
I'm going to attempt a summary here.
The release plugin has a requirement. It must be true that you can go
to the SCM, checkout a brand new copy of the tree rooted at the scm/
element, _change the versions_ in the pom(s), and run a build as
configured by the profiles and goals. If that's not true
maven-release-plugin. But till we are there it feels like there is no way
without patching this plugin in order to have an easy transition path.
What about some legacy or quirks mode for the plugin that allows such a
thing ... it might even output warnings and pages of text explaining why
to the
final goal of having everything in Maven and be able to use the default
maven-release-plugin. But till we are there it feels like there is no way
without patching this plugin in order to have an easy transition path.
Keep in mind that the release *plugin* is just the recommended best
The release plugin is a tool that does a specified set of steps. It's
built out of reusable components. Turning it into MS Word with
10,000,000 options is not, in my view, a good plan.
If you can write down a clear spec for an alternative workflow, you
can study the source and make a plugin
[mailto:bimargul...@gmail.com]
Gesendet: Sonntag, 30. November 2014 22:22
An: Maven Users List
Betreff: Re: Problems with the release plugin
The release plugin is a tool that does a specified set of steps. It's built out
of reusable components. Turning it into MS Word with
10,000,000 options
| Software Designer/Concepteur de logiciels
From: Robert Scholte rfscho...@apache.org
To: Maven Users List users@maven.apache.org,
Date: 2014-11-28 12:46 PM
Subject:Re: release plugin issue
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
alejandro.e...@grassvalley.com:
I'm
tests to run without so that anyone else
can still build from the tag). The point being that most people just don't
see all the good stuff the release plugin does for you by default and
instead they try to hack around it... Your trick may work for you, but we
can't let people think it should work
To: Maven Users List users@maven.apache.org,
Date: 2014-11-27 07:44 PM
Subject:Re: release plugin issue
On Thursday, 27 November 2014, alejandro.e...@grassvalley.com wrote:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now
Op Thu, 27 Nov 2014 14:12:58 +0100 schreef Dutz, Christofer
c.d...@ing-diba.de:
Hi,
I just ran into a problem I was having a few times now with the release
plugin. This time the usage scenario is different, but the code needed
to be changed is still the same.
This time I am helping
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
alejandro.e...@grassvalley.com:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due to errors in the javadoc. This is not a
problem, the problem
Fri, 28 Nov 2014 00:54:29 +0100 schreef alejandro.e...@grassvalley.com
:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due to errors in the javadoc. This is not a
problem, the problem
@maven.apache.org,
Date: 2014-11-28 12:52 PM
Subject:Re: release plugin issue
O wait a sec you're using the evil job type...
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
Well all bets are off then that will most likely royally screw you
@maven.apache.org,
Date: 2014-11-28 12:46 PM
Subject:Re: release plugin issue
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
alejandro.e...@grassvalley.com:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due
Hi,
I just ran into a problem I was having a few times now with the release plugin.
This time the usage scenario is different, but the code needed to be changed is
still the same.
This time I am helping migrate a large set of projects from Ant to Maven. As
this involves a large amount
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due to errors in the javadoc. This is not a
problem, the problem is that IF there are problems in the javadoc the
release doesn't complete but the two commits
On Thursday, 27 November 2014, alejandro.e...@grassvalley.com wrote:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due to errors in the javadoc. This is not a
problem, the problem
Hello!
I has already posted this question to StackOverflow, though I didn’t get much
help (expect warning about git requirements for 2.5.x version).
The thing is that I’m trying to set up our project deployment to Nexus process
via release-plugin. My script is:
git checkout -b release
plugin
artifactIdmaven-release-plugin/artifactId
version2.5.1/version
/plugin
does the job
as does
mvn org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare
org.apache.maven.plugins:maven-release-plugin:2.5.1:perform
On 23 October 2014 09:51, Vlad Slepukhin slp@gmail.com
Hi,
the plugin causing this problem must be the maven-javadoc-plugin :)
the release:perform isn't that magic, you can do the same steps by hand:
- check out the code from tag (created by release:prepare)
- go to target/checkout
- execute mvn deploy site-deploy (site-deploy depends on the
Hello all,
I've a project since several years and I had not problem to build it.
I recently installed JDK1.7 on my Windows 7 and now my build fail during mvn
release:perform !
The build fail saying unmappable character for encoding utf-8.
That's true as my source file are encoded in
1 - 100 of 1802 matches
Mail list logo
