The Maven team is pleased to announce the release of the Maven PDF Plugin, version
1.0.
This plug-in allows you to generate a PDF version of your project's
documentation.
http://maven.apache.org/plugins/maven-pdf-plugin/
You should specify the version in your project's plugin
Wendy Smoak wrote:
Thanks for doing this, this is one thing I've really missed from Maven
1. And thanks for starting with 1.0 instead of -alpha or -beta. :)
I'd like to stress that this was a very conscious decision! :)
-Lukas
Hi,
We solved 11 issues since the plugin was promoted from the sandbox:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932styleName=Htmlversion=15118
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11932status=1
ms? word? never heard... ;)
-Lukas
nicolas de loof wrote:
+1
nice work !
any chance you create a maven-msword-plugin now ? :)
2009/6/25 Lukas Theussl ltheu...@apache.org
Hi,
We solved 11 issues since the plugin was promoted from the sandbox:
http://jira.codehaus.org/secure
-pdf-plugin/Cheers,
Nicolas
2009/6/25 Lukas Theussl ltheu...@apache.org
Hi,
We solved 11 issues since the plugin was promoted from the sandbox:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932styleName=Htmlversion=15118
There are still a couple of issues left in JIRA:
http
to
re-check the signatures, but the vote is formally closed now.
Thanks,
-Lukas
Lukas Theussl wrote:
Hi again,
We have cranked some more 23 issues into this release since the last
failed attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:
http://jira.codehaus.org/secure
We are pleased to announce the release of Maven Doxia and Maven Doxia Sitetools,
version 1.1.1.
Doxia is a content generation framework that provides powerful techniques for
generating static and dynamic content: Doxia can be used in a web-based publishing
context to generate static sites,
Benjamin Bentmann wrote:
Lukas Theussl wrote:
Staging repos:
https://repository.apache.org/content/repositories/maven-staging-019/
https://repository.apache.org/content/repositories/maven-staging-020/
+1 in general, only the signatures for the POMs would need to be
double-checked
+1
-Lukas
John Casey wrote:
Hi,
I'm opening a new vote for Maven 2.2.0 after closing:
http://jira.codehaus.org/browse/MNG-4169
http://jira.codehaus.org/browse/MNG-4207
All URLs below have been updated where appropriate.
---
Okay, it looks like there haven't been many problems
Hi again,
We have cranked some more 23 issues into this release since the last failed
attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=15073
Jason van Zyl wrote:
On 11-Jun-09, at 8:53 AM, Lukas Theussl wrote:
Hi Olivier,
How does this relate to MNG-3402?
This doesn't relate to anything in 3.x because it's not going to be an
issue because no doxia classes will be distributed with 3.x. Not sure
what you guys are planning
Jason van Zyl wrote:
On 15-Jun-09, at 10:29 AM, Lukas Theussl wrote:
Jason van Zyl wrote:
On 11-Jun-09, at 8:53 AM, Lukas Theussl wrote:
Hi Olivier,
How does this relate to MNG-3402?
This doesn't relate to anything in 3.x because it's not going to be
an issue because no doxia
Hi Olivier,
How does this relate to MNG-3402?
Just wondering because we had a lot of discussions about this issue in the past
wrt Doxia release plan [1], and from other peoples' comments I always got the
impression that it will lead to trouble... even though I never noticed anything
myself.
.
I'm currently made some tests with current trunk on some projects
(company ones and oss ones) to test backward compatibility/
And I have noticed I couldn't run anymore : mvn site:site (just
generate the site works now all reporting looks to be an other story
:-) ).
--
Olivier
2009/6/11 Lukas
Hi Nicolas,
Please also log a short description of the commit in addition to the issue number,
not everybody knows by heart what a specific issue is about... ;) See [1] for a
template.
Thanks,
-Lukas
[1] http://maven.apache.org/developers/conventions/svn.html
nico...@apache.org wrote:
Hi,
We solved 27 (Doxia) and 3 (Sitetools) issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=15073
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624styleName=Htmlversion=15075
There are still a couple of issues left in JIRA:
-defined procedure that allows me
to do a release without spending a whole day on it.
Cheers,
-Lukas
Brian Fox wrote:
There's no source bundle.
On Thu, May 14, 2009 at 3:59 AM, Lukas Theussl ltheu...@apache.org wrote:
Hi,
We solved 27 (Doxia) and 3 (Sitetools) issues:
http
Hi John,
I just came across that same issue as reported before:
http://www.mail-archive.com/dev@maven.apache.org/msg80592.html
There is no conclusion in this thread (apart from that it works with maven 2.1,
which I verified) and I haven't found a jira, did I miss it or should I open one?
Vincent,
I'm trying to understand some of the issues we have with entities in the
XmlParser. Is there a special reason why entities are emitted as rawText and not text?
I think they should be emitted as text:
First, custom entities can be used to simply define some replacement text inside
Benjamin Bentmann wrote:
Author: bentmann
Date: Fri Apr 10 22:42:19 2009
New Revision: 764090
URL: http://svn.apache.org/viewvc?rev=764090view=rev
Log:
[MSITE-400] Make repository id for stage-deploy configurable
Modified:
+1
-Lukas
Brian Fox wrote:
Time to release the updated parent poms:
https://repository.apache.org/content/repositories/apache-staging-011/org/apache/apache/6/apache-6.pom
+1
-Lukas
Benjamin Bentmann wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName=Htmlversion=14831
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11540status=1
Hi,
Is there any reason why we have this setting in the doxia parent pom:
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModenever/forkMode
/configuration
/plugin
I just noticed that this is the cause of
Wendy Smoak wrote:
On Mon, Mar 9, 2009 at 3:31 PM, Lukas Theussl ltheu...@apache.org wrote:
Rémy Sanlaville wrote:
Otherwise three possible improvements:
1. Why it's a (build) plugin and not a report plugin ?
I have no strong opinion for or against either but I guess we'll have to pin
+1
-Lukas
John Casey wrote:
Hi everyone,
It looks like Maven 2.1.0 is ready to release.
You can try the binaries here:
http://tinyurl.com/maven-2-1-0-vote
(https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/)
We've
Done:
http://jira.codehaus.org/browse/MPDF
Cheers,
-Lukas
Wendy Smoak wrote:
On Thu, Mar 19, 2009 at 5:35 AM, jevica.arianne
jevica.aria...@gmail.com wrote:
Hi!
I have tried the maven-pdf-plugin and I've encountered some bugs. Where can
I file those?
You can use
This vote passed with 12 x +1 and no objections.
Thanks!
-Lukas
Lukas Theussl wrote:
Hi,
With Doxia 1.1 released, I'd like to promote the pdf plugin out of the
sandbox so we can release it. Snapshot is deployed:
https://repository.apache.org/content/repositories/snapshots/org/apache
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=13362
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1
Staging
Hi,
With Doxia 1.1 released, I'd like to promote the pdf plugin out of the sandbox so
we can release it. Snapshot is deployed:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-pdf-plugin/
The site with basic instructions is here:
Thanks for the feedback!
Rémy Sanlaville wrote:
big +1 (thanks).
Just try it for a project. I have to dig a little because I have two parsing
error like:
Embedded error: Error parsing ...\src\site\fml\doc\faq.fml: Error validating
the model: Error:
Public ID: null
System ID: null
Line
+1
-Lukas
Vincent Siveton wrote:
Hi,
We solved more than 100 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13617styleName=HtmlprojectId=10780
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780status=1
Hi John,
If you would have used the time it took you to write this email for installing and
testing Doxia 1.1 you probably wouldn't have to ask anymore if it's a terrible
idea. ;)
I also don't see a compelling reason for upgrading now. As I didn't 5 weeks ago.
Or the week before that.
+1
-Lukas
Vincent Siveton wrote:
Hi,
This is a maintenance release due to MPIR-146.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14325styleName=HtmlprojectId=11142Create=Create
There are still a couple of issues left in JIRA:
+1
-Lukas
Dennis Lundberg wrote:
Hi,
Another step in the Doxia Release Plan:
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=14950
The most notable fix is
+1
-Lukas
John Casey wrote:
Hi everyone,
It's time to do another release of maven-plugin-tools. This version
contains several improvements, mainly to provide feature parity with the
maven-antrun-plugin for ant-based mojos, and to provide support for
non-default encodings.
The staging
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624styleName=Htmlversion=14835
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11624status=1
Staging
+1
-Lukas
Brian E. Fox wrote:
Time to release a beta with a few bug fixes:
Release Notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14948styleName
=HtmlprojectId=11530Create=Create
Staged site:
+1
-Lukas
Brett Porter wrote:
anyone? This is blocking the 2.1.0 release.
Cheers,
Brett
On 20/02/2009, at 3:24 AM, Brett Porter wrote:
The Wagon 1.0-beta-5 candidate has been staged. This is a
pre-requisite for the 2.1.0 release.
This release includes 17 fixes. You can take a look at the
Hi Wendy,
First, thanks for testing!
Wendy Smoak wrote:
I initially got a build failure because the plugin uses _itself_
during the build. I commented that part out and jumped through some
hoops building doxia and various parent poms, then it worked.
The plugin is only used to build the
*) I have to investigate the image warnings, it seems that some
resources are not copied
This was actually a bug in relative link resolution for figure sources, it's fixed
and new snapshot deployed.
-Lukas
-
To
It would also be nice if snapshots were deployed before bumping deps all over the
place.
-Lukas
Vincent Siveton wrote:
Hi Brian,
Do you plan to release the parent shortly?
Vincent
2009/2/13, bri...@apache.org bri...@apache.org:
Author: brianf
Date: Fri Feb 13 23:54:30 2009
New
+1
-Lukas
Dennis Lundberg wrote:
Hi,
(resending due to SMTP-server problems)
The time has finally come to release Doxia 1.0. For more info on the
relationship to plugins and other components, see the Doxia Release Plan at
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
We've
I am still available. However, somehow I can't help the feeling that with your
experience it might be quicker if you did it right away instead of walking me
through the process...
-Lukas
Dennis Lundberg wrote:
I'm undecided about what version number to use, and leave that decision
to
Picking up the doxia thread:
I have the feeling Doxia is never going to get out of it's vicious circle: we are
hesitant to release 1.1 because without the site plugin using it, it doesn't get
any hard-core testing, and for maven you guys don't want to use it because it
hasn't been released
+1
-Lukas
John Casey wrote:
Hi everyone,
I've had the pleasure of working with Petar since sometime around August
or a bit earlier. He's been instrumental in getting this latest release
of the Assembly Plugin tested, patched, and ready to go. His continued
focus on the release cycle for
One side remark about the site: for doxia-1.1 (was 1.0-beta-1) we have modified
the apt format with the plan to render obsolete the original apt used in maven
2.0.x. If we are going to support and maintain both doxia-1.0 (was alpha branch)
and doxia-1.1 then we have to keep both formats
I just noticed that the fml module now takes ~5min to build instead of a few secs
for all other modules. There are some svn checkouts during testing, are those
necessary? Does it mean you can't build doxia off-line?
-Lukas
Vincent Siveton wrote:
Hi guys,
IMHO Doxia 1.0-beta-1 could be
Hi Herve,
I haven't looked at the doxia modules for a while, and I am not a
docbook expert but IIRC, the doxia docbook module is for Simplified
Docbook only and in Simplified DocBook the root element is always article.
Correct me if I'm wrong...
Cheers,
-Lukas
[EMAIL PROTECTED] wrote:
+1
-Lukas
John Casey wrote:
Hi everyone,
After fixing 70 issues and spending about 2 months going through release
candidate after release candidate, we finally have a stable codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release
notes are here:
Sounds good to me. I haven't quite followed the discussion on release
plans recently but it's still itching me to get doxia released.
Just a few comments:
- I proposed on the doxia-dev list to release the alpha branch as 1.0
final but haven't gotten any feedback. I think it's a good idea,
+1
-Lukas
Vincent Siveton wrote:
Hi,
We solved more than 30 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14120styleName=HtmlprojectId=11138
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11138status=1
+1
-Lukas
Vincent Siveton wrote:
Hi,
This is mainly a bug fix release.
We solved around 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14442styleName=HtmlprojectId=11139
There are still a couple of issues left in JIRA:
wrt to the changes
you discussed?
Thanks,
-Lukas
Lukas Theussl wrote:
IMO these are all changes that should go into beta-1. The coupling with
maven/plexus has always been a major frustration, the sooner this is
removed, the better. The logging API was only added in beta-1, so if you
are going
+1
-Lukas
Vincent Siveton wrote:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11310styleName=Htmlversion=13182
There are just one issue left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11310status=1
Staging repo:
+1
-Lukas
Jason van Zyl wrote:
Hi,
Shane has been been working on NMaven for a couple years now, he's
worked on the new maven-toolchain, has recently done a huge amount of
work on cleaning up the project builder in the sandbox, and has some
PGP tools that he would like to contribute.
+1
-Lukas
Vincent Siveton wrote:
Hi,
We solved less than 70 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142styleName=Htmlversion=12621
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11142status=1
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=14366
There are still 1 issue left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761status=1component=13263
Dennis Lundberg wrote:
Lukas Theussl wrote:
Hrm, ok. But if we release site and pir plugins (which is slated to
happen soonish, right?), these people will be bitten by the same
problems anyway, unless maven-2.0.10 gets released in the meantime and
they upgrade immediately. (And btw
Vincent Siveton wrote:
2008/6/2, Dennis Lundberg [EMAIL PROTECTED]:
Lukas Theussl wrote:
Hrm, ok. But if we release site and pir plugins (which is slated to happen
soonish, right?), these people will be bitten by the same problems anyway,
unless maven-2.0.10 gets released
I have uploaded the new snapshots with changed version number exactly
because I didn't want to interrupt the release process for
site-plugin-2.0-beta-7 and pir-2.1. How come people are already getting
these snapshots, I thought they'd have to explicitly ask for them?
-Lukas
Brian E. Fox
anyway?)
I just wanted to make it easy to test doxia-beta-1, but if this causes
confusion, I don't care to remove it (can I just remove a snapshot from
the repo?).
-Lukas
Dennis Lundberg wrote:
Lukas Theussl wrote:
I have uploaded the new snapshots with changed version number exactly
because
Hi Dennis,
For single-document transformations, I think it's true: a string with a
'/' is always an external link. However, for sinks that aggregate
several source documents into one output file (eg the FoAggregateSink
used by the pdf plugin), an 'external' link (like
+1
-Lukas
Dennis Lundberg wrote:
Hi,
This vote is to release doxia-sitetools-1.0-alpha-11.
The Release Notes show only 1 issue solved, but there are a few other
minor changes as well:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624styleName=Htmlversion=13908
Tags:
+1
-Lukas
Dennis Lundberg wrote:
Hi,
This vote is to release doxia-1.0-alpha-11, which will be followed by
another vote for doxia-sitetools-1.0-alpha-11.
The Release Notes show only 1 issue solved, but there are a few other
minor changes as well:
Hi,
I'd like to fix http://jira.codehaus.org/browse/DOXIA-208 in beta-1
still to avoid possible breaking changes later on. I am a bit confused
about APT though as we seem to have a lot of different standards
floating around in our own docs. Just to make sure I am on the right
track, this is
Another doubt about faq id's: in m1 an id had to be a valid HTML id, in
m2 fml files I see frequently things like [1]
faq id=What is a Mojo
which is internally converted to a name=What_is_a_Mojo. I think the
faq id should be valid in the first place, correct?
-Lukas
[1]
Dennis Lundberg wrote:
Vincent Siveton wrote:
Hi Jason,
2008/4/28 Jason van Zyl [EMAIL PROTECTED]:
Hi,
After chatting with Lukas and Vincent on IRC I think if we want to
continue
with changes to Doxia then we should release the 1.0 for the site
plugin and
move on.
I know that
+1
-Lukas
Raphaël Piéroni wrote:
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
+1
-Lukas
Raphaël Piéroni wrote:
Hi,
According To the committer list in
http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
We have currently:
2 non binding vote (Jason, Raphaël)
1 binding vote (Arnaud)
IIRC the voting process, we need 3 binding vote (PMC), for a
plugin release.
Coming back to your original mail, I actually don't quite see the
necessity of the change. Intuitive is probably a subjective concept, but
I don't find the current behavior that un-intuitive. If current apt
makes {{foo}bar}} an internal link then I would intuitively expect that
{{foo.x}bar}}
Benjamin Bentmann wrote:
See my comment at http://jira.codehaus.org/browse/DOXIA-208
Your proposal at
http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+APT+Format
already suggests to break compat with the original APT format. I beg you to
go this route down to its end and make
+1
Great work, thanks everyone!
-Lukas
Brian E. Fox wrote:
Time to vote on the final Maven 2.0.9 Release. We went through 8 Release
Candidates and fixed all know regressions from 2.0.8 to 2.0.9 during
that time. Note that there were no source changes between RC8 and this
final build.
+1 :)
-Lukas
Arnaud HERITIER wrote:
I have not enough PMCs votes to launch the release. If some of you can test it.
thx
cheers
arnaud
On Thu, Apr 3, 2008 at 4:27 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
Ok that's right. The prerequisite is intended for tools and isn't
inherited (making
+1
-Lukas
Brian E. Fox wrote:
Restaged, only the group Id has changed back to
org.apache.maven.reporting. The original was out for 3 days, this vote
will be for an additional 24 hours given the small change.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent:
+1
-Lukas
Brian E. Fox wrote:
The old version 2.0.4 is trying to use an obsolete method in the
plugin-plugin tools. This was removed in 1.0-alpha-10 of the
doxia-site-render and causes problems with newer plugin tools and 2.0.9.
This release was cut from the old 2.0.4 tag because it's 2 years
+1
-Lukas
Brian E. Fox wrote:
There were several regressions in the 2.4 release. 2.4.1 seeks only to
address these to restore compatibility. This release is dependent on the
maven-reporting-impl-2.0.4.1 release and 2.0.9 is dependent on this
release.
Staged at:
beta-1 is actually ready IMO, the two open issues are minor and can be
postponed.
However, I do not understand why you say that MNG-3402 is dependent on a
doxia release? The aim of MNG-3402 is exactly to make maven independent
of the doxia version. If your intention is to bumb to doxia-beta-1
I'm not aware of any issues, doxia is using 3.8.2 everywhere.
-Lukas
Benjamin Bentmann wrote:
Hi,
I noticed that Maven is using junit:3.8.1 quite everywhere for its tests
although a later maintenance release of the 3.x line exists with
junit:3.8.2. Is there a known issue with 3.8.2 that
+1
-Lukas
Brian E. Fox wrote:
It's time to release the next Javadoc plugin. Besides the fixes listed
below, the most important change is the reverting of javadoc acting as
an aggregator. This caused most users tons of grief during releases. The
issue for this is MJAVADOC-137 (reverted
+1
-Lukas
Dennis Lundberg wrote:
Hi
To get the latest version of maven-source-plugin into our toolchain, I'd
like to release the shared components parent r635758 as version 9. A
site.xml has been added in this release.
Source:
+1
-Lukas
Vincent Siveton wrote:
Hi,
It s again me :) I would like to release (again) the Maven Plugin
Tools projects:
* maven-plugin-plugin-2.4
* maven-plugin-tools-beanshell-2.4
* maven-plugin-tools-java-2.4
* maven-plugin-tools-2.4
* maven-plugin-tools-javadoc-2.4
*
+1
not tested, just to release it :)
-Lukas
Milos Kleint wrote:
Only 2 votes +1 (me and brett). So I suppose the vote failed.
What to do now?
Milos
On Mon, Mar 3, 2008 at 1:32 PM, Brett Porter [EMAIL PROTECTED] wrote:
+1 to the currently released artifacts and tag.
I reviewed the code,
+1
-Lukas
John Casey wrote:
I'd like to propose giving commit access to Paul Gier.
He's been instrumental in the recent push to release the assembly
plugin, and I see his work (debugging some issues, patches for other
issues) all over JIRA. Not to mention he's pretty active on IRC, and
Welcome Benjamin!
-Lukas
Lukas Theussl wrote:
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he
I'd like to propose giving commit access to Benjamin.
During the last few months, he has provided patches in so many areas of
Maven that I can't list them all here (various plugins, surefire,
doxia,...), including documentation and translations, and he has not
been afraid to actively discuss
.
-Lukas
Brian E. Fox wrote:
What if all the maven 1.x jira projects where collapsed into one?
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 17, 2008 3:34 PM
To: Maven Developers List
Subject: Re: JIRA for Maven 1.x?
If I'm not mistaken we
If I'm not mistaken we didn't get a single critical bug report after 1.1
was released. But that's not surprising, after all, it's a perfect
product... :)
I am not sure about closing the JIRAs, after all, maintenance mode means
that we still do accept bug reports, right? If anyone would submit
- leave permissions as is for the consolidated project.
Cheers,
Brett
On 18/02/2008, at 8:12 AM, Lukas Theussl wrote:
I wanted to propose that too, but what to do with the issues that are
open? As long as m1 is in maintenance mode, I think we should keep
reported issues visible. We could remove
+1
-Lukas
Dan Fabulich wrote:
Fabrizio found a last-minute bug. I've rolled a new candidate. Let's
vote again!
[Boy, the temptation to let the rules slide on a change this small is
almost irresistable. ;-)]
-Dan
-- Forwarded message --
Date: Sat, 26 Jan 2008 11:53:28
+1
-Lukas
Brian E. Fox wrote:
It's been a long time since the last release and we have lots of
improvements/fixes:
Release Notes - Maven 2.x Dependency Plugin - Version 2.0
** Bug
* [MDEP-59] - dependency:unpack can't extract rar archives
* [MDEP-74] - dependencies in test
Hi Vincent,
The figure handling is not very consistent across doxia modules anyway,
it would be good to have at least an idea of how it should work...
Eg the img parsing in the xdoc module used to be handled via rawText, I
changed that in alpha-9 but it is obviously less general now (if you
+1
-Lukas
Olivier Lamy wrote:
Hi,
No more PMC to push a vote ?
Thanks,
--
Olivier
2008/1/14, Dennis Lundberg [EMAIL PROTECTED]:
+1
Olivier Lamy wrote:
Hi,
I'd like to release the Maven Jar Plugin version 2.2.
We solved 26 issues:
+1
-Lukas
[EMAIL PROTECTED] wrote:
Hi,
I'd like to release maven-invoker-plugin 1.1.
This release fixes some bugs and makes some improvements. The last release was
made over 1 year ago.
We solved 11 issues :
+1
-Lukas
Carlos Sanchez wrote:
ping
On Dec 3, 2007 7:05 PM, Carlos Sanchez [EMAIL PROTECTED] wrote:
some more votes please ;)
On Nov 29, 2007 12:11 AM, Stuart McCulloch [EMAIL PROTECTED] wrote:
On 29/11/2007, Carlos Sanchez [EMAIL PROTECTED] wrote:
It includes bugfixes in the
+1
-Lukas
Dan Fabulich wrote:
Hi,
Maven Surefire version 2.4 is on the runway. Hopefully folks have spent
some time trying out the SNAPSHOT version, because we expect ordinary
users to get auto-upgraded to version 2.4 when we decide to release.
This version fixes numerous
Sorry to tell you that this doesn't make your vote binding ;-p (Olivier
himself is a committer too), only PMC votes are. See
http://www.apache.org/foundation/voting.html
Cheers,
-Lukas
nicolas de loof wrote:
Hey, I'm a maven committer now ! ;-p
(non binding) Nicolas
2007/12/20, olivier
trunk but for the twiki module this is identical to
r592499, if I'm not mistaken).
Can you clarify the order of patches to apply, or maybe attach one big
patch for everything?
Cheers,
-Lukas
Lukas Theussl wrote:
Hi Juan!
It will take me a while to review the bunch but I'll take a look
+1
-Lukas
Hervé BOUTEMY wrote:
Hi,
Following Maven release, I'd like to release (again) Maven Ant Tasks 2.0.8.
Problem with dependencies order has been fixed.
We solved 16 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=13618
The tasks can be
+1
-Lukas
[EMAIL PROTECTED] wrote:
Hi,
In the preparation of the Maven Invoker Plugin release, I would like to release
maven-invoker:2.0.7
The last release was done around one year ago.
Staging repo :
http://people.apache.org/~olamy/staging-repo/
Vote open for 72 hours.
Here my +1 (non
+1
-Lukas
Daniel Kulp wrote:
I'd like to release version 1.0-beta-2 of the
maven-remote-resources-plugin. The only change between this and
1.0-beta-1 is to fix the fact that 1.0-beta-1 would not work with JDK
1.4 due to it overriding a method that was final in 1.4, but not in 1.5.
301 - 400 of 1441 matches
Mail list logo
