The Maven team is pleased to announce the release of the Apache Maven GPG
Plugin, version 1.6
Signs the project artifacts with GnuPG.
http://maven.apache.org/plugins/maven-gpg-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-gpg
This is exactly the situation that the plugin I referenced resolves :)
https://github.com/basepom/duplicate-finder-maven-plugin
On Jan 19, 2015, at 8:47 AM, Adrien Rivard wrote:
> Then you need to explicitely exclude one of them. Eclipse can help for that
> via the pom editor in the dependency H
Ok, then I know. Tanks for your help, Hervé!
I guess this case is closed then, although I'd say this is a bug in the
default skin.
Cheers,
Mikko.
Den 19 jan 2015 22:27 skrev "Hervé BOUTEMY" :
> Hi,
>
> If you look at output when running "mvn site":
> [INFO] Rendering site with
> org.apache.maven.
Hi,
If you look at output when running "mvn site":
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
I tried and changed the skin used, by adding followin content in site.xml
org.apache.maven.skins
maven-fluido-skin
1.3.0
then the width and hei
Is there a way to get the archive section of the maven-jar-plugin to include
test scope dependencies in the classpath? I'm trying to use the test-jar goal
to create a test jar alongside my main jar. I've used two different executions
of the maven-dependency-plugin to put dependencies with runt
Then you need to explicitely exclude one of them. Eclipse can help for that
via the pom editor in the dependency Hierarchy tab.
On Mon, Jan 19, 2015 at 9:24 AM, Kevin Burton wrote:
> The main situation I see is when the artifact and group ID differ …
>
> so an older version of jdom used just jd
That is trickier to find.
I don't think that my IDE will find that one!
Ron
On 19/01/2015 3:24 AM, Kevin Burton wrote:
The main situation I see is when the artifact and group ID differ …
so an older version of jdom used just jdom and the newer version used
org.jdom and then I ended up with bot
If you use an IDE with Maven support it will tell you what version has
been resolved by Maven and will show you the source(s) of the conflict
in your transitive dependencies.
Eclipse/STS is free and includes m2e so you get this solved OOTB with no
additional work required (besides opening the
Hi,
I'm pretty new to this, so I guess I'm using the "default" skin? I haven't
configured anything
special involving a choice of skin.
I've attached to this e-mail a gzipped tar file with a little Maven project
to demostrate the issue.
The project is based on the "maven-archetype-quickstart" (ver
The main situation I see is when the artifact and group ID differ …
so an older version of jdom used just jdom and the newer version used
org.jdom and then I ended up with both :)
On Sun, Jan 18, 2015 at 10:31 PM, Adrien Rivard
wrote:
> Hi,
>
> if youre artifacts have the same artifactId/group
10 matches
Mail list logo