On Mon, Jan 16, 2012 at 12:34 AM, Barrie Treloar baerr...@gmail.com wrote:
2012/1/16 Arnaud Héritier aherit...@gmail.com:
Thanks a lot for this hard wok Barrie
yes it was my problem too Robert.
ITs are now very difficult to use/maintain and sadly are covering only
the
fact that what
The marriage of eclipse and maven poses fundamental challenges that
don't exist for Intellij or Netbeans.
Of the three major Java IDE's, only Eclipse incorporates its own
classpath and compiler system. IJ and NB 'just run maven' and analyze
the output for display. Eclipse, on the other hand,
Hello,
So it looks we don't have any issues here.
I will proceed a non RC release procedure tomorrow.
Thanks for your testing time !
2012/1/11 Robert Scholte apa...@sourcegrounds.com:
looking good.
Tested on a lot of mojo projects.
-Robert
On Tue, 10 Jan 2012 15:31:12 +0100, Jeff MAURY
On 15 January 2012 11:11, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
personally i think we need to draw a line in the sand for all plugins...
2.2.1 is the best line at the moment imho...
+1
2.1.0 and 2.2.0 are not recommended
On 16 January 2012 15:45, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 15 January 2012 11:11, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
personally i think we need to draw a line in the sand for all plugins...
2.2.1 is
Hi all guys,
I am having troubles with the skin (lst check before re-proposing the
skins releases) and while trying to apply fluido on Apache Commons I
noticed that, attaching a site.xml descriptor to a parent, while the
body.head element is inherited from cildren, body.footer is not.
Did I miss
So what you're actually saying:
Let's force people to NOT use Maven-2.1.0 of 2.2.0 by setting the
prerequisite for maven to 2.2.1
And hence, we get the Doxia verison we want.
That would solve two problems at once.
-Robert
On Mon, 16 Jan 2012 16:47:39 +0100, Stephen Connolly
Well actually I'd say force people to use 2.2.2 after rolling a 2.2.2
that does not barf on the 3.0.3 metadata in local repo... such a 2.2.2
does not need to understand the extra metadata, just not barf on it
(i.e. copy the 2.2.1 tag, make the metadata forgiving, release 2.2.2
so that the changes
I am developing a Maven 2.2.1 plugin that will leverage JAR file(s) that
vary depending on the target runtime system.
These two examples describe the logic.
1) When the Maven plugin executes on a Linux box, it is going to
fork off a Java application with a CLASSPATH that includes: a.jar
While fixing MEAR-60 is something very good, I am a bit worried about the
lack of tests. There's only one IT.
Other than that, looks good except a few things I've seen in recent commits
but I have contacted 'rfscholte' to get some feedback.
My +1
Thanks Dennis!
S.
On Thu, Jan 12, 2012 at
Hi,
The vote has passed with the following result :
+1 (binding): Olivier Lamy, Dennis Lundberg, Hervé Boutemy, Stephane Nicoll
I will promote the artifacts to the central repo.
On 2012-01-12 23:40, Dennis Lundberg wrote:
Hi,
We solved 4 issues, including
[MEAR-60] Improve support for
Hi
When looking through the build log for the EAR Plugin release, I noticed
a couple of errors like this one:
---
[INFO] Generating JavaDocs report--- Maven Javadoc Plugin 2.8
[ERROR] Error fetching link:
http://xmlunit.sourceforge.net/apidocs/package-list. Ignored it.
[INFO]
Loading source
I'm eager to get a release that has some of the fixes already on trunk,
particularly those related to aggregating javadocs using dependencies.
Does anyone have any objection to me calling a vote to release 2.8.1
with the seven closed issues that are currently assigned to it?
The release
I would love for those changes to go out..
On 12-01-16 12:42 PM, John Casey wrote:
I'm eager to get a release that has some of the fixes already on
trunk, particularly those related to aggregating javadocs using
dependencies.
Does anyone have any objection to me calling a vote to release
Hi Dennis,
Check the
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocLink(MavenProject)
It will build a javadoc link relative to the project URL as described in
the pom of the dependency.
-Robert
On Mon, 16 Jan 2012 21:27:07 +0100, Dennis Lundberg denn...@apache.org
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.7
The most noteworthy in this release is the support for skinny WAR files.
It is one of the most voted on issues in our JIRA with 50 votes. We
would love to hear your feedback on this new feature.
The plugin
Sounds good
On Monday, January 16, 2012, John Casey jdca...@commonjava.org wrote:
I'm eager to get a release that has some of the fixes already on trunk,
particularly those related to aggregating javadocs using dependencies.
Does anyone have any objection to me calling a vote to release 2.8.1
17 matches
Mail list logo
