Hi Benoît,
Hope I'm not going to be flammed for freshing up that old discussion we had a
little more than a year ago :-)
I had a customer that had a similar requirement (And no ... there was no way to
work around the requirement to release modules with separate versions). I
actually did implem
HI Benoit,
Given you scenario, it really sounds as though your project is essentially a
single project, and your modules should just inherit the version from the
parent. Maven tools, especially the release plugin, make this easy.
If not, I would regard what you are creating is a set of interrel
The Maven team is pleased to announce the release of the Apache Maven
Jarsigner,
version 1.2
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 project
The Apache Maven team is pleased to announce the release of the
maven-shared-utils, version 0.5
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
:
lots of
> Date: Fri, 20 Dec 2013 21:37:01 -0800
> From: poubelle2...@limule.com
> To: users@maven.apache.org
> Subject: RE: Maven for C/C++ development usable as well? Hudson server?
>
> > I must admit that even with this patch, I did not success to convince my
> > colleagues (who were using Borland C++ u
Thanks. We are using osgi. I'd be happy if I could just exclude all
third-party libs from the javadoc generation.
On Fri, Dec 20, 2013 at 11:13 PM, Mirko Friedenhagen <
mfriedenha...@gmail.com> wrote:
> Hello Richard,
>
> a wild guess: you have the same packages included by different dependenci
For me PDF plugin is working with Markdown:
org.apache.maven.plugins
maven-pdf-plugin
1.2
pdf
site
pdf
${project.build.directory}
Hi,
At least I can produce PDF from Markdown:
org.apache.maven.plugins
maven-pdf-plugin
1.2
pdf
site
pdf
${project.build.directory}
