Hello,
I am forwarding this to the dev list because it did not get any
attention on the users list. I guess the dev list is more appropriate
for this anyways.
Should I open a Jira? Thanks for any feedback.
Thanks,
Reinhard
Original-Nachricht
Betreff:Possible
Hi,
There is a bug already, see[1].
Thanks,
Stéphane
[1] http://jira.codehaus.org/browse/MWAR-187
On Tue, Jul 7, 2009 at 9:31 AM, Reinhard Nägele reinhard.naeg...@mgm-tp.com
wrote:
Hello,
I am forwarding this to the dev list because it did not get any attention
on the users list. I guess
Hi,
According the rst plugin page [1], it uses generated-site dir.
Unfortunately, the PDF plugin doesn't handle this dir right now.
Please create an issue [2]. A patch is always welcome!
Cheers,
Vincent
[1] http://jrst.labs.libre-entreprise.org/maven-jrst-plugin/jrst-mojo.html
[2]
Le Tue, 7 Jul 2009 05:42:45 -0400,
Vincent Siveton vincent.sive...@gmail.com a écrit :
Hi,
According the rst plugin page [1], it uses generated-site dir.
Unfortunately, the PDF plugin doesn't handle this dir right now.
Please create an issue [2]. A patch is always welcome!
Hi :)
We made
Hi,
On Fri, Jul 3, 2009 at 10:21 AM, Jukka Zittingjukka.zitt...@gmail.com wrote:
BTW, the copyright year in the NOTICE file should (AFAIK) be the year
of publication of the compilation (e.g. the jar artifact) instead of
the range of years of during which the contents of the compilation
have
I'm not sure I agree with this change. Why should it just be the present
year? If the jar contains schemas or other works that are copyright over the
entire range, why would it NOT be the full range?
Dan
On Tue July 7 2009 11:15:23 am Jukka Zitting wrote:
Hi,
On Fri, Jul 3, 2009 at
On Tue July 7 2009 11:22:38 am Daniel Kulp wrote:
I'm not sure I agree with this change. Why should it just be the present
year? If the jar contains schemas or other works that are copyright over
the entire range, why would it NOT be the full range?
The text on the apache legal page
Hi Vincent,
Author: vsiveton
Date: Mon Jul 6 12:38:12 2009
New Revision: 791464
URL: http://svn.apache.org/viewvc?rev=791464view=rev
Log:
o added MavenOpts for the invoker
Modified:
Hello,
I have a plugin which needs to download copy somewhere the transitive
dependencies of the project's dependencies (at least level 1, I'll see about
the rest).
So I have this: project - dependencies - transitive dependencies.
I extracted artifacts from the direct dependencies, so this part
On 08/07/2009, at 2:25 AM, Benjamin Bentmann wrote:
Modified:
maven/plugins/trunk/maven-javadoc-plugin/src/main/java/org/
apache/maven/plugin/javadoc/AbstractFixJavadocMojo.java
maven/plugins/trunk/maven-javadoc-plugin/src/test/java/org/
I think that the codebases are diverging enough that it makes sense to
separate them. I'd only say we should do this if we move both,
though...and I guess we'd need to move the maven 2.x branches over with
maven/* as well.
+1
-john
Brett Porter wrote:
Hi,
I did some of the branch and
Brett Porter wrote:
In the spirit of fresh start, does it make sense for moving
components/trunk to maven3/trunk in SVN?
+0
There's already a maven-1 directory so for the sake of consistency I
would expect maven-X instead of mavenX.
Benjamin
Sure, that sounds fine for consistency. I do think this is a good idea
in concept, though.
Benjamin Bentmann wrote:
Brett Porter wrote:
In the spirit of fresh start, does it make sense for moving
components/trunk to maven3/trunk in SVN?
+0
There's already a maven-1 directory so for the
On Jul 6, 2009, at 6:52 PM, Brett Porter wrote:
Hi,
I did some of the branch and version maintenance I mentioned in the
other mail.
In the spirit of fresh start, does it make sense for moving
components/trunk to maven3/trunk in SVN? If so, would someone
actively working on it like to
Hi Costin,
I assume you have a project defined in your plugin's mojo, i.e.:
/**
* The Maven Project
*
* @parameter expression=${project}
* @required
* @readonly
*/
private MavenProject project;
Then getting *all* the dependencies (including the transitive ones) of
your project is as
Take a look at the maven-dependency-plugin copy-dependencies code,
this is pretty much exactly what you're trying to do. There are
filters that are in a common jar you can reuse to filter out
transitivity etc.
On Tue, Jul 7, 2009 at 6:21 PM, Samuel Le
Berrigaudsamuel.lb.w...@gmail.com wrote:
Hi
I have a massive checkin coming and when I'm finished that I'll sync
up with Benjamin and swizzle the branches.
On 7-Jul-09, at 2:44 PM, Ralph Goers wrote:
On Jul 6, 2009, at 6:52 PM, Brett Porter wrote:
Hi,
I did some of the branch and version maintenance I mentioned in the
other
Hi,
I have developed a maven plugin for Jlint 3.1 and want to contribute the
plugin code back to the maven project. I've gone through the maven
developer documentation, but somehow cannot find instruction related to
contributing plugin source code.
Can someone please point me to any instructions
18 matches
Mail list logo
