Will do. Thanks for the response.
Howard
On 1/30/15 6:32 PM, Dan Tran wrote:
additionalClasspathElements is a list and it does not accept arguments via
system properties
[1]
http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html#additionalClasspathElements
There is a feature request to
Hi,
isn't it an option to update to 3.2.5 ? Have you tried it ?
On 2/2/15 10:27 AM, Bichov, Vitaly wrote:
Hi,
There is this (http://jira.codehaus.org/browse/MNG-5315) bug.
The bug has a fix proposal and a workaround.
Due to some restrictions I can't apply the workaround on my environment.
Hi,
There is this (http://jira.codehaus.org/browse/MNG-5315) bug.
The bug has a fix proposal and a workaround.
Due to some restrictions I can't apply the workaround on my environment.
Will the bug be fixed in the next (3.0.6) release?
When will 3.0.6 version will be released if ever?
Thank
That's great that Jenkins does this but we need it built into Maven
directly. Our CI infrastructure is TeamCity with many hundreds of builds
and that's not going to change any time soon and we need developers to get
the same feature from the command line integrated with their IDE.
-Dave
On
Hi Karl,
Our posts crossed. We use several different Maven versions but upgrading
has always been problematic because it's hard if not impossible to upgrade
all projects to the latest. It's easy to upgrade the trunk (usually) but
we have older branches where we do not want to upgrade because we
I would add :
1) maven-eclipse-plugin is not to be used anymore. If you need it in
eclipse don't use any maven plugin but only http://eclipse.org/m2e/
2) exec-maven-plugin is not for compilation, it's for execution inside a
maven build (comment says otherwise). You seem to have mixing it with
Hi,
first rule in Maven keep the conventions[1]...meaning convention over
configuration:
source code:
src/main/java
resources for production code:
src/main/resources
Tests:
src/test/java
resources for tests:
src/test/resources
move your files to the correct location
etc.
Remove the
Hi David,
On 2/2/15 4:05 PM, David Hoffer wrote:
On a somewhat related note, one feature I'd like to see added to Maven is
the ability to easily upgrade the version of Maven used. I want the build
to specify the version of Maven used and automatically download and use
that version.
If you
Hi,
I can’t compile my java class using my |pom.xml|, and I can’t find the
problem. Can anyone help me to point what it is wrong?
Directory structure
|hadoop-wordcount-coc$ tree
.
├── output.txt
├── pom.xml
└── src
└── org
└── apache
└── hadoop
└──
On a somewhat related note, one feature I'd like to see added to Maven is
the ability to easily upgrade the version of Maven used. I want the build
to specify the version of Maven used and automatically download and use
that version. Currently it's the system that determines what version is
I have to admit, this would be pretty cool.
However, Jenkins already has this functionality. You specify the Maven version
in the job and configure Jenkins to automatically download that version (it
does with this with Java and Ant as well).
I highly suggest you look into it. Even running it
* We're studying Jira migration from Codehaus to Apache for better
end-users
consistency, since we've got feedback about users lost when requiring
to
create a Jira account at Codehaus.
Thumbs up for this. Is there (ahem) a ticket to follow for progress?
James
Hi David,
unfortunately you really didn't answer my question...
From which versions of Maven would you like to update...? And what are
the problems you/devs have been faces with?
You can test it via CI ...
BTW: Jenkins was just an example for any kind of CI solution is doesn't
matter if
For the first question, there is not one answer. As an example one current
project is on 3.0.4. I did upgrade that one to 3.2.5 and I found I had to
update several plugins (unfortunately I don't recall which ones those
were). In trunk I made those changes so we could use 3.2.5 but I can't
make
On Mon, Feb 2, 2015 at 8:30 AM, David Hoffer dhoff...@gmail.com wrote:
The issue is for developers...I don't
want devs to have to constantly switch their environment around just to run
different maven versions. We often have to run both at the same time as we
are fixing something in a branch
It looks like http://mvnvm.org/ configures a system for a version of Maven
which is nice but not really what I'm asking for. What I'm asking for is
no system config. We want to run multiple Maven builds on the same box at
the same time with different Maven versions. E.g. pom specifies
Rest assured that this *will* happen in the next couple of months
On 2 February 2015 at 15:38, James Green james.mk.gr...@gmail.com wrote:
* We're studying Jira migration from Codehaus to Apache for better
end-users
consistency, since we've got feedback about users lost when
Hi,
based on the JIRA not...but i'm not sure if this is just left over cause
the text sounds like it has been solved for 3.0.5 and
3.1.0...furthermore i'm using a parallel build with 180 modules without
any issue...for a long time...Maven 3.1.1
On 2/2/15 6:58 PM, Bichov, Vitaly wrote:
You can specify a empty settings file with -s and define MAVEN_SKIP_RC,
this will avoid all system specific configs (as long as nobody modifies
the maven program folder).
However to my experience sooner or later you do need some specific
landscape settings in the settings.xml file. So it is a
Here is a link to how Gradle does this
http://gradle.org/docs/current/dsl/org.gradle.api.tasks.wrapper.Wrapper.html
looks like it does a build tool download and builds against that version.
Not sure if this allows simultaneous builds to use different versions but I
assume it does.
-Dave
On Mon,
Hi Chris,
On 2/2/15 6:23 PM, Curtis Rueden wrote:
Hi David,
I feel compelled to throw out the obligatory It's open source; scratch
your itch response here. It sounds like your team could really use this
feature, you seem to think it would be easy to implement, you have an
existing template for
Hi David,
I feel compelled to throw out the obligatory It's open source; scratch
your itch response here. It sounds like your team could really use this
feature, you seem to think it would be easy to implement, you have an
existing template for how another related build tool already does this,
Hello,
In practise it seems to be a small issue (at least for us). Older
branches are seldomly touched and nearly all work with any 3.x
versions (the main reason for this is, that we prefer to use Eclipse
with its internal default maven). My main pain of switching (mostly
JVM) comes from working
Hi Curtis,
I understand the obligatory reply. I want to point out I'm not saying it
would be easy to implement...just that the concept/feature seems simple. I
have no idea if the seemingly simple concept would be simple to
implement...that would probably take deep knowledge of how Maven is
Hi,
Was the issue resolved in 3.2.5?
Thank you,
Vitaly
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: יום ב 02 פברואר 2015 15:27
To: users@maven.apache.org
Subject: Re: maven 3.0.6 release date
Hi,
isn't it an option to update to 3.2.5 ? Have you tried
Hi,
I think you either changes Maven or its wagon-library.
See https://jira.codehaus.org/browse/MNG-5605 for details.
Root cause is https://jira.codehaus.org/browse/WAGON-429
thanks,
Robert
Op Sat, 31 Jan 2015 21:05:25 +0100 schreef Kevin Burton
bur...@spinn3r.com:
I’m really confused
26 matches
Mail list logo
