Hi Herve,
just from intuition I would say it's the update date, but I don't think
there is a formal definition/specification on the level of the sink API.
The only distinction between creation and update date that I remember is
in the document MetaData
see related https://issues.apache.org/jira/browse/DOXIA-436
Greetings! :)
-Lukas
Am 12.08.2015 um 23:54 schrieb herve.bout...@free.fr:
now that you told it, I'd seriously prefer change Doxia Markdown parser to use
an XhtmlParser instance internally instead of extending XhtmlParser while
Hi Stephen,
The Sink API only knows 5 section levels, which in html are mapped to
h2 - h6: http://jira.codehaus.org/browse/DOXIA-203
HTH,
-Lukas
Am 13.11.2013 10:13, schrieb Stephen Connolly:
-1 (non-binding)
-Lukas
On 05/29/2013 12:01 PM, Stephen Connolly wrote:
We have been using a policy of only making releases without skipping
version numbers, e.g.
3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, etc
Whereby if there is something wrong with the artifacts staged for release,
+1 (non-binding)
However, the staging sites are still not there...?
Thanks!
-Lukas
On 04/24/2013 12:21 AM, Hervé BOUTEMY wrote:
Hi,
We solved 21 issues in Doxia base:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780version=18423
We solved 4 issues in Doxia Sitetools:
Seems to be a good fix, thanks Robert!
I'm only missing some documentation, could you add an example to
http://maven.apache.org/doxia/references/doxia-apt.html ?
Cheers,
-Lukas
rfscho...@apache.org wrote:
Author: rfscholte
Date: Sat Apr 6 12:21:13 2013
New Revision: 1465234
URL:
:12:37 Lukas Theussl a écrit :
Seems to be a good fix, thanks Robert!
I'm only missing some documentation, could you add an example to
http://maven.apache.org/doxia/references/doxia-apt.html ?
Cheers,
-Lukas
rfscho...@apache.org wrote:
Author: rfscholte
Date: Sat Apr 6 12:21:13 2013
New
+1 (not binding)
-Lukas
Benson Margulies wrote:
Based on the sentiment on the discussion thread, I call a formal vote
to end support for Maven 1.x. This is a vote to:
1: Remove maven 1 release materials from the primary distribution
area, leaving them only on the archive.
2: Make
Hi,
First: are you aware of the maven pdf plugin:
http://maven.apache.org/plugins/maven-pdf-plugin/
It seems that you are trying to re-write it? ;)
See further comments in-line:
On 02/25/2013 11:22 AM, Corentin Groix wrote:
Hi
First, I am quite a newbie at submitting feedback to an apache
Lennart Jörelid wrote:
Good evening, all.
Today, maven-site-plugin performs its site:stage goal by copying the site
of a project into a staging directory, and relativizing some URLs. The
latter part is done by calculating the difference between the current
project's
grrr, I wanted to do that for such a long time, I have also been using
the snapshot ever since I fixed MPDF-36 (almost 3 years ago!).
Unfortunately, I still have no time to help but you'll have my +1 for
a release!
Thanks!
-Lukas
On Mon, Nov 5, 2012 at 2:35 PM, Benson Margulies
+1 !!! (non-binding)
There is still one open issue [1] scheduled for this release. I am not
using Maven 2 anymore, so I don't know what the status is there, but
it's assigned to Herve anyway... :p
Thanks!
-Lukas
[1] http://jira.codehaus.org/browse/MPDF-46
Benson Margulies wrote:
To: Maven
Hi,
First: thanks for working on this!
I have had a brief look and have a few comments:
1) your patch of IT MSITE-604 seems to address a different issue than
the one originally described in the JIRA. If this is the case you
should open a separate ticket.
2) I am wondering about the validity of
+1
-Lukas
Dennis Lundberg wrote:
Hi,
This is the first release of the Doxia Tools parent after the
restructuring of these components. It now works in the same way as the
parents for Plugins and Shared Components.
Doxia Integration Tools moved from Shared Components to Doxia Tools in
://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Wed, Aug 29, 2012 at 8:15 AM, Lukas Theussl ltheu...@apache.org wrote:
FYI: I've had troubles trying to upgrade velocity beyond version 1.5:
http://jira.codehaus.org/browse/DOXIASITETOOLS-39
IIRC
FYI: I've had troubles trying to upgrade velocity beyond version 1.5:
http://jira.codehaus.org/browse/DOXIASITETOOLS-39
IIRC, the main problem was backward compatibility. It should be ok with
current skin versions but that's not tested.
HTH,
-Lukas
Hervé BOUTEMY wrote:
Hi Simone,
Velocity
+1
-Lukas
Hervé BOUTEMY wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142version=18715styleName=Html
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11142status=1
+1
-Lukas
On Fri, Jul 6, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to propose Tony Chemit as a committer.
He is active on Mojo for long time now.
He proposed some patches time ago and recently some more (I'm a bit
boring applying his patches: it probably means
+1 (non-binding)
-Lukas
Olivier Lamy wrote:
Hi,
I'd like to release Maven Clean Plugin 2.5
We fixed 3 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=16456
Staging repository: https://repository.apache.org/content/repositories/maven-122
Staging site:
I see the same problem on osx with svn 1.7.4 but not on linux with svn
1.6.17. Maybe an svn issue?
-Lukas
Olivier Lamy wrote:
Hi,
A user asked a release of maven clean plugin and I said: yes I will
take care!.
But I have some issues with svn on osx and some filenames used for an
it test.
+1
-Lukas
Benson Margulies wrote:
Hi,
We solved 1 issues: MCHANGES-281
There are still plenty of issues left in JIRA.
Staging repo:
https://repository.apache.org/content/repositories/maven-077/
Staging site:
http://maven.apache.org/plugins/maven-changes-plugin-2.7.1/
Guide to testing
For the record: my vote is not binding.
Thanks for the release anyway! :)
-Lukas
Benson Margulies wrote:
Subject:
Hi,
The vote has passed with the following result :
+1 (binding): hboutemy, bimargulies, olamy, ltheussl
+1 (non binding): Tony Chemit
I will promote the artifacts to the
same here: my vote is not binding.
same here: thanks for the release anyway! :)
-Lukas
Olivier Lamy wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Hervé Boutemy, Kristian Rosenvold, Stephane Nicoll, Mark
Struberg, Lukas Theussl, Emmanuel Venisse, Olivier Lamy
+1
Hervé BOUTEMY wrote:
I'm a little late, but needed time to think more on my comments :)
Le lundi 9 avril 2012 17:27:09 John Casey a écrit :
Hi all,
I finally have some cycles free to work on Maven, and I'd like to spend
some time thinking about how we might tackle some of the bigger-picture
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=16489
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1
Staging
+1
-Lukas
Benson Margulies wrote:
Hi,
We resolved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS%7Cb183085c89ca85abde86540c1f02cb433b8719dd%7Cloutversion=17447styleName=TextprojectId=11212Create=Create
There are still a couple of issues left in
+1
-Lukas
Olivier Lamy wrote:
Hi,
I'd like to release Apache Maven Compiler Plugin 2.4.
We fixed: 13 issues (http://s.apache.org/MCOMPILER-2.4)
Staging repository:
https://repository.apache.org/content/repositories/maven-008/
Staging site:
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=17454
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1
Staging
See
http://maven.apache.org/doxia/issues/index.html#Verbatim_blocks_not_boxed
I have fixed the apt sources.
Cheers,
-Lukas
Karl Heinz Marbaise wrote:
Hi,
i have checked the staged Site and observed that the frames around the
source examples or code snippet are not there...
For example
Hi,
The newly added IT for MSITE-582 fails when run with maven 3.0.4. Not a
blocking issue, since everything else works (site-plugin-2 with m2,
site-plugin-3 with m2 3), but I'd like to understand why, if someone
has a clue...
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 9 issues:
AbstractSiteMojo.isMaven3OrMore() is an example how to check if you're
running maven 3. In any case, fixing this this would require a release
of doxia-integration-tools-1.5. Or was that planned anyway?
-Lukas
Vincent Latombe wrote:
On my side, I really would like to see MSITE-604 fixed,
MSITE-601 is a wagon issue IIUC, the other issues can be delayed.
Thanks Denis for doing this!
-Lukas
Robert Scholte wrote:
Hi Dennis,
I don't see any blockers in Jira, only one critical (MSITE-601) but this
seems to be a rare case, so I'd prefer to push that one to a later
release too.
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 12 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624styleName=Htmlversion=13714
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11624status=1
Staging
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=17336
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780status=1
Staging
+1
-Lukas
Dennis Lundberg wrote:
Hi,
This is the first in a series of release culminating with the release of
Maven Site Plugin 3.1.
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=17469
There are no issues left in JIRA:
story I still don't fully understand, it stays for
the moment in Doxia: we can have another look at it after previous changes
Regards,
Hervé
[1] http://maven.apache.org/shared/maven-doxia-tools/project-summary.html
Le vendredi 30 mars 2012 10:07:16 Lukas Theussl a écrit :
Dennis Lundberg wrote
Hervé BOUTEMY wrote:
Le samedi 31 mars 2012 08:24:50 Lukas Theussl a écrit :
The other way round was it? doxia-book into Doxia Tools and
doxia-maven-plugin into Sitetools.
-Lukas
no, Tools can depend on Sitetools, but not the other way
Right, didn't think about the dependencies. I'd move
the
artifactId for both of them.
Do we agree on this?
On 2012-03-31 08:55, Lukas Theussl wrote:
Hervé BOUTEMY wrote:
Le samedi 31 mars 2012 08:24:50 Lukas Theussl a écrit :
The other way round was it? doxia-book into Doxia Tools and
doxia-maven-plugin into Sitetools.
-Lukas
no, Tools can depend
Dennis Lundberg wrote:
On 2012-03-31 14:31, Lukas Theussl wrote:
Why do you want to remove doxia-tools? I like the idea to have all the
independent apps collected in one folder.
There are two problems as I see it:
1. It looks like an umbrella for releasing several modules at once
Dennis Lundberg wrote:
On 2012-03-29 09:13, Lukas Theussl wrote:
I agree that they don't belong into core, but I rather thought of moving
them into doxia-tools instead. Not sure what is better.
This was my thought also.
OTOH, neither book nor maven-plugin have been maintained (AFAIK
release (not the current development version) as configured in the
report, so it can always be re-generated.
Cheers,
-Lukas
Regards,
Hervé
Le mercredi 28 mars 2012 21:36:47 Dennis Lundberg a écrit :
On 2012-03-28 08:35, Lukas Theussl wrote:
The JIRA report should go into the doxia sub-site
I agree that they don't belong into core, but I rather thought of moving
them into doxia-tools instead. Not sure what is better.
OTOH, neither book nor maven-plugin have been maintained (AFAIK) since
they were moved out of the sandbox, and IMO they don't work too well. In
particular there
The JIRA report should go into the doxia sub-site (and corresponding
doxia-sitetools, etc), then you link to that from the base site for each
sub-project. WDYT?
-Lukas
Hervé BOUTEMY wrote:
notice that I tried to commit improvements based on previous thoughts and
found in index.apt.vm the
Salut Herve,
Just a comment: my IDE (netbeans) now shows a javadoc error because the
{@inheritDoc} doesn't pick up the description of the corresponding
parameter. Could the parameter name be changed in the interface as well?
-Lukas
hbout...@apache.org wrote:
Author: hboutemy
Date: Mon
Benson Margulies wrote:
The maven-project-info-reports-plugin generates files with
'inconsistent newlines'. Is it worthwhile to try to fix this, or is it
the beginning of an unbounded collection of other examples.
Shooting from the hip I would guess the latter. I know I started
A quick look at the source code shows that the footer is not taken care
of in doxia-decoration-model's
DefaultDecorationModelInheritanceAssembler. The footer was only
introduced in the last doxia release and this was apparently overlooked.
So the only thing to do is file an issue... :)
Which version of site-plugin-2.x are you comparing with? I would expect
2.3 to be equivalent with 3.0.
-Lukas
Simone Tripodi wrote:
Hi all guys,
while redeploying the Cocoon3 site, using mvn3+site-plugin:3.0, I
noticed a big difference in the generated page using
mvn2+site-plugin:2.X,
Hi Lennart,
Thanks for picking this up!
Personally I don't like either of the two solutions you propose... :p
The APT format was above all designed to be simple, which necessarily
implies some functional limitations. Eg it is on purpose that APT does
not support styles [1], if any fancy
There is a feature request for that:
https://jira.codehaus.org/browse/DOXIA-439
It's not implemented yet...
HTH,
-Lukas
On Sat, Nov 26, 2011 at 2:16 AM, Lennart Jörelid
lennart.jore...@gmail.comwrote:
Hello Simone,
Looking good.
So ... given that this is a skin to maven, could you
Have you actually tested the doxia markdown module? It's new and not yet
complete IMO (see http://jira.codehaus.org/browse/DOXIA-436). OTOH, xdoc
is well supported and tested, especially with the new doxia 1.1 API. If
it's just for one page, I would go for xdoc.
-Lukas
On 11/23/2011 09:59
I moved it out of the sandbox after a standard set of test cases was
supplied, as documented at http://jira.codehaus.org/browse/DOXIA-426. So
the module should be functional for basic purposes, but it hasn't been
hard-core tested (or tested at all AFAIK) for anything else. Also,
fixing
It's been a while for me but I remember I ran into several issues when
trying to upgrade to a newer velocity version, see eg [1]. For the
trademark, there has been an attempt to improve the footer customization
[2], but I'm not sure how far this went.
-Lukas
[1]
Hi Simone,
The evaluate directive was added in velocity 1.6 [1],
doxia-site-renderer still uses velocity 1.5.
HTH,
-Lukas
[1] https://issues.apache.org/jira/browse/VELOCITY-509
On 11/20/2011 04:45 PM, Simone Tripodi wrote:
Hi all guys,
is anyone aware about some Issue that prevents
+1
-Lukas
On 11/08/2011 07:05 PM, Olivier Lamy wrote:
Hello,
I'd like to release Apache Maven PMD Plugin 2.6.
We fixed 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140version=16437.
Staging repository:
https://repository.apache.org/content/repositories/maven-169/
+1
-Lukas
On Wed, Oct 26, 2011 at 11:36 PM, John Casey jdca...@commonjava.org wrote:
Hi everyone,
MAE is a new project that I've been working on for about a year and a half.
It's goal is to wrap the Maven APIs and make them easier to embed inside
other applications. This enables
+1
-Lukas
On 10/24/2011 04:03 PM, Mark Hobson wrote:
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=17520
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1
looks like http://jira.codehaus.org/browse/MSITE-333
The problem is certainly in Doxia, not velocity.
-Lukas
On 10/17/2011 08:55 PM, Robert Scholte wrote:
I've just discovered there's an escaping issue with the menu items (both fluido
and current maven skin).
The ampersand of 'Maven 2
Looking at the source code of doxia's
DefaultDecorationModelInheritanceAssembler, I would expect this to work.
Can you provide a test project?
-Lukas
Simone Tripodi wrote:
Hi again guys
I just figured out that if project B pom inherits from project A pom
which has attached the site
It's a bug.
-Lukas
On 10/13/2011 10:03 PM, Simone Tripodi wrote:
Hi all guys!
while generating the Apache DirectMemory site[1] using the xdoc
format, I noticed that for everysection element, if `class`
attribute is specified, it is replicated to the nestedh2 element.
For example, for
Doxia's JIRA is still at codehaus:
http://jira.codehaus.org/browse/DOXIA
Cheers,
-Lukas
On 10/14/2011 09:19 AM, Simone Tripodi wrote:
Thanks for confirming Lukas!
I just need to know if the Issue has to be filled in the Apache's or
Codehaus' JIRA...
TIA!
Simo
Note that this is the default behaviour of all standard maven skins,
your workaround is actually the solution I would have suggested. You can
change this default in the fluido skin site template if you wish.
-Lukas
On 10/14/2011 10:18 AM, Christian Grobmeier wrote:
Hey folks,
did you
This is a bug in Doxia, it should work by wrapping the content of the
style tag in a CDATA section, but it doesn't. I will file an issue.
Cheers,
-Lukas
On 10/14/2011 10:29 AM, Christian Grobmeier wrote:
Just found out... as per defintion you can usually add additional head
elements to
On 10/14/2011 11:31 AM, Christian Grobmeier wrote:
On Fri, Oct 14, 2011 at 11:16 AM, Lukas Theusslltheu...@apache.org wrote:
Note that this is the default behaviour of all standard maven skins, your
workaround is actually the solution I would have suggested. You can change
this default in
Could you specify what exactly you mean with element generation
behavior? What are you trying to achieve?
-Lukas
On 10/11/2011 11:17 AM, Simone Tripodi wrote:
Salut Olivier!
apologize for my lack of knowledge about it, but I didn't understand
if I can customize element generation behavior
I would have guessed that this should work with
source class=prettyprint
but it doesn't, I have just filed an issue:
http://jira.codehaus.org/browse/DOXIA-446
So unfortunately the answer to your last question is 'no' for the moment...
-Lukas
On 10/11/2011 12:11 PM, Simone Tripodi wrote:
Dennis Lundberg wrote:
So for xdoc we need a fix in doxia, but what about for apt documents? Is
that even possible with the current model?
No, not with the current apt format specification, apt doesn't know
anything about styles [1]. But this is a limitation of the specific
language
Thanks Dennis, that must have been a bad copypaste from a web page.
-Lukas
On 09/28/2011 09:55 PM, denn...@apache.org wrote:
Author: dennisl
Date: Wed Sep 28 19:55:13 2011
New Revision: 1177032
URL: http://svn.apache.org/viewvc?rev=1177032view=rev
Log:
Fix garbage characters.
Modified:
+1
-Lukas
On 09/26/2011 03:56 PM, Olivier Lamy wrote:
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=TextprojectId=10335Create=Create
Staging repo :
Hi Benson,
By changing the faq id, you also change the html anchor generated by the
site plugin, so any old links to this faq, eg the one I added today [1],
will not work anymore. I suggest to leave the id unchanged.
Cheers,
-Lukas
[1] http://svn.apache.org/viewvc?rev=1170457view=rev
I got those mails as well, but it seems to have been cleared by now.
I'd like to keep those pages for historic reference (some issues
addressed are still relevant) and make them read only. Only new pages
should go to cwiki now.
-Lukas
On 08/26/2011 12:59 AM, Brett Porter wrote:
You'd
which version of the site-plugin did you use (it is not fixed in the
wagon pom?)? I did a quick build with site-plugin-3.0 and breadcrumbs
look ok.
HTH,
-Lukas
On 08/19/2011 04:09 PM, Benson Margulies wrote:
http://maven.apache.org/wagon/wagon-providers/wagon-ssh/
Try the breadcumbs.
Dennis Lundberg wrote:
Hi
I've done some testing, and as far as site generation all is well.
Unfortunately site:stage-deploy deploys the site to the wrong place.
This is the same issue I saw when releasing, and staging the site for,
Maven Site Plugin 2.3.
Here's what I get when doing 'mvn
+1
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 46+1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=16829
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=17501
There are still a couple of issues left in
Dennis Lundberg wrote:
Hi
Does MSITE-600 also affect maven-site-plugin version 3?
If so, can you please update that JIRA to also have the appropriate
3.0 version as Affects version.
I suppose it will affect 3.0 as well, the code is the same. However, it
was suggested to release 3.0 in a
+1
-Lukas
On 07/28/2011 04:56 PM, Stephen Connolly wrote:
Hi,
This is a patch release to fix a particularly nasty regression:
http://jira.codehaus.org/browse/MRELEASE-697
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502
I won't fight about it but I dislike the idea of providing web links in
error messages. In a few years from now they might not exist any more or
provide irrelevant information. A stack trace is not pretty but google
doesn't mind that. At least log the stack trace at debug level if you
green light from here, thanks Herve for the updates!
-Lukas
On 07/22/2011 12:48 AM, Hervé BOUTEMY wrote:
Maven Site Plugin 3.0 is now ready for release (with its documentation) for me
If anybody still has something to change, please explain what so we can fix it
and release ASAP
Regards,
I uncommented the module as it passed for me locally and jenkins seems
happy too now:
https://builds.apache.org/job/maven-plugins-ITs-2.x/251/changes
https://builds.apache.org/job/maven-plugins-ITs-3.x/126/changes
(there are failures from other plugins though...).
Cheers,
-Lukas
On
The maven installation instructions [1] explicitly mention the M2_HOME
variable (and not MAVEN_HOME), is this obsolete?
-Lukas
[1] http://maven.apache.org/download.html#Installation
On 07/19/2011 08:26 AM, Stephen Connolly wrote:
I run m2 and m3 on the same machine at the same time (but
FYI: Dennis has had similar problems at the last release:
http://maven.40175.n5.nabble.com/VOTE-Release-Maven-JXR-version-2-2-td216534.html
but I'd have guessed that this was fixed since then.
There is still something else wrong with the cobertura report: the main
index page
I think it is common usus in maven land to keep plugins inside their
respective projects (see eg maven-archetype-plugin,
maven-enforcer-plugin, maven-scm-plugin, maven-surefire-plugin,...), the
main advantage being that they are released together and kept in sync
and up-to date with the main
an alternative is to give it maven-plugins as parent, but leave it
inside jxr, (like scm is doing). WDYT?
-Lukas
On 07/18/2011 02:50 PM, Benson Margulies wrote:
There's a lot of common stuff in the parent of the plugins:
announcements, changes, site config. Without mixins :-) we can't take
Benson: I have locally built and staged the site before and after this
commit and I don't see any of the mentioned issues. Have you actually
checked your local site? Did you run the site phase or the site:site
goal? Anyway, with site-plugin-2.3 the locally built and
stage(-deployed) sites
Tony Chemit wrote:
On Thu, 7 Jul 2011 21:22:43 +0200
Hervé BOUTEMYherve.bout...@free.fr wrote:
I forgot we had this great Jenkins instance with lots of OSes and
configuration combinations, and improved ITs to cover a lot of cases
(more than +50% over 3.0-beta-3)
Then I'm now confident that
SinkEventAttributes was added in Doxia-1.1, so there is apparently a
mixup with some some plugin/component that uses the old doxia-1.0. Not
sure it helps, but here are some notes about upgrading from doxia-1.0 to
1.1:
http://maven.apache.org/doxia/whatsnew-1.1.html
+1
-Lukas
Benson Margulies wrote:
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS|54cb0a05f789c3d1c147937a1867cbad60dfe04a|linversion=16884styleName=TextprojectId=10335Create=Create
There are still a plenty of issues left in JIRA:
Hi Mark,
Please use the Maven SVN Conventions for commit messages:
http://maven.apache.org/developers/conventions/svn.html
Thanks!
-Lukas
strub...@apache.org wrote:
Author: struberg
Date: Fri Jul 8 12:57:27 2011
New Revision: 1144300
URL: http://svn.apache.org/viewvc?rev=1144300view=rev
Hervé BOUTEMY wrote:
the rationale behind not going directly to 3.0 was that site plugin is hard to
test, particularly now that it is both compatible with Maven 2 and Maven 3,
which is something really new and probably tested by only a few of us
I don't quite agree with this rationale. Ease
+1
-Lukas
Olivier Lamy wrote:
Hi,
Here a vote to release the first version of maven-reporting-exec component
This component contains necessary code to run site plugin with maven 3.
So currently no jira issues as it's a simply an extraction of code
from maven site plugin for maven 3 branch
Any objections to making this 3.0-final? AFAICT the plugin is
functionally (almost) equivalent to the 2.x trunk version (only
exception is MSITE-484?), so why keep the beta?
-Lukas
Dennis Lundberg wrote:
Hi
What's the status on this? I know Hervé worked on extracting a shared
component
I get the same failure on my Mac. I recommend to configure a jenkins job
as multi-configuration type, see eg
https://builds.apache.org/job/doxia/
(Just choose multi-configuration-project instead of maven2/3 project
when adding the job)
HTH,
-Lukas
Benson Margulies wrote:
I just added
The first failure is expected since site-plugin-2.3:
http://maven.apache.org/plugins/maven-site-plugin/migrate.html
The other one, I don't know...
-Lukas
Stephen Connolly wrote:
Hervé, FYI things are not perfect yet
The woes of getting site:stage-deploy to work...
[stephenc@stephenc
Gavin McDonald wrote:
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Sunday, 19 June 2011 6:08 AM
To: Maven Developers List; Maven Project Management Committee List
Subject: [VOTE]: release maven-changes-plugin 2.6
Hi,
We solved 3 issues:
Really?
wrote:
-Original Message-
From: Lukas Theussl [mailto:ltheu...@gmail.com] On Behalf Of Lukas Theussl
Sent: Monday, 20 June 2011 7:25 PM
To: Maven Developers List
Subject: Re: [VOTE]: release maven-changes-plugin 2.6
Gavin McDonald wrote:
-Original Message-
From: Benson
unsubscribed from the list.
Gav...
--benson
On Mon, Jun 20, 2011 at 6:08 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 20 June 2011 10:48, Gavin McDonaldga...@16degrees.com.au
wrote:
-Original Message-
From: Lukas Theussl [mailto:ltheu...@gmail.com] On Behalf Of Lukas
hrm, sorry but I think there is actually a problem now with the stage
site. In r1136499 [1] you removed the version number from the staging
location. I'm not sure if there is a formal rule but we usually stage
the RC sites at a unique location that is kept after the release for
reference.
Isn't the correct staging site here:?
http://maven.apache.org/plugins/maven-enforcer-plugin-1.0.1/
It got deployed by you yesterday...
HTH,
-Lukas
Kristian Rosenvold wrote:
There is something weird with the multi-module site in enforcer. I
don't have the time
to debug this one at the
adressing to link from the plugin to the enforcer rules.
I'm a bit at loss at what is the correct way to fix it.
Kristian
Den 16.06.2011 11:17, skrev Lukas Theussl:
Isn't the correct staging site here:?
http://maven.apache.org/plugins/maven-enforcer-plugin-1.0.1/
It got deployed by you
links in site.xml uses relative
adressing to link from the plugin to the enforcer rules.
I'm a bit at loss at what is the correct way to fix it.
Kristian
Den 16.06.2011 11:17, skrev Lukas Theussl:
Isn't the correct staging site here:?
http://maven.apache.org/plugins/maven-enforcer-plugin
+1
-Lukas
Benson Margulies wrote:
Hi,
We solved 1 issues:
** Improvement
* [MPOM-12] - Update maven-plugins to new org.apache.maven:maven-parent:20
There are no open JIRAs against the maven-plugins parent.
1 - 100 of 1441 matches
Mail list logo
