Well if you wanted to explore this, the way I would come at this is via
maven's toolchains api
Thus if the SCM tool had an entry for the HG executable in
~/.m2/toolchains.xml then that path would be used, otherwise whatever is
resolved from the path would get resolved.
Working on this will
Hi.
Is it possible to enable the fetching of snapshots as dependencies in
settings.xml, as opposed to using a distributionManagement element in
the project's pom file?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
On Thu, 20 Dec 2012 12:18:11 +
org.apache.maven.u...@io7m.com wrote:
Hi.
Is it possible to enable the fetching of snapshots as dependencies in
settings.xml, as opposed to using a distributionManagement element in
the project's pom file?
*ahem*
Fixed my own problem. Dependencies
Hi.
I can't find any documentation on the Maven site about snapshots. I'm
trying to determine whether a snapshot is considered to be older or
newer than the version number prefix.
Is 1.0.0-SNAPSHOT considered to be the current HEAD, having a
theoretical 1.0.0 at some point in the past, or is
I don't have the time to check the doc but if it's not in, this is a big
error (don't hesitate to open an issue)
A SNAPSHOT is the development version before producing the release.
A SNAPSHOT is older than its release
1.0.0-SNAPSHOT - 1.0.0- 1.0.1-SNAPSHOT - 1.0.1 - ..
Cheers
On Thu, Dec 20,
On Thu, Dec 20, 2012 at 3:02 PM, org.apache.maven.u...@io7m.com wrote:
Hi.
I can't find any documentation on the Maven site about snapshots. I'm
trying to determine whether a snapshot is considered to be older or
newer than the version number prefix.
Is 1.0.0-SNAPSHOT considered to be the
x.x.x-SNAPSHOT is the precursor to x.x.x The SNAPSHOT value is used to allow
the version to refer to the 'latest' code along a branch and provides no
guarantee that the code is stable or unchanging. The release process changes
x.x.x-SNAPSHOT to x.x.x, freezes the code to provide a guarantee that
On Thu, 20 Dec 2012 15:08:26 +0100
Arnaud Héritier aherit...@gmail.com wrote:
I don't have the time to check the doc but if it's not in, this is a big
error (don't hesitate to open an issue)
A SNAPSHOT is the development version before producing the release.
A SNAPSHOT is older than its
Thanks Wayne,
Double checked with the network guys here and they assured me we are not
behind a proxy.
At this point I am just confused. Have tried various versions of Java and Maven
only to
have this same problem with commons-collections.ExtendedProperties. Oddly, I
can find the
jar file in
Is it only when you run this one plug-in.
Does maven clean work
Are you using Eclipse or some IDE to develop your code? (Eclipse/STS
from Springsource comes ready to run maven).
On 20/12/2012 10:58 AM, Kammer, John wrote:
Thanks Wayne,
Double checked with the network guys here and they
maybe a bit simpler with something similar to svn/git with
$HOME/.scm/svn-settings.xml / $HOME/.scm/git-settings.xml.
See http://maven.apache.org/scm/subversion.html and
http://maven.apache.org/scm/git.html
a simple $HOME/.scm/hg-settings.xml
with
hg-settings
We already have toolchains to handle this type of thing, plus toolchains
only needs one cli param to use an alternative one, whereas your scheme
just keeps on expanding
On Thursday, 20 December 2012, Olivier Lamy wrote:
maybe a bit simpler with something similar to svn/git with
I just noticed that our large project has a lot of poms with dependencies with
no version specified. I'd like to detect that at build time. I see that the
enforcer plugin comes close out of the box, with the requirePluginVersions
rule. However, there doesn't appear to be a
Hi,
if you have really dependencies without version the build will fail in Maven.
This sounds more like having a dependencyManagement block somewhere in the
parents which define the appropriate versions which is ok.
The question is what you like to achieve?
Kind regards
Karl-Heinz Marbaise
Well, you're going to laugh but I ended up installing a Jenkins
plugin for setting environment variables and forced it to add HG to the
PATH (of the job, not the entire system). In an ideal world I would have
liked to pass an extra parameter to Maven -Dhg.path=some-full-path as
opposed
Hi Ron,
I can run mvn clean once I've gotten a sample pom file and that works fine.
I've never gotten mvn archetype:generate to run successfully, that and other
targets blow up with the problem finding the ExtendedProperties class in the
commons-collections jar.
So far I've been working
Hi Olivier,
I've created a JIRA issue here
http://jira.codehaus.org/browse/MSHARED-269with two project used to
reproduce the problem.
Thanks for the help guys,
Baptiste
2012/12/19 Olivier Lamy ol...@apache.org
Can you create a jira entry with a sample ?
2012/12/18 Baptiste Gaillard
I would suggest downloading Eclipse/STS since it comes with a fully
configured and properly set up Maven.
Use the Eclipse - New=Project to get started.
It looks like it is a problem with that plug-in. We never use it so I
can not give you much help on that and you don't need it anyway.
If
Anyone know of a way to set environment variables that will be used while
Maven is running?
I've tried the following, but it doesn't get picked up by subsequent plug-in
executions:
plugin
groupIdorg.codehaus.mojo/groupId
Thanks Ron,
Working through Eclipse is definitely superior. Turns out it has identified
some of the jar files as being corrupted (commons-collections among those).
Trying
to delete the bad ones and trying again. At least I am making progress
-- john
--
I would suggest
Suppose I have the following:
A - B,C,D,E
B - F[1.1]
C - F[1.0.1]
D - F[1.2]
E - F[1.1]
I know of 2 ways to resolve the transitive dependency conflict:
1. Add excludes to all but 1 of A's dependencies
2. Use dependencyManagement to specify the version of F that I really
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Thursday, December 20, 2012 9:17 AM
To: Maven Users List; users@maven.apache.org
Subject: Re: Detecting any dependencies specified without versions?
Hi,
if you have really dependencies without version
I created this bug report:
Maven Getting Started Guide should clarify SNAPSHOT qualifier of
'version' element precedes release
http://jira.codehaus.org/browse/MNGSITE-167
Dan
On 12/20/2012 12:47 PM, users-digest-h...@maven.apache.org wrote:
Subject:
Re: 1.0.0-SNAPSHOT considered older
The Maven team is pleased to announce the release of
maven-shared-utils, version 0.2
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
with improvements:
the Maven core reference doc is http://maven.apache.org/ref/3.1-
SNAPSHOT/maven-
artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
Le jeudi 20 décembre 2012 14:02:02 org.apache.maven.u...@io7m.com a écrit :
Hi.
I can't find any documentation on the Maven site about
#2
/Anders
On Thu, Dec 20, 2012 at 4:37 PM, Ben Noland b...@clearwateranalytics.comwrote:
Suppose I have the following:
A - B,C,D,E
B - F[1.1]
C - F[1.0.1]
D - F[1.2]
E - F[1.1]
I know of 2 ways to resolve the transitive dependency conflict:
1. Add excludes to
26 matches
Mail list logo
