Re: Why are extensions project based and not global?

[Lyons, Roy]

Jason,

My 2 cents...  The idea of organization-wide settings is not a new one.  I
would be hard-pressed to find an organization that is not using a maven
repository internally and the distributed .m2/settings.xml seems like the
right place for this.  Everyone in the organization has to have the right
entries in settings.xml for it to work, and most people can't be bothered
to run the plugin themselves to generate the settings - much less actually
hand edit a file to remove polyglot settings or something.

For instance, in order for any of your builds to work, you need to run
'mvn org.sonatype.plugins:nexus-m2settings-maven-plugin:1.6.5:download
-DtemplateId=OURTEMPLATEID'.  That takes a template in Nexus and injects
an encrypted form of the token id and token password, saving it to the
user's .m2/settings.xml

Since settings.xml is not polyglot - it is also a safe place to put it!

So:


  
  
  
  
  
  
  



Thanks,

Roy Lyons
Sr. Software Configuration Management Engineer

Next Chicago Atlassian User Group meeting:
http://aug.atlassian.com/cities/chicagoil




On 5/28/15, 7:08 AM, "Jason van Zyl"  wrote:

>So just to be clear you don't actually have to add the artifact itself
>but a declaration of the artifact and it will be downloaded. We really
>only first thought about project specific extensions, making sure the
>mechanism worked with the type of bootstrapping required, proper
>classloader isolation, that a complex project I was working on
>functioned, and that polyglot worked for JRuby. We have discussed in the
>hangouts how an extension might work on an organizational basis but never
>really decided anything.
>
>So how would an organization say they wanted to use the Groovy DSL? The
>POM is likely ideal but we have obvious bootstrapping issues doing that
>as you can imagine with extensions like Polyglot which actually need to
>read the POM. 
>
>I think the options are:
>
>- user level
>  - .m2/extensions.xml: i think it is hard here to enforce what projects
>to operate on, i don't think you want the groovy extension loaded for
>every project
>
>- distribution level: you have to ensure that everyone actually uses the
>same distribution. this is possible with the Maven Wrapper
>(http://github.com/takari/maven-wrapper)
>
>- project level
>  - .mvn/extensions.xml: what is currently implemented
>
>- organization level
>  - ${url}/extensions.xml: we need to use something outside the POM
>currently. we might be able to get clever making a couple passes but
>we're not currently doing that.
>
>Jordan, what do you think would be most convenient and least error prone?
>
>On May 27, 2015, at 2:52 PM, Jordan Zimmerman
> wrote:
>
>> What is the reason that .mvn/extensions.xml has to be added to every
>>project? It would be much more useful to add it globally in the .m2
>>directory. If I want to standardize, say, on Groovy polyglot I don¹t
>>want to have to have every developer in our org remember to add the
>>extension to every project. That would be a big pain.
>> 
>> 
>> 
>> 
>
>Thanks,
>
>Jason
>
>--
>Jason van Zyl
>Founder, Takari and Apache Maven
>http://twitter.com/jvanzyl
>http://twitter.com/takari_io
>-
>
>In short, man creates for himself a new religion of a rational
>and technical order to justify his work and to be justified in it.
>
>  -- Jacques Ellul, The Technological Society
>
>
>
>
>
>
>
>
>
>
>
>
>
>-
>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

Re: Install Problem on Mac OS

[Lyons, Roy]

I can't believe I just did that.  Please disregard this last email.




On 3/17/14 10:03 AM, "Lyons, Roy"  wrote:

>I'd recommend deleting settings.xml and running the plugin to grab a fresh
>one from Nexus
>
>mvn org.sonatype.plugins:nexus-m2settings-maven-plugin:1.4.8:download
>-DnexusUrl=https://nexus:8443/nexus -DtemplateId=CME
>
>Thats the much shorter way to configure yourself instead of messing with
>the dmg installer.
>
>
>Thanks,
>
>Roy Lyons
>Sr. Configuration Engineer
>20 S. Wacker 2S 67
>(312) 648 3659
>
>https://wiki.chicago.cme.com/confluence/display/CM/Home
>
>Next Chicago Atlassian User Group meeting:
>https://aug.atlassian.com/display/calendar/2014-03-18+Chicago+AUG+March+20
>1
>4 
>
>
>
>
>On 3/17/14 9:41 AM, "Wayne Fay"  wrote:
>
>>> mvn clean package
>>> [ERROR] Error executing Maven.
>>> [ERROR] 9 problems were encountered while building the effective
>>>settings
>>> [WARNING] Unable to parse element 'port', must be an integer (position:
>>> END_TAG seen ...\n  ... @15:14) caused by:
>>> java.lang.NumberFormatException: For input string: "" @
>>> /Users/joeterro/.m2/settings.xml, line 15, column 14
>>
>>Obviously you have problems with the data in your settings.xml file.
>>What exactly do you want us to do for you, considering you did not
>>provide that file so we can't view it, so we can't tell you how to fix
>>it?
>>
>>Wayne
>>
>>-
>>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

Re: Install Problem on Mac OS

[Lyons, Roy]

I'd recommend deleting settings.xml and running the plugin to grab a fresh
one from Nexus

mvn org.sonatype.plugins:nexus-m2settings-maven-plugin:1.4.8:download
-DnexusUrl=https://nexus:8443/nexus -DtemplateId=CME

Thats the much shorter way to configure yourself instead of messing with
the dmg installer.


Thanks,

Roy Lyons
Sr. Configuration Engineer
20 S. Wacker 2S 67
(312) 648 3659

https://wiki.chicago.cme.com/confluence/display/CM/Home

Next Chicago Atlassian User Group meeting:
https://aug.atlassian.com/display/calendar/2014-03-18+Chicago+AUG+March+201
4 




On 3/17/14 9:41 AM, "Wayne Fay"  wrote:

>> mvn clean package
>> [ERROR] Error executing Maven.
>> [ERROR] 9 problems were encountered while building the effective
>>settings
>> [WARNING] Unable to parse element 'port', must be an integer (position:
>> END_TAG seen ...\n  ... @15:14) caused by:
>> java.lang.NumberFormatException: For input string: "" @
>> /Users/joeterro/.m2/settings.xml, line 15, column 14
>
>Obviously you have problems with the data in your settings.xml file.
>What exactly do you want us to do for you, considering you did not
>provide that file so we can't view it, so we can't tell you how to fix
>it?
>
>Wayne
>
>-
>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

Re: dependency plugin strangeness

[Lyons, Roy]

After Stephen mentioned trying different versions, I had the developer try
out maven 2.2.1.  I was about to report back that this worked and how
strange it was -- but before sending I saw this email from Vincent.

I'll pass along the system scope issue - perhaps that is the nail in the
coffin.  We reverted with 2.2.1, with instructions to work on making it
3.x compliant in the background.

Thank you for all the input on this issue.  It is very much appreciated.

Thanks,

Roy

On 1/29/14 12:33 PM, "Vincent Latombe"  wrote:

>Hi,
>
>I have already seen such error.
>It is caused by the combination of a managed dependency (through
>dependencyManagement) defining a dependency with system scope + Maven 3 +
>Sonar. The same with Maven 2.2.1 should work.
>Though, I have never seen it directly in a dependency:tree execution; only
>through a sonar analysis.
>
>On my side, I got rid of the system scope usages.
>
>Vincent
>
>
>2014-01-29 Stephen Connolly 
>
>> The crucial detail was omitted... what version of Maven?
>>
>> I suspect it could be a transitive dependency with system scope causing
>>a
>> bug of some sort.
>>
>> Most likely if you switch to a different version of Maven the command
>>will
>> work... in which case you might be able to construct a test case to
>>prove a
>> regression.
>>
>> Touchstone versions of Maven to try are: 2.2.1, 3.0.4/3.0.5 and 3.1.1
>>
>> If you see the error on all three then it is something different... but
>> still an important data point.
>>
>> More of the stack trace would help... ideally include a line or two
>>above
>> and below... there is often crucial details therein... if you need to
>>hide
>> GAV details, change the groupId's to something gibberish, e.g.
>> com.foobar:foo-manchu:1.0-SNAPSHOT and other dummy GAVs
>>
>>
>> On 28 January 2014 22:55, Lyons, Roy  wrote:
>>
>> > So, I tried my google-fu first - and in general my google-fu is very
>>very
>> > strong...
>> >
>> > I've been fighting with this multi-module plan for some time now with
>>the
>> > developer who is reporting the issue to me.  The issue manifested
>>itself
>> as
>> > part of a Sonar failure...  the funny thing is, that the failure was
>>on a
>> > dependenct tree resolution that Sonar was doing - so I had him try the
>> > dependency plugin and perform a dependency:tree
>> >
>> > dependency tree failed us...  well, it probably isn't dependency
>>plugin's
>> > fault but I am at a loss as to what it is really dying on or why.
>> >
>> > I would absolutely love it if someone saw this and said "Oh yeah, I
>>know
>> > that issue.  Its a real pain.  They have XXX defined incorrectly in
>>their
>> > multimodule build so the dependency plugin is in a circular dependency
>> > loop" (or something like that).  I have no idea if its a dependency
>>loop,
>> > was just an example.
>> >
>> > I can't share the poms because its all proprietary closed source stuff
>> > (and I have to be careful about what is shared).  If this means that I
>> dont
>> > have enough info to help, I can live with that - and will continue to
>> plow
>> > forwards...  I just wanted to see if theres someone on the list who
>>knows
>> > exactly what I should be looking for to help shorten my investigation
>> time.
>> >
>> > Here's an example of what dependency:tree is complaining about.
>> >
>> >
>> >  mvn dependency:tree -Dverbose=true -DoutputFile=dependencies.txt -e
>>-X
>> >
>> > urls[38] =
>> >
>> 
>>file:/C:/Users/thisguysuserid/.m2/repository/commons-collections/commons-
>>collections/3.2.1/commons-collections-3.2.1.jar
>> > Number of foreign imports: 1
>> > import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
>> > -
>> >
>> > at
>> >
>> 
>>org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuil
>>dPluginManager.java:139)
>> > at
>> >
>> 
>>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.jav
>>a:209)
>> > ... 19 more
>> > Caused by: org.apache.maven.plugin.PluginContainerException: An API
>> > incompatibility was encountered while executing
>> > org.apache.maven.plugins:maven-dependency-plugin:2.8:tree:
>> > java.lang.AbstractMethodError:
>> >
>> 
>>org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.
>>manageArtifactSystemPath(Lorg/apache/maven/artifact/Artifact;Lorg/apache/
>>maven/artifact/Artifact;)V
>> >
>> >
>> >
>> >
>> >
>> >
>> > -
>> > 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

dependency plugin strangeness

[Lyons, Roy]

So, I tried my google-fu first - and in general my google-fu is very very 
strong...

I've been fighting with this multi-module plan for some time now with the 
developer who is reporting the issue to me.  The issue manifested itself as 
part of a Sonar failure...  the funny thing is, that the failure was on a 
dependenct tree resolution that Sonar was doing - so I had him try the 
dependency plugin and perform a dependency:tree

dependency tree failed us...  well, it probably isn't dependency plugin's fault 
but I am at a loss as to what it is really dying on or why.

I would absolutely love it if someone saw this and said "Oh yeah, I know that 
issue.  Its a real pain.  They have XXX defined incorrectly in their 
multimodule build so the dependency plugin is in a circular dependency loop" 
(or something like that).  I have no idea if its a dependency loop, was just an 
example.

I can't share the poms because its all proprietary closed source stuff (and I 
have to be careful about what is shared).  If this means that I dont have 
enough info to help, I can live with that - and will continue to plow 
forwards...  I just wanted to see if theres someone on the list who knows 
exactly what I should be looking for to help shorten my investigation time.

Here's an example of what dependency:tree is complaining about.


 mvn dependency:tree -Dverbose=true -DoutputFile=dependencies.txt -e -X

urls[38] = 
file:/C:/Users/thisguysuserid/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar
Number of foreign imports: 1
import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
-

at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:139)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.plugin.PluginContainerException: An API 
incompatibility was encountered while executing 
org.apache.maven.plugins:maven-dependency-plugin:2.8:tree: 
java.lang.AbstractMethodError: 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener.manageArtifactSystemPath(Lorg/apache/maven/artifact/Artifact;Lorg/apache/maven/artifact/Artifact;)V






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

Re: New logo?

[Lyons, Roy]

I asked my wife on the drive to the train today what animal she thinks
fits Maven.  Her response made me chuckle.

Without hesitation, she said "Honey Badger"

When I asked why, she said that Honey Badgers are part of nature and
generally do their thing nicely -- but if you piss it off, things will get
really really bad...  She said she had the same experience with Maven.  It
works nicely, but if you try to do something really non-standard, you will
feel its wrath :)

Heh.

Anyhow, I thought it was funny enough to share - not really a serious
consideration to make a Honey Badger our mascot.

On 1/10/14 1:20 AM, "Kristian Rosenvold" 
wrote:

>I think the association-work around what maven /is/ is a great way to
>approach a logo contest elsewhere. I have worked with some great graphic
>designers in my time, and the kind input the good ones want are typically
>related around your thoughts/feelings around the product rather than which
>particular animal you prefer, which is a bit of a secondary kind of input
>along with all different kinds of other constraints/ideas (the boss
>prefers
>blue).
>
>When I first encountered maven I had come to the realization that all my
>ant projects were basically the same, and that there was no reason for
>customizing
>what was basically a standard process. So maven gives me associations to a
>mass-production line at a factory, rather than a tailor making individual
>processes. Furthermore, the lifecycle amplifies the idea of a
>conveyor-belt
>mass-production line; all parts move through the same conveyor belt
>process, stopping at
>individual stages to get work done. I would almost be willing to think of
>a
>waterfall (Uh-oh...)
>
>So it would appear to me that I'm not thinking of an animal at all !
>
>Kristian
>
>
>
>
>
>
>
>2014/1/9 Mark H. Wood 
>
>> On Thu, Jan 09, 2014 at 09:32:54AM -0600, Curtis Rueden wrote:
>> > All of the logos are OK, but none of them really symbolize anything in
>> > particular about Maven. IMO the best logos encapsulate the purpose of
>>the
>> > project somehow, either overtly, covertly or both.
>>
>> Good point.  I was associating with the name "Maven", looking for a
>> symbol of in-depth understanding of a specialized field.
>>
>> http://en.wiktionary.org/wiki/maven
>>
>> So, what does Maven do?  It passes unique source and object code
>> inputs through a standardized process, guided by an expression of the
>> relationships among those inputs, to assemble a well-specified
>> configuration of runnable code.  What does that look like?
>>
>> --
>> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>> Machines should not be friendly.  Machines should be obedient.
>>


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

Re: New logo?

[Lyons, Roy]

HAH.  I like that.  It makes me think of the kids toy where you put shapes
into holes.

http://www.toysrus.com/graphics/media/trus/Aplusplus/2012/2501235/MATTEL-25
01235-01.jpg

Each block shape represents a type of output (.war, .jar, .ear, .so, .dll,
.zip, .someotherextensionthatyoudreamup)

Each hole represents a workflow to make that happen.  Ok its a little bit
reverse order, and more like http://static.ddmcdn.com/gif/play-doh-12.jpg




Anyhow, I like the "cookie cutter" approach to a logo because it goes with
Kristian's sentiment (which I happen to agree with once I read it).

Perhaps even an actual logo as a set of cookie cutters (kind of like
http://ecx.images-amazon.com/images/I/41BUOIKf4zL.jpg which is funny
because it has all kinds of animals in it too )




On 1/10/14 1:20 AM, "Kristian Rosenvold" 
wrote:

>I think the association-work around what maven /is/ is a great way to
>approach a logo contest elsewhere. I have worked with some great graphic
>designers in my time, and the kind input the good ones want are typically
>related around your thoughts/feelings around the product rather than which
>particular animal you prefer, which is a bit of a secondary kind of input
>along with all different kinds of other constraints/ideas (the boss
>prefers
>blue).
>
>When I first encountered maven I had come to the realization that all my
>ant projects were basically the same, and that there was no reason for
>customizing
>what was basically a standard process. So maven gives me associations to a
>mass-production line at a factory, rather than a tailor making individual
>processes. Furthermore, the lifecycle amplifies the idea of a
>conveyor-belt
>mass-production line; all parts move through the same conveyor belt
>process, stopping at
>individual stages to get work done. I would almost be willing to think of
>a
>waterfall (Uh-oh...)
>
>So it would appear to me that I'm not thinking of an animal at all !
>
>Kristian
>
>
>
>
>
>
>
>2014/1/9 Mark H. Wood 
>
>> On Thu, Jan 09, 2014 at 09:32:54AM -0600, Curtis Rueden wrote:
>> > All of the logos are OK, but none of them really symbolize anything in
>> > particular about Maven. IMO the best logos encapsulate the purpose of
>>the
>> > project somehow, either overtly, covertly or both.
>>
>> Good point.  I was associating with the name "Maven", looking for a
>> symbol of in-depth understanding of a specialized field.
>>
>> http://en.wiktionary.org/wiki/maven
>>
>> So, what does Maven do?  It passes unique source and object code
>> inputs through a standardized process, guided by an expression of the
>> relationships among those inputs, to assemble a well-specified
>> configuration of runnable code.  What does that look like?
>>
>> --
>> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>> Machines should not be friendly.  Machines should be obedient.
>>


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

short and snappy description of what Maven is

[Lyons, Roy]

on https://cwiki.apache.org/confluence/display/MAVEN/New+Main+Site it says:

We need a short and snappy description of what Maven is:

"Apache Maven is a software project management and comprehension tool."

Is just not an easy to understand description of what Maven is.




I would like to submit my short description for review.

"Apache Maven is a convention-over-configuration build tool which has great 
dependency management features."

I know that it does more than that - but I feel that at its core, this is what 
it really is.

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

Re: New logo?

[Lyons, Roy]

Lettering eh, how about comic sans?  :)



...



J/K btw  

Jason & company might let you re-use the letting from
http://blog.sonatype.com/wp-content/uploads/2010/03/maven1.jpg if you
wanted something a little edgier and crisp.


On 1/2/14 3:36 PM, "Stephen Connolly" 
wrote:

>Well our current "icon" is somebody's arse behind a laptop... Which with a
>cleaner site looks a tad odd
>
>With the old header bar it was fine though
>
>I have no issue changing the font or colouring, but I think an actual icon
>or emblem is something good to have.
>
>There was some effort to pick a new font, and I would be happy to see
>examples with a different font... My typographic skills are not near the
>level of my poor sketching skills, so I have been hoping somebody else
>could tackle the lettering
>
>
>On Thursday, 2 January 2014, Mark Derricutt wrote:
>
>> Is it me or are a lot of these purely changing the icon, not the "logo".
>>
>> i.e. is the "logo" inclusive of the "mAven" name ( side question - why
>>is
>> the A always a different colour, historic Ant reference? )
>>
>> On 3 Jan 2014, at 2:18, Stephen Connolly wrote:
>>
>> > As 9 is particularly problematic I have sketched -14 which is not a
>> direct
>> > copy of a silhouette. This still has the issue w.r.t. other marks
>>called
>> > maven using a silhouetted raven...
>>
>
>
>-- 
>Sent from my phone


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

Re: Searching for artifacts which are used as a dependency by other artifacts

[Lyons, Roy]

I can say that Sonatype has a solution for this in CLM - as long as you
scan everything it will maintain the relationships for the reverse
dependency lookup. 

I think I heard that they were thinking about bringing this capability to
Nexus (by querying CLM in the backend).

Other than that, I ended up writing a perl script that would parse the
following out of every branch in every repository:
mvn help:effective-pom
mvn dependency:list
pom.xml

I then read that into a wonderful hash structure which I used to create a
reverse hash, and then create a nice csv file from that data which I can
use in and excel-like program to search for the dependency - and see the
results.  I created a forward-dependency.csv and a reverse-dependency.csv
with my hash structures to present the data in different ways.

Either way, its totally possible to do.

On 12/19/13 8:36 AM, "Karl Heinz Marbaise"  wrote:

>Hi,
>
>currently i'm searching for a solution to the given problem:
>
>Given maven coordinates: GAV
>
>I would like to know of which other artifacts (GAV) this given GAV is
>used by. Or in other words which artifacts having a dependency to the
>above artifact.
>
>I've found in the meantime the maven-indexer project which uses the
>repository index (central or others like from Nexus). But it looks like
>it can't solve this...may be i miss something in relationship with
>maven-indexer ..
>
>
>Does someone have an idea how to solve the above problem ?
>
>I appreciate any hints etc. links or so...
>
>Kind regards
>Karl-Heinz Marbaise
>-- 
>SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
>Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
>Hauptstrasse 177 USt.IdNr: DE191347579
>52146 Würselen   http://www.soebes.de
>
>-
>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

Re: how to run compile and packaging before test?

[Lyons, Roy]

I have a feeling that you aren't running unit tests, but instead
integration tests...

http://maven.apache.org/surefire/maven-failsafe-plugin/ is what you want!
that happens after the package phase.

On 12/11/13 4:57 PM, "Andrew E. Davidson"  wrote:

>
>Hi 
>
>my unit test require I a *.tar.gz. The *.tar.gz needs to include the 3rd
>party dependencies and the projects jar file artifact.
>
>I tried using an assembly and setting the phase, so it will run before
>the unit tests run, how ever my project artifact has not been packaged yet
>
>Any comments or suggestions would be greatly appreciated
>
>Andy
>
>$ mvn -version
>Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>05:51:28-0800)
>
>from my pom.xml
>
>   
>   
>   org.apache.maven.plugins
>   maven-assembly-plugin
>   2.4
>   
>   
>   createTarball-assembly
>   
>   
> process-test-classes
>   
>   single
>   
>   false
>   
>   
>   
>   
>
> src/createTarballAssembly.xml
>   
>   
> ${project.build.finalName}
>   
> false
>   
>   
>
>
>
>here is my assembly file
>
>   
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1
>.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin
>/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
>
>   
>
>   createTarball-assembly
>   
>   tar.gz
>   
>   false
>   
>   
>   
>   
> ${project.build.directory}/${project.build.finalName}e>
>   aid-athena-common
>   
>   true
>   false
>   runtime
>   lib
>   
>   
>   
>   
>   
>   
>
>


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

Feature idea - global excludes

[Lyons, Roy]

Today the dependency exclude works on a artifact by artifact basis.  I was just 
thinking that someone might want to do a blanket exclude without having to 
dependency:tree -Dverbose=true to see all the items which might have it...

Before submitting an enhancement request, I thought I would get the community's 
input on whether or not this idea has merit, or if it is such an edge case that 
noone really cares...

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

Re: System-wide, read-only repository

[Lyons, Roy]

gah, resending with the link this time.

http://openbenchmarking.org/result/1304257-FO-MERGE786390



On 10/30/13 11:21 AM, "Lyons, Roy"  wrote:

>I am trying to get my unix admins to use it for us.  here are some
>benchmarks I have seen.
>
>
>On 10/30/13 10:51 AM, "Curtis Rueden"  wrote:
>
>>Hi Roy,
>>
>>> zfs has built in de-duplication.
>>
>>ZFS sounds awesome in theory but have you actually tried it? If so, how
>>is
>>it working for you? In particular, how is the performance?
>>
>>-Curtis
>>
>>
>>On Wed, Oct 30, 2013 at 10:43 AM, Lyons, Roy 
>>wrote:
>>
>>> :) but like I said, you wouldnt worry about the space if it was all on
>>> zfs.  zfs has built in de-duplication.  you could have 2000 local maven
>>> repos and probably not fill your disk since most of it has to do with
>>> duplicate jars and such.
>>>
>>> On 10/30/13 10:37 AM, "Curtis Rueden"  wrote:
>>>
>>> >Hi all,
>>> >
>>> >There is plenty of room for improvement regarding reuse of Maven's
>>>local
>>> >repository cache. Releases in particular are supposed to be immutable
>>>so
>>> >once they are downloaded they could go into a read-only tier as
>>>suggested
>>> >by Stephen. Inventing such a scheme to reuse large portions of the
>>>repo
>>> >cache would be of great benefit to the Maven community.
>>> >
>>> >E.g.: the recommended CIS strategy is for every job to use its own
>>>local
>>> >repo cache, which becomes very large. My Jenkins has dozens of Maven
>>>build
>>> >jobs and I cannot afford the bloat; my Jenkins backups are huge enough
>>> >already. So what I do instead is limit my Maven Jenkins node to a
>>>single
>>> >executor, which is a real waste on a 16 core machine. Much better
>>>would be
>>> >if the jobs could share the bulk of the repo cache.
>>> >
>>> >So it's definitely an itch, but not quite itchy enough for anyone to
>>> >scratch yet...
>>> >
>>> >Regards,
>>> >Curtis
>>> > On Oct 30, 2013 8:35 AM, "Mark H. Wood"  wrote:
>>> >
>>> >> On Wed, Oct 30, 2013 at 10:18:49AM +0100, Matthieu Moy wrote:
>>> >> > Barrie Treloar  writes:
>>> >> >
>>> >> > > On 29 October 2013 23:56, Lyons, Roy 
>>> wrote:
>>> >> > >> Unfortunately, you will always have something in
>>> >>$HOME/.m2/repository
>>> >> > >> because that's how maven works.
>>> >> > >>
>>> >> > >> Can I suggest perhaps that you use zfs for deduplication in
>>>/home?
>>> >> > >> Otherwise, you can add something like
>>> >> > >
>>> >> > > Or give them more disk space - isn't this stuff meant to be
>>>cheap
>>> >> now-a-days?
>>> >> >
>>> >> > Local disk space is cheap. NFS-shared, RAID & backed-up disk
>>>space,
>>> >>less
>>> >> > so. I can live with a few Gb of waste, but I was just wondering
>>> >>whether
>>> >> > we could do any better.
>>> >>
>>> >> Disks are cheap.  But not free.  Running the procurement gantlet is
>>> >> not free.  Downtime to install new storage is not free.  Lord knows
>>> >> that additional backup tapes are not free, not even cheap.  Longer
>>> >> backup windows are not free.  Throwing storage at the problem is
>>>often
>>> >> a reasonable choice, but it's also reasonable to always ask if there
>>> >> isn't a better way.
>>> >>
>>> >> Sorry, I've been aching to write that for a long time
>>> >>
>>> >> --
>>> >> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>>> >> Machines should not be friendly.  Machines should be obedient.
>>> >>
>>>
>>>
>>> -
>>> 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

Re: System-wide, read-only repository

[Lyons, Roy]

I am trying to get my unix admins to use it for us.  here are some
benchmarks I have seen.


On 10/30/13 10:51 AM, "Curtis Rueden"  wrote:

>Hi Roy,
>
>> zfs has built in de-duplication.
>
>ZFS sounds awesome in theory but have you actually tried it? If so, how is
>it working for you? In particular, how is the performance?
>
>-Curtis
>
>
>On Wed, Oct 30, 2013 at 10:43 AM, Lyons, Roy 
>wrote:
>
>> :) but like I said, you wouldnt worry about the space if it was all on
>> zfs.  zfs has built in de-duplication.  you could have 2000 local maven
>> repos and probably not fill your disk since most of it has to do with
>> duplicate jars and such.
>>
>> On 10/30/13 10:37 AM, "Curtis Rueden"  wrote:
>>
>> >Hi all,
>> >
>> >There is plenty of room for improvement regarding reuse of Maven's
>>local
>> >repository cache. Releases in particular are supposed to be immutable
>>so
>> >once they are downloaded they could go into a read-only tier as
>>suggested
>> >by Stephen. Inventing such a scheme to reuse large portions of the repo
>> >cache would be of great benefit to the Maven community.
>> >
>> >E.g.: the recommended CIS strategy is for every job to use its own
>>local
>> >repo cache, which becomes very large. My Jenkins has dozens of Maven
>>build
>> >jobs and I cannot afford the bloat; my Jenkins backups are huge enough
>> >already. So what I do instead is limit my Maven Jenkins node to a
>>single
>> >executor, which is a real waste on a 16 core machine. Much better
>>would be
>> >if the jobs could share the bulk of the repo cache.
>> >
>> >So it's definitely an itch, but not quite itchy enough for anyone to
>> >scratch yet...
>> >
>> >Regards,
>> >Curtis
>> > On Oct 30, 2013 8:35 AM, "Mark H. Wood"  wrote:
>> >
>> >> On Wed, Oct 30, 2013 at 10:18:49AM +0100, Matthieu Moy wrote:
>> >> > Barrie Treloar  writes:
>> >> >
>> >> > > On 29 October 2013 23:56, Lyons, Roy 
>> wrote:
>> >> > >> Unfortunately, you will always have something in
>> >>$HOME/.m2/repository
>> >> > >> because that's how maven works.
>> >> > >>
>> >> > >> Can I suggest perhaps that you use zfs for deduplication in
>>/home?
>> >> > >> Otherwise, you can add something like
>> >> > >
>> >> > > Or give them more disk space - isn't this stuff meant to be cheap
>> >> now-a-days?
>> >> >
>> >> > Local disk space is cheap. NFS-shared, RAID & backed-up disk space,
>> >>less
>> >> > so. I can live with a few Gb of waste, but I was just wondering
>> >>whether
>> >> > we could do any better.
>> >>
>> >> Disks are cheap.  But not free.  Running the procurement gantlet is
>> >> not free.  Downtime to install new storage is not free.  Lord knows
>> >> that additional backup tapes are not free, not even cheap.  Longer
>> >> backup windows are not free.  Throwing storage at the problem is
>>often
>> >> a reasonable choice, but it's also reasonable to always ask if there
>> >> isn't a better way.
>> >>
>> >> Sorry, I've been aching to write that for a long time
>> >>
>> >> --
>> >> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>> >> Machines should not be friendly.  Machines should be obedient.
>> >>
>>
>>
>> -
>> 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

Re: System-wide, read-only repository

[Lyons, Roy]

:) but like I said, you wouldnt worry about the space if it was all on
zfs.  zfs has built in de-duplication.  you could have 2000 local maven
repos and probably not fill your disk since most of it has to do with
duplicate jars and such.

On 10/30/13 10:37 AM, "Curtis Rueden"  wrote:

>Hi all,
>
>There is plenty of room for improvement regarding reuse of Maven's local
>repository cache. Releases in particular are supposed to be immutable so
>once they are downloaded they could go into a read-only tier as suggested
>by Stephen. Inventing such a scheme to reuse large portions of the repo
>cache would be of great benefit to the Maven community.
>
>E.g.: the recommended CIS strategy is for every job to use its own local
>repo cache, which becomes very large. My Jenkins has dozens of Maven build
>jobs and I cannot afford the bloat; my Jenkins backups are huge enough
>already. So what I do instead is limit my Maven Jenkins node to a single
>executor, which is a real waste on a 16 core machine. Much better would be
>if the jobs could share the bulk of the repo cache.
>
>So it's definitely an itch, but not quite itchy enough for anyone to
>scratch yet...
>
>Regards,
>Curtis
> On Oct 30, 2013 8:35 AM, "Mark H. Wood"  wrote:
>
>> On Wed, Oct 30, 2013 at 10:18:49AM +0100, Matthieu Moy wrote:
>> > Barrie Treloar  writes:
>> >
>> > > On 29 October 2013 23:56, Lyons, Roy  wrote:
>> > >> Unfortunately, you will always have something in
>>$HOME/.m2/repository
>> > >> because that's how maven works.
>> > >>
>> > >> Can I suggest perhaps that you use zfs for deduplication in /home?
>> > >> Otherwise, you can add something like
>> > >
>> > > Or give them more disk space - isn't this stuff meant to be cheap
>> now-a-days?
>> >
>> > Local disk space is cheap. NFS-shared, RAID & backed-up disk space,
>>less
>> > so. I can live with a few Gb of waste, but I was just wondering
>>whether
>> > we could do any better.
>>
>> Disks are cheap.  But not free.  Running the procurement gantlet is
>> not free.  Downtime to install new storage is not free.  Lord knows
>> that additional backup tapes are not free, not even cheap.  Longer
>> backup windows are not free.  Throwing storage at the problem is often
>> a reasonable choice, but it's also reasonable to always ask if there
>> isn't a better way.
>>
>> Sorry, I've been aching to write that for a long time
>>
>> --
>> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>> Machines should not be friendly.  Machines should be obedient.
>>


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

Re: System-wide, read-only repository

[Lyons, Roy]

Unfortunately, you will always have something in $HOME/.m2/repository
because that's how maven works.

Can I suggest perhaps that you use zfs for deduplication in /home?
Otherwise, you can add something like
-Dmaven.repo.local=/tmp/${USER}_repository (with a mkdir -p in their
profile or something to make the directory ahead of time).  I believe this
can be added to MAVEN_OPTS and it would work...

Either way, with 200 students, I would recommend the zfs since there will
be LOTS of duplicated jars.

Making a single local cache is a very bad idea.  there isnt any locking,
so they would clobber each other and get errors.  One student would be
accessing the jar as part of compilation and the other will be
mid-overwriting the jar.  its messy.  Even messier if they change their
umask, and noone can read or write to the location.

So, thats my 2 bits on the topic.



On 10/29/13 4:38 AM, "Matthieu Moy"  wrote:

>Hi,
>
>I have a setup with many users (200 students), each of them having a
>limited $HOME. I'm looking for a way to provide them the most common
>plugins and dependencies and save disk space.
>
>Is there a way to have a system-wide (e.g. /usr/share/maven/... or so)
>repository, where the sysadmin could download stuff that the students
>wouldn't have to download and store in their $HOME ?
>
>I found many solutions using a proxy, that would allow me to download
>from the intranet, but these solutions still require a local repository
>in $HOME/.m2/, so this saves bandwidth but not disk space. I also saw
>some people advising to set localRepository in their pom.xml, but this
>does not seem to be a good idea (not thread-safe), and doesn't really
>solve my issue, as I would like the system-wide repository to be
>read-only (managed by root only), and to come in addition to $HOME/.m2/,
>not as a replacement.
>
>Thanks in advance,
>
>-- 
>Matthieu Moy
>http://www-verimag.imag.fr/~moy/
>
>-
>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

Re: Looking for class property-substitution plugin

[Lyons, Roy]

:) I have an obligatory recommendation.  If nothing else, theres the
antrun plugin which will allow you to do that substitution as well.  It
allows you to run ant functions within the pom.

You may be able to just keep the files in your src/main/language folder,
and do a " wrote:

>Before I write this myselfŠ
>
>I am converting an ant build to maven. One of the steps processes a
>template file, using properties from a properties file to replace tokens
>and produce a java source file, which is then compiled. Is there an
>existing plugin which does this? The resource plugin can do the
>substitution, but will not mark the resultant file for compilation. It's
>not all that difficult to write, but one fewer plugin to maintain is a
>good thing.
>
>Thanks,
>Russ
>-
>Come read my webnovel, Take a Lemon ,
>and listen to the Misfile radio play
>!
>
>
>
>
>


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

Maven 3.1 profile activation

[Lyons, Roy]

So...  They released sonar-maven-plugin 2.1...  and my corporate pom is nice 
enough to developers to choose the right sonar plugin based on maven version...


maven-2



${basedir}


...

maven-3



${basedir}



Now I have a problem...

The profile maven-3 will be activated for 3.1, and I have no currently known 
way to determine if it is 3.1 or not.


I am looking to get some suggestions from the community as to the best way to 
compensate for this issue.  I don't see any new variables I can test, and I 
dont see any properties which show the maven version...




Thanks,

Roy Lyons

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

Re: Putting buildNumber into Manifest...

[Lyons, Roy]

You may be even more interested in injecting the version control tool's
code identification, like say the commit hash being built from git.  Then
you can trace it back to the code directly!


Thanks,

Roy Lyons




On 6/12/13 1:17 PM, "Jeff"  wrote:

>We have a continuous deployment system that constantly triggered by SCM
>changes and builds/pushes our WAR files to our various environments.
>
>I use the maven-war-plugin to insert specifics of the artifact into the
>MANIFEST.MF.  However, the version for SNAPSHOTs is always in the form
>1.1.1-SNAPSHOT, but would like to have it include the build number that
>matches what is in our internal Maven Repository (e.g.,
>1.1.1-2013050323423-27).
>
>This might be a chicken and egg scenario, but is there a way to somehow
>use
>the buildNumber in the MANIFEST instead of the SNAPSHOT qualifier so we
>can
>easily see when troubleshooting which version is really deployed?
>
>Thanks!
>
>-- 
>Jeff Vincent
>See my LinkedIn profile at:
>http://www.linkedin.com/in/rjeffreyvincent
>I ♥ DropBox  !!


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

Re: For artifact {org.jvnet.staxex:stax-ex:null:jar}: The version cannot be empty.

[Lyons, Roy]

eclipse:eclipse is borked and deprecated.  please import your pom into
eclipse with the supported m2eclipse plugin.  I promise you a ton less
heartache.


Thanks,

Roy Lyons




On 6/7/13 5:52 PM, "Vladimir Sutskever" 
wrote:

>All,
>
>I am running eclipse:eclipse on a project and getting the
>
>[ERROR] Failed to execute goal
>org.apache.maven.plugins:maven-eclipse-plugin:2.9:eclipse (default-cli)
>on project installer: Execution default-cli of goal
>org.apache.maven.plugins:maven-eclipse-plugin:2.9:eclipse failed: For
>artifact {org.jvnet.staxex:stax-ex:null:jar}: The version cannot be
>empty. -> [Help 1]
>
>
>After some debugging, I notice the following warning
>
>[WARNING] Invalid POM for com.sun.xml.stream.buffer:streambuffer:jar:0.4,
>transitive dependencies (if any) will not be available, enable debug
>logging for more details: Some problems were encountered while processing
>the POMs:
>[ERROR] 'dependencies.dependency.version' for
>org.jvnet.staxex:stax-ex:jar is missing. @ line 7, column 17
>[ERROR] 'dependencies.dependency.version' for activation:activation:jar
>is missing. @ line 11, column 17
>
>I pulled up the pom file for
>com.sun.xml.stream.buffer:streambuffer:jar:0.4,  and it is in-fact
>missing versions for its dependancies.
>I figured I would include a newer version of streambuffer.jar  in my pom
>explicitly (which has correct pom) but for some reason,  maven is still
>choosing the transitive version of the dependency over my explicitly
>declared one.
>Removing it:
>com.sun.xml.stream.buffer:streambuffer:jar:0.7:compile (removed - nearer
>found: 0.4)
>
>This project is a child project of another project.
>
>
>TWO QUESTIONS:
>
>In what cases will maven choose a transitive dependency version over an
>explicitly declared one in the pom?
>Is there a way to make maven less sensitive  - to missing versions in
>poms?
>
>I am currently running:
>Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>13:51:28+)
>
>
>


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

Re: DLL Artifact

[Lyons, Roy]

You could use the maven native plugin to do this:

http://mojo.codehaus.org/maven-native/native-maven-plugin/usage.html

dll is one of the options.  There is also jnilib as one of the options (I
am assuming for linux jni binaries)


Thanks,

Roy Lyons




On 6/5/13 7:26 AM, "Andy"  wrote:

>Hi All,
>
>I have searched to death the jni project solutions and would just like a
>simple solution to a trivial issue, but having
>difficulty pulling it off.
>
>I have the classic jar and dll (I am really not interested the native
>plugin or packaging the dll in a jar yet, etc. I
>just don't have the time right now).
>
>I know I can manually deploy the dll artifact to our repo and declare a
>dep etc, then use the dependency module to get
>it - This is what I've done so far as a quick fix.
>
>What I'd like to do is more simple than that in the long run. I want to
>have the jar and dll projects as modules in a
>multi-module pom, that's done.
>
>parentjar/pom.xml
>  |dll/pom.xml
>  |dll/...my.dll
>
>Now I'd just like the dll/pom.xml to say 'do not package a jar, then
>deploy the dll as the artifact.
>
>To disable the jar is easy enough...
>
>
> default-jar
> none
>
>
>...but how to get the dll to automatically deploy on the deploy phase?
>
>I know I've see it done somewhere, but just can't find what I need.
>Thanks in advance.
>
>Andy.
>
>
>-
>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

Re: Source code verification/compliance with Maven?

[Lyons, Roy]

Well, I know that Sonatype has a product they have been pretty aggressive
with called CLM.

CLM shows both vulnerabilities and license threats -- including undefined
licenses...  Perhaps that is what you need?


Thanks,

Roy Lyons





On 5/9/13 4:15 AM, "Daniel Pocock"  wrote:

>
>Hi,
>
>There is a lot of confusion about the distinction between software that
>is free (like malware in app stores) and software that is really free
>with open source code.
>
>Several people have asked me how they can be sure that a Maven build
>(including all downloaded plugins) only uses genuine open source
>software, and that the binary downloads are identical to the source
>releases.  There are many users that want to build projects from source
>code in clean, non-networked environments.
>
>How can somebody tell Maven to
>a) recursively download source JARs for all plugins and dependencies
>(and their build plugins) and compile them one by one?
>b) stop if any source JAR contains binary artifacts or if a
>dependency/plugin source is not available?
>c) put all downloaded source in some kind of tree where it can be tarred
>up, copied onto a DVD and then built by a machine that is offline?
>
>I'm aware of the command "mvn dependency:sources", but this only appears
>to fetch the sources on a best effort basis and doesn't appear to
>compile them.
>
>Regards,
>
>Daniel
>
>
>
>-
>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

Re: Why does the release process seem to require duplicate effort?

[Lyons, Roy]

Russ,

Our team, for an example, performs the release:prepare to verify the code
and apply the label.  We then check out the label to perform the build,
perform an assembly, and call an outside script with parameters that it
reads from an outside system and updates that outside system with a
deployable package and logfiles from the build.

We find this a million times easier to regulate and enforce than having
500 different applications create a custom lifecycle in their projects and
have the possibility of having things out of sync with process.

That being said, we wouldn't want to see that go away (since we never ever
use release:perform) - but would welcome another target to the release
plugin which combines prepare and perform.

tl;dr - Even if there doesn't seem to be a need for modularity in some
process or plugin, invariably there is a team that relies on its existance
in order to function correctly.


Thanks,

Roy Lyons
Senior Configuration Engineer





On 4/17/13 12:34 PM, "Russell Gold"  wrote:

>Hi,
>
>Why does the normal release process require both release:prepare and then
>release:perform? Under what conditions would you choose not to do the
>perform step after a successful prepare step? Why do both generate source
>and javadoc jars and prompt for the PGP pass phrase?
>
>Thanks,
>Russ
>-
>Come read my webnovel, Take a Lemon ,
>and listen to the Misfile radio play
>!
>
>
>
>


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

RE: maven-antrun-plugin in interactive mode

[Lyons, Roy]

There is a kludge you could possibly use.  Of course I am feeding bad 
behaviors...  but what the heck, its an official codehaus plugin - it would be 
wrong not to mention it.

http://mojo.codehaus.org/properties-maven-plugin/ 

have your ant task write to a file instead of exporting the property, then have 
this plugin read it in.  You could repeat the plugin invocation in your child 
modules.



From: Stephen Connolly [stephen.alan.conno...@gmail.com]
Sent: Tuesday, March 12, 2013 5:45 AM
To: Maven Users List
Subject: Re: maven-antrun-plugin in interactive mode

Please read my answer to a similar question on stack overflow:
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072

When you use antrun to set properties, you are setting "Mojo injected
properties" to use the terminology of my answer. Such properties are only
available within the scope of the currently executing module and only after
the execution of the injecting mojo. Those properties are not available to
child modules. If you look at the reactor order in the build plan, you will
also probably see that the module you are executing this in is running
after the child modules, so even if you could "trick" maven to make this
available to the child modules, it would be too late in any case


On 12 March 2013 10:24, virg g <06v...@gmail.com> wrote:

> Hi,
> I am using maven-antrun-plugin 1.8 in interactive mode to accept user
> inputs for build version for my project.  i want to use this version to be
> updated in all manifests file of all the jars of my project creates.
> I have added this plugin in the parent pom, which has all the modules to be
> built and also the plugin for jar to add manifest info. But the input
> received from prompt i.e build version, not able to update the manifest
> info from this variable (build version). I getting this value as empty. How
> to make this value available to all the jars while updating manifest info.
> This is my sample code in the parent POM. I dont want to pass these
> parameters as command line arguments which i am able to update manifest
> info. My option is only interactive mode. I have set
> false without this, it prompts for each jar which
> when it creates. Any help is highly appreciated.
> 
> org.apache.maven.plugins
> maven-antrun-plugin
> 1.7
> 
> 
> catch-new-version
> false
> 
> run
> 
> validate
> 
> 
>
>  message="Please enter the new build
> version : "
> addproperty=build-version" />
> 
>
> true
> 
> 
>
>
>
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 2.3.1
>
> ---
> 
> 
>
> ${build-version}
> 
> 
> 
>
> Thanks
> virg
>

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

Re: Unpacking jars into target/classes

[Lyons, Roy]

I have always referred to it as the "local dot m2 cache".  people know
exactly what I am talking about when I say that...


Thanks,

Roy Lyons



On 3/8/13 8:16 AM, "Ron Wheeler"  wrote:

>On 08/03/2013 9:07 AM, Doug Douglass wrote:
>> On Fri, Mar 8, 2013 at 12:28 AM, Joachim Durchholz 
>>wrote:
>>>
>>> Matthew mentioned install-file, but I already explained why a Maven
>>>repo
>>> is not an option.
>>>
>>>
>> Just a point of clarification, install-file installs artifacts into a
>> machines local repository cache, and in no way requires an MRM. I think
>> Matthew was suggesting to use install-file specifically because you are
>>not
>> using an MRM.
>>
>> Unfortunately, the local repository cache is often referred to simply
>>as a
>> repository and this frequently causes confusion. Perhaps we (the maven
>> community) should refer to the local repository cache by a different
>>name
>> e.g. artifact cache.
>>
>> Cheers
>>
>workstation cache?
>
>-- 
>Ron Wheeler
>President
>Artifact Software Inc
>email: rwhee...@artifact-software.com
>skype: ronaldmwheeler
>phone: 866-970-2435, ext 102
>
>
>-
>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

Re: dynamically select resources and apply filtering

[Lyons, Roy]

I say that you could just run a post-deployment command that performs any
filtering.  You could use ant, perl, java, whatever you wanted to...  and
perhaps have it pull down content from a centralized git repository or
something to make it easy to maintain your properties/configs.

The obvious mess comes into play if you are performing deployments using
the maven tomcat plugin or something similar instead of a real packaging
tool.


Thanks,

Roy Lyons





On 2/26/13 9:43 AM, "Stephen Connolly" 
wrote:

>I have an answer on Stack Overflow that might help your thought processes:
>http://stackoverflow.com/questions/14650468/whats-a-practicable-way-for-au
>tomated-configuration-versioning-and-deployment/14661186#14661186
>
>
>On 26 February 2013 15:06, Jean-Noël Colin  wrote:
>
>> so your suggestion would be to have maven do the compile, and a kind of
>> 'war:exploded', and then run ant to add the customized files and create
>>the
>> war file, is that correct?
>>
>> or should I write a plugin that does that for me?
>>
>> You write: "Separating run-time deployment from Maven is a best
>>practice";
>> but then, what should I use to customise and deploy distribution kits?
>>
>> Best
>>
>> Jean-Noël
>>
>> On 26 Feb 2013, at 10:01, Ron Wheeler 
>> wrote:
>>
>> > On 26/02/2013 2:54 AM, Baptiste MATHUS wrote:
>> >> I *think* Ron means: using maven to produce your standard artifacts
>> >> (jar/war/ear ?), and then use pure ant somewhere in the process just
>> before
>> >> deploying for a specific customer to do the replacements you're
>>talking
>> >> about.
>> >>
>> >> (By the way, invoking ant from maven (using antrun-maven-plugin)
>>should
>> >> always be considered something bad and temporary. Writing or using a
>> >> dedicated maven plugin is the way to go).
>> >>
>> > Exactly.
>> > My suggestion would be to run the ant after all the maven work is
>> complete and you have a full set of release files in your repo
>> > Have Ant (or some other process) merge the released code with
>> configuration files, logos, etc to make distribution kits.
>> >
>> > Ron
>> >> 2013/2/26 Jean-Noël Colin 
>> >>
>> >>> Hi Ron,
>> >>>
>> >>> Do you mean invoking the ant plugin from the pom.xml file? I was
>> wondering
>> >>> whether this was a good practice, or something to be kept only for
>> >>> situations where you really can't avoid it
>> >>>
>> >>> Best regards
>> >>>
>> >>> Jean-Noël
>> >>>
>> >>> On 25 Feb 2013, at 21:31, Ron Wheeler
>>
>> >>> wrote:
>> >>>
>>  Why not move the production of the software to Maven and leave the
>> >>> assembly in Ant.
>>  That would give you the best of both worlds.
>> 
>> 
>>  On 25/02/2013 2:41 PM, Jean-Noël Colin wrote:
>> > Hi
>> >
>> > I'm trying to migrate my project from ant to maven, but I'm
>>facing a
>> >>> few difficulties; I need to build my project for different
>>environments
>> >>> (customers, so possibly a long list). In my ant project, I had
>>several
>> >>> .properties file, one per customer; in this file, I had properties
>> used to
>> >>> customize some config file; I managed to use resource filtering to
>> achieve
>> >>> this.
>> > However, some properties defined a filename that needed to be
>>copied
>> to
>> >>> the war archive, but under a common name. For instance, I had
>>several
>> >>> logos: logo_customer1.jpg, logo_customer2.jpg, logo_customer3.jpg;
>>the
>> >>> source file name was specified in the properties file
>> >>> (customer1.properties, customer2.properties, customer3.properties),
>> but the
>> >>> destination was always logo.jpg. How can I do that?
>> > Second, the properties file defines the name of the file
>>(resources)
>> to
>> >>> be filtered. For instance, I have a template for working with Spring
>> >>> Security in LDAP environment and another template when working when
>> Active
>> >>> Directory; the customer properties file defined the name of the
>> template to
>> >>> use, but in both cases, the result file needs to be
>> >>> applicationContext-security.xml. How can i achieve this? Or is
>>there a
>> way
>> >>> to define conditional profiles so that in the customer .properties
>> file, I
>> >>> would say LDAP or AD, and based on that value, different profile
>>would
>> be
>> >>> used?
>> > Many thanks for your help
>> >
>> > Jean-Noël
>> >
>> >
>> > 
>>-
>> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>> >
>> 
>>  --
>>  Ron Wheeler
>>  President
>>  Artifact Software Inc
>>  email: rwhee...@artifact-software.com
>>  skype: ronaldmwheeler
>>  phone: 866-970-2435, ext 102
>> 
>> 
>>  
>>-
>>  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>  For additional commands, e-mail: users-h...@mave

Re: Eclipse plugin and project references

[Lyons, Roy]

>From my experience to date, it has proven far better to use the m2eclipse
plugin and import the maven project directly.  It will then perform the
build using maven...

When people come to me with issues such as yours, I generally tell them to
delete the project and re-import using m2eclipse (and never use mvn
eclipse:eclipse again) -- and then everything works wonderfully for them.


Thanks,

Roy Lyons




On 2/25/13 11:03 AM, "Stiffler82"  wrote:

>I have a problem and can not find any support for it, also not in google.
>I
>created my own lib called "core.jar" and when I try to refer it as a
>dependency in from my POM all works fine:
>
>   
>  com.innosquared
>  core
>  1.1.10
>   
>
>But when I run mvn eclipse:eclipse Maven creates wrong .classpath and
>.project files. It resolves my jar as a java project instead of a jar
>library. The following entry will be created in my classpath:
>
>  
>
>In my .projects file there is now:
>
> 
>core
>  
>
>I do not define anything in my Build-Cycle in POM, so I don't understand
>this strange behaviour. What can I do to prevent Maven from resolving my
>jar
>as a java project and resolving it as a normal dependency instead?
>
>
>
>--
>View this message in context:
>http://maven.40175.n5.nabble.com/Eclipse-plugin-and-project-references-tp9
>9838p5748396.html
>Sent from the Maven - Users mailing list archive at Nabble.com.
>
>-
>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

Re: Way to limit the projects in the reactor of a maven build started with the invoker plugin

[Lyons, Roy]

I have a method which will summarily be poked at...  but it works for the
one team that uses it here...

They put the [modules] section in profiles...  and set a profile to
determine which set of modules are included.

In general the advice you will get is to never have a profile make a
difference in the binaries being built...  but it is kind of handy if its
an internal project that is well documented.

Thanks,

Roy Lyons
Senior Configuration Engineer






On 2/13/13 2:40 PM, "christofer.d...@c-ware.de"
 wrote:

>Hi,
>
>I'm currently trying to use the invoker plugin to start a maven build and
>to pass the list of projects that should be in the reactor of that build.
>Unfortunately I couldn't find a way to do so ... so is there a way and if
>not, how could I start a second maven build from a maven build?
>
>Chris


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

Re: How best to manage project dependency versions

[Lyons, Roy]

Is these the droids you are looking for?

http://mojo.codehaus.org/versions-maven-plugin/examples/advancing-dependenc
y-versions.html

http://mojo.codehaus.org/versions-maven-plugin/examples/update-parent.html

Thanks,

Roy Lyons
Senior Configuration Engineer





On 1/30/13 3:12 PM, "Pimentel, Robert"  wrote:

>Hi,
>
>Historically we've had a lot of trouble getting our developers to adhere
>to our company's stated best practices. For example, we want all projects
>to depend upon the latest version of other projects (unless they have a
>valid reason not to). Typically our developers will only update the
>dependency version for the projects they are changing, or someone on
>their project team is changing. They will not look at the full list of
>projects that are changing as part of the release. Consequently,  many
>projects get compiled against one version of a project, but at run-time
>they use the latest version of that project. This usually doesn't cause
>problems, but can.
>
>We audit the versions just prior to releasing them. Sometimes when we
>change the dependency version to the latest value, the project fails to
>compile. One reason is because the code is referencing non-existent code
>(no longer in newer version). We are usually up against it at this point
>because of our inefficient approach to releasing artifacts, so instead of
>chasing down the developer to fix it, we keep the dependency at the older
>version. Usually this isn't a problem because, even though the old code
>is required at compile time, it is never invoked (called) at run-time, so
>that application doesn't blow up. It will be a problem one day, and I am
>trying to prevent that from happening.
>
>Our approach to this problem has been to take the responsibility out of
>the developers' hands. We've implemented a bunch of properties (using
>groupid.artifactid-[dev/prod]-version naming convention) in our
>organization POM, and set the values there. We then replaced the
>hard-coded values in each of the project pom files with the appropriate
>-dev or -prod property. So essentially, we can change the version for
>each project that is used as a dependency from a single location. Another
>reason we opted for this approach is because it simplifies the release
>process for us. We simply validate that the property values have the
>correct values for this release in one place (org pom), and then we
>update the project pom files by replacing -dev for -prod prior to
>releasing them.
>
>This introduces its own set of problems. For example, every project
>references a particular version (2.0) of our organization POM as its
>parent. When we update the values for one or more of these properties (in
>preparation for release) in the org POM, we can either (a) leave the
>version of the org pom the same (2.0) or (b) increment the version (2.1,
>2.2, 2.3, etc.). Option 'a' seems problematic because I believe
>developers will not automatically pull down the latest version of org pom
>2.0 since it is supposed to be immutable. They'll need to purge it from
>their local repository after each release, or update the pom.xml (pull
>down latest changes from SVN), and run make install against it. Option
>'b' is good because developers would automatically pull down the newer
>version of the org pom when they ran a build on any of the projects
>referencing it. The tradeoff is that we would have to update X project
>pom files to refer to the new version of the org pom. X is sometimes 20
>or 30. It would be more manageable if we could use a property for the org
>pom version, but I am not sure we could define that property in the org
>pom...seems like a chicken and egg problem. I wonder if there is a
>plug-in that allows maven to check for the latest version of an artifact
>if the version is omitted.
>
>Can you please share what is considered the best practice approach for
>this?
>Thanks,
>Rob
>
>


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

Re: Jar file not in maven

[Lyons, Roy]

Actually...  if I may.  I might be able to end this a little easier by
providing some information which I think has been left out of the
conversation so far.

The newest release of Nexus does have something to help you in pinpointing
a particular revision.  Granted, you will need to do a little work in
order to make it do what you are looking for...

Nexus now comes with a functionality of metadata.  You can attach whatever
metadata you want to an artifact - and you can query Nexus to get the
information later on.

The work that would come into play is that you would need to have a plugin
created which would detect the current scm revision and then attach that
as metadata to the uploaded artifacts.  If I recall correctly, someone had
written a blog posting about wanting a plugin that would batch-upload to
nexus for snapshot in the same way that it batch-uploads for a staging
repository.  I feel that the addition of this kind of metadata would be an
excellent feature to add to such a tool...

Anyhow, in order to make this work a little bit of work has to take place
which will make using attributes in maven repositories an easier thing to
use.  


Thanks,

Roy Lyons
Senior Configuration Engineer






On 1/30/13 2:18 PM, "Joachim Durchholz"  wrote:

>Am 30.01.2013 10:20, schrieb Stephen Connolly:
>>> Now that's just crazy, who would roll back an SVN repo and overwrite a
>>> revision past?
>>> I'd download from http://repo/tags/1.3.2. And if that's borked, the
>>> maintainer will provide http://repo/tags/1.3.3 and I'll update the pom
>>>to
>>> download from there.
>>
>> STOP RIGHT THERE.
>
>Hey. Why are you screaming?
>
>> Once you publish 1.3.3 to a (pseudo) Maven repository you can NEVER
>>edit it
>> / update it / modify it
>
>Yeah. Not happenin. 1.3.3 is at http://repo/tags/1.3.3. 1.3.4 at
>http://repo/tags/1.3.4.
>
>And yes it's an SVN repo, not a Maven repo. I have mentioned that time
>and again, it's even in the quote above.
>I don't know why you're even talking about a Maven pseudo repo. I'm
>talking about importing from a non-Maven repo; somehow you've been
>missing that point entirely.
>
>> The reason is that anyone who downloaded that using Maven will *NEVER*
>>get
>> the modified version because release versions have the (Maven) contract
>> that they never change. That is a core principal of Maven.
>>
>> If you don't get that, well, quite frankly I will just plain stop.
>
>Well, I got that about five messages ago, and have expressed it in at
>least two of the three replies I wrote after that.
>
>If you don't get that, well, quite frankly I'll recommend you improve
>your reading skills.
>
>Really. It's been quite a while since I tried talking to somebody who
>was so intent on *not listening*, constantly reinterpreting what I wrote
>into something entirely different.
>
>>> The pom could carry a version of 1.3-SNAPSHOT (if it's not considered
>>> stable yet),
>>
>> If the pom is at a GAV of foo:bar:1.3.3 and that pom actually contains a
>> version of 1.3-SNAPSHOT, sorry all hell will break loose when Maven
>>tries
>> to unfurl that mess.
>
>Well it isn't, of course.
>However, you're more intent on pinpointing errors in my thinking rather
>than in looking for ways that the intention might work, but then you'd -
>heaven forbid! - *understand* what I'm saying, and you'd have to admit
>I'm not just a misguided idiot.
>
>>> or one of 1.3.2 which would then be updated to 1.3.3 and deployed to a
>>>new
>>> maven coordinate (and really be a different pom, in the latter case)
>>>
>>>
 but
>>>
 Maven is not going to re-download it because Maven repo is write once,
 delete never, modify never for all release artifacts.

 No SCM matches those semantics, so you will have an impedance
mismatch.

>>>
>>> ???
>>> SCMs don't modify revisions once they are published.
>>> That's generally considered extremely dubious practice.
>>
>> I am talking about people pushing modifications with a new revision.
>
>Yes, as am I.
>How is that breaking Maven's assumptions? I wouldn't download anything
>from an SVN HEAD (except for a Maven SNAPSHOT, where it's acceptable as
>far as I understand things).
>
> > There
>> are loads of examples of people using a Subversion repository as a Maven
>> repository... on the basis that a Maven repository is just a directory
>> layout convention and a Subversion repository published over http(s) is
>> just a set of directories.
>
>I am *so not* going to do that. The Maven docs are simply too thing to
>even attempt such a thing. I'd probably need to scrape the proper
>directory layout from the sources, and risk breakage whenever a new
>version of Maven comes out.
>
>> The most famous one was java.net2
>>
>> Where, because it was a Subversion repository, you had people *reverting
>> commits and publishing new builds of the same version*
>
>If you use revision numbers (e.g. r23462) as coordinates, that's
>technically impossible. (Unless somebody unloads the entire history 

Re: Upload arbitrary directories to maven repositories

[Lyons, Roy]

Perhaps this is what you want?

http://mojo.codehaus.org/wagon-maven-plugin/merge-maven-repos-mojo.html



On 1/16/13 11:00 AM, "Kuehlert, Burkhard"
 wrote:

>Hi,
>
>is it possible to upload arbitrary directories or filesets to maven
>repositories ? It seems to me, that artifacts have to be of type file and
>not directory.
>Is that right?
>
>Thanks
>Burkhard Kuehlert
>
>WINCOR NIXDORF International GmbH
>Sitz der Gesellschaft: Paderborn
>Registergericht Paderborn HRB 3507
>Geschäftsführer: Eckard Heidloff (Vorsitzender), Dr. Jürgen Wunram
>Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
>Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr.
>DE44477193
>
>Diese E-Mail enthält vertrauliche Informationen.
>Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
>erhalten haben,
>informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
>Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist
>nicht gestattet.
>
>This e-mail may contain confidential information.
>If you are not the intended recipient (or have received this e-mail in
>error)
>please notify the sender immediately and destroy this e-mail.
>Any unauthorised copying, disclosure or distribution of the material in
>this e-mail is strictly forbidden.


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

Re: maven-release-plugin and git

[Lyons, Roy]

This is what you want


http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-the
-poms-not-at-the-top







On 12/5/12 4:36 PM, "Coarr, Matt"  wrote:

>Hello,
>
>I'm able to use "mvn release:prepare" but I run into an issue when I use
>"mvn release:perform".
>
>My problem is that my scm data in my pom points to our git repository
>which contains multiple projects.
>
>Is there a way to tell release:perform to only checkout or export a
>subdirectory of the repository?  (This would be easy with svn ‹ you just
>specify the url to the project directory in svn).
>
>Another option would be to checkout the whole repository, but somehow
>tell the forked maven process to build from a certain subdirectory.
>
>I guess a third option would be maybe I'm doing something wrong with my
>tagging/branching in git.  Is it possible to tag just a subdirectory in
>git and then maybe I need to "git checkout mybranch"??
>
>Let me know if you have any ideas!
>
>Thanks!
>Matt


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

Re: Getting profile settings values in a Java class

[Lyons, Roy]

Taken from 
http://maven.apache.org/guides/introduction/introduction-to-profiles.html

Deactivating a profile

Starting with Maven 2.0.10, one or more profiles can be deactivated using
the command line by prefixing their identifier with either the character
'!' or '-' as shown below:

mvn groupId:artifactId:goal -P !profile-1,!profile-2

This can be used to deactivate profiles marked as activeByDefault or
profiles that would otherwise be activated through their activation config.



so you need to do ' -P vm,!dev '





On 12/5/12 7:53 AM, "Javix"  wrote:

>I'm back with a strange behaviour. In a separate project which has
>profiles
>defined exactly the same way, passing the option '-P [profile name]' does
>not work at all, Maven continues to use the default activated profile.
>Here
>is a working example:
>
>http://maven.apache.org/POM/4.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>   4.0.0
>
>   com.spot.sncf
>   java_cukes
>   1.0-SNAPSHOT
>   jar
>
>   java_cukes
>   http://maven.apache.org
>   
>   
>   
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   2.3.2
>   
>   1.6
>   1.6
>   
>   
>
>   
>   org.apache.maven.plugins
>   maven-site-plugin
>   3.1
>   
>   
>   
>   
> org.apache.maven.plugins
>   
> maven-surefire-report-plugin
>   2.4.3
>   
>   
>   
>   
>   
>
>   
>   
>   src/main/resources
>   true
>   
>   
>   
>   
>   
>   
> UTF-8
>   
> UTF-8g>
>   
>
>   
>   
>   dev
>   
>   true
>   
>   
>   http://toto.com
>   
>   
>   
>   vm
>   
>   http://yoyo.com
>   
>   
>   
>
>
>   
>   
>   info.cukes
>   cucumber-picocontainer
>   1.1.1
>   test
>   
>   
>   info.cukes
>   cucumber-junit
>   1.1.1
>   test
>   
>   
>   junit
>   junit
>   4.10
>   test
>   
>   
>
>
>
>Executing
>
>mvn test
>
>will run the activated default profile (vm).
>
>Running
>
>mvn test -P vm
>
>will run the 'vm' prifile.
>
>Using the same but in a different project runs only the activated profile,
>no matter if I pass -P option.
>Any idea?
>
>Thanks
>
>
>
>
>
>--
>View this message in context:
>http://maven.40175.n5.nabble.com/Getting-profile-settings-values-in-a-Java
>-class-tp5722740p5735821.html
>Sent from the Maven - Users mailing list archive at Nabble.com.
>
>-
>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

Re: Private Repository Server + Maven Standard Repos

[Lyons, Roy]

You may find it easier to simply ask them to run a "mvn
dependency:go-offline" before going home, and to run their builds with
"--offline" while disconnected from the corporate network.


Thanks,

Roy Lyons
Senior Configuration Engineer







On 10/30/12 1:05 PM, "Gintas"  wrote:

>Hello guys,
>
>I'm having some issues with repo configuration. What I want to set-up is
>that:
>
>1. Maven would primarily use company's internal maven Repository for
>PUBLIC
>and PRIVATE libraries. Settings to be used at the office.
>2. Maven would use DEFAULT Maven repos when internal company's repo is not
>available. 
>Settings to be used when working at home. Maven would be able to download
>all PUBLIC libraries and get private libs from m2 folder.
>
>Is it possible to achieve this?
>
>Currently i have a profile defined under m2 with my private repo settings,
>but when it fails, Maven does not fall back to the default settings.
>
>Thanks in advance!
>
>Gintas.
>
>
>
>--
>View this message in context:
>http://maven.40175.n5.nabble.com/Private-Repository-Server-Maven-Standard-
>Repos-tp5728854.html
>Sent from the Maven - Users mailing list archive at Nabble.com.
>
>-
>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

Re: Maven Central broken? (was: Broken link for avalon)

[Lyons, Roy]

Yet another reason to use a caching repository manager...  You never know
when a repository out of your control can be on the fritz...


Thanks,

Roy Lyons
Senior Configuration Engineer



On 10/17/12 10:33 AM, "Martin Hoeller"  wrote:

>On 17 Okt 2012, Anders Hammar wrote:
>
>> https://issues.sonatype.org/browse/MVNCENTRAL
>
>Thanks. Reported it as https://issues.sonatype.org/browse/MVNCENTRAL-252
>
>> It works for me though (Sweden/Europe) so I guess it depends on which
>> central mirror you're directed to.
>
>Maybe. I'm located in Austria/Europe.
>
>- martin


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

Re: HOWTO: git-flow + maven-release-plugin + multi-module maven project w/parent pom as sibling to other modules?

[Lyons, Roy]

Correct.  On the pom where it defines all of the s.  in your case,
you would specify "production/app/pom.xml" if that¹s where this exists.



Thanks,

Roy Lyons
Senior Configuration Engineer



On 10/16/12 9:14 AM, "Matthew Adams"  wrote:

>Stephen,
>
>It sounds like what you're referring to is what I've been calling the
>"root" pom in my example, as opposed to what I've been calling the
>"parent" pom.
>
>The root pom is sitting at the top of the maven project
>(production/app relative to the git repo root directory), and
>basically only contains the  section.  The parent pom is
>sitting in production/app/parent-pom, and it's the pom that all of
>other modules are inheriting from (via their  sections).
>
>So you're saying to invoke "mvn release:prepare release:perform" on my
>root pom, not my parent pom, right?
>
>-matthew
>
>On Tue, Oct 16, 2012 at 2:38 AM, Stephen Connolly
> wrote:
>> On 15 October 2012 22:24, Matthew Adams  wrote:
>>
>>> One of the questions in my original post was actually "which pom
>>> should you execute 'mvn release:prepare release:perform' on?".  I'm
>>> guessing, based on nothing else but intuition, that it's the parent
>>> pom, not the root pom, so, in my case,
>>
>>
>> It should be the pom that aggregates everything you want to release. IOW
>> the aggregation root of all projects that are to be released. That need
>>not
>> be the parent pom if aggregation does not follow inheritance
>>
>>
>>> I suppose that'd be
>>> production/app/parent-pom/pom.xml.  However, that SO question was just
>>> for poms that aren't at the repo root; my question is a touch more
>>> specific than that, what with a parent-pom as a sibling to its
>>> children, which is a common use case, IME.
>>>
>>> Thoughts?
>>>
>>> On Mon, Oct 15, 2012 at 4:03 PM, Lyons, Roy 
>>> wrote:
>>> >
>>> > The way I am reading this, you need to add it to the pom which you
>>>are
>>> > invoking maven on.  So whichever pom file you are running maven
>>>against
>>> > for the call to the release plugin (not talking the submodules here,
>>>but
>>> > the pom closest to the invocation of maven), add this in -- basically
>>> > pointing to the relative path (relative to your git repository root)
>>>to
>>> > the pom you are running maven against.
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Roy Lyons
>>> > Senior Configuration Engineer
>>> >
>>> >
>>> > On 10/15/12 3:31 PM, "Matthew Adams"  wrote:
>>> >
>>> >>Thanks, Roy.  The answer you pointed me to says "add the following to
>>> >>your build/plugins section", but it doesn't tell me **which** pom to
>>> >>add to...leaving me confused.  Can you clarify for the answerer
>>>(since
>>> >>I don't have enough repu points to comment on the answer & ask for
>>> >>clarification).
>>> >>
>>> >>On Mon, Oct 15, 2012 at 2:49 PM, Lyons, Roy 
>>> >>wrote:
>>> >>> I had remembered looking this up and thought I would share my
>>>finding
>>> >>>with
>>> >>> you:
>>> >>>
>>> >>>
>>> 
>>>http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-
>>>t
>>> >>>he
>>> >>> -poms-not-at-the-top
>>> >>>
>>> >>> Basically theres a
>>> >>> 
>>> >>> subdir/pom.xml
>>> >>> 
>>> >>> That you need to define as part of your plugin definition.
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> Thanks,
>>> >>>
>>> >>> Roy Lyons
>>> >>> Senior Configuration Engineer
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 10/15/12 1:17 PM, "Matthew Adams" 
>>>wrote:
>>> >>>
>>> >>>>Hi all,
>>> >>>>
>>> >>>>I'm trying to visualize how to perform a release properly, given
>>>that
>>> 

Re: HOWTO: git-flow + maven-release-plugin + multi-module maven project w/parent pom as sibling to other modules?

[Lyons, Roy]

The way I am reading this, you need to add it to the pom which you are
invoking maven on.  So whichever pom file you are running maven against
for the call to the release plugin (not talking the submodules here, but
the pom closest to the invocation of maven), add this in -- basically
pointing to the relative path (relative to your git repository root) to
the pom you are running maven against.


Thanks,

Roy Lyons
Senior Configuration Engineer


On 10/15/12 3:31 PM, "Matthew Adams"  wrote:

>Thanks, Roy.  The answer you pointed me to says "add the following to
>your build/plugins section", but it doesn't tell me **which** pom to
>add to...leaving me confused.  Can you clarify for the answerer (since
>I don't have enough repu points to comment on the answer & ask for
>clarification).
>
>On Mon, Oct 15, 2012 at 2:49 PM, Lyons, Roy 
>wrote:
>> I had remembered looking this up and thought I would share my finding
>>with
>> you:
>> 
>>http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-t
>>he
>> -poms-not-at-the-top
>>
>> Basically theres a
>> 
>> subdir/pom.xml
>> 
>> That you need to define as part of your plugin definition.
>>
>>
>>
>>
>> Thanks,
>>
>> Roy Lyons
>> Senior Configuration Engineer
>>
>>
>>
>>
>>
>>
>> On 10/15/12 1:17 PM, "Matthew Adams"  wrote:
>>
>>>Hi all,
>>>
>>>I'm trying to visualize how to perform a release properly, given that
>>>
>>>* I'm using git with git-flow on a
>>>* multi-module maven project with a
>>>* parent pom module that is located in a sibling directory to the
>>>other modules which are
>>>* located in a directory other than the git repository's root directory.
>>>
>>>The docs for using the maven-release-plugin seem a little sparse when
>>>used with multi-module maven projects like mine.  For example, my git
>>>repo's root directory (the one containing the .git directory) has a
>>>subdirectory called "production/app".  The multi-module root pom is at
>>>production/app/pom.xml, and looks like this:
>>>
>>>http://maven.apache.org/POM/4.0.0";
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>>http://maven.apache.org/maven-v4_0_0.xsd";>
>>>   4.0.0
>>>   org.example
>>>   app-root
>>>   pom
>>>   0.2.0.BUILD-SNAPSHOT
>>>   Application Multimodule Root POM
>>>
>>>   
>>>   parent-pom
>>>   test-support
>>>   support
>>>   domain
>>>   dto
>>>   service
>>>   rest
>>>   web
>>>   
>>>
>>>
>>>Note that it basically only contains  entries, one of which is
>>>the parent-pom module, which is in the directory
>>>production/app/parent-pom (the parent pom is then
>>>production/app/parent-pom/pom.xml) and all of the other modules in the
>>>project, then, declare the relative path to the parent pom to be
>>>"../parent-pom/pom.xml".  Now, I'm trying
>>>to use the maven-release-plugin with this project along with git-flow.
>>> I'm planning on using the following settings, which I've seen in
>>>several posts on using it with git-flow:
>>>
>>>   
>>>
>>>org.apache.maven.plugins
>>>
>>>maven-release-plugin
>>>   2.3.2
>>>   
>>>
>>>true
>>>
>>>true
>>>   false
>>>
>>>v@{project.version}
>>>   
>>>   
>>>
>>>* Into which pom do I put this plugin configuration:  the root pom
>>>(production/app/pom.xml) or the parent pom
>>>(production/app/parent-pom/pom.xml)?
>>>* Into which root or parent's section should this  section be
>>>placed:   or ?
>>>
>>>Here's my  section (I'm using "xxx" & "yyy" protect the innocent):
>>>
>>>   
>>>   
>>>scm:git:

Re: HOWTO: git-flow + maven-release-plugin + multi-module maven project w/parent pom as sibling to other modules?

[Lyons, Roy]

I had remembered looking this up and thought I would share my finding with
you:
http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-the
-poms-not-at-the-top

Basically theres a

subdir/pom.xml

That you need to define as part of your plugin definition.




Thanks,

Roy Lyons
Senior Configuration Engineer






On 10/15/12 1:17 PM, "Matthew Adams"  wrote:

>Hi all,
>
>I'm trying to visualize how to perform a release properly, given that
>
>* I'm using git with git-flow on a
>* multi-module maven project with a
>* parent pom module that is located in a sibling directory to the
>other modules which are
>* located in a directory other than the git repository's root directory.
>
>The docs for using the maven-release-plugin seem a little sparse when
>used with multi-module maven projects like mine.  For example, my git
>repo's root directory (the one containing the .git directory) has a
>subdirectory called "production/app".  The multi-module root pom is at
>production/app/pom.xml, and looks like this:
>
>http://maven.apache.org/POM/4.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>http://maven.apache.org/maven-v4_0_0.xsd";>
>   4.0.0
>   org.example
>   app-root
>   pom
>   0.2.0.BUILD-SNAPSHOT
>   Application Multimodule Root POM
>
>   
>   parent-pom
>   test-support
>   support
>   domain
>   dto
>   service
>   rest
>   web
>   
>
>
>Note that it basically only contains  entries, one of which is
>the parent-pom module, which is in the directory
>production/app/parent-pom (the parent pom is then
>production/app/parent-pom/pom.xml) and all of the other modules in the
>project, then, declare the relative path to the parent pom to be
>"../parent-pom/pom.xml".  Now, I'm trying
>to use the maven-release-plugin with this project along with git-flow.
> I'm planning on using the following settings, which I've seen in
>several posts on using it with git-flow:
>
>   
>   org.apache.maven.plugins
>   maven-release-plugin
>   2.3.2
>   
>   
> true
>   true
>   false
>   
> v@{project.version}
>   
>   
>
>* Into which pom do I put this plugin configuration:  the root pom
>(production/app/pom.xml) or the parent pom
>(production/app/parent-pom/pom.xml)?
>* Into which root or parent's section should this  section be
>placed:   or ?
>
>Here's my  section (I'm using "xxx" & "yyy" protect the innocent):
>
>   
>   scm:git:g...@github.com:xxx/yyy.git
>   
> scm:git:g...@github.com:xxx/yyy.gittion>
>   https://github.com/xxx/yyy
>   
>
>* How do I tell maven that this maven project is located off of the
>repo's root, in production/app? Do I use
>"scm:git:g...@github.com:xxx/yyy.git/production/app" or something else?
>
>* Into which pom do I put the  section:  the root pom, the parent
>pom, or in each module's pom?  If the root pom, do I use
>"scm:git:g...@github.com:xxx/yyy.git/production/app"?  If the parent
>pom, do I use 
>"scm:git:g...@github.com:xxx/yyy.git/production/app/parent-pom"?
> If in each module's pom, do I use
>"scm:git:g...@github.com:xxx/yyy.git/production/app/module_name"?
>
>* Into which pom to I put the  section:  the
>root pom, the parent pom, or each module's pom?
>
>* After I issue my "git flow release start 0.2.0.RELEASE" in my dev
>branch's production/app directory, in which directory (after switching
>to the release/0.2.0.RELEASE branch, of course) do I issue the command
>"mvn release:prepare release:perform":  production/app or
>production/app/parent-pom?
>
>--
>mailto:matt...@matthewadams.me
>skype:matthewadams12
>googletalk:matt...@matthewadams.me
>http://matthewadams.me
>http://www.linkedin.com/in/matthewadams
>
>-
>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

Re: Antw: Re: Re: Corrupted Assembly, when using a type:pom dependency

[Lyons, Roy]

Hah.  I spoke too soon.  I just thought about it and using shade would be
very dangerous because of possible class collisions.  Let me modify my
statement to never do this for anything that will ever be consumed by
another build.


Thanks,

Roy Lyons
Senior Configuration Engineer






On 10/12/12 2:06 PM, "Lyons, Roy"  wrote:

>John,
>
>That is a pretty good observation.
>
>My assumption (even though assuming anything can be fatal) is that the
>resulting project was a top tier application -- one which would not be
>subjected to being consumed by another application as a library.
>
>I am in full agreement that this is not a valid method when generating
>anything other than an artifact which is not consumed by a subsequent
>maven build.
>
>The best way to achieve the same results in an item which is consumed
>would be to have a separate project which would consume the original
>artifact, and use the shade plugin to unpack it and the additional
>dependencies into a completely different artifact (artifactId being
>different).  This is of course also assuming that you aren't changing the
>compilation of your classes based on the presence of these other
>libraries.
>
>
>Thanks,
>
>Roy Lyons
>Senior Configuration Engineer
>
>
>
>
>
>
>On 10/12/12 12:25 PM, "John Kramer"  wrote:
>
>>Not that I'm an expert, but I thought the rule of thumb was this:
>>
>>Never use profiles in such a way that different profiles build different
>>versions of artifacts with the same id.
>>
>>I always restricted my use of profiles to activities such as deployment
>>or
>>testing that didn't affect the artifacts being built.
>>
>>This use seems like it could lead to some dependency issues.
>>
>>If you disagree, please explain your reasoning.
>>
>>
>>John Kramer
>>email: jkra...@mojiva.com
>>mobile: 314.435.2370
>>skype: kramer.mojiva
>>twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech>
>>0xCAFEBABE0032
>>
>>
>>
>>
>>
>>
>>
>>On 10/12/12 10:37 AM, "Lyons, Roy"  wrote:
>>
>>>I would approach this as an acceptable use of a profile.  Make a profile
>>>with these dependencies defined.  If you activate the profile, they will
>>>all be added.  If you don¹t activate the profile, none will be added.
>>>
>>>This should fix your issues.
>>>
>>>Thanks,
>>>
>>>Roy Lyons
>>>Senior Configuration Engineer
>>>
>>>From: Stefan Rademacher mailto:rademac...@hhla.de>>
>>>Reply-To: "'users@maven. org'"
>>>mailto:users@maven.apache.org>>
>>>Date: Friday, October 12, 2012 6:52 AM
>>>To: "'users@maven. org'"
>>>mailto:users@maven.apache.org>>
>>>Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom
>>>dependency
>>>
>>>Hi Curtis,
>>>
>>>yes, that's right. I want do declare a set of dependencies, which always
>>>must be used "all" or "none". That why I encapsulate those dependencies
>>>in a separate pom and reference it with a type=pom dependency.
>>>
>>>I didn't know about this scope "import" before and found your link very
>>>infomative! Thanks!
>>>Unfortunately, the assembly still gets corrupted, as soon as I have a
>>>type=pom dependency in my configuration... with or without scope=import.
>>>
>>>Any other suggestions?
>>>
>>>Regards,
>>>Stefan
>>>
>>>
>>>>>> Curtis Rueden mailto:ctrue...@wisc.edu>>
>>>>>>11.10.2012 18:05 >>>
>>>Hi Stefan,
>>>
>>>> 
>>>>de.hhla.test
>>>>test.assembly.core
>>>>0.0.1-SNAPSHOT
>>>>pom
>>>> 
>>>
>>>Personally, I have never used a dependency of type pom. But according to
>>>the Maven docs, the main use case for it is as a shortcut to import a
>>>group
>>>of dependencies transitively from that POM project. But in that case,
>>>you
>>>would declare that dependency with scope "import"; see:
>>>
>>>http://maven.apache.org/guides/introduction/introduction-to-dependency-m
>>>e
>>>c
>>>hanism.html#Importing_Dependencies
>>>
>>>Is that what you are trying to do? If you use scope import, does the
>>>problem go away? If scope import is not what you want, I am curious w

Re: Antw: Re: Re: Corrupted Assembly, when using a type:pom dependency

[Lyons, Roy]

John,

That is a pretty good observation.

My assumption (even though assuming anything can be fatal) is that the
resulting project was a top tier application -- one which would not be
subjected to being consumed by another application as a library.

I am in full agreement that this is not a valid method when generating
anything other than an artifact which is not consumed by a subsequent
maven build.

The best way to achieve the same results in an item which is consumed
would be to have a separate project which would consume the original
artifact, and use the shade plugin to unpack it and the additional
dependencies into a completely different artifact (artifactId being
different).  This is of course also assuming that you aren't changing the
compilation of your classes based on the presence of these other libraries.


Thanks,

Roy Lyons
Senior Configuration Engineer






On 10/12/12 12:25 PM, "John Kramer"  wrote:

>Not that I'm an expert, but I thought the rule of thumb was this:
>
>Never use profiles in such a way that different profiles build different
>versions of artifacts with the same id.
>
>I always restricted my use of profiles to activities such as deployment or
>testing that didn't affect the artifacts being built.
>
>This use seems like it could lead to some dependency issues.
>
>If you disagree, please explain your reasoning.
>
>
>John Kramer
>email: jkra...@mojiva.com
>mobile: 314.435.2370
>skype: kramer.mojiva
>twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech>
>0xCAFEBABE0032
>
>
>
>
>
>
>
>On 10/12/12 10:37 AM, "Lyons, Roy"  wrote:
>
>>I would approach this as an acceptable use of a profile.  Make a profile
>>with these dependencies defined.  If you activate the profile, they will
>>all be added.  If you don¹t activate the profile, none will be added.
>>
>>This should fix your issues.
>>
>>Thanks,
>>
>>Roy Lyons
>>Senior Configuration Engineer
>>
>>From: Stefan Rademacher mailto:rademac...@hhla.de>>
>>Reply-To: "'users@maven. org'"
>>mailto:users@maven.apache.org>>
>>Date: Friday, October 12, 2012 6:52 AM
>>To: "'users@maven. org'"
>>mailto:users@maven.apache.org>>
>>Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom
>>dependency
>>
>>Hi Curtis,
>>
>>yes, that's right. I want do declare a set of dependencies, which always
>>must be used "all" or "none". That why I encapsulate those dependencies
>>in a separate pom and reference it with a type=pom dependency.
>>
>>I didn't know about this scope "import" before and found your link very
>>infomative! Thanks!
>>Unfortunately, the assembly still gets corrupted, as soon as I have a
>>type=pom dependency in my configuration... with or without scope=import.
>>
>>Any other suggestions?
>>
>>Regards,
>>Stefan
>>
>>
>>>>> Curtis Rueden mailto:ctrue...@wisc.edu>>
>>>>>11.10.2012 18:05 >>>
>>Hi Stefan,
>>
>>> 
>>>de.hhla.test
>>>test.assembly.core
>>>0.0.1-SNAPSHOT
>>>pom
>>> 
>>
>>Personally, I have never used a dependency of type pom. But according to
>>the Maven docs, the main use case for it is as a shortcut to import a
>>group
>>of dependencies transitively from that POM project. But in that case, you
>>would declare that dependency with scope "import"; see:
>>
>>http://maven.apache.org/guides/introduction/introduction-to-dependency-me
>>c
>>hanism.html#Importing_Dependencies
>>
>>Is that what you are trying to do? If you use scope import, does the
>>problem go away? If scope import is not what you want, I am curious why
>>you
>>are using a dependency of type pom.
>>
>>Regards,
>>Curtis
>>
>>
>>On Thu, Oct 11, 2012 at 3:53 AM, Stefan Rademacher
>>mailto:rademac...@hhla.de>>wrote:
>>
>>>  Sorry, I didn't notice, that my original posting wasn't attached to my
>>> last email.
>>> Here is again, what I asked few weeks ago. Can anyone help me with
>>>this?
>>> ---
>>>
>>> Hi all,
>>>
>>> I want to create an assembly, using a moduleSet. With the following
>>> (simplified) example, I select a certain artifact, define the output
>>>directory
>>> and provide a naming pattern.
>>> 
>>>  distribution
>>>  
>>>   zip
>>>  
>>>  
>>>  

Re: Antw: Re: Re: Corrupted Assembly, when using a type:pom dependency

[Lyons, Roy]

I would approach this as an acceptable use of a profile.  Make a profile with 
these dependencies defined.  If you activate the profile, they will all be 
added.  If you don’t activate the profile, none will be added.

This should fix your issues.

Thanks,

Roy Lyons
Senior Configuration Engineer

From: Stefan Rademacher mailto:rademac...@hhla.de>>
Reply-To: "'users@maven. org'" 
mailto:users@maven.apache.org>>
Date: Friday, October 12, 2012 6:52 AM
To: "'users@maven. org'" mailto:users@maven.apache.org>>
Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom dependency

Hi Curtis,

yes, that's right. I want do declare a set of dependencies, which always must 
be used "all" or "none". That why I encapsulate those dependencies in a 
separate pom and reference it with a type=pom dependency.

I didn't know about this scope "import" before and found your link very 
infomative! Thanks!
Unfortunately, the assembly still gets corrupted, as soon as I have a type=pom 
dependency in my configuration... with or without scope=import.

Any other suggestions?

Regards,
Stefan


>>> Curtis Rueden mailto:ctrue...@wisc.edu>> 11.10.2012 
>>> 18:05 >>>
Hi Stefan,

> 
>de.hhla.test
>test.assembly.core
>0.0.1-SNAPSHOT
>pom
> 

Personally, I have never used a dependency of type pom. But according to
the Maven docs, the main use case for it is as a shortcut to import a group
of dependencies transitively from that POM project. But in that case, you
would declare that dependency with scope "import"; see:

http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies

Is that what you are trying to do? If you use scope import, does the
problem go away? If scope import is not what you want, I am curious why you
are using a dependency of type pom.

Regards,
Curtis


On Thu, Oct 11, 2012 at 3:53 AM, Stefan Rademacher 
mailto:rademac...@hhla.de>>wrote:

>  Sorry, I didn't notice, that my original posting wasn't attached to my
> last email.
> Here is again, what I asked few weeks ago. Can anyone help me with this?
> ---
>
> Hi all,
>
> I want to create an assembly, using a moduleSet. With the following
> (simplified) example, I select a certain artifact, define the output directory
> and provide a naming pattern.
> 
>  distribution
>  
>   zip
>  
>  
>   
>true
>
> ${artifact.groupId}:test.assembly.server
>
>
> .
> false
> ${module.artifactId}.${module.extension}
> 
>
>   
>  
> 
>
> The module I select in this assembly.xml contains one dependency:
> 
>de.hhla.test
>test.assembly.core
>0.0.1-SNAPSHOT
>pom
> 
>
> The resulting assembly is unusable, as soon as the following two conditions 
> are
> true:
> - The module has a dependency with pom
> AND
> - The outputDirectory of the moduleSet is "."
>
> In this case, the resulting assembly (e. g. zip file) looks like this:
> ZIP
> |
> |-- ""
> ||-- test.assembly.server.jar
> |
> |-- test.assembly.server.jar
>
> The file "test.assembly.server.jar", which is contained in that directory with
> an empty name, is not actually a jar, but the POM of the dependency, which I
> specified with pom !!! That's totally weird, isn't it?
> Extracting this zip structure leads to a corrupted "test.assembly.server.jar",
> because the first jar in the dir with no name (which actually is an XML file)
> overwrites the correct jar at the actual root level of the zip file.
>
> Another hint is this debug output of the assembly plugin:
> [DEBUG] Adding file: C:\Dokumente und
> Einstellungen\\.m2\repository\de\hhla\test\test.assembly.core\0.0.1-SNAPSHOT\test.assembly.core-0.0.1-SNAPSHOT.pom
>  to archive location: TEST_0.0.1-SNAPSHOT//test.assembly.server.jar
> (Please notice the two slashes in the destination path.)
>
> Is this already a known issue or should I file a bug?
>
> Thanks and best regards,
> Stefan
>
> ---
>
> Thanks and best regards
> Stefan
>
>
> >>> tobias maslowski 
> >>> mailto:tobiasmaslow...@gmail.com>> 08.10.2012 
> >>> 11:45 >>>
>
> You probably should provide some information about your problem, like what
> you tried to do, the setup ...
>
> Anyway there are a few issues in the tracker, maybe you stumbled accross
> http://jira.codehaus.org/browse/MASSEMBLY-609?
>
> 2012/10/8 Stefan Rademacher mailto:rademac...@hhla.de>>
>
> >  Hi,
> >
> > is there nobody, who can confirm, if this is a known issue?
> >
> > Thanks,
> > Stefan
> >
> >
> > -
> > 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.or

Re: How to optimize maven dependencies to get better performance?

[Lyons, Roy]

Ooh.  More on the original topic (big old trees and having to sort through
stuff)

mvn dependency:tree -Dverbose=true

That¹s a powerful tool in your pruning crusade.  Putting verbose on will
tell you about the decisions maven made in deciding which dependency
versions to keep and where they came from.  Using this, you could also
figure out what items you might like to put in  block of
dependency declarations.  Most likely you aren't using everything in your
dependencies and you can figure out what fat you want to trimŠ

Of course, this is the most intrusive and time consuming optionŠ  but I
suspect that it will yield the greatest results.




Thanks,

Roy Lyons
Senior Configuration Engineer
(312) 648-3659 [w] 
(773) 551-8335 [c] 
roy.ly...@cmegroup.com

CME Group 
20 S. Wacker Drive
Chicago, Illinois 60606
Self Help 
https://wiki.chicago.cme.com/confluence/display/CM/Home






On 10/11/12 9:02 AM, "Barrie Treloar"  wrote:

>On Thu, Oct 11, 2012 at 6:57 PM, Wang, Simon 
>wrote:
>> Hi, Barrie,
>>Ask a stupid question about enforcer plugin.
>> I added enforcer plugin into project pom like this:
>> 
>> 
>>org.apache.maven.plugins
>> 
>>maven-enforcer-plugin
>> 1.1.1
>> 
>>   
>> enforce
>> 
>> 
>> 
>>
>> 
>> 
>> 
>>   enforce
>> 
>>   
>> 
>> 
>
>I'm not sure, your example is a copy-and-paste of
>http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
>
>However I would normally expect things to be case sensitive and the
>rule index (http://maven.apache.org/enforcer/enforcer-rules/index.html)
>uses "dependencyConvergence"
>
>You could try that instead.
>If it does work, I'd file a bug against the enforcer documentation.
>
>Also, I dont expect dependencyConvergence to actually help you with
>performance.
>Try running maven with -X and then scouring the copious amount of
>output to see what it is doing and where it is spending its time.
>Always measure before you optimize.
>
>-
>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

Re: How to optimize maven dependencies to get better performance?

[Lyons, Roy]

Tim's idea could workŠ  however, I could say that a shorter term fix might
help (if you aren't already on maven 3.0.4)

--snip--
With 3.0.4, the default wagon http(s) is now the HttpClient based on
Apache Http Client 4.1.2 .
 There is now a http connection pooling to prevent reopening http(s) to
remote server for each requests. This pool feature is configurable with
some parameters [4].
This new defaut wagon comes with some default configuration:

* http(s) connection pool: default to 20.
* readTimeout: default to 180ms (~30 minutes) (see section Read time
out below)
* default Preemptive Authentication.
--/snip--

Taken from http://maven.apache.org/guides/mini/guide-http-settings.html


I do see a couple of obstacles to Tim's ideas.  Most of them are related
to bad practices which are regularly evangelized as good ideasŠ  like
using variables for version names (I am looking at you Atlassian
[http://blogs.atlassian.com/2010/09/bamboo_jira_release_management_plugin_p
art_2/]).



Another snippet (I didn't read this before this discussion thread and it
enlightened me)


--snip--

Maven Wagon HTTPThis project is an implementation of Wagon provider for
HTTP access. It uses Apache HttpComponents client
 as lower level layer.
It enables Maven to use remote repositories stored in HTTP servers.

FeaturesPrior
 to version 2.0, a pooled http connection manager is used. The pooled
feature is enabled by default, you can configure it trough the following
 system properties :

* maven.wagon.http.pool = true/false (default true), enable/disable the
pooled mechanism.
* maven.wagon.httpconnectionManager.maxPerRoute = integer (default : 20),
maximum number of http(s) connection per destination.
* maven.wagon.httpconnectionManager.maxTotal = integer (default 40),
maximum number of htp(s) connection.
* maven.wagon.http.ssl.easy = true/false (default true), enable/disable
use of easy ssl check for user generated certificates.
* maven.wagon.http.ssl.allowall
 = true/false (default true), enable/disable match of the server's X.509
 certificate. If disable, a browser like check will be used.
* maven.wagon.http.ssl.ignore.validity.dates = true/false (default true),
ignore issue with certifactes dates.
* maven.wagon.rto=time in ms (default 180) read time out.

--/snip--

Taken from 
http://maven.apache.org/wagon/wagon-providers/wagon-http/index.html



AlsoŠ  You could start your day out with mvn dependency:go-offline -- and
then add --offline for subsequent compilations throughout the day.



Thanks,

Roy Lyons
Senior Configuration Engineer




On 10/11/12 4:01 AM, "Martin Höller"  wrote:

>On 11 Okt 2012, Wang, Simon wrote:
>
>> Hi, Barrie,
>>That's really helpful!
>> 
>>Even I have local cache, it also takes about 2 mins to resolve
>>dependencies.
>>Also it seems maven still will talk with remote maven server even I
>>have local cache.
>
>You could try "mvn -o" and see if this helps.
>
>And maybe this blog post of Tim O'Brien might be of interest:
>http://www.sonatype.com/people/2012/08/download-it-all-at-once-a-maven-ide
>a/
>
>hth,
>- martin


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

Re: how to deploy maven 1 artifact into artifactory

[Lyons, Roy]

I know that in Nexus, you would create a "virtual repository" specifying
the Maven1-to-Maven2 provider, and it would translate the items into a
Maven2 format (which is still in use for Maven3).  You would then want to
create a repository group which would combine the items from that new
virtual repository and the current maven2 hosted repository type for use
in resolving artifacts.  I would go a step further and add any external
repositories (via proxy repository type) to this repository group, and
force resolution through that group with a  in your settings.xml.

Yes, that was a Nexus-based response -- but I suspect Artifactory has
similar functionality.  Your mileage may vary.



Thanks,

Roy Lyons
Senior Configuration Engineer





On 10/3/12 10:49 AM, "ktaeter"  wrote:

>unfortunately I have 500 maven 1 projects to migrate, therefore I have to
>live with maven 1 and maven 3 projects simultaneously for now.
>
>
>
>--
>View this message in context:
>http://maven.40175.n5.nabble.com/how-to-deploy-maven-1-artifact-into-artif
>actory-tp5724683p5724768.html
>Sent from the Maven - Users mailing list archive at Nabble.com.
>
>-
>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

include tests jar, exclude main artifact

[Lyons, Roy]

I have an interesting use case to pick everyone's brain on…

A developer came to my desk and said "We want to allow other teams to put a 
dependency on our tests jar for their test scope, but don't want to allow them 
access to the non-tests jars in our project."

At first I said "No problem.  I can easily do that with patterns in Nexus."  
And then I started thinking deep thoughts…

The tests jar has its pom defined as the same pom which was used for the main 
jar, and so all the transitive dependencies will come from that pom when you 
reference the tests jar.

I can hear many of you thinking "Well yeah.  That’s what dependency exclusions 
are for."  However, it can be much more complicated than that.  As far as I 
know, you cannot exclude a groupId/artifactId combination and then include the 
same groupId/artifactId with a classifier (in this case "tests") being named.  
(please correct me if that is false)

Also, since I am writing this anyhow…  Will the declaration of a dependency on 
the tests jar cause a transitive inclusion of the regular jar?  My gut Maven 
knowledge tells me "no" but I want to make sure of this before I start shooting 
myself in the foot.



Thanks,

Roy Lyons

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

Re: Ability to use latest plugin snapshot from maven 3 command line

[Lyons, Roy]

Extremely easy fix for that:

http://maven.apache.org/guides/introduction/introduction-to-plugin-resoluti
on.html

-- snip --

For clarity, the following are the three ways to reference a mojo
from the command line. These will all result in the clean mojo of the
maven-clean-plugin being invoked:
  mvn org.apache.maven.plugins:maven-clean-plugin:2.0:clean
  mvn org.apache.maven.plugins:maven-clean-plugin:clean
  mvn clean:clean




-- /snip --

So just reference your snapshot plugin with:
 mvn :::

That's it.




On 9/27/12 10:35 AM, "Dan Tran"  wrote:

>Hello
>
>Back in Maven 2, when executing  a plugin goal from command line,
>Maven always tries to look for latest version and its snapshot
>
>In Maven 3, this capability disappear, Maven only looks for latest
>released version.
>
>Would it possible to turn it on from command line?
>
>I fully understand the benefit of predictability. However, it becomes
>very inconvenient to cut the plugin release while still testing.
>and we cannt use maven2 because the plugin itself uses maven 3 api ( ie
>aether )
>
>Is there already a request for this?
>
>Big thanks
>
>-D
>
>-
>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

Re: Invoking Maven goals outside a project directory structure

[Lyons, Roy]

I have a possible interesting suggestion for you.  Scm plugin
bootstrapping.

http://maven.apache.org/scm/maven-scm-plugin/bootstrap-mojo.html


Given a pom with an scm section defined, you could bootstrap its entire
repo down and the perform the tasks you are trying to accomplish.

http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-po
m.html


Right now there isn't a great way to do the effective pom -- I know I have
tried to do so as well, and ended up just cloning down the repositories I
needed.





On 9/21/12 11:26 AM, "Curtis Rueden"  wrote:

>Hi everyone,
>
>I was wondering whether there is a way to utilize certain useful Maven
>goals when outside of a particular Maven project's actual source directory
>structure. For example, I would like to ask Maven for the effective POM of
>an installed artifact.
>
>Why? Because I want to know the classpath fragment (all necessary JARs
>from
>the local repository cache) for a given GAV.
>
>I started writing a script to compute it manually. Current work in
>progress
>is here:
>https://gist.github.com/3762396
>
>However, it would be nice to lean on the Maven command line tool to do the
>heavy lifting, rather than doing recursive parsing like my script does
>now.
>I definitely don't want to reinvent all the goodness that Maven provides.
>Right now, there are many things the script can't deal with:
>   1) downloading missing artifacts from a remote repository;
>   2) computing an effective POM for the project;
>   3) resolving properties properly from that effective POM...
>Just to name a few at the tip of the iceberg.
>
>It seems like many Maven goals (e.g., help:effective-pom, dependency:list,
>dependency:tree) would make sense to invoke with respect to a given Maven
>project, when outside of that project's actual source folder.
>
>Is this at all possible? Or any alternative suggestion to achieve my goals
>here?
>
>Thanks,
>Curtis


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

Re: How to make release:prepare ask for password?

[Lyons, Roy]

If this is related to your Nexus authentication, 2.1 is an awesome release
with regards to this.  They introduced an API token authentication
approach, so that you won't be handing over the keys to the castle if
someone compromises your API token password.

We are using it with encryption as well, and are storing the master
settings-security.xml in a secure location, pointing to it with a
relocation tag in the HOME/.m2/settings-security.xml file.

If you are already in linux, simply chmod go-rwx it.

Also, use SSL as a connection, so that the password cannot be sniffed.
Again, that might be overkill since it isn't a system account password.

If this is for your SCM, you may want to consider git instead of svn.  You
can use an ssh key with that, and will allow you to connect without
revealing a password.


Thanks,

Roy Lyons
Senior Configuration Engineer
(312) 648-3659 [w] 
(773) 551-8335 [c] 
roy.ly...@cmegroup.com

CME Group 
20 S. Wacker Drive
Chicago, Illinois 60606
Self Help 
https://wiki.chicago.cme.com/confluence/display/CM/Home
 






On 9/21/12 7:54 AM, "Anders Hammar"  wrote:

>Feature requests are good. Patches are even better. :-)
>
>/Anders
>
>On Fri, Sep 21, 2012 at 1:29 PM, Magne Nordtveit  wrote:
>> That puts us back to having the password stored in some bash history
>>file, in plain text... Looks like I might have to put in for a feature
>>request. Just have to figure out where to put it :-P
>>
>> Magne
>>
>> -Original Message-
>> From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
>>Behalf Of Anders Hammar
>> Sent: Friday, 21 September, 2012 12:58
>> To: Maven Users List
>> Subject: Re: How to make release:prepare ask for password?
>>
>> Don't think you can have it ask for the password, but you can provide
>>it as a Java (system) property on command-line.
>> mvn release:prepare -Dpassword=blabla
>>
>> /Anders
>>
>> On Fri, Sep 21, 2012 at 11:52 AM, Magne Nordtveit  wrote:
>>> How can I make the release-plugin ask for a password when it needs it,
>>>rather than having to either a) provide it as a property when building,
>>>or b) putting it in a settings.xml file or equivalent. I don't like the
>>>fact that I have to have the password stored in a batch history file
>>>somewhere, or in a settings.xml file everybody knows where is...
>>>
>>> Thanks,
>>> --
>>> Magne Nordtveit
>>> Senior Systems Engineer
>>>
>>> Mobile: +47 957 20 187
>>>
>>> Offshore Simulator Centre AS
>>> Visiting address: Borgundvegen 340, N-6009, Aalesund, Norway
>>> Postal address:   Borgundvegen 340, N-6009, Aalesund, Norway
>>> www.offsim.no
>>>
>>
>> -
>> 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
>


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

Re: Getting profile settings values in a Java class

[Lyons, Roy]

I would like to say that there is definitely a better way.  You *could*
continue to use maven for filtering your properties, but I wouldn't use it
as part of the build of the application.
 
If you are simply using scp or other similarly crude method of deployment
(meaning you are just deploying as a file transfer), I would say that you
could set up a maven project on the server side which handle the
deployment.  You can setup a pom.xml with all of the maven objects as
dependencies (including your jar/war/ear files you already built) and then
use the assembly plugin to create a staged application environment
including a variable replacement on template-ized external property files
which your application can reference (the replacement being done by
filtering within assembly directives).  As a matter of fact, I would argue
that this could be all stuffed in a git repository and your installation
could be done with:

ssh $servername "git clone -b $branchname $gitprojecturl \; cd 
$targetdir
\; mvn -P $envname dependency:resolve assembly:assembly \; $startscript"

Or

ssh $servername "cd $targetdir \; $stopscript \; git clean -f \; git 
pull
origin \; mvn -P $envname dependency:resolve assembly:assembly \;
$startscript"

Long and short is that it is still possible to do what you want with
maven, but not inside of the box you are thinking in.  As a configuration
engineer, I know that environment specific properties (and usually other
properties too) should always be stored in files external to your jar.
"The Maven Way" will tell you to make re-usable stuff.  Your deployment
artifacts are no exception.  Don't force a rebuild when a property has to
change.  Your QA folks will be extra thankful since the jar/war/ear will
maintain a constant md5sum that they can use to justify not performing
full regression tests.

Disclaimer:  We are using a highly sophisticated and expensive tool for
deployments and can't use this method due to auditing needs.  However we
still have our tool perform a post-process interpolation of variables
within config files based on environment to achieve a similar end result.

Also, to prevent a flame-war -- I am presenting this as a feasible
alternative way to use maven for the purpose of filtering properties based
on a profile being set (the original poster's intention) that will perhaps
help the original poster think outside of the box to achieve their goals.

Thanks,

Roy




On 9/20/12 4:48 PM, "Zak Mc Kracken"  wrote:

>OK, I understand that in general it should be considered an
>anti-pattern. Despite that, in my organisation we deploy a number of
>internal tools on a couple of servers and with different configurations
>(dev, test, production). To achieve this we do what it was originally
>asked in this thread.
>
>I think the only way for that with the assistance of Maven is how it was
>suggested: use property files with ${placeholders} and tell Maven to
>resolve them, then define the corresponding properties in the profiles.
>This is an example:
>
>   http://github.com/EBIBioSamples/core_model/blob/master/pom.xml
>
>Note that the  and  sections have:
>true and then there are parametrised files like:
>
>http://github.com/EBIBioSamples/core_model/blob/master/src/test/resources/
>hibernate.properties
>
>In this particular module, things are set only to change the
>configuration that JUnit tests receive, but the trick works the same way
>if you have another property file in src/main/resources. Yes, it makes
>the final jar dependent on Maven profiles and on a particular
>environment, however it may be acceptable in certain situations (like
>ours).
>
>Marco.
>
>
>On 20/09/2012 21:16, Ron Wheeler wrote:
>> Maven is not the place to set run-time information.
>> Trying to use profiles in this way, will only lead you to heartache
>> and a dislike of Maven.
>>
>> http://blog.artifact-software.com/tech/?p=150
>> http://blog.artifact-software.com/tech/?p=58
>>
>> Ron
>>
>>
>
>
>
>-
>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

RE: Is the release plugin intended to be run manually?

[Lyons, Roy]

My recommendation is to keep your release builds manual or cron based.  You can 
add a "release:prepare -DdryRun=true -B" to your CI if you want to make sure 
that a future release build will work properly.  The main issue with using 
source change detection in a CI job and running the release plugin is that you 
will end up in an infinite loop, and your version will be "over 9000" by 
morning.

My personal belief is that release builds should not be happening every hour or 
every few minutes.  That's what snapshots are for.  Whether you are agile or 
waterfall, the goal is to always produce a release build on code that has 
working features (or so developers claim anyhow).  Basically, that's a piece 
which is best left to either human eyes, or to a set of automated testing 
scripts which could also kick off a release build upon success.  Perhaps I take 
it a little too seriously -- but that's my job as an SCM engineer :) 

Thanks,

Roy

-Original Message-
From: KARR, DAVID [mailto:dk0...@att.com] 
Sent: Tuesday, September 11, 2012 11:02 AM
To: Maven Users List
Subject: Is the release plugin intended to be run manually?

I noticed a comment in 
http://www.dzone.com/links/r/continuous_delivery_using_maven_3.html about not 
using the release plugin because it checks in POMs after updating versions, 
which isn't suited to a continuous delivery pipeline.  Is the release plugin 
intended to be run manually, and not part of an automated build?

The documentation for the plugin doesn't really address this question.

-
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

RE: alternative deploy strategy

[Lyons, Roy]

one word of caution here.  I've employed rsync in the past.  the only issue is 
maven-metadata.xml is not fixed up (and you have to exclude it from your rsync 
or you will royally mess it up)...  you also have a bunch of other crap files 
which aren't used in the main repo...

**/* .lastUpdated
**/ _maven.repositories


It also only uses sha1 in local repo, and so md5 will be missing.


Just some friendly advice...  It may be more pain than you are thinking.

-Original Message-
From: Max Spring [mailto:m2spr...@springdot.org] 
Sent: Wednesday, August 29, 2012 10:15 AM
To: users@maven.apache.org
Subject: Re: alternative deploy strategy

I'm thinking of rsync'ing the "local-remote" repository to the machine running 
Nexus.
Then I'd do the deploy via HTTP (localhost) which would avoid the wire.

So, I'd preserve the auth.

Keeping the copy of the "local-remote" repository around on the Nexus machine 
would improve the next build's rsync.

-Max


On 08/28/2012 11:52 PM, Anders Hammar wrote:
> If you want to bypass the Repo manager (normally what happens if you 
> don't deploy through HTTP) you will also bypass authentication, 
> authorization, and other good stuff that a repo manager helps you 
> with. Don't do that!
>
> /Anders
>
> On Wed, Aug 29, 2012 at 6:17 AM, Max Spring  wrote:
>> I do use Nexus for the group repositories.
>> Using Nexus also locally defeats the purpose.
>> The deploy to a file://... repo gives me the performance I'm looking for.
>>
>> Nexus Pro's staging feature would give me what I want, but I'd still 
>> have to transport via HTTP.
>>
>> -Max
>>
>>
>>
>> On 08/28/2012 09:05 PM, Manfred Moser wrote:
>>>
>>> On Tue, August 28, 2012 4:26 pm, Max Spring wrote:

 To speed up my large Maven build I'm thinking of using a "local-remote"
 repository sitting on the local file system.

 1) build would start with a wiped local-remote repository
 2) build's deploys into the local-remote repository
 3) if build finished successfully, artifacts in the local-remote 
 repository get deployed into the real remote group repository.

 (The benefits would be that nothing gets deployed until the build 
 succeeds and the build result is available sooner.)

 Are there tools which would help with 3) ?
 I've looked into the Nexus Command Line Tools [1], but they don't 
 do what I want.

 Alternatively I could write my own using the Maven API, I suppose.
>>>
>>>
>>> Why not just use a local deployment of Nexus?
>>>
>>> manfred
>>>
>>>
>>> 
>>> - 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
>
>


-
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

RE: alternative deploy strategy

[Lyons, Roy]

Actually, the command line tools for nexus do this.  I guess the only gotcha is 
that it works with staging, and staging is only valid with release deployments, 
not with snapshot.

Perhaps they can enhance the tool to do pseudo-staging for snapshots as well, 
with automatic promotion to the full snapshot repository.

*nudge nudge Sonatype*

-Original Message-
From: Max Spring [mailto:m2spr...@springdot.org] 
Sent: Tuesday, August 28, 2012 6:27 PM
To: users@maven.apache.org
Subject: alternative deploy strategy

To speed up my large Maven build I'm thinking of using a "local-remote" 
repository sitting on the local file system.

1) build would start with a wiped local-remote repository
2) build's deploys into the local-remote repository
3) if build finished successfully, artifacts in the local-remote repository get 
deployed into the real remote group repository.

(The benefits would be that nothing gets deployed until the build succeeds and 
the build result is available sooner.)

Are there tools which would help with 3) ?
I've looked into the Nexus Command Line Tools [1], but they don't do what I 
want.

Alternatively I could write my own using the Maven API, I suppose.

-Max

[1] https://docs.sonatype.com/display/SPRTNXOSS/Nexus+Command+Line+Tools

-
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

RE: Using ant-contrib in ant based plugin development

[Lyons, Roy]

I would like to report back that indeed the issue was with needing to use the 
xml instead.  I had thought for sure that it was an issue with the classpath 
within maven, but I have a feeling that ant-contrib was already in my path when 
it came to running ant externally -- and this is why I saw a different behavior.

I am not sure if anyone on this list has write-access to the how-to on writing 
maven plugins with ant...  but if there is, can you update the page to include 
a section on using ant-contrib functions and include this information to allow 
those who come after me to not have to bang their head for a few hours?  The 
functions included in contrib would be very useful for moving official build 
scripts into a plugin method instead (which is what I plan to do here).

Thanks,

Roy

-Original Message-
From: Lyons, Roy 
Sent: Monday, July 30, 2012 9:23 AM
To: Maven Users List
Subject: RE: Using ant-contrib in ant based plugin development

Excellent!  That explains why I had so much trouble with the 'for' task.  I 
will give this method a try with the xml instead.  I very much appreciate your 
reply on this.

-Original Message-
From: Aurélien Girardeau [mailto:aurelien.girard...@gmail.com]
Sent: Saturday, July 28, 2012 8:26 AM
To: Maven Users List; manf...@mosabuam.com
Subject: Re: Using ant-contrib in ant based plugin development

Hi Roy,

I use ant-contrib in a Ant-based Mojo and it works fine for me.

Here is my ant-contrib declaration in my build.xml:







Note that antcontrib.properties doesn't contain "for" declaration. Prefer 
antlib.xml.

and here is my mojos.xml for ${ant-contrib-jar} parameter:


ant-contrib-jar
ant-contrib-jar
true
${ant-contrib-jar}
${project.build.directory}/antcontrib/
ant-contrib-1.0b3.jar
java.lang.String



Note that I don't use a antcontrib artifact deployed in my local repo, but a 
antcontrib jar installed in my ${project.build.directory}. I dont't think it 
change anything.

Did you try an echo on your  ${settings.localRepository}  or  ${user.home} to 
check they are correcty loaded at Maven runtime?

Hope it can help,

Aurélien


2012/7/27 Manfred Moser 

> Why are you not implementing your plugin in Java or even Groovy?
>
>
> http://www.sonatype.com/books/mcookbook/reference/writing-plugins-alte
> rnative-sect-writing-groovy.html
>
> Shell script seems like a bad idea to me if you want it to run everywhere..
>
> manfred
>
> On Fri, July 27, 2012 2:26 pm, Lyons, Roy wrote:
> > Update:
> >
> > Not hearing anything made me give up on pure ant...  I was able to 
> > get things working with the  task, and just
> embedding
> > kornshell.  That, of course, defeats the usual idea of a plugin 
> > since it is platform specific...  but later on, I can add in support 
> > for windows
> by
> > doing a similar shellscript directive with cmd based on the osfamily
> task.
> >  Interestingly, I was able to use both of those from ant-contrib...  but
> > not  >
> > Odd.
> >
> >
> > I am still interested in possibilities of using ant in its pure 
> > form, so any responses to this thread are still welcome.
> >
> > Thanks,
> >
> > Roy
> > 
> > From: Lyons, Roy
> > Sent: Friday, July 27, 2012 12:16 PM
> > To: Maven Users List
> > Subject: RE: Using ant-contrib in ant based plugin development
> >
> > my webmail made me login again, and I didnt see part of my message 
> > was missing.  here is the full thing:
> >
> >
> > Maven User List,
> >
> > I waited in sending to this list until after I had exhausted my 
> > other resources, including google searching, documentation, and 
> > experimentation of my own.
> >
> > As such, I hope that your collective minds can take on this challenge.
> >
> >
> > So here is the problem:
> >
> > [INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging]
> > (aggregator-style)
> > [INFO]
> > 
> >  [INFO] [cme-packaging:cme-packaging {execution: default-cli}]
> >
> > cmepackage:
> >  [echo] We are in UNIX
> > [INFO]
> > 
> > 
> > [ERROR] BUILD ERROR
> > [INFO]
> > 
> >  [INFO] Failed to execute: Executing Ant script: 
> > package.build.xml
> > [cmepackage]: Failed to execute.
> >
> > Could not create task or type of type: for.
> >
> > Ant could not find the task or a class this 

RE: Using ant-contrib in ant based plugin development

[Lyons, Roy]

Excellent!  That explains why I had so much trouble with the 'for' task.  I 
will give this method a try with the xml instead.  I very much appreciate your 
reply on this.

-Original Message-
From: Aurélien Girardeau [mailto:aurelien.girard...@gmail.com] 
Sent: Saturday, July 28, 2012 8:26 AM
To: Maven Users List; manf...@mosabuam.com
Subject: Re: Using ant-contrib in ant based plugin development

Hi Roy,

I use ant-contrib in a Ant-based Mojo and it works fine for me.

Here is my ant-contrib declaration in my build.xml:







Note that antcontrib.properties doesn't contain "for" declaration. Prefer 
antlib.xml.

and here is my mojos.xml for ${ant-contrib-jar} parameter:


ant-contrib-jar
ant-contrib-jar
true
${ant-contrib-jar}
${project.build.directory}/antcontrib/
ant-contrib-1.0b3.jar
java.lang.String



Note that I don't use a antcontrib artifact deployed in my local repo, but a 
antcontrib jar installed in my ${project.build.directory}. I dont't think it 
change anything.

Did you try an echo on your  ${settings.localRepository}  or  ${user.home} to 
check they are correcty loaded at Maven runtime?

Hope it can help,

Aurélien


2012/7/27 Manfred Moser 

> Why are you not implementing your plugin in Java or even Groovy?
>
>
> http://www.sonatype.com/books/mcookbook/reference/writing-plugins-alte
> rnative-sect-writing-groovy.html
>
> Shell script seems like a bad idea to me if you want it to run everywhere..
>
> manfred
>
> On Fri, July 27, 2012 2:26 pm, Lyons, Roy wrote:
> > Update:
> >
> > Not hearing anything made me give up on pure ant...  I was able to 
> > get things working with the  task, and just
> embedding
> > kornshell.  That, of course, defeats the usual idea of a plugin 
> > since it is platform specific...  but later on, I can add in support 
> > for windows
> by
> > doing a similar shellscript directive with cmd based on the osfamily
> task.
> >  Interestingly, I was able to use both of those from ant-contrib...  but
> > not  >
> > Odd.
> >
> >
> > I am still interested in possibilities of using ant in its pure 
> > form, so any responses to this thread are still welcome.
> >
> > Thanks,
> >
> > Roy
> > 
> > From: Lyons, Roy
> > Sent: Friday, July 27, 2012 12:16 PM
> > To: Maven Users List
> > Subject: RE: Using ant-contrib in ant based plugin development
> >
> > my webmail made me login again, and I didnt see part of my message 
> > was missing.  here is the full thing:
> >
> >
> > Maven User List,
> >
> > I waited in sending to this list until after I had exhausted my 
> > other resources, including google searching, documentation, and 
> > experimentation of my own.
> >
> > As such, I hope that your collective minds can take on this challenge.
> >
> >
> > So here is the problem:
> >
> > [INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging]
> > (aggregator-style)
> > [INFO]
> > 
> >  [INFO] [cme-packaging:cme-packaging {execution: default-cli}]
> >
> > cmepackage:
> >  [echo] We are in UNIX
> > [INFO]
> > 
> > 
> > [ERROR] BUILD ERROR
> > [INFO]
> > 
> >  [INFO] Failed to execute: Executing Ant script: 
> > package.build.xml
> > [cmepackage]: Failed to execute.
> >
> > Could not create task or type of type: for.
> >
> > Ant could not find the task or a class this task relies upon.
> >
> > This is common and has a number of causes; the usual solutions are 
> > to read the manual pages then download and install needed JAR files, 
> > or fix the build file:
> >  - You have misspelt 'for'.
> >Fix: check your spelling.
> >  - The task needs an external JAR file to execute
> >  and this is not found at the right place in the classpath.
> >
> >
> > What is extremely interesting to me is the fact that it can use the 
> > task definition for "osfamily", but not for the "for" task.  Also of 
> > interest to me is the fact that I can use this script with "ant -f" 
> > without a problem.
> >
> > Before I get suggestions that I should use java instead, I need to
> confess
> > that I am only now just learning java.  My job in configuration
> management
> > uses a whole

RE: Using ant-contrib in ant based plugin development

[Lyons, Roy]

Update:

Not hearing anything made me give up on pure ant...  I was able to get things 
working with the  task, and just embedding kornshell.  
That, of course, defeats the usual idea of a plugin since it is platform 
specific...  but later on, I can add in support for windows by doing a similar 
shellscript directive with cmd based on the osfamily task.  Interestingly, I 
was able to use both of those from ant-contrib...  but not 

  
maven-plugin-plugin
2.5


  
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.5
  
  
 ant-contrib
 ant-contrib
 1.0b3



I also placed a dependency on ant-contrib in my pom's dependencies section.

my build xml has this in it...  as you can see, I was experimenting with 
different methods of forcing it to find the items.  I have nothing special in 
mojos xml.  Perhaps that is where my issue is?













I had the most luck so far with







From: Lyons, Roy
Sent: Friday, July 27, 2012 12:15 PM
To: Maven Users List
Subject: Using ant-contrib in ant based plugin development

Maven User List,

I waited in sending to this list until after I had exhausted my other 
resources, including google searching, documentation, and experimentation of my 
own.

As such, I hope that your collective minds can take on this challenge.


So here is the problem:

[INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging] 
(aggregator-style)
[INFO] 
[INFO] [cme-packaging:cme-packaging {execution: default-cli}]

cmepackage:
 [echo] We are in UNIX
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to execute: Executing Ant script: package.build.xml [cmepackage]: 
Failed to execute.

Could not create task or type of type: for.

Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
 - You have misspelt 'for'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
 and this is not found at the right place in the classpath.


What is extremely interesting to me is the fact that it can use the task 
definition for







Here is my declaration in my pom:



  
maven-plugin-plugin
2.5


  
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.5
  
  
 ant-contrib
 ant-contrib
 1.0b3



I also placed a dependency on ant-contrib in my pom's dependencies section.

my build xml has this in it...  as you can see, I was experimenting with 
different methods of forcing it to find the items.  I have nothing special in 
mojos xml.  Perhaps that is where my issue is?













I had the most luck so far with






-
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

RE: Using ant-contrib in ant based plugin development

[Lyons, Roy]

my webmail made me login again, and I didnt see part of my message was missing. 
 here is the full thing:


Maven User List,

I waited in sending to this list until after I had exhausted my other 
resources, including google searching, documentation, and experimentation of my 
own.

As such, I hope that your collective minds can take on this challenge.


So here is the problem:

[INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging] 
(aggregator-style)
[INFO] 
[INFO] [cme-packaging:cme-packaging {execution: default-cli}]

cmepackage:
 [echo] We are in UNIX
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to execute: Executing Ant script: package.build.xml [cmepackage]: 
Failed to execute.

Could not create task or type of type: for.

Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual 
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file: 
 - You have misspelt 'for'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
 and this is not found at the right place in the classpath.


What is extremely interesting to me is the fact that it can use the task 
definition for "osfamily", but not for the "for" task.  Also of interest to me 
is the fact that I can use this script with "ant -f" without a problem.  

Before I get suggestions that I should use java instead, I need to confess that 
I am only now just learning java.  My job in configuration management uses a 
whole lot more in perl and ksh than anything...

Also, my research showed lots of ways to cope with it in antrun, with an inline 
script -- but that won't do so much for me as I am trying to make a plugin...

Here is my declaration in my pom:



  
maven-plugin-plugin
2.5


  
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.5
  
  
 ant-contrib
 ant-contrib
 1.0b3



I also placed a dependency on ant-contrib in my pom's dependencies section.

my build xml has this in it...  as you can see, I was experimenting with 
different methods of forcing it to find the items.  I have nothing special in 
mojos xml.  Perhaps that is where my issue is?













I had the most luck so far with 






________
From: Lyons, Roy
Sent: Friday, July 27, 2012 12:15 PM
To: Maven Users List
Subject: Using ant-contrib in ant based plugin development

Maven User List,

I waited in sending to this list until after I had exhausted my other 
resources, including google searching, documentation, and experimentation of my 
own.

As such, I hope that your collective minds can take on this challenge.


So here is the problem:

[INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging] 
(aggregator-style)
[INFO] 
[INFO] [cme-packaging:cme-packaging {execution: default-cli}]

cmepackage:
 [echo] We are in UNIX
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to execute: Executing Ant script: package.build.xml [cmepackage]: 
Failed to execute.

Could not create task or type of type: for.

Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
 - You have misspelt 'for'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
 and this is not found at the right place in the classpath.


What is extremely interesting to me is the fact that it can use the task 
definition for







Here is my declaration in my pom:



  
maven-plugin-plugin
2.5


  
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.5
  
  
 ant-contrib
 ant-contrib
 1.0b3



I also placed a dependency on ant-contrib in my pom's dependencies section.

my build xml has this in it...  as you can see, I was experimenting with 
different methods of forcing it to find the items.  I have nothing special in 
mojos xml.  Perhaps that is where my issue is?













I had the most luck so far with






---

Using ant-contrib in ant based plugin development

[Lyons, Roy]

Maven User List,

I waited in sending to this list until after I had exhausted my other 
resources, including google searching, documentation, and experimentation of my 
own.

As such, I hope that your collective minds can take on this challenge.


So here is the problem:

[INFO]task-segment: [com.cme.plugins:cme-packaging:cme-packaging] 
(aggregator-style)
[INFO] 
[INFO] [cme-packaging:cme-packaging {execution: default-cli}]

cmepackage:
 [echo] We are in UNIX
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to execute: Executing Ant script: package.build.xml [cmepackage]: 
Failed to execute.

Could not create task or type of type: for.

Ant could not find the task or a class this task relies upon.

This is common and has a number of causes; the usual 
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file: 
 - You have misspelt 'for'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
 and this is not found at the right place in the classpath.


What is extremely interesting to me is the fact that it can use the task 
definition for 







Here is my declaration in my pom:



  
maven-plugin-plugin
2.5


  
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.5
  
  
 ant-contrib
 ant-contrib
 1.0b3



I also placed a dependency on ant-contrib in my pom's dependencies section.

my build xml has this in it...  as you can see, I was experimenting with 
different methods of forcing it to find the items.  I have nothing special in 
mojos xml.  Perhaps that is where my issue is?













I had the most luck so far with 






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

RE: archetype prompting

[Lyons, Roy]

I found my answer finally.  Sharing with everyone here since noone else seems 
to know the answer on this list...

http://jira.codehaus.org/browse/ARCHETYPE-359

" The build fails in the integration-test phase, because the new property is 
not assigned in the src/test/resources/projects/basic/archetype.properties.
Simply adding a line to that file with an assignment for the new property will 
solvve this."

-Original Message-----
From: Lyons, Roy 
Sent: Thursday, June 28, 2012 4:58 PM
To: users@maven.apache.org
Subject: archetype prompting

Archetype gurus...

So I want to prompt for the following in my own in-house archetype:

parentGroupId
parentArtifactId
parentVersion
scmUrl

Based on performing rigorous RTFM and blog reading I came upon the method to do 
so.

$ tail src/main/resources/META\-INF/maven/archetype\-metadata.xml
  

  
  




  


Right.

So it seems to be confused about when it happens to be required.  I need it to 
be required when I execute the archetype:create -- not when I am performing a 
"mvn install" on the archetype project...

[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO]
Archetype IT 'basic' failed: Missing required properties in 
archetype.properties: scmUrl, parentGroupId, parentArtifactId, parentVersion 
[INFO] 
[INFO] For more information, run Maven with the -e switch [INFO] 


Without these required properties defined in the descriptor, it packages and 
installs real nicely...  And the resulting archtype works as expected (minus 
these extra prompts).


What could I possibly be overlooking or doing wrong?

Thanks,

Roy

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

archetype prompting

[Lyons, Roy]

Archetype gurus...

So I want to prompt for the following in my own in-house archetype:

parentGroupId
parentArtifactId
parentVersion
scmUrl

Based on performing rigorous RTFM and blog reading I came upon the method to do 
so.

$ tail src/main/resources/META\-INF/maven/archetype\-metadata.xml
  

  
  




  


Right.

So it seems to be confused about when it happens to be required.  I need it to 
be required when I execute the archetype:create -- not when I am performing a 
"mvn install" on the archetype project...

[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO]
Archetype IT 'basic' failed: Missing required properties in 
archetype.properties: scmUrl, parentGroupId, parentArtifactId, parentVersion
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 

Without these required properties defined in the descriptor, it packages and 
installs real nicely...  And the resulting archtype works as expected (minus 
these extra prompts).


What could I possibly be overlooking or doing wrong?

Thanks,

Roy

RE: purpose of pom.xml in the META-INF

[Lyons, Roy]

I have one idea of where this can be useful.  The pom can contain SCM 
information to allow someone who is troubleshooting an issue know where they 
can find the source code for the object.

I am sure that there are other reasons, mainly surrounding use of other 
metadata or tags which are contained within the pom...  but mostly for 
troubleshooting or identification purposes (especially when the version isn't 
known because someone used finalName).

-Original Message-
From: chad.da...@emc.com [mailto:chad.da...@emc.com] 
Sent: Thursday, June 28, 2012 2:11 PM
To: users@maven.apache.org
Subject: purpose of pom.xml in the META-INF

What are the general reasons for having the pom deployed into the META-INF?  
What kind of use cases leverage this info?

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

RE: Maven for Software Installation

[Lyons, Roy]

I have thought about this as well, but thinking that perhaps a pom with 
dependencies and then using the assembly plugin to create the final 
distribution would be good...  but then I realized that it would be better in a 
corporate environment to provide them in a single tested archive or deployment 
automation package.

You can be certain in such an environment that nothing has been tampered with, 
and that all required pieces are actually available.

The idea is neat, but it has certain traceability drawbacks.  I've been a 
little more interested in the possibility of deployment using 'git'.  The ease 
of upgrade with a fetch/pull and rollback with a simple checkout command has me 
intrigued.  It also has great anti-tamper and traceability built in.

I suppose all of these concerns are more pertinent in a server deployment 
environment as opposed to an end user client application experience though...  
I can see where a distribution through maven would be nice there, although if 
that trended you may find that central repos wouldn't be too happy about an 
uptick in traffic.


-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] 
Sent: Thursday, June 21, 2012 2:54 PM
To: Maven Users List
Subject: Maven for Software Installation

I have brought this notion up before, but I have been thinking about it a bit 
more.

Would it make sense to use Maven technology for software deployment and 
installation as opposed to just builds?

What I envision is something akin to the Global Assembly Cache in .NET, but for 
Maven artifacts. In particular, the local repository would act like a GAC, but 
you might want to separate a system local repository from the user local 
repositories.

The basic idea is that when deploying/installing software you would not bundle 
all your dependent artifact into your installer, rather you would just bundle 
their coordinates. At installation time you would install the Maven Installer 
if it was not already there, then your installer would work in conjunction with 
the Maven Installer. Basically the Maven Installer subsystem would simply 
download the dependent artifacts from Maven Central or elsewhere, and put them 
in the System Repository (similar to the GAC).

One benefit of this is that if you have a lot of software that all reference 
the same artifacts, they can share copies. Other benefits would be similar to 
those for the .NET GAC, although hopefully we could avoid some of the problems 
the GAC has created.

Another benefit is that installers could be smaller by not bundling in 
dependent artifacts. Installation could be faster in that if dependent 
artifacts are already in the System Repository downloading and installing them 
is unnecessary.

So am I just thinking crazy, or is there any potential benefit to this idea?

Cheers, Eric

-
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

RE: How does one mirror a maven repository?

[Lyons, Roy]

I think that this is what you might be looking for...

http://mojo.codehaus.org/wagon-maven-plugin/merge-maven-repos-mojo.html 

-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com] 
Sent: Friday, June 01, 2012 12:48 PM
To: Maven Users List
Subject: Re: How does one mirror a maven repository?

On a related note, is it safe to use both Nexus set up with a proxy repository, 
and to also have rsync routinely updating it?

Phillip

On Fri, Jun 1, 2012 at 10:53 AM, Phillip Hellewell  wrote:

> Hi,
>
> Our company would like to mirror our Maven repository at a remote 
> location.  Currently we've been using Nexus with a proxy repository, 
> which works as advertised, but we really need a full mirror not just 
> an on-demand cache.
>
> The reason we need it to be a full mirror is because we want it to 
> also serve as a remote backup, should our central repository have a 
> catastrophic disk failure.
>
> Is there any way to accomplish this with Nexus, or do I just need to 
> set up rsync or something?
>
> Thanks,
> Phillip
>

RE: How to do a release build in Maven?

[Lyons, Roy]

I believe that this is the documentation that you are looking for.

http://maven.apache.org/plugins/maven-release-plugin/



-Original Message-
From: hujirong [mailto:jirong...@gmail.com] 
Sent: Tuesday, May 22, 2012 10:15 AM
To: users@maven.apache.org
Subject: How to do a release build in Maven?

Hi

I just set up a snapshot build, I call it continuously build. A "mvn deploy"
will upload the snapshot to the Nexus repository. Here is the project
pom.xml:

com.nbfg.max.wesb
CDIPubSubMgmtMed
0.0.1-SNAPSHOT
CDIPubSubMgmtMed Mediation

Now I want to know how to do a release build in Maven. I am using RTC and for 
other build tools like CruiseControl, here is what we do:

1. We have a continuously build workspace/branch to build the code every 10 
minutes. Every build has a baseline created.
2. We do a release build every night, which takes the latest successful 
continuously build baseline.

How can I do something similar in Maven, or how does Maven do a release build?

Thanks
Jirong


--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-do-a-release-build-in-Maven-tp5709440.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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

RE: How can I trigger a makefile through Maven? is there any plugin for this?

[Lyons, Roy]

I would like to submit that the issue is that "make" already sees the built 
binaries and the sources have not modified so a re-build is not triggered.

http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html

you will want to modify your pom to include these items in a clean, and add 
"clean" as your first maven target to force a build to take place.

-Original Message-
From: bettypop [mailto:yashu@gmail.com] 
Sent: Wednesday, April 25, 2012 4:56 AM
To: users@maven.apache.org
Subject: Re: How can I trigger a makefile through Maven? is there any plugin 
for this?

Hi,
I did as you said. 
But it is not compiling the target which I have mentioned in the makefile.
My target is a C file and in the makefile I am just compiling the target. My 
updated POM.xml and the result I got on execution- 




*POM.xml*

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0

com.nds.TestProjectMaven
nativeTestProjectMaven
1.0-SNAPSHOT


TestProjectMaven
http://maven.apache.org


C:\Program
Files\apache-maven-3.0.4\maven-native-example\src\main\native
../../../target/native







org.codehaus.mojo
exec-maven-plugin
1.1  
  


exe
compile  
  
   
exec

   
C:\Program Files\GnuWin32\bin\make  

   
C:\Program
Files\apache-maven-3.0.4\maven-native-example\src\main\makefile


  

  











*On mvn install:*
C:\Program Files\apache-maven-3.0.4\maven-native-example>mvn install 
[INFO] Scanning for projects... 
[INFO] 
[INFO]
 
[INFO] Building TestProjectMaven 1.0-SNAPSHOT 
[INFO]
 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
nativeTest 
ProjectMaven --- 
[debug] execute contextualize 
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, 
i.e. build is platform dependent! 
[INFO] skip non existing resourceDirectory C:\Program
Files\apache-maven-3.0.4\m 
aven-native-example\src\main\resources 
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
nativeTestPro 
jectMaven --- 
[INFO] No sources to compile 
[INFO] 
[INFO] --- exec-maven-plugin:1.1:exec (exe) @ nativeTestProjectMaven --- 
[INFO] make: Nothing to be done for `C:\Program
Files\apache-maven-3.0.4\maven-n 
ative-example\src\main\makefile'. 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources)
@ na 
tiveTestProjectMaven --- 
[debug] execute contextualize 
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, 
i.e. build is platform dependent! 
[INFO] skip non existing resourceDirectory C:\Program
Files\apache-maven-3.0.4\m 
aven-native-example\src\test\resources 
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
nativ 
eTestProjectMaven --- 
[INFO] No sources to compile 
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @
nativeTestProjectMav 
en --- 
[INFO] No tests to run. 
[INFO] Surefire report directory: C:\Program
Files\apache-maven-3.0.4\maven-nati 
ve-example\target\surefire-reports 

--- 
 T E S T S 
--- 

Results : 

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 

[INFO] 
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ nativeTestProjectMaven
--- 

[WARNING] JAR will be empty - no content was marked for inclusion! 
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @
nativeTestProj 
ectMaven --- 
[INFO] Installing C:\Program
Files\apache-maven-3.0.4\maven-native-example\targe 
t\nativeTestProjectMaven-1.0-SNAPSHOT.jar to C:\Documents and
Settings\yashaswin 
is\.m2

Re: Bug in Maven 3?

[Lyons, Roy]

This sounds familiar.  I recall that maven 3 does some sort of metadata thing 
with respect to the repository cache, which is different compared to maven 2.


Either way I would recommend setting up a repository manager like nexus on your 
machine or local network, and use a repository group to aggregate proxy repos 
to all the sites you need.  Then your metadata should all be from the same url 
and repo Id and as an added bonus your builds should be a lot faster.


Sent from my Blackberry.

- Original Message -
From: Jane Young 
To: users@maven.apache.org 
Cc: GRECOURT,ROMAIN ; Sanjeeb Sahoo 

Sent: Tue Apr 03 23:46:44 2012
Subject: Bug in Maven 3?

Hi Maven Gurus,

Looks like Maven 3 always try to download the transitive dependencies 
even though it's available in the local repo.

In the pom, I have the following dependency defined:

org.glassfish.fighterfish
osgi-web-container
1.0.2

This artifact is available in Maven central.  However, the transitive 
dependency "org.eclipse.persistence:javax.persistence" is not available 
in Maven central.  So I added the EclipseLink repo in settings.xml:

eclipse-repo


eclipselink.repository
EclipseLink Repo

true


false

http://download.eclipse.org/rt/eclipselink/maven.repo/
default



The build succeeded when I compiled with "-Peclipse-repo" profile since 
it was able to download the javax.persistence artifact from EclipseLink 
Maven repo.
The local maven repo is now populated with javax.persistence artifact.  
The second time I compiled w/o "-Peclipse-repo" profile, it failed with 
the following message:

[ERROR] Failed to execute goal on project test.maven3: Could not resolve 
dependencies for project test:test.maven3:jar:1.0-SNAPSHOT: Failure to 
find org.eclipse.persistence:javax.persistence:jar:2.0.3 in 
http://repo1.maven.org/maven2/ was cached in the local repository, 
resolution will not be reattempted until the update interval of 
maven-central has elapsed or updates are forced -> [Help 1]

Why is Maven trying to download the artifact if it's available in the 
local maven repo?
This works in Maven 2 but not Maven 3.  Is this a bug in Maven 3?

Thanks,
Jane

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

RE: private key definition through profile activated property

[Lyons, Roy]

Just a gentle 2 week nudge.

Some additional info that I have, realizing that this didn't really outline 
some infrastructure details...

The idea here is that we can give a package to our support group to allow 
distribution to all developers.  Since the key location will be different for 
each user, and most users find maven to be a magical being that cavorts with 
unicorns on rainbows, it would be awesome to create a definition for the 
location of the keyfile that can be determined through use of known (and always 
set) variables -- as well as a path determination based on what OS the user is 
on.

>From my experimentation so far, it appears that the key location is evaluated 
>before any profiles are -- and that presents a problem for me.

I am really hoping to be proven wrong, and perhaps have something silly pointed 
out, like "hey, if you want to change the variable just use 
${settings.somevar.someothervar.privateKey} -- it won't evaluate variables in 
this field so forget putting one in there."

I have searched and searched, and have not found any documentation which tells 
me something like that though -- and that makes me a sad panda.  Turn my frown 
upside-down!

Thanks,

Roy

From: Lyons, Roy
Sent: Wednesday, March 14, 2012 1:16 PM
To: 'users@maven.apache.org'
Subject: private key definition through profile activated property

I am looking to set the location of the key file to be used based on the OS the 
user is executing within a distributable settings.xml file.  This would be for 
a company-wide change, not just a per-project basis.  Unfortunately, All I get 
is:

[WARNING] repository metadata for: 'org.apache.maven.plugins' could not be 
retrieved from repository: InternalReleasePlugin due to an error: 
Authentication failed: Private key '${scp.key}' not found


windows


windows




//fileserverhostname/home/${user.name}/.ssh/${user.name}



linux


unix




/home/${user.name}/.ssh/${user.name}




This happens on both unix and windows executions, and "mvn 
help:active-profiles" reports that the correct profile is being activated.

Is there a different way in which I need to address this property to allow it 
to be expanded to the value I provided?

RE: There is a way to override distributionManagement in Maven

[Lyons, Roy]

:) that looks exciting actually.  That would be quite usable.  Hopefully this 
will fix the original poster's issue as well.

Somehow I didn't run across this in my documentation travels, and my 
documentation passport is generally well stamped...  

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Wednesday, March 28, 2012 8:42 AM
To: Maven Users List
Subject: Re: There is a way to override distributionManagement in Maven

and what is exactly wrong with

mvn -DaltDeploymentRepository=id::default::url deploy

?

no change to pom required

On 28 March 2012 14:35, Lyons, Roy  wrote:
> Actually, this makes some sense to me.  If you really want to test out your 
> build scripts, but do not want to make actual changes to the corporate repo, 
> you would want to instead publish to a temporary area.  You don't actually 
> want to disable the "deploy" but you don't want it overwriting your current 
> binaries since Java was so awesome as to always create binaries with a new 
> md5sum (AWESOME feature let me tell you...).
>
> I would be interested in the outcome of this as well, since at the moment our 
> only way of setting up a test environment is to create entirely new code 
> repos and update poms.  Of course code and poms get out of date -- so 
> unexpected "goodness" has the ability to creep up on us during production 
> builds.
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Wednesday, March 28, 2012 2:45 AM
> To: Maven Users List
> Subject: Re: There is a way to override distributionManagement in 
> Maven
>
> Take a step back and try and explain exactly what the problem is that you 
> think you are trying to solve.
>
> I have a sneaky feeling you are trying to get functionality similar to 
> staging/promotion available from the good repository managers (iirc 
> nexus free does not, but nexus pro and artifactory certainly have the 
> capability, I would need to check archivia, but I suspect it might)
>
> On Tuesday, 27 March 2012,   wrote:
>> Hello Maven users,
>>
>> I have a project master pom.xml with a distribution management 
>> section
> defined like this:
>>
>>  
>>    
>>      one
>>      Blah Managed Releases Repository
>>      http://:8080/archiva/repository/one/
>>      default
>>    
>>    
>>      snapshots
>>      Blah Managed Snapshots Repository
>>      http://:8080/archiva/repository/snapshots/
>>      true
>>      default
>>    
>>  
>>
>> I want to be able to override this values on a test and production 
>> setup,
> having the production setting enabled by default; After reading the Maven 
> site it seems than the only way to do this is by using profiles but after 
> some reading on this list it seems than the are not a good choice (many 
> caveats).
>>
>> There is a cleaner way to achieve this?
>> Can someone point me to some examples? I'm not sure what to put where
>>
>> Thanks in advance,
>>
>> --Jose
>>
>> Barclays is one of the world's leading banks, and we believe that by
> continuing to integrate the organisation we can better deliver the full power 
> of Barclays to customers, clients and the communities in which we work. As a 
> visible sign of that integration we are moving to a single Barclays brand for 
> the majority of our divisions, including those formerly known as Barclays 
> Capital, Barclays Wealth and Barclays Corporate.
>>
>> ___
>>
>> This e-mail may contain information that is confidential, privileged 
>> or
> otherwise protected from
>> disclosure. If you are not an intended recipient of this e-mail, do 
>> not
> duplicate or redistribute
>> it by any means. Please delete it and any attachments and notify the
> sender that you have received
>> it in error. Unless specifically indicated, this e-mail is not an 
>> offer
> to buy or sell or a
>> solicitation to buy or sell any securities, investment products or 
>> other
> financial product or
>> service, an official confirmation of any transaction, or an official
> statement of Barclays. Any
>> views or opinions presented are solely those of the author and do not
> necessarily represent those
>> of Barclays. This e-mail is subject to terms available at the 
>> following
> link: www.barcap.com/emaildisclaimer.
>> By messaging with Barclays you consent to the foregoing.  Barclays 
>> offers
> premier investment banking
>> products and services to its c

RE: There is a way to override distributionManagement in Maven

[Lyons, Roy]

Actually, this makes some sense to me.  If you really want to test out your 
build scripts, but do not want to make actual changes to the corporate repo, 
you would want to instead publish to a temporary area.  You don't actually want 
to disable the "deploy" but you don't want it overwriting your current binaries 
since Java was so awesome as to always create binaries with a new md5sum 
(AWESOME feature let me tell you...).  

I would be interested in the outcome of this as well, since at the moment our 
only way of setting up a test environment is to create entirely new code repos 
and update poms.  Of course code and poms get out of date -- so unexpected 
"goodness" has the ability to creep up on us during production builds.

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Wednesday, March 28, 2012 2:45 AM
To: Maven Users List
Subject: Re: There is a way to override distributionManagement in Maven

Take a step back and try and explain exactly what the problem is that you think 
you are trying to solve.

I have a sneaky feeling you are trying to get functionality similar to 
staging/promotion available from the good repository managers (iirc nexus free 
does not, but nexus pro and artifactory certainly have the capability, I would 
need to check archivia, but I suspect it might)

On Tuesday, 27 March 2012,   wrote:
> Hello Maven users,
>
> I have a project master pom.xml with a distribution management section
defined like this:
>
>  
>
>  one
>  Blah Managed Releases Repository
>  http://:8080/archiva/repository/one/
>  default
>
>
>  snapshots
>  Blah Managed Snapshots Repository
>  http://:8080/archiva/repository/snapshots/
>  true
>  default
>
>  
>
> I want to be able to override this values on a test and production 
> setup,
having the production setting enabled by default; After reading the Maven site 
it seems than the only way to do this is by using profiles but after some 
reading on this list it seems than the are not a good choice (many caveats).
>
> There is a cleaner way to achieve this?
> Can someone point me to some examples? I'm not sure what to put where
>
> Thanks in advance,
>
> --Jose
>
> Barclays is one of the world's leading banks, and we believe that by
continuing to integrate the organisation we can better deliver the full power 
of Barclays to customers, clients and the communities in which we work. As a 
visible sign of that integration we are moving to a single Barclays brand for 
the majority of our divisions, including those formerly known as Barclays 
Capital, Barclays Wealth and Barclays Corporate.
>
> ___
>
> This e-mail may contain information that is confidential, privileged 
> or
otherwise protected from
> disclosure. If you are not an intended recipient of this e-mail, do 
> not
duplicate or redistribute
> it by any means. Please delete it and any attachments and notify the
sender that you have received
> it in error. Unless specifically indicated, this e-mail is not an 
> offer
to buy or sell or a
> solicitation to buy or sell any securities, investment products or 
> other
financial product or
> service, an official confirmation of any transaction, or an official
statement of Barclays. Any
> views or opinions presented are solely those of the author and do not
necessarily represent those
> of Barclays. This e-mail is subject to terms available at the 
> following
link: www.barcap.com/emaildisclaimer.
> By messaging with Barclays you consent to the foregoing.  Barclays 
> offers
premier investment banking
> products and services to its clients through Barclays Bank PLC, a 
> company
registered in England
> (number 1026167) with its registered office at 1 Churchill Place, 
> London,
E14 5HP.  This email may
> relate to or be sent from other members of the Barclays Group.
>
> ___
>

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

Re: Transitive Dependencies for Unused Artifact

[Lyons, Roy]

You can use dependencymanagement section to define the version as a filter to 
any subsequent dependencies section.

Putting it in dependencymanagement does not declare it as a dependency but does 
define the version to be used when it find the dependency declared.
Sent from my Blackberry.

- Original Message -
From: kdobrik 
To: users@maven.apache.org 
Sent: Mon Mar 19 09:06:03 2012
Subject: Re: Transitive Dependencies for Unused Artifact

Thank you for the answer.
I will revisit my question. At the end of the day I need to centralize the
versions used among all modules. Nevertheless these modules do not share all
the jars needed. I need to refresh my Maven knowledge :)

Once again thank you!

--
View this message in context: 
http://maven.40175.n5.nabble.com/Transitive-Dependencies-for-Unused-Artifact-tp5570805p5577176.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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

RE: private key definition through profile activated property

[Lyons, Roy]

Shameless bump...  Is there a way to define the key location as a property 
activated by OS?  Perhaps a way to set server definitions within the profile (I 
couldn't get that to work either)

-Original Message-
From: Lyons, Roy 
Sent: Wednesday, March 14, 2012 1:16 PM
To: users@maven.apache.org
Subject: private key definition through profile activated property

I am looking to set the location of the key file to be used based on the OS the 
user is executing within a distributable settings.xml file.  This would be for 
a company-wide change, not just a per-project basis.  Unfortunately, All I get 
is:

[WARNING] repository metadata for: 'org.apache.maven.plugins' could not be 
retrieved from repository: InternalReleasePlugin due to an error: 
Authentication failed: Private key '${scp.key}' not found


windows


windows




//fileserverhostname/home/${user.name}/.ssh/${user.name}



linux


unix




/home/${user.name}/.ssh/${user.name}




This happens on both unix and windows executions, and "mvn 
help:active-profiles" reports that the correct profile is being activated.

Is there a different way in which I need to address this property to allow it 
to be expanded to the value I provided?

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

RE: overlay all artifacts of a particular classifier/type combo

[Lyons, Roy]

I have seen customizations of war files done mainly through the assembly 
plugin.  You *can* specify a wildcard inclusion of dependencies based on 
classifier with assembly.

-Original Message-
From: Maven User [mailto:maven.2.u...@gmail.com] 
Sent: Wednesday, March 14, 2012 5:10 PM
To: Maven Users List
Subject: overlay all artifacts of a particular classifier/type combo

Hi all -

Is there a way to wildcard the overlaying of various dependencies?

I'd like to take all the artifacts of a given  and stick them at 
the root of the war.

Currently, we're doing a dependency:unpack of them, then including them as the 
base web dir.

In the end, I guess it works, but I was wondering if there was a way to do the 
same thing via the maven-war-plugin (doesn't seem so).

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

private key definition through profile activated property

[Lyons, Roy]

I am looking to set the location of the key file to be used based on the OS the 
user is executing within a distributable settings.xml file.  This would be for 
a company-wide change, not just a per-project basis.  Unfortunately, All I get 
is:

[WARNING] repository metadata for: 'org.apache.maven.plugins' could not be 
retrieved from repository: InternalReleasePlugin due to an error: 
Authentication failed: Private key '${scp.key}' not found


windows


windows




//fileserverhostname/home/${user.name}/.ssh/${user.name}



linux


unix




/home/${user.name}/.ssh/${user.name}




This happens on both unix and windows executions, and "mvn 
help:active-profiles" reports that the correct profile is being activated.

Is there a different way in which I need to address this property to allow it 
to be expanded to the value I provided?

RE: how to custom decrypt settings.xml passwords

[Lyons, Roy]

To address the issue of weak encryption of passwords, CME Group has contracted 
with Sonatype to create a custom build of Nexus that uses ssh keys and PKI for 
authentication.  We are expecting to receive a delivery early to mid April on 
the ssh based approach.  The PKI approach will require some customization on 
the maven client end, to allow for certificate based authentication.

You may want to contact Sonatype to address your issues, they will have a 
solution.

Thanks,

Roy

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: Tuesday, March 13, 2012 4:41 AM
To: Maven Users List
Subject: Re: how to custom decrypt settings.xml passwords

I don't think this is possible to do through a Maven plugin. It has to be part 
of Maven core.
Unfortunately, Maven Core currently does not (that I've found) provide with a 
hook or extension to switch the encryption mechanism. Until that is 
implemented, I believe you need to create your own extended Maven installation 
with support for this.

I'm in a similar situation. For a corporate environment with fairly high 
security concerns, the current solution with passwords in settings.xml is a 
problem in general. Also, it causes problems on CI as the credentials are quite 
easy to get hold of (a simple Maven build will reveal it). So, currently, we've 
not allowed CI to deploy artifacts to the repo.

So, from my perspective there are different things to solve (in my case at 
least):
* A simpler/better solution to handle the users' credentials. This could be 
integration with smart cards, Windows SSO (kerberos?), etc.
The user shouldn't have to update the settings.xml.
* A good/secure integration between CI and the repo. Ultimately I'd like the 
end user's credentails to be used (not a generic CI account as I want to know 
exactly who pressed the build button). If a generic CI account is used, it has 
to be kept outside of the Maven Core loop so that it can't be snooped.

/Anders
On Tue, Mar 13, 2012 at 10:07, Lannoye Xavier  wrote:
> Hi
>
> I'm working in a corporate environment, with maven builds processed on 
> atlassian bamboo servers. I've been asked to investigate a solution to 
> encrypt passwords present in the custom settings.xml file against our 
> corporate encryption software.
>
> I've started with the maven's master-password procedure, but with this 
> procedure, we faced the distributed bamboo's remote agents issue. 
> passwords must be encrypted using the master password of the server it 
> is going to be decrypted later on, and with bamboo agents, you cannot 
> guarantee on which server the build will be executed.
>
> Then I read about ssh encrypted passwords, but this requires ssh login 
> for each of our customers on our servers, which they don't have. We 
> have to many users to create unix accounts for each of them, and 
> furthermore, we don't want them to access our servers by other 
> meanings than the bamboo interface. Not mentioning they should have access to 
> every remote agent.
>
> so this is why we finally get to the point we need to force our bamboo 
> users to include in their project their own settings.xml file, which 
> they call in their build with the "-s" parameter.
> in settings.xml however, the passwords are plain text, and so are 
> readable by anyone.
>
> I was thinking about writing a maven plugin which could use our 
> corporate encryption software to decrypt passwords. But I cannot 
> figure out how to hook this inside maven. I already wrote a plugin 
> that reads the settings.xml file, but how to "push" the decrypted 
> password inside the maven build process? I'd need something as a "hook" but 
> cannot find any.
>
> Thanks for everyone for taking the time to read this (quite) long message.

-
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

RE: (Re-)Deploy artifacts to (different) repositories

[Lyons, Roy]

Most distributed teams would use nexus for that.  deploy once, propagate many.

-Original Message-
From: M. Richey [mailto:mric...@gmx.de] 
Sent: Thursday, March 08, 2012 8:14 AM
To: Maven Users List
Subject: (Re-)Deploy artifacts to (different) repositories


Hi everyone,

we would like to make our artifacts available for our teams being spread across 
different locations.

So what would be the best way to do that?

We did a mvn install before. So all projects are build already. Therefore it 
would be great if we could use the projects artifacts (or the ones from the 
local repository) and deploy it to the different repositories. But executing 
mvn deploy more than once, will cause maven to reassemble all the artifacts 
which is just wasting time. And afaik the is no way to deploy to different 
repositories in one go.

Is there a way to do it like that? Can you use the local repository to deploy 
from there? Any other ideas on how to get this done?

Thanks in advance!

Kind regards,

Maik

-
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

Re: Importing Maven projects in Eclipse

[Lyons, Roy]

I saw that sonatype was collaborating with m2e and egit to make a plugin that 
does both.  Just providing the info here so you can google it properly to find 
your solution!


Sent from my Blackberry.

- Original Message -
From: Marko Asplund 
To: users@maven.apache.org 
Sent: Wed Mar 07 02:48:11 2012
Subject: Importing Maven projects in Eclipse

Hi,

I'm using Maven 3 and the m2e Eclipse plugin.
Normally i import my Maven projects into Eclipse using the Import /
Existing Maven projects.
There are some cases where this option doesn't seem to be available e.g.
(with EGit) so I need an alternative method.
Can I use the Maven eclipse:eclipse plugin for generating the Eclipse
project files and then import as regular, existing projects?
Or is there another way to do this?

There were some notes on m2e FAQ that the two plugins are somehow
incompatible:
http://wiki.eclipse.org/M2E_FAQ#Maven_Integration_for_Eclipse_vs._Maven_eclipse:eclipse_plugin

Is this correct?


marko

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

Re: Maven concurrent builds

[Lyons, Roy]

You can use -Dmaven.repo.local in your builds to use separate cache repos.  I 
assume you already made sure that jenkins was compiling in separate workspace 
areas?  Otherwise as he said, it would probably trip over itself as any other 
builder would.
Sent from my Blackberry.

- Original Message -
From: Jörg Schaible 
To: users@maven.apache.org 
Sent: Wed Mar 07 02:29:41 2012
Subject: Re: Maven concurrent builds

Hi Guillaume,

Guillaume Polet wrote:

> Dear all,
> 
> I was having some doubts regarding Maven's ability to handle properly
> concurrent builds. Lately, I had several builds of our project that
> failed and it seemed that it was due to interferences between concurrent
> builds of the same version of the same project.
> 
> I have a jenkins server which have 6 different builds:
> * 1 for continuous build (which runs tests but does not deploy the
> artifacts)
> * 1 for nightly build
> * 1 for releases (or almost release, ie, the pom is still in SNAPSHOT
> version but could become a release)
> All this is multiplied by two, because I have two versions (on 2
> different branches).
> 
> So I had 2 questions:
> 1. Can/Does Maven support concurrent builds of the same version of the
> same project?

Not out of the box. Since by default both builds will use the same local 
repository creating the same artifacts at same time, the artifacts in the 
repository are likely to be corrupted.

> If yes, do I need to do something to achieve this?

Use separate local repositories, it can be defined using separate 
settings.xml files or by call with a system property. Actually I don't know 
if Jenkins already supports something like this, because it's a general 
problem, see below.

> If not,
> is it something that Maven developers are considering?

It's not the first time this problem has been risen.

> 2. Can/Does Maven support concurrent builds of different versions of the
> same project?

They may still corrupt the metadata.xml files, but it is less likely and has 
AFAICS less consequences.

However, every concurrent build may corrupt a shared local repository, 
because both builds may download the same artifacts at same time. A scenario 
where this might happen is when you upgrade versions (e.g. of plugins) in a 
common master-pom and start two parallel builds then. Actually I am not sure 
if you're safe when running one Maven build in parallel mode. A repository 
manager like Nexus might prevent this scenario by detecting the same 
request, but again I am not sure if it does.

BTW: This is also the reason why you should never share a local repository 
with a network mount by multiple users.


> 
> Cheers,
> Guillaume



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

Re: Is it possible to tie current git branch to project version?

[Lyons, Roy]

:-) we tag our repo with "branchname!RP-BL-mavenlabel" to help in location.  Rp 
is for release prepare and bl is for baseline (carryover from clearcase 
terminology)

Just remember that in git a hash doesn't belong to a branch, it is simply 
attached to a linked list of hashes.  A "branch" is simply a tag pointing to a 
hash being designated as a "head".  You can just as easily use the tag created 
by the release plugin to checkout, and then make some bugfix branch from that 
location.


Sent from my Blackberry.

- Original Message -
From: Seth Call 
To: users@maven.apache.org 
Sent: Tue Mar 06 22:01:07 2012
Subject: Is it possible to tie current git branch to project version?

Hi there,

I've seen indication when searching the internet that it isn't possible to
put variables in  of a project (unless those variables are
hardcoded  or provided at the command line), but I thought I'd
ask the list ...

Say there was a plugin that would invoke 'git branch' to determine the
current branch, and to then make that available to the project as a
variable; call it ${branch}.   I'd like to use this variable then in the
version tag:


blah
blah
${branch}-SNAPSHOT


The reason I want to do this is that I'm realizing, for our internal-only
code projects, that a branch is always synonymous with a version of a
project, and ideally the act of being of switching branches would be all it
takes to switch your maven project's version.

Is this possible if I were to make a maven plugin? 

Thanks!
Seth




--
View this message in context: 
http://maven.40175.n5.nabble.com/Is-it-possible-to-tie-current-git-branch-to-project-version-tp5543110p5543110.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: Preferring local repository over remote for 'work sessions'

[Lyons, Roy]

You could specify the timestamped version of the snapshot for the items you 
don't wish to get updates for.  That should do what you are looking for.

If I recall correctly, there is a maven versions plugin that can convert your 
open ended or vague versions into solid concrete timestamped ones.


Sent from my Blackberry.

- Original Message -
From: sethcall 
To: users@maven.apache.org 
Sent: Tue Mar 06 19:32:05 2012
Subject: Preferring local repository over remote for 'work sessions'

I'm trying to understand how I can accomplish a particular workflow.

First, some terms:

org:project-a:1.0-SNAPSHOT
org:project-b:1.0-SNAPSHOT
org.project-c:1.0-SNAPSHOT  DEPENDS_ON org.project-a:1.0-SNAPSHOT,
org.project-b:1.0-SNAPSHOT

Assume that we have a build server regularly building project-a and
project-b, and placing into an HTTP repository, like Artifactory.

Problem workflow:

User downloads project-b and project-c, but not project-a.  User fixes a bug
in project-b.  User does a 'mvn install' locally on both project-b and
project-c.The user hasn't checked in anything yet to SCM.

For the time being, project-c should use project-b from the local repository
because it's the latest 1.0-SNAPSHOT, right?

Ok. Assume that now, the build server builds a new 1.0-SNAPSHOT of
project-b.  From the documentation I've read on maven, project-c will now
resolve against the latest version; which is in the remote repository.

This is problematic if you have actively changed project-b and were hoping
it to remain active while your working on it.  Your bug fix won't be in
effect because you are using the remote/build-server project-b, which
doesn't have your fix.

Also, I don't want to use mvn -o (offline), because if I haven't downloaded
project-a, and if there are changes, then I'd still like to get updates to
it as I'm working, per usual SNAPSHOT behavior.Another way to put this:
I'm trying to solve this in a per-dependency way.

I have some ideas on how to solve this, none of which sound good to me, but
I first wanted to hear what anyone would suggest that I do, before I make
this post longer...

Thanks for any help,
Seth

--
View this message in context: 
http://maven.40175.n5.nabble.com/Preferring-local-repository-over-remote-for-work-sessions-tp5542872p5542872.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: There is a way to download all the artifacts and dependencies for a given project without compiling

[Lyons, Roy]

Mvn dependency:go-offline -Dmaven.repo.local=/some/folder/where/you/want/them.  
That will download all of the items needed including plugins.  
Sent from my Blackberry.

- Original Message -
From: jose.nunez-zul...@barclayscapital.com 

To: users@maven.apache.org 
Sent: Tue Mar 06 15:52:14 2012
Subject: RE: There is a way to download all the artifacts and dependencies for 
a given project without compiling

Thanks, that's a good start.

--Jose

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: Tuesday, March 06, 2012 4:45 PM
To: Maven Users List
Subject: Re: There is a way to download all the artifacts and dependencies for 
a given project without compiling

> Let me rephrase the question to "it is possible to download all the artifacts 
> that belong
> to a specific group and version without getting the master pom".

Probably you could make something work with Aether API:
http://www.sonatype.org/aether/
http://www.sonatype.com/people/category/aether/

Wayne

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


___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

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

RE: Configure pom for build

[Lyons, Roy]

if you are in a unix-like environment, for the logfile you can use 'tee'

mvn clean install 2>&1 | tee log.file

that will display it to the screen and put it into your logfile.

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: Thursday, March 01, 2012 4:34 PM
To: Maven Users List
Subject: Re: Configure pom for build

> 1)Log to a file the flow of steps from Maven execution.( Is there an 
> alternative to ant echo in Maven)
>  I dont want to use  [* mvn clean install  > log.file* ]

I am unaware of any way to do this and use "... > log.file" if I need to do 
this.

> 2) Does Maven accept custom arguments from command line? something 
> like -Darguments

Yes.

> 3)Backup files using pom.

What does "backup files" mean? Why would you need to do this?

> 4) Do checksum in Maven.

http://lmgtfy.com/?q=maven+checksum+plugin

Wayne

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

RE: POM missing in Maven

[Lyons, Roy]

What he is trying to point out is that the missing pom didn’t fail the build.  
It couldn’t find the file you pasted -- that’s the problem in a nutshell.  Its 
an issue with their build setup most likely, and not with maven itself.

-Original Message-
From: monkeyMan [mailto:thebig...@hotmail.com] 
Sent: Friday, February 24, 2012 2:11 PM
To: Maven Users List
Subject: Re: POM missing in Maven

OK. Should the POM for Maven be in the Maven directory? The reason I ask it 
that it seems to be Mavens attempts to resolve dependencies when  the error 
occurs because of a missing POM.

A POM is evident in the Synapse directory, Maven functions on the command line. 
The directory path does not exist. Is this because Maven is not completing the 
install?

If these are basic questions, sorry, I am just trying to get to the bottom of 
it really.

-Original Message-
From: Wayne Fay
Sent: Friday, February 24, 2012 2:55 PM
To: Maven Users List
Subject: Re: POM missing in Maven

> I have two functioning Maven builds. When using Maven to install a 
> copy of Apache Synapse I get the following message amongst several 
> regarding build
> failure:
>
> [Error] Failed to execute goal org.apache.maven .plugins:maven-remote- 
> resources-plugin:1.1:process (default) on project Apache-Synapse: 
> Error finding remote resources manifests: 
> c:\ASF\synapse-2.1.0-src\target\maven-shared-
> archive-resources\META-INF\Notice (The system cannot find the path
> specified)
> This path is missing in the directory structure.

I would ask for help with this issue on the Apache Synapse developers or users 
list. They are more familiar with that product's build process than we are.

Wayne

-
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

RE: maven: scm: clearcase URL help

[Lyons, Roy]

the biggest problem is that you are trying to use physical locations.

The load rule is definitely incorrect.  this needs to be the component root.

vob name is incorrect -- this needs to be the vob tag, not some physical 
location

you also don't need to specify the view -- it creates its own view -- hence you 
need to give it a view storage location where it can create a view.

also, don't use \  -- use /.


load rule as I see it here would be "load /Comp_Local_finApp_vob"  and the view 
storage location would be //remotehost/ccstg_d/views/comp/Username

-Original Message-
From: sarmahdi [mailto:sarma...@hotmail.com] 
Sent: Wednesday, February 22, 2012 8:13 AM
To: users@maven.apache.org
Subject: Re: maven: scm: clearcase URL help

Im sorry if i seem to be annoying, hence you taking it offline.

But in pure maven's sense, its still is the maven's style of URL that is needed 
here. (not trying to argue, just my own understanding of my problem which of 
course can be wrong)

I have the view name, stream name, the remote path to config_spec (in clear 
case), the local path to my local vob in my local view.

it says:
[INFO] viewName = '5510041_Local_eCorp_II_Dev' ; configSpec = 'load 
\\remotehost\ccstg_d\views\comp\Username\Username_Local_finApp_Dev.vws\config_spec'
; vobName = 'C:/cc_views/Username_Local_finApp_Dev/Comp_Local_finApp_vob' ; 
streamName = 'Local_finApp_Dev' ; elementName = 'null'

[INFO] project.scm.connection scm connection string is valid.

then the maven exception: maven's exception doesnt give me anything more than

Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -4

I think I got all the info from CC for the URL, so What am I missing in maven? 
if it is the element name then where do i specify that?

pls help.

I will really appreciate it.

Thanks
Syed...



--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5505214.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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

Re: maven: scm: clearcase URL help

[Lyons, Roy]

I am taking this conversation off-line as it relates more to clearcase now than 
maven.
Sent from my Blackberry.

- Original Message -
From: sarmahdi 
To: users@maven.apache.org 
Sent: Wed Feb 22 04:23:58 2012
Subject: RE: maven: scm: clearcase URL help

Lyons,

I tried to use pipes in my url as i had to add my local path for the vob and
there was a colon in C:\My\localpath  : 

 
   
scm:clearcase|[UserName_Local_finApp_Dev]|\\222.222.222.222\cc_drivespace\views\Company\Useranme\Username_Local_finApp_Dev.vws\config_spec|C:\My\localpath\Comp_Local_finApp_vob|Local_finApp_Dev




it says that when i run mvn scm:validate

[INFO] connectionUrl scm connection string is valid.
[INFO] project.scm.connection scm connection string is valid.

but then it fails with this error.

Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal org.apache.maven.plugins:maven-scm-plugin:1.6:validate
failed: String index out of range: -4
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)


I will appreciate your help.

Thanks.



--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5504733.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

RE: maven: scm: clearcase URL help

[Lyons, Roy]

FYI -- this is the format we used for a couple of years here with the release 
plugin, before we moved to git.  

You also need a clearcase-settings.xml in your $MAVEN_HOME/conf directory 
containing something like this:

  UCM
  true
  /net/ccview1/viewstg1/
   
scm:clearcase:load 
/some/load/rule:/your/project/vob:your_stream_name 



-Original Message-
From: sarmahdi [mailto:sarma...@hotmail.com] 
Sent: Tuesday, February 21, 2012 10:09 AM
To: users@maven.apache.org
Subject: maven: scm: clearcase URL help

Hello all,
I am trying to connect to a remote clearcase to update my view

I just started on this project with Clear case and been asked to maven ize the 
project and update the view from clearcase 

I added the scm tag and added the clearcase-settings.xml defining the 
clearcasetype as UCM

I need some help with the connection URL: 

I went to the SCM plugin for CC page and the URL for UCM is :

scm:clearcase[view_name]config_specvob_namestream_name

At some places it says that the POM in the folder of the project (inside the 
clear case view) should only contain scm:clearcase, but when i try mvn 
scm:validate with that then i get the error :

[ERROR] Validation of scm url connection (connectionUrl) failed :
[ERROR] Illegal URL: (ClearCaseUCM need more parameters. Expected url format
: [view_name]|[configspec]|[vob_name]|[stream_name])
[ERROR] The invalid scm url connection: 'scm:clearcase:'.


I added the view name , vob name and stream name but I dont know what the 
config spec and elementName should be. is the config-spec the host name of the 
clear case server. After adding the hostname as the config spec i get
this error :   http://codepad.org/ZXCLskCR  exception on mvn validate with
URL on codepad 



I will appreciate if anyone can guide me to complete these two values for my 
URL connection.

Thanks
Syed...





--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5502632.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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

RE: maven: scm: clearcase URL help

[Lyons, Roy]

   
scm:clearcase:load 
/some/load/rule:/your/project/vob:your_stream_name 



-Original Message-
From: sarmahdi [mailto:sarma...@hotmail.com] 
Sent: Tuesday, February 21, 2012 10:09 AM
To: users@maven.apache.org
Subject: maven: scm: clearcase URL help

Hello all,
I am trying to connect to a remote clearcase to update my view

I just started on this project with Clear case and been asked to maven ize the 
project and update the view from clearcase 

I added the scm tag and added the clearcase-settings.xml defining the 
clearcasetype as UCM

I need some help with the connection URL: 

I went to the SCM plugin for CC page and the URL for UCM is :

scm:clearcase[view_name]config_specvob_namestream_name

At some places it says that the POM in the folder of the project (inside the 
clear case view) should only contain scm:clearcase, but when i try mvn 
scm:validate with that then i get the error :

[ERROR] Validation of scm url connection (connectionUrl) failed :
[ERROR] Illegal URL: (ClearCaseUCM need more parameters. Expected url format
: [view_name]|[configspec]|[vob_name]|[stream_name])
[ERROR] The invalid scm url connection: 'scm:clearcase:'.


I added the view name , vob name and stream name but I dont know what the 
config spec and elementName should be. is the config-spec the host name of the 
clear case server. After adding the hostname as the config spec i get
this error :   http://codepad.org/ZXCLskCR  exception on mvn validate with
URL on codepad 



I will appreciate if anyone can guide me to complete these two values for my 
URL connection.

Thanks
Syed...





--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5502632.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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

RE: Copy two versions of same jar

[Lyons, Roy]

or...  if you REALLY want to cheat the system (yes, this is terrible, but we do 
have a certain use case for it).  We put some jar files inside a zip file so 
that we could make the zip a dependency and it wouldn't be added to the 
classpath of the application.  These jars are used by an ant process to 
interpolate variables on the target host to match values expected for the 
environment (port and IP for example).

I am also morally obligated to warn you that including both versions is 
hazardous to your health.  You can't exactly specify the order in which they 
are resolved on the classpath -- and so you never know which class definition 
will really be resolved first.

If this is to resolve an issue where a dependency of yours needs a newer 
version, but you use an older version -- I would say that you either have to 
use a version of the dependency that uses that older version, or you need to 
update your code to handle the newer version.  It's pretty dangerous to just 
stick both versions in and cross your fingers.

Disclaimer aside, here is what we do:


com.companyname
antdeploymentjars
01
zip







 
com.companyname:antdeploymentjars:zip:01 
   


deployment/Ant
true



-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Friday, February 17, 2012 2:28 AM
To: Maven Users List
Subject: Re: Copy two versions of same jar

Alternatively, if you just need a copy of the jar, and not the jar on the 
classpath, ie you are writing some app that builds its own classpath, some 
parts of the app use one version and other parts use the other version, and you 
have fancy code that sets up the class loaders correctly, this would be an 
ideal illustration of why dependency:copy can be needed sometimes (ie 
dependency:copy-dependencies does not fit this use-case)

Though IMHO I would rather wrap the code that needs the older version in a 
separate jar that uses maven-shade-plugin to remove the need for class loader 
trickery, if you have your own plugin framework, that might not be tractable...

Having said all that, 99% chance is that none of the above apply to your case, 
and you are just fighting maven because you think you can win... Well you won't 
win.

On Friday, 17 February 2012, Wayne Fay  wrote:
>> 
>>   
>>   test
>>   castor
>>   0.9.5
>>   
>>   
>>   test
>>   castor
>>   1.0.4
>>   
>> 
> ...
>> But this copies only one version and it ignores the other one.. 
>> Please provide a solution for copying both the versions.
>
> Why do you want to do this? As you've already discovered, Maven will 
> generally "collapse" two such dependencies into a single element and 
> pick one version over the other.
>
> If you have any ability to control the GA coordinates or to add a C
> (classifier) to one of the artifacts, you should do so as that would 
> be the easiest possible solution. Then Maven would consider them as 
> "different" and you could bring in both versions very easily.
>
> Wayne
>
> -
> 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

RE: How do I make a dependency both system and test scope?

[Lyons, Roy]

:-) I work at the company in question -- we don't block access to the repo...  
and we are using Nexus to proxy our 3rd party elements.

The problem is that this particular jar has a .exe file in it that the virus 
scanner goes nutso over.  So when its detected on the filesystem, it 
immediately quarantines/deletes it.  What should probably be done is that we 
make a copy of this jar with a classifier -- and the .exe file deleted and 
upload it to our internal 3rd party repo in nexus.

I am adding the user list at large in case they run into this issue with this 
jar, and can troubleshoot this as it may relate to their virus scanner!

Thanks,

Roy

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Friday, February 10, 2012 2:45 PM
To: Maven Users List
Subject: Re: How do I make a dependency both system and test scope?

In the light of idiocy you resort to complete and utter foolishness...

Where is your repository manager? Just deploy it there.

Friends don't let friends use maven without a repository manager

On Friday, 10 February 2012, laredotornado-3 
wrote:
> Hi,
>
> I'm using Maven 3.0.3.  For bizarre reasons, our company has blocked
access
> to a certain Maven repo, so I have chosen to load the dependency 
> through
the
> inclusion
>
>
>org.openqa.selenium.server
>selenium-server
>2.0b3
>system
>
>
${project.basedir}/lib/selenium-server-standalone-2.0b3.jar
>
>
> However, I only want this dependency referenced during the test phase.
 How
> do I make a dependency both available through a system scope and a 
> test scope?
>
> Thanks, - Dave
>
> --
> View this message in context:
http://maven.40175.n5.nabble.com/How-do-I-make-a-dependency-both-system-and-test-scope-tp5473053p5473053.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> 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

RE: Removing some modules in a maven profile

[Lyons, Roy]

I have seen this accomplished through the use of profiles and defining the 
modules within the profile.

-Original Message-
From: Ashish Srivastava [mailto:ashis...@yahoo.com] 
Sent: Friday, January 20, 2012 12:27 PM
To: users@maven.apache.org
Subject: Removing some modules in a maven profile

Hi,
   I have say a few modules defiled in the parent pom.xml as:
 

   a
   b
   c


I want the default profile builds the entire module list but create a new 
profile that say only builds a and b but not c. I have seen a thread where 
adding a module is suggested in a profile instead of removing (excluding) one. 
I tried to give module a and b in the profile and still mvn built everything, I 
guess because it builds the parent list first (?). Is there a way to accomplish 
this? 


Thanks for your help,
-Ashish

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