Re: [ANN] Apache Maven Assembly Plugin 2.5 Released

AS can be seen from http://jira.codehaus.org/browse/MASSEMBLY-722, this can be fixed for 2.5 by adding the following to your pom (these component updates are available in central): plugin artifactIdmaven-assembly-plugin/artifactId ... dependencies dependency groupIdorg.codehaus.plexus/groupId

Re: [pre-verify over deploy]

Many thanks to Barrie. I think what you have clarified is the normal flow of maven practice. The deploy in the context of my previous post means: our developer invoke a mvn deploy command to share the output(bytecode) through the repository so as to shorten the build time of whole project(as its

Re: [pre-verify over deploy]

On 29 October 2014 18:48, Fay Wong philip584...@gmail.com wrote: Many thanks to Barrie. I think what you have clarified is the normal flow of maven practice. The deploy in the context of my previous post means: our developer invoke a mvn deploy command to share the output(bytecode) through

Re: [pre-verify over deploy]

http://developer-blog.cloudbees.com/2012/12/should-you-deploy-snapshots.html On 29 October 2014 08:18, Fay Wong philip584...@gmail.com wrote: Many thanks to Barrie. I think what you have clarified is the normal flow of maven practice. The deploy in the context of my previous post means: our

JIRA project per Maven Project?

We have a few JIRA projects and many more Maven projects. Some are one-to-one related, in several cases many Maven projects make up a JIRA project. Just wondering how other organisations lay stuff out. Particularly of relevance given Jenkins can operate JIRA projects as it builds releases Maven

Why does reporting exist?

According to: * http://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html * http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html * http://mojo.codehaus.org/findbugs-maven-plugin/usage.html * http://maven.apache.org/plugins/maven-pmd-plugin/usage.html and

ApacheCon EU 2014, Budapest

Hi there, would like to know who will be attending ApacheCon EU 2014, Budapest.  Some folks (like local JUGs and other) plan to kidnap Maven developers, make them have some beer or wine, chat and so, so the “kidnappers are curious about attendees :) Also, some personal way for contact

Re: [pre-verify over deploy]

On 29/10/2014 5:19 AM, Barrie Treloar wrote: On 29 October 2014 18:48, Fay Wong philip584...@gmail.com wrote: Many thanks to Barrie. I think what you have clarified is the normal flow of maven practice. The deploy in the context of my previous post means: our developer invoke a mvn deploy

Client-side SSL certifcates and Maven

Hello, I am trying to get Maven (3.2.2) to work with an instance of Archiva hosted behind a webserver secured with client-side SSL certificates. I have followed the guide at https://maven.apache.org/guides/mini/guide-repository-ssl.html, and imported the server-side SSL certificate into a Java

RE: [ANN] Apache Maven Assembly Plugin 2.5 Released

This fixes the issue for me. Thanks Kristian! Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Kristian Rosenvold [mailto:krosenv...@apache.org] Sent: Wednesday, October 29, 2014 2:21 AM To: Maven Users List Cc: Maven Developers List

Re: [pre-verify over deploy]

Hi Fay, Could i define a intermediate repository, everytime they deploy, jenkins will verify it. Why not have Jenkins do your deploys? I.e.: make it so that only Jenkins has deploy permission to your remote repository. So your devs can no longer run mvn deploy from the CLI and expect it to

Re: [pre-verify over deploy]

On 30 October 2014 08:38, Curtis Rueden ctrue...@wisc.edu wrote: Hi Fay, Could i define a intermediate repository, everytime they deploy, jenkins will verify it. Why not have Jenkins do your deploys? I.e.: make it so that only Jenkins has deploy permission to your remote repository. So

Not the usual authenticity can't be established post.

I'm trying to use the deploy goal to upload a built library to our local repository. I get the message: The authenticity of host 'FQDN' can't be established. followed by a request for a password, despite the fact that I should be using a private key to authenticate. I googled round and found

Re: [pre-verify over deploy]

Hi Barrie, Whether its Jenkins, or a developer, you've still pushed a release that could break the build. This is where you need some isolation available to your workflow. Agreed! However, for Fay's stated requirement, it may be sufficient to have a broken master branch as long as the

mvn release:branch not updating POM

Good day, I hope someone can assist. Running mvn release:branch -Dbranchname=foo . The problem is that my POM file's SCM connection does not always update to point to my new branch. I ran this command a few times with different branch names. Sometimes the SCM connection updates, other times

Re: ApacheCon EU 2014, Budapest

Hi, I'll be there, ready for beer and wine :) Regards, Hervé Le mercredi 29 octobre 2014 13:41:11 Tamas Cservenak a écrit : Hi there, would like to know who will be attending ApacheCon EU 2014, Budapest. Some folks (like local JUGs and other) plan to kidnap Maven developers, make them

Re: [pre-verify over deploy]

2014-10-30 6:15 GMT+08:00 Barrie Treloar baerr...@gmail.com: On 30 October 2014 08:38, Curtis Rueden ctrue...@wisc.edu wrote: Hi Fay, Could i define a intermediate repository, everytime they deploy, jenkins will verify it. Why not have Jenkins do your deploys? I.e.: make it so