Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

Hi Charles & everyone, > To prevent SNAPSHOT churn you can use a plugin like > exists-maven-plugin > (https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html > ) > to prevent re-releasing unchanged artifacts. Thank

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

To prevent SNAPSHOT churn you can use a plugin like exists-maven-plugin (https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html ) to prevent re-releasing unchanged artifacts. chas > On Apr 24, 2017, at 1:52 PM,

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

SUBMIT ME On Mon, Apr 24, 2017 at 1:52 PM, Curtis Rueden wrote: > Hi Karl, > > Thanks very much for your reply! > > > Not only for displaying...you can also use it to update them... > > Understood. But I actually don't want to always auto-update everything to > latest releases. The point of the

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

Hi Karl, Thanks very much for your reply! > Not only for displaying...you can also use it to update them... Understood. But I actually don't want to always auto-update everything to latest releases. The point of the BOM is that the versions it references have been tested to work together. Especi

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

Hi, On 24/04/17 19:46, Curtis Rueden wrote: Hi Jesse, Prefer to harden the version # in a corporate pom. Then use versions-m-p to detect and update bulk dependencies across all our projects. We manage about 350 dependencies in the corporate pom Definitely agreed. I am managing a similar numb

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

1:46:59 PM Subject: Re: Please officially support RELEASE and LATEST (was: Re: dependency question) Hi Jesse, Prefer to harden the version # in a corporate pom. Then use versions-m-p to detect and update bulk dependencies across all our projects. We manage about 350 dependencies in the corporate

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

Hi Jesse, > Prefer to harden the version # in a corporate pom. Then use > versions-m-p to detect and update bulk dependencies across all our > projects. We manage about 350 dependencies in the corporate pom Definitely agreed. I am managing a similar number, and indeed versions-m-p is super nice f

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

Prefer to harden the version # in a corporate pom. Then use versions-m-p to detect and update bulk dependencies across all our projects. We manage about 350 dependencies in the corporate pom, and that doesn't even include the huge number that are scope=import for Arquillian and Selenium, etc. On M

Re: Please officially support RELEASE and LATEST (was: Re: dependency question)

> I would like to argue for the inclusion / restoration / continued > support of the RELEASE and LATEST tags. Really? No one else cares enough to respond? I am very often running into use cases where the easiest solution seems to be LATEST and/or RELEASE. I have to manage a large Bill of Material

Please officially support RELEASE and LATEST (was: Re: dependency question)

ible builds is to use fixed release versions, always. >>>>> >>>>> Regards, >>>>> Curtis >>>>> >>>>> -- >>>>> Curtis Rueden >>>>> LOCI software architect - https://loci.wisc.edu/software >>>>> ImageJ2 le

Stale wiki link question [was: Re: dependency question]

en >>>> >>>> >>>> On Tue, Apr 11, 2017 at 9:57 AM, Magnanao, Hector < >>> hector.magna...@sap.com >>>>> >>>> wrote: >>>> >>>>> This is fine as long as the dependency is always set to >>

Re: dependency question

e picked up ? -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Friday, April 7, 2017 10:50 AM To: Maven Users List Subject: Re: dependency question Hi Russlel, On 07/04/17 17:29, Russell Gold wrote: That’s the way it works: when you specify a snapshot, it take

Re: dependency question

t; > > This is fine as long as the dependency is always set to > x.y.z-Snapshot > > > and > > > > the dependency is always overwritten this way. What if the producer > > > > produces x.y.z.1-Snapshot, x.y.z.2-Snapshot, x.y.z.3-Snapshot and I > > want > &

Re: dependency question

pshot, x.y.z.3-Snapshot and I > want > > > the dependent build to always get the latest in this case, > > > x.y.z.3-Snapshot ? The difference with this scenario is that the > producer > > > will always have a new build number. > > > As for your solution of u

Re: dependency question

gt; As for your solution of using the range, do I always have to change the > > pom file in the dependent build whenever a new build is produced by the > > producer ? > > > > -Original Message- > > From: Benson Margulies [mailto:bimargul...@gmail.com] > > Sent: Monday,

Re: dependency question

> producer ? > > -Original Message- > From: Benson Margulies [mailto:bimargul...@gmail.com] > Sent: Monday, April 10, 2017 10:39 AM > To: Maven Users List > Subject: Re: dependency question > > On Mon, Apr 10, 2017 at 8:18 AM, Magnanao, Hector > wrote: > > I&#x

RE: dependency question

Margulies [mailto:bimargul...@gmail.com] Sent: Monday, April 10, 2017 10:39 AM To: Maven Users List Subject: Re: dependency question On Mon, Apr 10, 2017 at 8:18 AM, Magnanao, Hector wrote: > I'm still a little confused about the answers I'm getting. So, if build A is > being updated

Re: dependency question

be picked up ? > > -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Friday, April 7, 2017 10:50 AM > To: Maven Users List > Subject: Re: dependency question > > Hi Russlel, > On 07/04/17 17:29, Russell Gold wrote: > >>

RE: dependency question

ll be picked up ? -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Friday, April 7, 2017 10:50 AM To: Maven Users List Subject: Re: dependency question Hi Russlel, On 07/04/17 17:29, Russell Gold wrote: > That’s the way it works: when you specify a snap

RE: dependency question

://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Magnanao, Hector [mailto:hector.magna...@sap.com] Sent: Friday, April 07, 2017 10:28 AM To: Maven Users List Subject: RE: dependency question Can you give me an example of using a range in the pom file as a

Re: dependency question

. -Original Message- From: Russell Gold [mailto:russell.g...@oracle.com] Sent: Thursday, April 6, 2017 2:27 PM To: Maven Users List Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally

RE: dependency question

t one of our builds uses: false always fail -Original Message- From: Russell Gold Sent: Friday, April 07, 2017 10:30 AM To: Maven Users List Subject: Re: dependency question That’s the way it works: when you spec

Re: dependency question

> time for this scenario. > > -Original Message- > From: Russell Gold [mailto:russell.g...@oracle.com] > Sent: Thursday, April 6, 2017 2:27 PM > To: Maven Users List > Subject: Re: dependency question > > The simplest way is simply to use a snapshot version of A

RE: dependency question

Can you give me an example of using a range in the pom file as a dependency ? -Original Message- From: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Thursday, April 6, 2017 2:34 PM To: Maven Users List Subject: RE: dependency question The other way is to use a version range

RE: dependency question

[mailto:russell.g...@oracle.com] Sent: Thursday, April 6, 2017 2:27 PM To: Maven Users List Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the

RE: dependency question

Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the released version instead of the snapshot. > On Apr 6, 2017, at 2:52 PM, Magnanao, Hector wrote: >

Re: dependency question

The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the released version instead of the snapshot. > On Apr 6, 2017, at 2:52 PM, Magnanao, Hector wrote: > > I have to 2 java projects a and

RE: Dependency question

The dependency:tree goal does show test dependencies by default. -Original Message- From: stanlick [mailto:stanl...@gmail.com] Sent: Wednesday, March 04, 2009 7:16 AM To: users@maven.apache.org Subject: Re: Dependency question I hear you pal, but the lawyers are concentrating on the

Re: Dependency question

You could write a plugin... it's not that hard 2009/3/4 stanlick > > I hear you pal, but the lawyers are concentrating on the fact that the > archives are on our machine following a download of the full zip. So do > you > think Maven might be able to report on them for the lawyers even though >

Re: Dependency question

I hear you pal, but the lawyers are concentrating on the fact that the archives are on our machine following a download of the full zip. So do you think Maven might be able to report on them for the lawyers even though they are not "dependencies?" Peace, Scott Stephen Connolly-2 wrote: > >

Re: Dependency question

> I realize that, but shouldn't they show up as dependencies even though they > are only depended on during testing? If you aren't building and testing Struts but merely using it, then they aren't used, so no. Wayne - To unsubsc

Re: Dependency question

Thanks bro -- I realize that, but shouldn't they show up as dependencies even though they are only depended on during testing? Peace, Scott Stephen Connolly-2 wrote: > > Those dependencies are required to *test* struts they are not required > by your project as struts has already been te

Re: Dependency question

Those dependencies are required to *test* struts they are not required by your project as struts has already been tested. -Stephen 2009/3/3 stanlick > > Thanks guys -- > > If you look at the POM for Struts 2.1.6 there are many more dependencies > than what show up running > dependency:resol

RE: Dependency question

esday, March 03, 2009 2:52 PM > To: Maven Users List > Subject: Re: Dependency question > >> I am running mvn dependency:tree and expecting a large dependency tree, >> when >> in fact all I get is what you see below.  I *know* there are more >> dependencies than this!

RE: Dependency question

If every jar present in dependency:resolve is shown in the tree, then that's all folks. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Tuesday, March 03, 2009 2:52 PM To: Maven Users List Subject: Re: Dependency question > I am running mvn dependency:

Re: Dependency question

> I am running mvn dependency:tree and expecting a large dependency tree, when > in fact all I get is what you see below.  I *know* there are more > dependencies than this!  Can someone help me out with this flags and > switches please? How do you *know* there are more dependencies? Have you tried

RE: Dependency question

Declare the dependency as test scope: ${jdbc.groupId} ${jdbc.artifactId} ${jdbc.version} test Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640 -Original Message- From: Jason Po

Re: Dependency question

As you said "When the application is deployed the jar is provided via the container". So simply try the "provided" scope ! provided dependencies are commonly used for java API (servlet, jta ...) taht are part of the JEE server runtime BUT required to compile and test. Nico. 2007/12/7, Jason Por

RE: dependency question

Thx. This worked. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 1:41 PM To: Maven Users List Subject: Re: dependency question On 10/18/06, Chen, Anning <[EMAIL PROTECTED]> wrote: > thirdparty.sun.servlet.2.3 is a thirdparty

Re: dependency question

On 10/18/06, Chen, Anning <[EMAIL PROTECTED]> wrote: thirdparty.sun.servlet.2.3 is a thirdparty jar from sun, which I packaged and installed to the repository. However, when I compile, I get "package javax.servlet does not exist". Is there something else I have to setup to add the classes in t

Re: Dependency question: Designate class from jar instead of whole jar?

I do not think it is possible although wrting a plugin to do just that should be a piece of cake. On 7/8/06, Chris Wall <[EMAIL PROTECTED]> wrote: This might be an odd request, but does Maven allow you to designate a class or set of classes within a jar as a dependency? The use case is that I'd

Re: Dependency question

Craig is spot on here - you use nextVersion-SNAPSHOT in both currentVersion ad dependency versions until it is released. Some extra things to note: - jar:deploy-snapshot is deprecated. In the latest artifact plugin, jar:deploy will behave that way if the version contains SNAPSHOT, or behave like a

Re: Dependency question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All my answers assume you're using Maven 1.0.2. On Aug 4, 2005, at 10:22, Jamie Bisotti wrote: - I have two active, rapidly changing, projects, A & B, I'm going to build and deploy to an in-house remote repository. - B depends on A. - Currently, A'

Re: dependency question

Gisbert Amm wrote: Gisbert Amm wrote: Isn't an easier way in Maven to resolve the full path of the dependency? Missed the closing bracket: ${pom.getDependencyPath('atifactId:groupId')} Even worse: Wrong order of elements: ${pom.getDependencyPath('groupId:artifactId')} Gisbert --

Re: dependency question

Gisbert Amm wrote: Isn't an easier way in Maven to resolve the full path of the dependency? Probably this: ${pom.getDependencyPath('atifactId:groupId') Missed the closing bracket: ${pom.getDependencyPath('atifactId:groupId')} ^ Gisbert --

Re: dependency question

Janos Mucsi wrote: I declare an ear artifact in my project.xml: opcert USOpcert ${pom.currentVersion} ear In maven.xml I want to resolve its full path so that I can pass it to an external script like this: *${home.dir}*${maven.repo.local}/${dependency.gr