> > wrote:
> > >
> > > > That's good to know Robert, thank you
> > > >
> > > > I will add that to our release dryrun and hopefully it will catch
> more
> > of
> > > > the uncaught problems early on
> > > >
> &g
; >
> > > That's good to know Robert, thank you
> > >
> > > I will add that to our release dryrun and hopefully it will catch more
> of
> > > the uncaught problems early on
> > >
> > > Alejandro Endo | Software Designer/Concepteur de logicie
n and hopefully it will catch more of
> > the uncaught problems early on
> >
> > Alejandro Endo | Software Designer/Concepteur de logiciels
> >
> >
> >
> >
> >
> > From: "Robert Scholte" >
> > To: "Maven Users List&q
Software Designer/Concepteur de logiciels
>
>
>
>
>
> From: "Robert Scholte"
> To: "Maven Users List" ,
> Date: 2014-11-28 12:46 PM
> Subject:Re: release plugin issue
>
>
>
> Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
>
te: 2014-11-28 12:46 PM
Subject: Re: release plugin issue
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
:
> 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 j
14-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
over
On 28 November
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 over
On 28 November 2014 at 17:45, Robert Scholte wrote:
> Op Fri, 28 Nov 2014 00:5
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
:
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
14-11-27 07:44 PM
Subject: Re: release plugin issue
On Thursday, 27 November 2014, 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. T
On Thursday, 27 November 2014, 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 is that IF there are problems in the javadoc the
>
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 an
I'm also using a flat structure.
I found that the keys to making this work seem to be:
1) use release 2.0 of the release plugin. This is the release with the support
for "flat" hierarchies. Note that the Apache common parent POM version 7 (the
latest) still doesn't specify this release, it spe
I've configured the release plugin in my build. I'm using a flat
directory structure like:
Aggregator
Common
Ejb
Web
When I do a release:prepare from the aggregator directory everything
seems to work however the aggregator/... is the only path labeled.
Also, when I do a release:perf
Hello Kalle and thank you for your reply.
You helped a lot! The problem was that under the MAVEN_OPTS
environement variable given to hudson at start, an invalid keystore
location was passed by "-Djavax.net.ssl.trustStore=/path/to/
inexisting.jks". This variable was not available in the comma
The keystore/some root certificates are not available to the JVM. Are
you running Hudson as the same user as you logged on and run the
release successfully? Also the same came up before, see
http://www.nabble.com/Plugins-Upgrades:-java.security.InvalidAlgorithmParameterException:--the-trustAnchors-
Hello everyone,
i have an issue when trying to release from the hudson CI tool. The
releasing works fine until the deployment to the repository where it
fails with the following error:
---snip---
[INFO] [INFO] [deploy:deploy {execution: default-deploy}] [INFO]
Uploading:https://maven.ador
> >> extract-xsds
> >> initialize
> >>
> >>
> >>
> >>
> >>
gt;>
>>
>>
>>
>> Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
>> This jar does get generated in abc-interface-api\target. But it does not
>> get
>>
run
>
>
>
>
>
> Why is abc-websvc-api-1.5.jar being called before it is deployed in .m2 ?
> This jar does get generated in abc-interface-api\target. But
r does get generated in abc-interface-api\target. But it does not get
deployed in .m2
Any ideas ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp23375978p23375978.html
Sent from the Maven - Users mailing list archive at
ven-release-plugin
>>>>
>>>> 2.0-beta-9-SNAPSHOT
>>>>
>>>>
>>>> true
>>>>
>>>> false
>>>>
ase:plugin it is not able to tag SVN.
>>>
>>> Provider message:
>>> The svn tag command failed.
>>> Command output:
>>> svn: Commit failed (details follow):
>>> svn: '/abc_repos/sip/tags' path not found
>>>
>>> This is
age:
>> The svn tag command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: '/abc_repos/sip/tags' path not found
>>
>> This is because I am running the plugin inside a module, which exists
>> under
>> a SVN repo.
should be
> be /abc_repos/tags. How can I run this ?
>
> thanks,
> --
> View this message in context:
> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
ould be
be /abc_repos/tags. How can I run this ?
thanks,
--
View this message in context:
http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
> [INFO] Error deploying artifact: Failed to transfer file:
> http://fpsvn00
> 1.na.coglobal.com:8081/nexus/content/repositories/releases/com/co/maven/co-m
> aven/1.0/co-maven-1.0.pom. Return code is: 401
HTTP Error 401 is... Unauthorized, right? Solve that, and deploy will
proceed. Check f
:
http://www.nabble.com/Maven-release-plugin-issue--Error-code-401-tp22729480p22729480.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
...@ginerativ.fr]
Sent: Tuesday, January 27, 2009 9:55 AM
To: Maven Users List
Subject: RE: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
Thanks for you answer, Brian.
How do I "redefine at the top of my project" so that the URLs are
De : Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr]
Envoyé : mardi 27 janvier 2009 15:16
À : Maven Users List
Objet : RE: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
Indeed, no, I didn't set the tagBase. Even though I don'
er 2009 15:06
À : Maven Users List
Objet : RE: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
The parent / child relationship != modules. That is a given pom can inherit
from one parent and be aggregated as a module via another. It is true that
u
igine-
De : bmat...@gmail.com [mailto:bmat...@gmail.com] De la part de Baptiste MATHUS
Envoyé : mardi 27 janvier 2009 15:07
À : Maven Users List
Objet : Re: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
We have a parent pom for the exact kind
We have a parent pom for the exact kind of things you speak about. But our
projects are not modules (at least not all). So no.
Your problem with scm tag might just be related to the fact you didn't set
the maven-release-plugin tagBase configuration?
See http://maven.apache.org/plugins/maven-releas
e url.
-Original Message-
From: Lesaint Sébastien [mailto:sebastien.lesa...@ginerativ.fr]
Sent: Tuesday, January 27, 2009 9:01 AM
To: Maven Users List
Subject: Does having a parent POM mean the current POM is a module ? (or a
possible release plugin issue)
Hello,
I want to use a parent POM as a w
Hello,
I want to use a parent POM as a way to easily give some organisation specific
information to the new projects in our company or the old one being mavenized.
I don't want to declare all the projects of my company as being a module of
this parent POM. It doesn't make much sense. So the par
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use
xmlns="http://maven.autf-8.org/POM/4.0.0
", release plugin report problem. The problem is fixed after I changed to
xmlns="http://maven.apache.org/POM/4.0.0";. Does anyone kno
I ran into an issue with maven release plugin. The problem is caused by
xmlns value in project tag of the pom. If I use xmlns="
http://maven.autf-8.org/POM/4.0.0";, release plugin report problem. The
problem is fixed after I changed to xmlns="http://maven.apache.org/POM/4.0.0";.
Does anyone kno
36 matches
Mail list logo
