Re: ConcurrentContinuous Delivery Maven Builds

[Paul Hammant]

Have a Jenkins job that runs at 10pm that picks up the *last green build*
of the day and re-does it (skipping tests this time) but goes on to push
the war file (or equiv) to the appropriate QA machines servers.

That builds ran in parallel earlier in the day, is not longer important.
Again, skip the pushing to Artifactory/Nexus for QA builds.

And that's CI not CD by the way (CD would be every commit into an env if
the build passes at the bleeding edge or every N builds through the day
from trunk/master).

- Paul

On Wed, Mar 14, 2018 at 5:44 PM, Dan Tran  wrote:

> @Paul yes the final build artifacts go to QA. I guess I can instrument
> Maven only deploy the necessary files.  But I still need to deploy full
> snapshot build once a day
>
> @Francois, for my case, it very very possible that 2 parallel pipelines
> pushing same artifact ( different versions) to maven repo and step on each
> other maven-metadata.xml files
>
> Thanks
>
> -D
>
> On Wed, Mar 14, 2018 at 2:14 PM, Francois MAROT 
> wrote:
>
> > What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
> > Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
> > which is solved in Maven 3.5.2 (even 3.5.1 I think) ?
> >
> >
> >
> > --
> > Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>



-- 
Paul Hammant DevOps  Let me give your
enterprise a step by step plan to get out of the hell of crazy branching
models (ClearCase maybe?) and into the world of high-throughput CD on
DevOps foundations.

Re: javadoc:jar and generated sources

[Hervé BOUTEMY]

strange

can you provide a test project, please?

Regards,

Hervé

Le mardi 13 mars 2018, 18:56:45 CET Laird Nelson a écrit :
> I am finding that the sourcepath for javadoc:jar (when run as part of the
> release profile) is different from the sourcepath for javadoc:javadoc in my
> project that involves (protoc-) generated sources.
> 
> (The net effect is that at release time, everything works fine up until
> release:perform, which fails (!) during the attach-javadocs execution I've
> configured following the documentation (
> https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-ar
> tifacts.html#Configuring_Maven_Javadoc_Plugin) ).
> 
> I have a  stanza centralizing my maven-javadoc-plugin
> configuration that does not mention sourcepath in any way.
> 
> mvn help:effective-pom -Prelease shows exactly what I would expect, and no
> additional maven-javadoc-plugin configuration.
> 
> Somehow, the sourcepath for javadoc:javadoc has the generated-sources
> directory in it; the sourcepath for javadoc:jar does not.
> 
> Here is the pluginManagement section (it's quite ordinary):
> 
> 
>   maven-javadoc-plugin
>   3.0.0-M1
>   
> -missing
>   
> 
> 
> When I run mvn -X javadoc:javadoc and inspect the options file, I see this:
> 
> -sourcepath
> '/Users/ljnelson/Projects/frob/src/main/java:
> */Users/ljnelson/Projects/frob/target/generated-sources/protobuf/java:/Users
> /ljnelson/Projects/frob/target/generated-sources/protobuf/grpc-java*
> :/Users/ljnelson/Projects/frob/src/main/javadoc'
> 
> When I run mvn -X javadoc:jar and inspect the options file, I see only this:
> 
> -sourcepath
> '/Users/ljnelson/Projects/frob/src/main/java:/Users/ljnelson/Projects/frob/s
> rc/main/javadoc'
> 
> The javadoc:jar goal outputs a bunch of warnings.  When I run it locally
> (mvn javadoc:jar), they show up as warnings.  When it is run as part of the
> maven-release-plugin's perform goal, it fails the build.
> 
> I'm at a loss as to how to go about fixing this.  Is it, perhaps, the job
> of the plugin in charge of generating the sources to do something here?
> 
> Best,
> Laird



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: ConcurrentContinuous Delivery Maven Builds

[Dan Tran]

@Paul yes the final build artifacts go to QA. I guess I can instrument
Maven only deploy the necessary files.  But I still need to deploy full
snapshot build once a day

@Francois, for my case, it very very possible that 2 parallel pipelines
pushing same artifact ( different versions) to maven repo and step on each
other maven-metadata.xml files

Thanks

-D

On Wed, Mar 14, 2018 at 2:14 PM, Francois MAROT 
wrote:

> What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
> Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
> which is solved in Maven 3.5.2 (even 3.5.1 I think) ?
>
>
>
> --
> Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: ConcurrentContinuous Delivery Maven Builds

[Francois MAROT]

What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
which is solved in Maven 3.5.2 (even 3.5.1 I think) ?



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

old version of dependencies getting included into project

[Jonathan Yom-Tov]

hi,

I have a fairly large project which compiles to a war file. I've upgraded
the jackson dependency to 2.7.3 but for some reason 2.4.3 and 2.4.0 jar
files are included into the war file in addition to the 2.7.3 version. I
ran mvn dependency:tree to figure out the reason but the old versions don't
appear there. They also don't appear in the build log. I deleted the old
versions from my local maven repo. Didn't help. Any ideas on how to figure
this out?

thanks,
Jon.

Re: Looking for recommendations how to best use Maven in a muti-stagePipeline build to only deploy at the end

[Brian Fox]

On Wed, Feb 14, 2018 at 9:31 PM, Eric B  wrote:
> Bernd,
>
> Nexus 3.x does not support staging repos b/c they are rewriting the entire
> platform to support not just Maven artifacts, but any type of repo-based
> artifact.  Ex: docker images, npm dependencies, etc...


This is true and it's getting close to being done. Also included is a
pipeline plugin for Jenkins to help you effect the promotions
directly.

>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven build failure - first install

[kobano]

I found the origin of the problem:
The apache-maven-3.5.3 files were in a folder created in c:\Program Files.
I changed and created a directory at the root of
c:\apache\apache-maven-3.5.3 and the script now works without problems.
Thanks for your help



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: ConcurrentContinuous Delivery Maven Builds

[Paul Hammant]

Continuous Delivery is into QA / UAT, right?
Continuous Deployment is into Prod.

You need the jars in Artifactory because other teams depend on them?  If
not then just deploy to QA/UAT and don't drop jars (or anything) into
Nexus/Artifactory/WebDAV.

- Paul



On Wed, Mar 14, 2018 at 4:31 AM, Dan Tran  wrote:

> Hi
>
> I have a requirement to run concurrent maven continuous deliver style.
> Each new commit/PR triggers new pipeline with unique version.
>
> Since maven deployment also pushing maven-metadata.xml which can be
> corrupted for concurrent pipeplines
>
> I wonder if Artifactory or Nexus have some type of protection for this
> scenario?
>
> Thanks
>
> -Dan
>



-- 
Paul Hammant DevOps  Let me give your
enterprise a step by step plan to get out of the hell of crazy branching
models (ClearCase maybe?) and into the world of high-throughput CD on
DevOps foundations.

Re: Maven build failure - first install

[Anders Hammar]

As " -DarchetypeVersion=1.1" is specified it should get version 1.1 of the
archtype. It's hard to tell why it's not based on the little info provided.

I suggest use
mvn archtype:generate
and you'll get prompted for archetype

/Anders

On Wed, Mar 14, 2018 at 11:17 AM, Bernd Eckenfels 
wrote:

> Hello,
>
> Looks like the tutorial is wrong, I only see a 1.1 version of that
> archetype. Since you normally cannot remove artifacts from Maven Central it
> looks like this never worked. You can see the content here:
>
> https://repo.maven.apache.org/maven2/org/apache/maven/
> archetypes/maven-archetype-quickstart/
>
> Gruss
> Bernd
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> From: kobano 
> Sent: Wednesday, March 14, 2018 11:12:07 AM
> To: users@maven.apache.org
> Subject: Maven build failure - first install
>
> Hello, I'm a beginner and follow the course OpenClassroom " Organize and
> package a Java application with Apache Maven
>  une-application-java-avec-apache-maven/creez-votre-premier-projet-maven>
> "On this first part I have to  create a Maven project qsuelette from the
> quickstart archetype
>  une-application-java-avec-apache-maven/creez-votre-
> premier-projet-maven#/id/r-4608836>
> .Following the line :mvn -X archetype:generate
> -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.1I
> get
> a build failure and I can not find the source of the problem.I added -X for
> more info, and here are the last lines I can get :I'm working on windows 8,
> and have not created a settings.xml file.For info, here is what mvn -v
> shows:A line in what is displayed indicates that "quickstart" is not
> found:Could not find artifact
> org.apache.maven.archetypes:maven-archetype-quickstart:jar:3.0.1 in
> central
> ( https://repo.maven.apache.org/maven2
>   )Could it be that the
> OpenClassroom
> course uses a skeleton that no longer exists?Or the problem would come from
> elsewhere?Thanks in advance for the help !!
>
>
>
> --
> Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
>

Re: Maven build failure - first install

[Bernd Eckenfels]

Hello,

Looks like the tutorial is wrong, I only see a 1.1 version of that archetype. 
Since you normally cannot remove artifacts from Maven Central it looks like 
this never worked. You can see the content here:

https://repo.maven.apache.org/maven2/org/apache/maven/archetypes/maven-archetype-quickstart/

Gruss
Bernd

Gruss
Bernd
--
http://bernd.eckenfels.net

From: kobano 
Sent: Wednesday, March 14, 2018 11:12:07 AM
To: users@maven.apache.org
Subject: Maven build failure - first install

Hello, I'm a beginner and follow the course OpenClassroom " Organize and
package a Java application with Apache Maven

"On this first part I have to  create a Maven project qsuelette from the
quickstart archetype

.Following the line :mvn -X archetype:generate
-DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.1I get
a build failure and I can not find the source of the problem.I added -X for
more info, and here are the last lines I can get :I'm working on windows 8,
and have not created a settings.xml file.For info, here is what mvn -v
shows:A line in what is displayed indicates that "quickstart" is not
found:Could not find artifact
org.apache.maven.archetypes:maven-archetype-quickstart:jar:3.0.1 in central
( https://repo.maven.apache.org/maven2
  )Could it be that the OpenClassroom
course uses a skeleton that no longer exists?Or the problem would come from
elsewhere?Thanks in advance for the help !!



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

Maven build failure - first install

[kobano]

Hello, I'm a beginner and follow the course OpenClassroom " Organize and
package a Java application with Apache Maven

 
"On this first part I have to  create a Maven project qsuelette from the
quickstart archetype

 
.Following the line :mvn -X archetype:generate
-DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.1I get
a build failure and I can not find the source of the problem.I added -X for
more info, and here are the last lines I can get :I'm working on windows 8,
and have not created a settings.xml file.For info, here is what mvn -v
shows:A line in what is displayed indicates that "quickstart" is not
found:Could not find artifact
org.apache.maven.archetypes:maven-archetype-quickstart:jar:3.0.1 in central
( https://repo.maven.apache.org/maven2
  )Could it be that the OpenClassroom
course uses a skeleton that no longer exists?Or the problem would come from
elsewhere?Thanks in advance for the help !!



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

ConcurrentContinuous Delivery Maven Builds

[Dan Tran]

Hi

I have a requirement to run concurrent maven continuous deliver style.
Each new commit/PR triggers new pipeline with unique version.

Since maven deployment also pushing maven-metadata.xml which can be
corrupted for concurrent pipeplines

I wonder if Artifactory or Nexus have some type of protection for this
scenario?

Thanks

-Dan