Re: generate a POM with dependencies only?

[Maxim Solodovnik]

I would like to ask related question here

Is it possible to get dependency version?
I'm creating one big jar for all dependencies using assembly plugin, but
org.bouncycastle:bcprov-jdk15on cannot be repacked
So I need to manually track it's version :(
Would be great if I can get bcprov version and automatically set it using
xslt transformation

On Thu, May 4, 2017 at 1:39 AM, Richard Sand  wrote:

> Woohoo!
>
> Thanks Robert!
>
> -Richard
>
>
>
>
> -- Original Message --
> From: "Robert Scholte" 
> To: "Maven Users List" 
> Sent: 5/3/2017 2:38:56 PM
> Subject: Re: generate a POM with dependencies only?
>
> Yes, http://www.mojohaus.org/flatten-maven-plugin/
>>
>> On Wed, 03 May 2017 20:37:52 +0200, Richard Sand 
>> wrote:
>>
>> Is there a plugin/goal that will generate a "reduced" POM for a project
>>> that only contains the dependencies, but none of the other build/profile
>>> or any other tags?
>>>
>>> May sound like a strange ask - but the scenario I'm facing is that I'm
>>> building a particular set of jars/wars/zips (using assembly plugin), and
>>> the POMs for these artifacts all rely on a heirarchy of parent POMs  which
>>> have many dependencyManagement, build, and profile elements. My  customers
>>> have their own internal Maven repositories, and are not  connecting to my
>>> company's private repos, so their ask is that I provide  the POM for each
>>> artifact we distribute in the zip file. So basically I  want to give them a
>>> stripped down POM that only has the dependencies in  it so that they can
>>> upload the artifacts into their internal repos and  include them in their
>>> projects. They will never actually be building our  artifacts.
>>>
>>> Best regards,
>>>
>>> Richard
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Continuous Delivery with Maven now possible?

[Dan Tran]

I am able to bring it to production with very small project with few
modules. Where I hook up jenkins build number with the version

  1.0.0-${env.BUILD_NUMBER}  See Karl's Blog

At the same time,  use buildnumber-m-p to deploy text file with SCM info,
and finally push to staging repo using Artifactory

Once a build is promoted (GAed), I then remove the rest from staging,  and
manually tag the build using the recorded SCM info

My next task is a much bigger project with 300+ modules and lots of
dev/qa.  So it is crucial i dont break their development environments

Thanks

-Dan


On Wed, May 3, 2017 at 5:34 PM, Eric B  wrote:

> Hi Karl,
>
> Can you provide a little more information how you are doing this? Or do you
> have a blog about it somewhere? It's something I desperately need to insert
> into my build pipeline but haven't had the time to work on yet.  So far,
> the best I've been able to think of is to use a parameter for a build
> number, have Jenkins assign a build number, pass it to maven, and have the
> version reflect the build number using the external parameter.  But I
> really don't like that idea as the version is now dependent on a variable,
> which I find is contrary to the whole concept.
>
> The other option is to have Jenkins took the build number in the pom using
> the release plugin or the version plugin, commit the new pom, and then
> build from a newly checked out code.  My issue there is that I'm having
> Jenkins do a lot of scm manipulations which are more subject to failing
> (ie: version updates, commit, tag, push, etc).
>
> Finally, I'm trying to think of a good way of rolling all this into Nexus
> staging repos and only promoting a build out of a staging repo once it
> passes the pre prod environment and is certified for prod.
>
> Any ideas, thoughts, feedback and/or tips would be greatly appreciated.
>
> Thanks,
>
> Eric
>
> On May 3, 2017 2:50 PM, "Karl Heinz Marbaise"  wrote:
>
> > Hi Dan,
> >
> > I'm trying to do something in this direction starting next week...
> >
> > Apart from that already tested it with Eclipse Neon without any
> > issue...(at the moment only test projects with 10-15 modules)...
> >
> > But it works at the moment..
> >
> > In the meantime I have found one issue which is related to
> > maven-enforcer-plugin where I already opened an issue for it [1]..
> >
> > Kind regards
> > Karl Heinz
> >
> > [1]: https://issues.apache.org/jira/browse/MENFORCER-268
> >
> > On 03/05/17 20:39, Dan Tran wrote:
> >
> >> Hi
> >>
> >> I have been experimenting with suggestion from Karl [1] with small multi
> >> module maven project.
> >>
> >>
> >> Is there any one actually bring this to production for large scale
> project
> >> yet? Love to learn from your experience integration specially with
> >> Jenkins,
> >> IDE ( eclipse,  intellij, Netbean)
> >>
> >> this allows us to stop using maven-release-plugin
> >>
> >> Thanks
> >>
> >> -Dan
> >>
> >> [1]
> >> http://blog.soebes.de/blog/2017/04/02/maven-pom-files-withou
> >> t-a-version-in-it/
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Re: Continuous Delivery with Maven now possible?

[Eric B]

Hi Karl,

Can you provide a little more information how you are doing this? Or do you
have a blog about it somewhere? It's something I desperately need to insert
into my build pipeline but haven't had the time to work on yet.  So far,
the best I've been able to think of is to use a parameter for a build
number, have Jenkins assign a build number, pass it to maven, and have the
version reflect the build number using the external parameter.  But I
really don't like that idea as the version is now dependent on a variable,
which I find is contrary to the whole concept.

The other option is to have Jenkins took the build number in the pom using
the release plugin or the version plugin, commit the new pom, and then
build from a newly checked out code.  My issue there is that I'm having
Jenkins do a lot of scm manipulations which are more subject to failing
(ie: version updates, commit, tag, push, etc).

Finally, I'm trying to think of a good way of rolling all this into Nexus
staging repos and only promoting a build out of a staging repo once it
passes the pre prod environment and is certified for prod.

Any ideas, thoughts, feedback and/or tips would be greatly appreciated.

Thanks,

Eric

On May 3, 2017 2:50 PM, "Karl Heinz Marbaise"  wrote:

> Hi Dan,
>
> I'm trying to do something in this direction starting next week...
>
> Apart from that already tested it with Eclipse Neon without any
> issue...(at the moment only test projects with 10-15 modules)...
>
> But it works at the moment..
>
> In the meantime I have found one issue which is related to
> maven-enforcer-plugin where I already opened an issue for it [1]..
>
> Kind regards
> Karl Heinz
>
> [1]: https://issues.apache.org/jira/browse/MENFORCER-268
>
> On 03/05/17 20:39, Dan Tran wrote:
>
>> Hi
>>
>> I have been experimenting with suggestion from Karl [1] with small multi
>> module maven project.
>>
>>
>> Is there any one actually bring this to production for large scale project
>> yet? Love to learn from your experience integration specially with
>> Jenkins,
>> IDE ( eclipse,  intellij, Netbean)
>>
>> this allows us to stop using maven-release-plugin
>>
>> Thanks
>>
>> -Dan
>>
>> [1]
>> http://blog.soebes.de/blog/2017/04/02/maven-pom-files-withou
>> t-a-version-in-it/
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Continuous Delivery with Maven now possible?

[Karl Heinz Marbaise]

Hi Dan,

I'm trying to do something in this direction starting next week...

Apart from that already tested it with Eclipse Neon without any 
issue...(at the moment only test projects with 10-15 modules)...


But it works at the moment..

In the meantime I have found one issue which is related to 
maven-enforcer-plugin where I already opened an issue for it [1]..


Kind regards
Karl Heinz

[1]: https://issues.apache.org/jira/browse/MENFORCER-268

On 03/05/17 20:39, Dan Tran wrote:

Hi

I have been experimenting with suggestion from Karl [1] with small multi
module maven project.


Is there any one actually bring this to production for large scale project
yet? Love to learn from your experience integration specially with Jenkins,
IDE ( eclipse,  intellij, Netbean)

this allows us to stop using maven-release-plugin

Thanks

-Dan

[1]
http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/




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

Re: generate a POM with dependencies only?

[Richard Sand]

Woohoo!

Thanks Robert!

-Richard



-- Original Message --
From: "Robert Scholte" 
To: "Maven Users List" 
Sent: 5/3/2017 2:38:56 PM
Subject: Re: generate a POM with dependencies only?


Yes, http://www.mojohaus.org/flatten-maven-plugin/

On Wed, 03 May 2017 20:37:52 +0200, Richard Sand  
 wrote:


Is there a plugin/goal that will generate a "reduced" POM for a 
project  that only contains the dependencies, but none of the other 
build/profile  or any other tags?


May sound like a strange ask - but the scenario I'm facing is that I'm 
 building a particular set of jars/wars/zips (using assembly plugin), 
and  the POMs for these artifacts all rely on a heirarchy of parent 
POMs  which have many dependencyManagement, build, and profile 
elements. My  customers have their own internal Maven repositories, 
and are not  connecting to my company's private repos, so their ask is 
that I provide  the POM for each artifact we distribute in the zip 
file. So basically I  want to give them a stripped down POM that only 
has the dependencies in  it so that they can upload the artifacts into 
their internal repos and  include them in their projects. They will 
never actually be building our  artifacts.


Best regards,

Richard


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


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




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

Continuous Delivery with Maven now possible?

[Dan Tran]

Hi

I have been experimenting with suggestion from Karl [1] with small multi
module maven project.


Is there any one actually bring this to production for large scale project
yet? Love to learn from your experience integration specially with Jenkins,
IDE ( eclipse,  intellij, Netbean)

this allows us to stop using maven-release-plugin

Thanks

-Dan

[1]
http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/

Re: generate a POM with dependencies only?

[Robert Scholte]

Yes, http://www.mojohaus.org/flatten-maven-plugin/

On Wed, 03 May 2017 20:37:52 +0200, Richard Sand   
wrote:


Is there a plugin/goal that will generate a "reduced" POM for a project  
that only contains the dependencies, but none of the other build/profile  
or any other tags?


May sound like a strange ask - but the scenario I'm facing is that I'm  
building a particular set of jars/wars/zips (using assembly plugin), and  
the POMs for these artifacts all rely on a heirarchy of parent POMs  
which have many dependencyManagement, build, and profile elements. My  
customers have their own internal Maven repositories, and are not  
connecting to my company's private repos, so their ask is that I provide  
the POM for each artifact we distribute in the zip file. So basically I  
want to give them a stripped down POM that only has the dependencies in  
it so that they can upload the artifacts into their internal repos and  
include them in their projects. They will never actually be building our  
artifacts.


Best regards,

Richard


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


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

generate a POM with dependencies only?

[Richard Sand]

Is there a plugin/goal that will generate a "reduced" POM for a project 
that only contains the dependencies, but none of the other build/profile 
or any other tags?


May sound like a strange ask - but the scenario I'm facing is that I'm 
building a particular set of jars/wars/zips (using assembly plugin), and 
the POMs for these artifacts all rely on a heirarchy of parent POMs 
which have many dependencyManagement, build, and profile elements. My 
customers have their own internal Maven repositories, and are not 
connecting to my company's private repos, so their ask is that I provide 
the POM for each artifact we distribute in the zip file. So basically I 
want to give them a stripped down POM that only has the dependencies in 
it so that they can upload the artifacts into their internal repos and 
include them in their projects. They will never actually be building our 
artifacts.


Best regards,

Richard


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

[ANN] Apache Maven Shared Component: Maven Dependency Analyzer Version 1.7 Released

[Karl Heinz Marbaise]

The Apache Maven team is pleased to announce the release of the 
Apache Maven Shared Component: Maven Dependency Analyzer Version 1.7
 
https://maven.apache.org/shared/maven-dependency-analyzer/

Analyzes the dependencies of a project for undeclared or unused artifacts.

 
You should specify the version in your project's plugin configuration:
 

  org.apache.maven.shared
  maven-analyzer
  1.7


You can download the appropriate sources etc. from the download page:
 
https://maven.apache.org/shared/maven-dependency-analyzer/download.cgi
 
Release Notes Maven Archiver 1.7:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12334271

Bugs:

 * [MSHARED-428] - maven-dependency-analyzer does not detect method references
 * [MSHARED-545] - maven-dependency-analyzer fails on classes containing 
constant long or double

Improvements:

 * [MSHARED-412] - Change the visibility of DefaultProjectDependencyAnalyzer's 
buildArtifactClassMap() from private to protected
 * [MSHARED-470] - Upgrade maven-shared-components parent to version 22
 * [MSHARED-525] - Upgrade maven-shared-components parent to version 30

Tasks:

 * [MSHARED-633] - Upgrade plexus-component-metadata / 
plexus-component-annotation to 1.7.1
 * [MSHARED-634] - Using maven-inovker 2.2 to ensure it works with all Maven 
versions on Windows
 
Enjoy,
 
-The Apache Maven team

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

Re: Maven hangs after lock file

[Daniel Watrous]

I updated that question to include a thread dump, but I’m still unsure how to 
track this back to a resolution.

On 5/2/17, 4:40 PM, "Daniel Watrous"  wrote:

Hi,

I posted an issue to stackoverflow, then I thought this list might be the 
best place to get some feedback:

http://stackoverflow.com/questions/43747117/maven-can-create-folders-and-lock-file-but-hangs-while-downloading

Any idea why maven would hang when it tries to download dependencies?

Thanks,
Daniel