Just a heads-up for whoever feels responsible for this: trying to build
maven 2.1 with jdk 1.4, I get:
bad class file:
/home/lukas/.m2/repository/org/apache/maven/artifact/maven-artifact/3.0-SNAPSHOT/maven-artifact-3.0-SNAPSHOT.jar(org/apache/maven/artifact/Artifact.class)
class file has
Trying to build maven 2.1 with java 5:
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 41.793
sec FAILURE!
testRunningScmPlugin(org.apache.maven.embedder.execution.EmbedderUsingScmPluginTest)
Time elapsed: 41.704 sec FAILURE!
junit.framework.AssertionFailedError:
+1
-Lukas
Vincent Siveton wrote:
Hi,
I'd like to release (again) maven-clean-plugin 2.2. All artifacts
respect the Apache release rules (Thanks Dan).
This release fixes some bugs and makes some improvements. The last
release was made over 1 year ago.
Release Notes:
saying you are using site-plugin beta-6 with doxia beta-1? I
haven't been able to make the two work together yet...
Hervé BOUTEMY wrote:
Le mercredi 28 novembre 2007, Lukas Theussl a écrit :
Herve,
Thanks for fixing this! Just two questions:
Why do we need a separate method
Bad news: jaxen is used in the core [1]
Good news: Arnaud had already upgraded a lot of deps and attached
patches (MAVEN-1797 - 1805), among them for jaxen [2]
Should we work on m1.1.1 with only upgraded deps?
:)
-Lukas
[1] http://maven.apache.org/maven-1.x/dependencies.html
[2]
+1
-Lukas
Dennis Lundberg wrote:
Hi,
I'd like to release maven-site-plugin 2.0-beta-6.
We have resolved 36 issues since the last release, 18 months ago.
Release Notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=12151
Tag:
+1
-Lukas
Vincent Siveton wrote:
Hi,
Always in the preparation of the Maven Clean Plugin release, I would like to
release the file-management:1.2
The last release was done around one year ago.
Staging repo:
http://people.apache.org/~vsiveton/staging-repo/
Vote open for 72 hours.
Here is my
Herve,
Thanks for fixing this! Just two questions:
Why do we need a separate method in AbstractXmlSink, can't we just
remove the EOL from writeEndTag()?
And what's the reason for selecting only special tags to write no
newline? Just because they are inline elements? This doesn't solve the
+1
-Lukas
Brian E. Fox wrote:
It's that time again, finally. The RC's have been floating for a few
weeks now and no new issues have surfaced. (the packaging issues with
the uber jar have been resolved since the last vote)
The release is staged at:
+1
-Lukas
Dennis Lundberg wrote:
Hi,
I'd like to release maven-help-plugin 2.0.2.
This release fixes a couple of bugs and improves the documentation.
There are still improvements and feature requests left in JIRA, but I
feel that they can be schedules for a future 2.1 release.
The last
+1
-Lukas
Brett Porter wrote:
Alex did the work to make TestNG support pretty much fully functional
on Surefire trunk some months back and he and Dan Fabulich are now
discussing this on the surefire-dev list and looking to complete the
work. Alex is already a committer on Struts at Apache
+1
-Lukas
Vincent Siveton wrote:
Hi,
In the preparation of the Maven Clean Plugin release, I would like to
release the maven-shared-io:1.1
The last release was done around one year ago.
Staging repo:
http://people.apache.org/~vsiveton/staging-repo/
Vote open for 72 hours.
Here is my +1
[
+1
-Lukas
Brett Porter wrote:
I'd like to call a vote for Nicolas de Loof as a committer, based
primarily on his work for Archiva, but also from being active in the
general Maven community for quite some time. He has been relentlessly
testing and identifying issues and providing patches
Hardcoding is certainly not ideal. Maybe I'm mixing something up here
but in m1 I remember the problem that oversized logos messed up the
whole page formatting. I haven't checked this here, but if a user has to
supply properly sized logos anyway, then it doesn't matter. It should at
least be
+1
-Lukas
Dennis Lundberg wrote:
Hi,
Here comes the follow up to the doxia-1.0-alpha-10 release. This time
the vote is for releasing doxia-sitetools-1.0-alpha-10.
Release Notes:
None.
The only real change is that this release uses doxia-1.0-alpha-10
instead of alpha-9.
Tags:
+1
-Lukas
Dennis Lundberg wrote:
Hi,
Due to a couple of issues we need to release doxia-1.0-alpha-10, before
we can start using it in the plugins. This time I will release doxia and
doxia-sitetools separately, so that we don't confuse Continuum this
time. A vote for
FYI: I have fixed a few issues that were within my reach :), for the
rest I have opened a jira: http://jira.codehaus.org/browse/DOXIA-184
-Lukas
Lukas Theussl wrote:
I've just checked the output of the identity test for the docbook
module, below is a list of discrepancies (note: the identity
I've just checked the output of the identity test for the docbook
module, below is a list of discrepancies (note: the identity test
doesn't tell you where the problem is, it could be in the parser or in
the sink, or both). These are definetely bugs and I'd be happy to apply
your patches if
Forgot to mention: for a confluence sink there is a feature request open
(DOXIA-124), any interest in writing one? :)
-Lukas
Lukas Theussl wrote:
Dave Syer wrote:
I already took that approach with the patch I submitted for
DOXIA-169. The
test actually goes beyond the one for the APT
Jason van Zyl wrote:
On 25 Oct 07, at 3:21 AM 25 Oct 07, Lukas Theussl wrote:
Vincent Massol wrote:
Hi,
The APT and Confluence parsers behave differently when parsing lists.
The APT parser generates paragraph()/paragraph_() events for each
list item whereas the Confluence parser
sorry, fixed.
-Lukas
Vincent Siveton wrote:
Hi Lukas,
2007/10/26, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Author: ltheussl
Date: Fri Oct 26 05:21:38 2007
New Revision: 588621
URL: http://svn.apache.org/viewvc?rev=588621view=rev
Log:
DOXIA-176: strip leading space in section titles. Thanks to
Vincent Massol wrote:
Hi,
The APT and Confluence parsers behave differently when parsing lists.
The APT parser generates paragraph()/paragraph_() events for each list
item whereas the Confluence parser doesn't.
So my questions are:
1) Who's right? This is very important since a Sink
by itself doesn't assert anything (apart some basic
well-formedness), it only parses the document so as long as parsing is
fine, you won't break anything.
-Lukas
Lukas Theussl-3 wrote:
Hi Dave,
I am a currently active doxia committer but I'm not really familiar with
the confluence module. If you
Carlos Sanchez wrote:
you guys realize that final versions of Maven have been using Doxia
for quite some time now and the fact that it's being called alpha as
an excuse to make more API changes, which will affect the future
development of maven, instead of evolving the API in a backwards
+1
-Lukas
Dennis Lundberg wrote:
Hi,
I'd like to once more try to release maven-changes-plugin 2.0-beta-3. On
the second try, Olivier Lamy found an issue with anchors not being
properly encoded in the report. This has now been solved.
Over 20 issues have been resolved for this release.
+1
-Lukas
Carlos Sanchez wrote:
Please vote for a release of maven parent and two of the children
Maven parent 7
- upgraded remote resources plugin and apache resources bundle to latest release
- added javadoc urls
- added developers
maven-shared-components parent
- use latest maven parent
I have reverted the whole patch at DOXIA-78 (it also affected the
XdocParser), and also my erroneous javadoc comments in the Sink. If you
want to go for an alpha-10, you should merge those changes into the branch.
-Lukas
Vincent Siveton wrote:
Hi,
This fix is an important issue for report
be done from the alpha-9 tag. So, any
objections if I go ahead committing on trunk?
Cheers,
-Lukas
Lukas Theussl wrote:
Just summing up some stuff I've been discussing with some people on IRC
already: I am working on several enhancements for doxia-beta-1
(DOXIA-137, DOXIA-154, DOXIA-155) which
The second one sounds more reasonable to me, to leave space for other
sandbox components. I remember though trying to build a multi-module web
site for the sandbox and the problem is that a lot of stuff is just
broken. I haven't tried recently though, but generally I support the
idea of a
Just summing up some stuff I've been discussing with some people on IRC
already: I am working on several enhancements for doxia-beta-1
(DOXIA-137, DOXIA-154, DOXIA-155) which involve some changes to the sink
API and I'd like to test it with the current site plugin (aside: all
tests pass within
Hi Vincent,
I had noticed this already (this bug was introduced with DOXIA-78) but
when I tried to fix it like you done it now, it broke several plugin
reports (btw, zones seems to be down again right now). I don't remember
exactly now which ones, but it was complicated enough that I assumed
+1
-Lukas
Dennis Lundberg wrote:
Hi
In preparation for the release of maven-site-plugin I'd like to release
the plugin parent pom r575842 as version 9.
Source:
https://svn.apache.org/viewvc/maven/plugins/trunk/pom.xml?revision=575842content-type=text%2Fplain
The vote will be open for
Post-site goal binding will be necessary for the linkcheck plugin to
work, and also, I think, for a dashboard plugin, so +1 from me in
principle. However, I don't think that it *must* go into beta-6 still.
-Lukas
Vincent Siveton wrote:
Hi,
Just a thought about the site plugin and the
We have 3 +1s now (Jason, Lukas, Vincent), I will go ahead with the
promotion.
Cheers,
-Lukas
Lukas Theussl wrote:
Hi,
I'd like to promote the fo module from sandbox/doxia to
doxia/doxia/doxia-modules. It has some basic docs and tests, has 0 bugs
:) and it's needed by the (sandbox) pdf
good catch, there is indeed a design flaw that's being revealed.
The point is that I use two sinks in the fo module, the 'normal' FoSink,
and the FoAggregateSink. The latter is used to transform a set of input
files into only one target file, as required by a pdf plugin. For this
to work, you
+1
-Lukas
Jason van Zyl wrote:
Hi,
Hervé has been submitting patches on the Maven Ant Tasks for a long
time, done lots of fixes on encoding, in Modell and Plexus so he knows
the system very well and he just keeps on giving us more patches. Given
what I've seen I would propose to make
I don't quite grog the m2 release process yet...
Sorry for my ignorance (I never did a release with m2 yet), but tagging
a release before the vote has passed is not what is described at [1].
The new version tags make continuum (temporarily) unhappy [2,3].
I can't build the doxia site from
Most often there are not enough docs, sometimes there are too many...
Thanks for the clarification and for doing all this!
-Lukas
Dennis Lundberg wrote:
Lukas Theussl wrote:
I don't quite grog the m2 release process yet...
Sorry for my ignorance (I never did a release with m2 yet
Vincent Siveton wrote:
Hi,
Mainly for Dennis who kindly suggests to do the release, here are some
doc issues:
* publish the site decoration descriptor XSD and the associated doc.
Actually, it is decoration-1.0.0.xsd but I would prefer to name it
decoration-1.0.0-alpha-9.xsd. WDYT?
Moreover,
+1
-Lukas
Brian E. Fox wrote:
Mauro is an existing Apache Committer on the Excalibur project
(http://excalibur.apache.org/team-list.html) as well as the mojo project
at Codehaus. He has recently been working on the shade plugin currently
up for vote to be moved to Apache. As he has
Dennis Lundberg wrote:
See below...
[EMAIL PROTECTED] wrote:
Author: ltheussl
Date: Mon Sep 3 08:13:54 2007
New Revision: 572361
URL: http://svn.apache.org/viewvc?rev=572361view=rev
Log:
Fix links
Modified:
(A)
-Lukas
Brett Porter wrote:
I'd like to hear from as many people as possible their opinion this
topic (even if you just want to say '0' so we know where you stand).
[ ] (A) All plugin versions must be specified by the project or its
parent hierarchy somewhere, at the cost of some
(C)
-Lukas
Brett Porter wrote:
Like the other poll, I'd like to hear from as many people as possible
their opinion this topic (even if you just want to say '0' so we know
where you stand).
[ ] (A) Having a way to include a set of plugins in one small POM
fragment would be a useful
+1
-Lukas
Brian E. Fox wrote:
The shade-maven-plugin is currently in the codehaus mojo sandbox. This
plugin is used by maven core to package the uberjar for distribution and
should be moved to the maven project.
Please vote {+1,0,-1], vote is open for 72 hrs.
+1
Dennis Lundberg wrote:
Lukas Theussl wrote:
Why do we need to use the full absolute path to the plugins?
Shouldn't ./maven-clean-plugin/ be enough?
It's enough to generate a valid link on your web site.
However, I just committed an enhancement to doxia-linkcheck that lets
you specify
It's part of a bug-fix: external links in apt files (ie links outside
the current source document) have to start with './' or '../', otherwise
I don't see how we could fix http://jira.codehaus.org/browse/DOXIA-47.
We have implemented a hacky workaround for html files to preserve
backward
user input at all
(apart from parse exceptions if the source can't be parsed in the first
place), that should really be done by an independent tool.
-Lukas
Cheers,
Brett
On 31/08/2007, at 5:10 PM, Lukas Theussl wrote:
It's part of a bug-fix: external links in apt files (ie links outside
FYI: I have checked the current maven site with the sandbox linkchecker
and fixed all errors plus a couple of redirect warnings. Below is a list
of links that are still missing and I'm unsure what to do, if someone
could have a look. I have also commented out all links to the jetty home
page (
Vincent Siveton wrote:
Hi Lukas,
2007/8/27, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Author: ltheussl
Date: Mon Aug 27 03:45:20 2007
New Revision: 570064
URL: http://svn.apache.org/viewvc?rev=570064view=rev
Log:
Align sandbox poms
Modified:
maven/sandbox/trunk/doxia/doxia-book/pom.xml
[sorry for the late reply, I didn't have any email for 2 days]
I agree with Jason here. The site-tools seem to belong rather into the
site-plugin than into doxia. I think the current close connection has
some drawbacks, it provokes confusion about responsibilities (example:
anchor creation
Definetely +1. I wouldn't have thought that we need a vote for this...
As a sidenote: Arnaud once had a continuum instance set up for maven1,
which I don't see anymore. Not that I expect much development anymore
but just in case, could that be added to the project groups on zones?
Thanks,
with the RenderingContext and
Map?). I guess it's been tweaked to fit the needs of maven/site
rendering but AFAICT it can't be used stand-alone right now.
-Lukas
Lukas Theussl wrote:
It's in the core: o.a.m.d/module/AbstractIdentityTest.java, see eg the
AptIdentityTest.java in the apt module for how to use
+1
-Lukas
Emmanuel Venisse wrote:
Hi,
I'd like to give to Olivier commit access to Continuum.
He provided lot of good patches, implemented new features
(installations/profiles) and help users on the mailing lists
here, my +1
Emmanuel
Yeah! Now let anybody say that we can't write docs! (well, why couldn't
you do that before I started getting familiar with doxia?... ;) )
Two comments:
- I never quite understood the (apparently general) maven philosophy of
separating the site from the rest of the project. I would at least
[replying to doxia-dev@ as I think this was meant to go there]
I'd like to chime in here and try to clarify a design issue that I've
been thinking about recently.
The general doxia philosophy is clear from your description, what is not
specified IMO is the separation of responsibilities of a
-archive I see 5 messages.
Subject:
[continuum] BUILD FAILURE: Doxia Site Renderer Component
I have missed several (Maven-mailing-list) messages lately, but I
thought it was something wrong with my mail-provider, since the messages
are available in the archives.
Lukas Theussl wrote:
I know, I am
Ok, took me 10min to fix the issue and half a day to do my first m2
deploy ... anyway, should be done now, enjoy!
-Lukas
Cabasson Denis wrote:
Thanks for this patch Lukas.
Could you publish a new SNAPSHOT of doxia-core with this patch?
Thx for the fix and sorry to have charged DOXIA-47
(you know there is a doxia list?...)
I don't quite understand your evaluation of the problem.
StructureSink.isExternalLink uses text.indexOf( . + File.separatorChar
), so this returns true for ./link (Unix) and .\link (Windows). In
any case you should get an external link (no #) for
the
StructureSink.isExternalLink method to use / instead of
separatorChar (and repbulish a SNAPSHOT version).
Denis.
-Message d'origine-
De : Lukas Theussl [mailto:[EMAIL PROTECTED] Envoyé : mardi 17
juillet 2007 16:46
À : Maven Developers List
Objet : Re: [DOXIA] Revert doxia revision 555417
(you know
always have to make sure they are converted first.
IMO we should not allow it anywhere, as it encourages people to write
malformed URIs.
Lukas Theussl wrote:
Ok, I got it :)
Shouldn't we still allow .\ and ..\ as well as windows people might
use that for internal links? Or is that illegal also
+1
-Lukas
Vincent Siveton wrote:
Hi,
I would like to release the Maven Javadoc Plugin 2.3. The last release
has been about 6 months ago.
We solved around 30 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138styleName=Htmlversion=13304
There are still a couple of
+1
-Lukas
Vincent Siveton wrote:
Hi,
The last release (beta) of maven-antlr-plugin was more than two years
ago. We did some small enhancements.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11123fixfor=12931
A release could be done shortly but I would like to move the
Vincent Siveton wrote:
Hi,
2007/7/13, Lukas Theussl [EMAIL PROTECTED]:
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
For the log and AFAIK, here is a brief history of the Maven JXR project.
o The orignal JXR code was merged in 2004
Could you clarify a bit your intentions, I don't know if I missed that
in the discussion so far.
If we accept the code, is it going to stay a separate project or will it
be merged with jxr? Are they going to compete or supplement each other?
What is the concrete advantage for the Maven
No, it's still supported and not deprecated in Maven 1.1:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html#class_dependency
-Lukas
Brett Porter wrote:
Probably referring to the jar tag which let you hack the repository
path. It's forbidden in Maven 2 (and was
at some point?
- Brett
On 21/06/2007, at 6:27 PM, Arnaud HERITIER wrote:
I'm sure that in the current 1.1 code, entities are supported and
there's no
activation mechanism.
Arnaud
On 21/06/07, Lukas Theussl [EMAIL PROTECTED] wrote:
Hi,
Reviewing the site I can't figure out what
+1
Mission accomplished! :) I also consider that we finally finished a job
that should have been done a long time ago, but it's out now at last and
I'm pretty impressed and proud of what we have achieved. (Merci Arnaud,
c'etait tout a cause de toi!) Being somewhat unsure about my future in
Hi,
Reviewing the site I can't figure out what this FAQ is supposed to mean:
http://maven.apache.org/maven-1.x/faq.html#using-entities
As of Maven 1.1, external entities will not be enabled by default in
project.xml ... There will still be the ability to use them, but it will
have to be
Please use the user list for this kind of questions.
Try clearing your cache, that often has a miraculous effect in maven
1.0.2. Otherwise, provide more information.
Cheers,
-Lukas
bala reddy wrote:
I'm getting the below error when i do a maven dist:build-bin; please help.
Thanks
-B
+1
-Lukas
Dennis Lundberg wrote:
Hi,
I'd like to release maven-one-plugin 1.1. Half of the issues filed
against 1.0 have been closed in this release. The main reason for the
release is the addition of the M1 to M2 pom converter.
Release Notes:
See http://jira.codehaus.org/browse/MPA-43
You have my +1 if you want to go for it... :)
-Lukas
Dennis Lundberg wrote:
Hi
We get some JIRA issues for the M1 plugins that really belongs to the M2
plugins. To help get these issues into the correct JIRA project from the
start, I propose that
The vote passed with 4 binding (Jason, Stephane, Arnaud, myself) and one
non-binding (Jeff) +1.
Vote thread:
http://www.nabble.com/-vote---m1--release-artifact-plugin-1.9.1-and-test-plugin-1.8.2-tf3779381s177.html
Thanks,
-Lukas
Lukas Theussl wrote:
We discovered two rather severe issues
We discovered two rather severe issues in plugins bundled in
Maven-1.1-RC1 which are fixed and I would like to include the updated
plugins in 1.1-final (to be released hopefully next week). One concerns
a problem with artifact signing in the artifact plugin, the other is a
performance
+1
-Lukas
Arnaud HERITIER wrote:
Hi folks,
The time has come to release maven 1.1 RC1.
Since the beta 3 we fixed several issues [1] and particularly :
- We fixed latest incompabilities that avoided maven 1.1 to read POM
working with maven 1.0.X [MAVEN-1755]. The new parser is a little
[I'm taking this one over from Arnaud while he is trying to repair his
harddisc]
Result: three binding +1s (Arnaud, Stephane, myself), voting thread is here:
http://www.nabble.com/-vote--m1--maven-nsis-plugin-2.1-tf3684043s177.html
I'll do the release asap, and then will wait until Arnaud
We have three binding (Arnaud, Stephane, myself) and 1 non-binding
(Jeff) +1s, voting thread is here:
http://www.nabble.com/-vote---m1--couple-of-plugins-for-rc1-tf3677026s177.html
I'll do the releases ASAP.
Thanks,
-Lukas
Lukas Theussl wrote:
Hi,
Here's a bunch of plugins I'd like
+1
-Lukas
Arnaud HERITIER wrote:
And now, Ladies and Gentlemen,
(the drum is rumbling )
This is the last plugin that we need to release for maven 1.1 RC1 ;-)
Changes included in this version :
New Features:
o Add a new template using MODERN_UI macros for a better Look and Feel.
Thanks Stephane!
I have deployed a stage site with your last changes [1] and a snapshot
as well. I will call a vote for a number of plugins later.
Apparently, we don't have a paragraph explaining how to deploy snapshots
[2] but it's basically just 'maven plugin:repository-deploy' for the
Hi,
Here's a bunch of plugins I'd like to release for inclusion in m11-rc1:
maven-artifact-plugin-1.9
maven-changelog-plugin-1.9.2
maven-dist-plugin-1.7.1
maven-eclipse-plugin-1.12
maven-ejb-plugin-1.7.3
maven-linkcheck-plugin-1.4.1
maven-multiproject-plugin-1.5.1
maven-test-plugin-1.8.1
Both idea and plugin still have one issue scheduled for the releases
that you propose (MPIDEA-41 and MPPLUGIN-30), are we going to
un-schedule those?
-Lukas
Arnaud HERITIER wrote:
Here is a new list of plugins to release for maven 1.x.
--
IDEA 1.7
--
Changes in this version
+1
-Lukas
Arnaud HERITIER wrote:
Here is a new list of plugins to release for maven 1.x.
--
IDEA 1.7
--
Changes in this version include :
New Features:
o Autodetect which version control system to use Fixes MPIDEA-43.
Download :
maven plugin:download
+1
Thanks! Let's get ready for m11 now...
-Lukas
Arnaud HERITIER wrote:
Hi team,
We finalized the new version of maven-model 3.0.2 for maven 1.1.
You can find the new web site in [1] and the model documentation [2] will
replace the one actually in the maven 1 site [3].
I deployed a
We have talked about it in private already: I think we have made the
error far too often now, that we waited for 'small' releases in order to
get the big one out. I also don't like adding new features in the last
minute, eg I haven't had time to really test Jeff's last changes to the
javadoc
+1
-Lukas
Arnaud HERITIER wrote:
Hi,
I encountered some problems with the site plugin and its rsync deployment
feature.
I propose to release a new version to fix these problems.
Changes :
+1
-Lukas
Arnaud HERITIER wrote:
Hi,
In the logic to try to release often I propose to release the announcement
which has only one minor change. It's to have these one included in the
RC1.
Changes :
+1
-Lukas
Arnaud HERITIER wrote:
Hi,
Those two plugins have a similar fix and weren't release for several
months (more than 1 year in fact).
Changes :
+1
You still need one more though...
-Lukas
Brian E. Fox wrote:
I need 1 more PMC please.
-Original Message-
From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 11, 2007 2:07 AM
To: Maven Developers List
Subject: Re: [VOTE] maven-enforcer-plugin:1.0-alpha-2
We are pleased to announce the Maven Clover Plugin 1.11.2 release!
http://maven.apache.org/maven-1.x/plugins/clover/
The Clover plugin allows measuring test coverage using Clover
(http://www.cenqua.com/clover).
===
We are pleased to announce the Maven JDiff Plugin 1.5.1 release!
http://maven.apache.org/maven-1.x/plugins/jdiff/
Plugin for JDiff - reports on the differences in the public API of two
releases by comparing the sources of two SCM checkouts.
We are pleased to announce the Maven PMD Plugin 1.10 release!
http://maven.apache.org/maven-1.x/plugins/pmd/
The Maven PMD plugin is a plugin that wraps the PMD framework
(http://pmd.sourceforge.net). PMD is a source checking framework that works by
scanning Java source code and looks for
We are pleased to announce the Maven Source Control Management Plugin 1.6.1
release!
http://maven.apache.org/maven-1.x/plugins/scm/
A plugin for SCM tasks.
===
Changes in this version include:
Fixed bugs:
o The
We are pleased to announce the Maven Site Plugin 1.7.1 release!
http://maven.apache.org/maven-1.x/plugins/site/
Generate web site.
===
Changes in this version include:
Fixed bugs:
o Update files modes on the
This vote passed with 3 binding (Arnaud, Jason, Lukas) and one
non-binding (Jeff) +1s.
Thanks to those who voted, I'll do the releases soon.
-Lukas
Lukas Theussl wrote:
Hi,
These are the plugins that do not need the updated maven-model, so I'd
like to release them already:
maven-clover
I just updated the license headers, +1 now for the release and to move
it out of the sandbox.
Thanks!
-Lukas
Arnaud HERITIER wrote:
Hi,
I think that it is the time to release the modello plugin for maven 1.x in
version 1.0.
This plugin allows to use modello (1.0-alpha-15) inside a maven
+1 to your plans.
(However, I couldn't see how your ref.[1] illustrates the new pom features?)
-Lukas
Arnaud HERITIER wrote:
Hi,
With release of the modello plugin we'll be able in some days to release
the new version of the maven-model for maven 1.x.
This new release includes
, Lukas Theussl [EMAIL PROTECTED] wrote:
I just updated the license headers, +1 now for the release and to move
it out of the sandbox.
Thanks!
-Lukas
Arnaud HERITIER wrote:
Hi,
I think that it is the time to release the modello plugin for maven
1.xin
version 1.0.
This plugin allows to use
To whom it may concern, ;)
After some discussion with Arnaud and Jeff on IRC last night, we decided
to give maven 1.1 another kick. We have run again into a situation where
everything is basically ready, but we wanted to wait for some external
releases and then got distracted, etc.
The
Hi,
These are the plugins that do not need the updated maven-model, so I'd
like to release them already:
maven-clover-plugin-1.11.2
maven-jdiff-plugin-1.5.1
maven-pdf-plugin-2.5.1
maven-pmd-plugin-1.10
maven-scm-plugin-1.6.1
maven-site-plugin-1.7.1
Changes are mostly minor, have a look at
The clover plugin had no changes at all (version 1.11.1 was only
released last November) apart from the clover license being updated,
which had expired a few weeks ago.
-Lukas
Jeff Jensen wrote:
+1 for all but clover (never used it!).
Ooops, ;)
I had the plugin dependency in my local copy since a long time and never
noticed any problems. I just committed it now because I was afraid to do
it accidentally with the license header updates. Please revert it (with
appropriate documentation ;) ), the multichanges plugin is not
401 - 500 of 1441 matches
Mail list logo
