Does
http://svn.codehaus.org/mojo/trunk/mojo/extra-enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/AbstractResolveDependencies.java
help
you?
Cheers
2014/1/6 Laird Nelson ljnel...@gmail.com
On Sun, Jan 5, 2014 at 3:56 PM, Laird Nelson ljnel...@gmail.com wrote:
What is the
I have written my own maven mojo plugin and wish to use the truncated name
instead of the long name to invoke it, like so:
Instead of
mvn org.apache.maven.plugins:maven-pce-plugin:pull
I want use:
mvn pce:pull
But even though I put it under group 'org.apache.maven.plugins' and named
it
On 6 January 2014 12:40, Omar@Gmail omarnet...@googlemail.com wrote:
I have written my own maven mojo plugin and wish to use the truncated name
instead of the long name to invoke it, like so:
Instead of
mvn org.apache.maven.plugins:maven-pce-plugin:pull
I want use:
mvn pce:pull
But
Hello again,
OK, I suspected that I get a lot of replies on this :-).
From experience in other forums I also expected to have people tell me to go
screw myself, but that has not happened. There are apparently only
professionals here! That said, there some very good replies and explanations
I'll start with the latter. The arguments about quality I just don't buy. We
are only talking poms here. Whatever is in the poms says nothing about the
quality of the software itself.
I agree the pom says nothing about the quality of the software.
However, having a standard mechanism for
The arguments about quality I just don't buy. We are only talking poms
here. Whatever is in the poms says nothing about the quality of the
software itself.
Quality of metadata. POM serve as metadata in this case, so, I'd rather
say Central enforces quality of metadata (ie. POM properly
6 jan 2014 kl. 14:10 skrev Tamás Cservenák ta...@cservenak.net:
The arguments about quality I just don't buy. We are only talking poms
here. Whatever is in the poms says nothing about the quality of the
software itself.
Quality of metadata. POM serve as metadata in this case, so, I'd
Thanks Stephen,
What you suggest sounds like good practice (not sure why though) however
not a fix for my issue.
The fix is as follows: - somehow your response inspired me :)
In the pom.xml file of the custom plugin there is a plugin configured
maven-plugin-plugin in that plugin add
On Mon, Jan 6, 2014 at 1:05 AM, Baptiste Mathus bmat...@batmat.net wrote:
Does
http://svn.codehaus.org/mojo/trunk/mojo/extra-enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/AbstractResolveDependencies.java
help you?
Yes; I see that it uses maven-artifact-resolver. If indeed
On Mon, Jan 6, 2014 at 5:44 AM, Laird Nelson ljnel...@gmail.com wrote:
On Mon, Jan 6, 2014 at 1:05 AM, Baptiste Mathus bmat...@batmat.netwrote:
Does
http://svn.codehaus.org/mojo/trunk/mojo/extra-enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/AbstractResolveDependencies.java
I am assuming that you are putting this in Central so I can easily use
it without having to worry about the effect on my build process or
without having to get into your sources and dependencies to build my app
and I have appropriate license agreements included so I know what I am
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
I running a test using intelliJ13 and it would not run I did a mvn clean
test and got the following results (see video)
https://www.dropbox.com/s/44geyj4bhthi8mb/Pom%20File%20problem%20in%20maven.
mp4
How do I fix this.
Speak soon
Jacqueline George
Of course, you could say that about Gradle, too. And ant now does have the
ability to use those dependency features.
I went through this when creating my video course (not in the sig because this
is work email). It’s not clear to me that you can make a one sentence
description that will
When people ask me what Maven is, I tell them it's a build and library
management tool. If I take it a step further I explain it manages library
and dependency versions akin to how SCM systems manage source code. It's
not a perfect analogy but I find it works for a lay description.
Richard Sand
The goal is to put this on the front page so that people know enough to
decide if they need/want to dig deeper
On Monday, 6 January 2014, Russell Gold wrote:
Of course, you could say that about Gradle, too. And ant now does have the
ability to use those dependency features.
I went through
The mention of convention over configuration really is key. The biggest
problem I see when people switch from Ant to Maven is they really don't
want to buy into the convention philosophy. Even if they are willing to
do so, their project usually is not laid out in a complimentary way and
it
I think that the target has to be people deciding whether to try Maven.
They initially want to know what it does and why it is better than Ant
or whatever they are using now.
Trying to teach Maven in a single sentence is too much to ask.
Maven is a build tool which consumes and produces
On Monday, 6 January 2014, Ron Wheeler wrote:
I think that the target has to be people deciding whether to try Maven.
They initially want to know what it does and why it is better than Ant or
whatever they are using now.
Trying to teach Maven in a single sentence is too much to ask.
Maven
Several sentences sounds good. But here’s another question. Comparing Maven to
ant is almost too easy in terms of advantages. Is gradle now a serious
competitor (I had been working on converting an enormous project to maven, but
the architect decided to switch to gradle, so I am particularly
On 06/01/2014 3:08 PM, Russell Gold wrote:
Several sentences sounds good. But here’s another question. Comparing Maven to
ant is almost too easy in terms of advantages. Is gradle now a serious
competitor (I had been working on converting an enormous project to maven, but
the architect decided
I missed this earlier - I agree. The biggest advantage I find with Maven over
tools that have adopted its dependency management philosophy is that every
build essentially follows a predictable pattern, rather than being free form. A
new developer automatically knows how to invoke it. That is
Hi Russell,
Russell Gold wrote:
Is gradle now a serious competitor (I had been working on converting
an enormous project to maven, but the architect decided to switch to
gradle, so I am particularly sensitive to the issue). I can see some
superficial advantages of gradle that might appeal to
Hi there,
I have two resource files in the same dir: a.job and b.job. They have the
following line in both of them:
snip
mongo.home=${mongo.cli.home}
/snip
where mongo.cli.home is a property defined in a filter file.
When I run clean package, a.job gets filtered, the other does not. This is
The Maven team is pleased to announce the release of the Apache Maven
Jarsigner,
version 1.3.1
This component provides some utilities to sign/verify jars/files in your Mojos.
http://maven.apache.org/shared/maven-jarsigner/
To use the Maven Jarsigner, add the following dependency to your
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.1.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.1.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant
Can someone explain what is the difference between these two plugins.
Based on the description, they do the same
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
vs
This component provides some utilities to sign/verify
Ok, forget about the first question. I get know what is meant by shared.
i usually call this common so i missed it.
But still, the second question remains: how to just clear all signatures
from a jar. The removeExistingSignatures parameter states that the
resulting JAR will appear as being
I don't want a religious war. If Gradle or ANT are a better fit for the way
some people think about building software... well good for them... and the
faster we can help them realise that Maven takes a different tack the
better.
I happen to believe that the power of Maven comes from being model
maven-jarsigner-plugin is a plugin
apache maven shared jarsigner is the common dependency that is used by the
plugin... because signing jars is something that other plugins may want to
do, this dependency provides an API to do that signing
On 6 January 2014 20:56, alejandro.e...@miranda.com
Hi Tommy et al,
here's another option for you:
You can leverage bintray.com to sync to Maven Central from there. For
starter, you'll just get your artifacts to Maven Central in more sane way -
no parent poms, no maven-release-plugin, no 20 pages guides. Just get your
artifacts to Bintray,
Le 6 janv. 2014 22:34, Stephen Connolly stephen.alan.conno...@gmail.com
a écrit :
I don't want a religious war. If Gradle or ANT are a better fit for the
way
some people think about building software... well good for them... and the
faster we can help them realise that Maven takes a different
On 6 January 2014 22:18, Thomas Broyer t.bro...@gmail.com wrote:
Le 6 janv. 2014 22:34, Stephen Connolly stephen.alan.conno...@gmail.com
a écrit :
I don't want a religious war. If Gradle or ANT are a better fit for the
way
some people think about building software... well good for
Le 6 janv. 2014 23:25, Stephen Connolly stephen.alan.conno...@gmail.com
a écrit :
On 6 January 2014 22:18, Thomas Broyer t.bro...@gmail.com wrote:
Le 6 janv. 2014 22:34, Stephen Connolly
stephen.alan.conno...@gmail.com
a écrit :
I don't want a religious war. If Gradle or ANT are a
Barrie Treloar wrote
When you build Product X the libraries A, B and C should already
exist. You dont want to rebuild them just to build Product X, that
will slow down your development process.
Ideally A, B, and C are released versions, but if you find a bug in
them then you will be using
On 7 January 2014 09:42, erich8 eric.herrm...@intermedix.com wrote:
Barrie Treloar wrote
When you build Product X the libraries A, B and C should already
exist. You dont want to rebuild them just to build Product X, that
will slow down your development process.
Ideally A, B, and C are
I am not sure that you want to start a range war in the opening paragraph.
If there is a concise second or third sentence that clearly explains the
difference between Ant and Maven, it would be a great idea to add that.
If Gradle is likely to be in the running for a new developer, it might
be
During active development, we have found that libraries A,B and C should
be released as SNAPSHOTs with a spec and warranty from the developer.
These may be informal but without this, the developer of X has a hard
time testing if A,B and C are changing specification/behaviour without
warning.
When the project is relatively new and the internally-developed dependency
A is no where near being mature, nearly every change being made to
Project X requires a corresponding change to A. At this point in the
development cycle (and for many months in the foreseeable future) I actually
/do/
On 7 January 2014 15:29, Mark Derricutt m...@talios.com wrote:
When the project is relatively new and the internally-developed dependency
A is no where near being mature, nearly every change being made to
Project X requires a corresponding change to A. At this point in the
development cycle
41 matches
Mail list logo
