You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2009/03/02 20:11:29 UTC

Maven 2.1.0 and Doxia

Hi,

I know we've talked a bit about this already, but I'm still left with 
some questions. The most important of which is:

What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what to 
push this along?

I'm looking at the recent history of our attempt to get a Maven 2.1.0 
release ready to go, and I see that we've been talking about including a 
new release of Doxia for quite some time now....but where is the 
release? It looks like Doxia is still under development for 1.1, so I 
guess I'm just wondering:

1. What compelling reason do we have to upgrade Doxia in Maven 2.1.0? I 
understand that there's a largish assortment of plugins that cannot 
upgrade until Maven does...but what is in Doxia 1.1 that we can't live 
without until the next release of Maven (by which time - HOPEFULLY - 
Doxia would have been released and in the wild for some time)?

2. Is there a good reason why we can't publish a minimal set of 
interfaces and exceptions that are shared between Maven and Doxia, such 
that we could peg Maven to a version of that API and Doxia could 
maintain compatibility with that API, and specific versions of Doxia 
used in Maven could be a little more fluid?

For example, if the Site plugin were to instantiate the Doxia bits and 
pass them through the Maven core to the report plugins...can we make it 
so Maven core doesn't have much to do with it, and the site 
plugin/report plugins can be the ones to respond to new Doxia releases?? 
If we could agree on a minimal API artifact and just get that released 
ASAP, it seems like we could upgrade to Doxia 1.1 after the core 2.1.0 
release either through plugin-level deps or a new release of the site 
plugin.

I'm probably naive, but why aren't we moving in this direction?

I'm venting because I'm a little frustrated that this conversation came 
up back in August and here we are talking about it again...and again, we 
have no released version of Doxia to consume. So, we're in a position of 
rushing out a release of Doxia so we can push an unproven dependency 
into Maven just in time for a release. Doesn't this seem like a terrible 
idea to anyone else? Doxia isn't a small system like plexus-utils or 
plexus-ant-factory; judging from the length of its recent release 
cycles, it's much more complicated.

If we really are stuck with this sort of lock-step release cycle, isn't 
there something we can do right now, before releasing maven, doxia, or 
what-have-you, that would improve (solve?) the situation for next time?

Sorry for the gruffness, but it doesn't seem like we're taking steps to 
fix the underlying situation between Maven and Doxia...

-john

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Brett Porter <br...@apache.org>.
On 03/03/2009, at 11:45 PM, Brian E. Fox wrote:

>> 1.1 is NOT under development anymore, it hasn't been for at least  
>> over a year. All
>> we did was small bug fixes and enhancements that came along on the  
>> way because
>> there was nothing else to do.
>
> I don't follow this logic, if it's been done for over a year, why  
> has it been discussed for the last 3 maven releases and still no  
> release? It only seems relevant when a maven release is coming up  
> and then it's a hurry up and wait for doxia pattern.


There's a perception that there's no point releasing until Maven is  
going to adopt it (because nothing else can upgrade until the core  
supports it), and there's no point adopting it in Maven until its  
released. It's a deadlock that needs to be fixed, hence my proposal to  
just release it already and use it for the release to break it (and  
rollback if anything catastrophic happens in the RCs).

- Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Maven 2.1.0 and Doxia

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>1.1 is NOT under development anymore, it hasn't been for at least over a year. All 
>we did was small bug fixes and enhancements that came along on the way because 
>there was nothing else to do.

I don't follow this logic, if it's been done for over a year, why has it been discussed for the last 3 maven releases and still no release? It only seems relevant when a maven release is coming up and then it's a hurry up and wait for doxia pattern.

Re: Maven 2.1.0 and Doxia

Posted by John Casey <jd...@commonjava.org>.
For the record, the famous difficulties in testing multi-threaded code 
was one of the chief reasons I was hesitant to include the parallel 
resolution code. If we can achieve a degree of stability through the RC 
process, then fine.

But there is still a difference here between Doxia 1.1 and the parallel 
resolution issue: parallel artifact resolution is part of maven core, 
and is meant to mature alongside any other new code in time for the 
Maven release. Doxia, on the other hand, is separate and more complex to 
release in lock-step with other maven core code. As it stands, we 
*cannot* cut a release candidate for Maven to start looking at the 
stability with both of these modifications, at least in part because 
Doxia 1.1 doesn't exist yet.

This is a major issue for me; the Doxia release has been pending for 
months now, and only became interesting again when we started pushing 
for a Maven core release. That's backward IMO, since a software project 
ought to select from the field of available, *released* software for its 
dependencies. We've had the Doxia inclusion issue front-and-center in 
the 2.1.0 bucket for Maven this whole time, and we keep talking about 
releasing it...when can we actually get it started so we can get through 
the 72h voting period and get on to Maven release candidates? It's 
likely the RC process will take awhile, at least if the last go 'round 
is any indication, so it would be good to get on with it. We need a 
released version before we can even have an intelligent conversation 
about whether it ought to be included in the next Maven release, IMO.

-john

Vincent Siveton wrote:
> Hi Brian,
> 
> 2009/3/3 Brian E. Fox <br...@reply.infinity.nu>:
>> The more this thread goes on, the less optimistic I feel about this going into 2.1. We already know the 2.1M1 is stable and the point was to get it out in a release that people can use, ie non-milestone.
> 
> I hope that 2.1 is stable but I remember you that Benjamin found a
> parallel bug last week [1].
> 
> Making radical changes at the last minute is not good for stability
> and not good for the users. I think this should go into 2.2 and there
> should be a release cut and integrated into the 2.2 snapshots
> immediately so we have time to understand the issues. Using a maven
> release to effectively test doxia goes against all the progress we've
> made in the last year to stabilize the releases and improve quality.
>> (this is the same argument I think I used in 2.0.9, 2.0.10, and since the release didn't happen, it's still valid imo)
> 
> I don't remember the arguments for 2.0.10 but I have no arguments why
> 2.1 could not include Doxia 1.1.
> Maven 2.1 has new features Doxia too, it is a good combination IMHO.
> I guess we will have several RC before launching 2.1, similar to
> 2.0.10 release.
> So let's see what happen if we include Doxia 1.1, we could always do a
> revert if problems are found.
> 
> Cheers,
> 
> Vincent
> 
> [1] http://maven.markmail.org/message/st4h4i4hd5zljnf4
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Vincent Siveton <vi...@gmail.com>.
Hi Brian,

2009/3/3 Brian E. Fox <br...@reply.infinity.nu>:
> The more this thread goes on, the less optimistic I feel about this going into 2.1. We already know the 2.1M1 is stable and the point was to get it out in a release that people can use, ie non-milestone.

I hope that 2.1 is stable but I remember you that Benjamin found a
parallel bug last week [1].

Making radical changes at the last minute is not good for stability
and not good for the users. I think this should go into 2.2 and there
should be a release cut and integrated into the 2.2 snapshots
immediately so we have time to understand the issues. Using a maven
release to effectively test doxia goes against all the progress we've
made in the last year to stabilize the releases and improve quality.
>
> (this is the same argument I think I used in 2.0.9, 2.0.10, and since the release didn't happen, it's still valid imo)

I don't remember the arguments for 2.0.10 but I have no arguments why
2.1 could not include Doxia 1.1.
Maven 2.1 has new features Doxia too, it is a good combination IMHO.
I guess we will have several RC before launching 2.1, similar to
2.0.10 release.
So let's see what happen if we include Doxia 1.1, we could always do a
revert if problems are found.

Cheers,

Vincent

[1] http://maven.markmail.org/message/st4h4i4hd5zljnf4

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Maven 2.1.0 and Doxia

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The more this thread goes on, the less optimistic I feel about this going into 2.1. We already know the 2.1M1 is stable and the point was to get it out in a release that people can use, ie non-milestone. Making radical changes at the last minute is not good for stability and not good for the users. I think this should go into 2.2 and there should be a release cut and integrated into the 2.2 snapshots immediately so we have time to understand the issues. Using a maven release to effectively test doxia goes against all the progress we've made in the last year to stabilize the releases and improve quality.

(this is the same argument I think I used in 2.0.9, 2.0.10, and since the release didn't happen, it's still valid imo)

-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org] 
Sent: Tuesday, March 03, 2009 9:51 AM
To: Maven Developers List
Subject: Re: Maven 2.1.0 and Doxia

Lukas Theussl wrote:
> 
> 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. ;)

In my experience, five minutes isn't enough time to do anything when 
you've got more than one snapshot dependency/plugin you're trying to 
use. It's not trivial to replace a whole stack of artifacts with another 
whole stack of artifacts, then dig up a test project that will put the 
snapshots through their paces properly.

> 
> However, the main point is that I also see no reason for NOT upgrading 
> now (as I do not accept your FUD arguments). 

This is not merely my blowing smoke and trying to inject fear; we've 
been bitten time and again by bad/untested dependencies that get pushed 
out just ahead of a Maven release. I've spent quite a lot of time in the 
past on the front lines after these releases, answering questions about 
why things are messed up and debugging problems for people to find a 
workaround.

I don't think taking a slightly more conservative view of the release 
process as a result is in any way FUD. These are not unfounded views.


A few people have now taken
> their time to test 1.1 and have provided positive feedback (Brett, 
> Herve, Wendy). Doxia 1.1 (then beta-1) was present in the 2.0.x core for 
> 4 months [1], unfortunately it was reverted for the 2.0.10 release [2] 
> for reasons that I do not recall

These reasons were failing tests. I guess we didn't have the test 
coverage in place to figure that out for four months...good thing we're 
all set now, though.

> 
> As for the improvements you propose, it certainly sounds good and all, 
> and IIUC along the lines of what Jason is planning for Maven 3 [3], but 
> as long as there is nothing concrete on the table I don't see why we 
> shouldn't use what we have now (ie Doxia 1.1).

IMO, the only thing we know we have now is the released and 
battle-proven versions that went out with the previous release(s). These 
may have warts, but they're known quantities. We don't have a Doxia 1.1, 
that's kind of the point I was trying to make. We *may* have one soon, 
and maybe it'll work or maybe it won't. Maybe it'll introduce a crop of 
bugs that keep us from saying that this Maven release is *definitely* 
progress, *definitely* better.

Our problems with upgrading Doxia in Maven core are not simply 
prejudice, they have a long history of causing really difficult 
problems. This means Doxia has to be subject to extraordinary scrutiny 
before we include a new release in Maven itself.

-john


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by John Casey <jd...@commonjava.org>.
Lukas Theussl wrote:
> 
> 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. ;)

In my experience, five minutes isn't enough time to do anything when 
you've got more than one snapshot dependency/plugin you're trying to 
use. It's not trivial to replace a whole stack of artifacts with another 
whole stack of artifacts, then dig up a test project that will put the 
snapshots through their paces properly.

> 
> However, the main point is that I also see no reason for NOT upgrading 
> now (as I do not accept your FUD arguments). 

This is not merely my blowing smoke and trying to inject fear; we've 
been bitten time and again by bad/untested dependencies that get pushed 
out just ahead of a Maven release. I've spent quite a lot of time in the 
past on the front lines after these releases, answering questions about 
why things are messed up and debugging problems for people to find a 
workaround.

I don't think taking a slightly more conservative view of the release 
process as a result is in any way FUD. These are not unfounded views.


A few people have now taken
> their time to test 1.1 and have provided positive feedback (Brett, 
> Herve, Wendy). Doxia 1.1 (then beta-1) was present in the 2.0.x core for 
> 4 months [1], unfortunately it was reverted for the 2.0.10 release [2] 
> for reasons that I do not recall

These reasons were failing tests. I guess we didn't have the test 
coverage in place to figure that out for four months...good thing we're 
all set now, though.

> 
> As for the improvements you propose, it certainly sounds good and all, 
> and IIUC along the lines of what Jason is planning for Maven 3 [3], but 
> as long as there is nothing concrete on the table I don't see why we 
> shouldn't use what we have now (ie Doxia 1.1).

IMO, the only thing we know we have now is the released and 
battle-proven versions that went out with the previous release(s). These 
may have warts, but they're known quantities. We don't have a Doxia 1.1, 
that's kind of the point I was trying to make. We *may* have one soon, 
and maybe it'll work or maybe it won't. Maybe it'll introduce a crop of 
bugs that keep us from saying that this Maven release is *definitely* 
progress, *definitely* better.

Our problems with upgrading Doxia in Maven core are not simply 
prejudice, they have a long history of causing really difficult 
problems. This means Doxia has to be subject to extraordinary scrutiny 
before we include a new release in Maven itself.

-john


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Lukas Theussl <lt...@apache.org>.
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.

Neither do I want to pretend that there is anything in Doxia 1.1 that we 
absolutely cannot live without, - even though I certainly hope that there are a 
couple of new things that a lot of people will be happy about.

However, the main point is that I also see no reason for NOT upgrading now (as I 
do not accept your FUD arguments). A few people have now taken their time to test 
1.1 and have provided positive feedback (Brett, Herve, Wendy). Doxia 1.1 (then 
beta-1) was present in the 2.0.x core for 4 months [1], unfortunately it was 
reverted for the 2.0.10 release [2] for reasons that I do not recall, at least I 
do not remember that any problems ever cropped up. If you would have told me last 
Oct that 2.0.10 was about to be released we could have pushed Doxia 1.1 then. We 
are going to do it now.

1.1 is NOT under development anymore, it hasn't been for at least over a year. All 
we did was small bug fixes and enhancements that came along on the way because 
there was nothing else to do.


As for the improvements you propose, it certainly sounds good and all, and IIUC 
along the lines of what Jason is planning for Maven 3 [3], but as long as there is 
nothing concrete on the table I don't see why we shouldn't use what we have now 
(ie Doxia 1.1).

Cheers,
-Lukas


[1] http://svn.apache.org/viewvc?view=rev&revision=662398
[2] http://svn.apache.org/viewvc?view=rev&revision=705070
[3] http://www.nabble.com/Merging-with-XWiki-and-WikiModel-td21735399.html


John Casey wrote:
> Hi,
> 
> I know we've talked a bit about this already, but I'm still left with 
> some questions. The most important of which is:
> 
> What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what to 
> push this along?
> 
> I'm looking at the recent history of our attempt to get a Maven 2.1.0 
> release ready to go, and I see that we've been talking about including a 
> new release of Doxia for quite some time now....but where is the 
> release? It looks like Doxia is still under development for 1.1, so I 
> guess I'm just wondering:
> 
> 1. What compelling reason do we have to upgrade Doxia in Maven 2.1.0? I 
> understand that there's a largish assortment of plugins that cannot 
> upgrade until Maven does...but what is in Doxia 1.1 that we can't live 
> without until the next release of Maven (by which time - HOPEFULLY - 
> Doxia would have been released and in the wild for some time)?
> 
> 2. Is there a good reason why we can't publish a minimal set of 
> interfaces and exceptions that are shared between Maven and Doxia, such 
> that we could peg Maven to a version of that API and Doxia could 
> maintain compatibility with that API, and specific versions of Doxia 
> used in Maven could be a little more fluid?
> 
> For example, if the Site plugin were to instantiate the Doxia bits and 
> pass them through the Maven core to the report plugins...can we make it 
> so Maven core doesn't have much to do with it, and the site 
> plugin/report plugins can be the ones to respond to new Doxia releases?? 
> If we could agree on a minimal API artifact and just get that released 
> ASAP, it seems like we could upgrade to Doxia 1.1 after the core 2.1.0 
> release either through plugin-level deps or a new release of the site 
> plugin.
> 
> I'm probably naive, but why aren't we moving in this direction?
> 
> I'm venting because I'm a little frustrated that this conversation came 
> up back in August and here we are talking about it again...and again, we 
> have no released version of Doxia to consume. So, we're in a position of 
> rushing out a release of Doxia so we can push an unproven dependency 
> into Maven just in time for a release. Doesn't this seem like a terrible 
> idea to anyone else? Doxia isn't a small system like plexus-utils or 
> plexus-ant-factory; judging from the length of its recent release 
> cycles, it's much more complicated.
> 
> If we really are stuck with this sort of lock-step release cycle, isn't 
> there something we can do right now, before releasing maven, doxia, or 
> what-have-you, that would improve (solve?) the situation for next time?
> 
> Sorry for the gruffness, but it doesn't seem like we're taking steps to 
> fix the underlying situation between Maven and Doxia...
> 
> -john
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Maven 2.1.0 and Doxia

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>I'm venting because I'm a little frustrated that this conversation came

>up back in August and here we are talking about it again...and again,
we 
>have no released version of Doxia to consume. So, we're in a position
of 
>rushing out a release of Doxia so we can push an unproven dependency 
>into Maven just in time for a release. Doesn't this seem like a
terrible 
>idea to anyone else?

It does to me, and this is why it got yanked from 2.0.9. 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by John Casey <jd...@commonjava.org>.
Are they eagerly awaiting Doxia 1.1?

What I'm wondering is, what are we standing in the way of by not putting 
the latest, greatest Doxia into Maven 2.1.0?

Back in July/August of last year, we talked about pulling back from the 
Doxia upgrade so it could be released and soak into the community for 
awhile, as a substitute for in-depth testing. If Doxia had been released 
as 1.1 back in October, and had been used (or even tried) in the 
interim, a lot of this hand-wringing could be dispensed with. We could 
have bumped the Doxia version first thing in the 2.1.0 release process, 
and gone on our ways...and tested it all along while we fixed other bugs.

If Doxia doesn't really have other consumers, then that means Doxia 
effectively has a slave release cycle, locked to Maven's. In this case, 
releasing early doesn't matter, and the risks are unavoidable when we do 
an upgrade. The risks can be minimized with a large set of tests, but 
they're unavoidable.

I'm just trying to understand sort of why and how we got to this point. 
I'm not as convinced that the work we're doing in 2.1.x is pointless 
because 3.0 is right around the corner. So for me, it still makes sense 
to plan out our migration path WRT Doxia and other libraries in a way 
that will absolutely minimize the possible impact on our users.

-john

Vincent Siveton wrote:
> Hi John,
> 
> 2009/3/3 John Casey <jd...@commonjava.org>:
>> Is Maven the only consumer of Doxia? When you say "everything else moving
> 
> AFAIK, Xwiki and m2eclipse are also using Doxia
> 
> Cheers,
> 
> Vincent
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Jason van Zyl <jv...@sonatype.com>.
On 3-Mar-09, at 2:50 PM, Vincent Siveton wrote:

> Hi Jason
>
> 2009/3/3 Jason van Zyl <jv...@sonatype.com>:
>> XWiki is not using it because it doesn't work. Vincent created a  
>> wrapper to
>
> We added a lot of tests in 1.1 and all seems to work with 2.0.x and  
> 2.1.
> I can't see the problems/issues that you refer. Could you point me?

That's the whole point of the argument. A couple people working on  
something that gets pushed into a release is not going to be found by  
any of us, it's going to be found by users. Which is why we have  
longish release cycles where the context code is not shifting around.  
We have a hard enough time with Maven itself. If the 1.1 had been  
released and soaked the whole period of the initial RCs that would be  
easier to deal with.

>
>> try and help integrate it but as it seems no one here is interested  
>> it will
>
> If you refer to this thread [1], I can't see any consensus. Probably,
> you could ping the list or redirect this thread to dev@maven.
>

I'm frankly not interested any more. If no one here is interested  
that's fine.

>> likely be dropped. It's not being used in production for anything.
>
> Probably, Vincent will be the best person to response, but actually,
> XWiki uses Doxia [2]. I know it is not 1.1 in production.

It's in there because I asked him to and the only thing of interest is  
the Confluence parser right now. It will be redone with JavaCC using  
WikiModel as no one is using the Wiki markup parsers from Doxia on a  
daily basis so they just don't get the attention. There is also now  
WikiText in Mylyn which has now also surpassed Doxia.

>
> Cheers,
>
> Vincent
>
> [1] http://maven.markmail.org/message/azjndnva4y54kx7h
> [2] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwiki-rendering-parsers/xwiki-rendering-parser-doxia/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.

   -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Vincent Siveton <vi...@gmail.com>.
Hi Jason

2009/3/3 Jason van Zyl <jv...@sonatype.com>:
> XWiki is not using it because it doesn't work. Vincent created a wrapper to

We added a lot of tests in 1.1 and all seems to work with 2.0.x and 2.1.
I can't see the problems/issues that you refer. Could you point me?

> try and help integrate it but as it seems no one here is interested it will

If you refer to this thread [1], I can't see any consensus. Probably,
you could ping the list or redirect this thread to dev@maven.

> likely be dropped. It's not being used in production for anything.

Probably, Vincent will be the best person to response, but actually,
XWiki uses Doxia [2]. I know it is not 1.1 in production.

Cheers,

Vincent

[1] http://maven.markmail.org/message/azjndnva4y54kx7h
[2] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwiki-rendering-parsers/xwiki-rendering-parser-doxia/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Jason van Zyl <jv...@sonatype.com>.
On 3-Mar-09, at 9:52 AM, Vincent Siveton wrote:

> Hi John,
>
> 2009/3/3 John Casey <jd...@commonjava.org>:
>> Is Maven the only consumer of Doxia? When you say "everything else  
>> moving
>
> AFAIK, Xwiki and m2eclipse are also using Doxia
>

XWiki is not using it because it doesn't work. Vincent created a  
wrapper to try and help integrate it but as it seems no one here is  
interested it will likely be dropped. It's not being used in  
production for anything.

Inside m2eclipse we'll move toward the XWiki support.

> Cheers,
>
> Vincent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Vincent Siveton <vi...@gmail.com>.
Hi John,

2009/3/3 John Casey <jd...@commonjava.org>:
> Is Maven the only consumer of Doxia? When you say "everything else moving

AFAIK, Xwiki and m2eclipse are also using Doxia

Cheers,

Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Brett Porter <br...@apache.org>.
On 04/03/2009, at 1:59 AM, John Casey wrote:
>
> Is Maven the only consumer of Doxia?

That would be the indication I get, but anything is possible.

> When you say "everything else moving forward" do you mean Maven  
> plugins, or Doxia's development itself?

Plugins (eg, PDF plugin has to shade in doxia 1.1, and can't be used  
as a report).

Cheers,
Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by John Casey <jd...@commonjava.org>.
Brett Porter wrote:
> On 03/03/2009, at 6:11 AM, John Casey wrote:
> 
>> What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what 
>> to push this along?
> 
> You should first review the exact same question I asked 5 days ago :)

I had just finished reading this thread probably 30m before writing the 
email. My concern was that we weren't talking enough about whether it 
was a good idea to include Doxia at all...it seemed to be more about 
which new version of Doxia to include. I wanted to make sure the 
question of "why upgrade at all?" was asked.

I no longer believe in progress for the sake of progress, so I wanted a 
clear answer to that question.

> 
>> 1. What compelling reason do we have to upgrade Doxia in Maven 2.1.0? 
>> I understand that there's a largish assortment of plugins that cannot 
>> upgrade until Maven does...but what is in Doxia 1.1 that we can't live 
>> without until the next release of Maven (by which time - HOPEFULLY - 
>> Doxia would have been released and in the wild for some time)?
> 
> For me, because it breaks the deadlock on the release and facilitates 
> everything else moving forward rather than the split that occurred.
> 

Is Maven the only consumer of Doxia? When you say "everything else 
moving forward" do you mean Maven plugins, or Doxia's development itself?

-john

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Brett Porter <br...@apache.org>.
I can add a bit of detail on the core side in addition to Vincent and  
Lukas' mails.

On 03/03/2009, at 6:11 AM, John Casey wrote:

> What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what  
> to push this along?

You should first review the exact same question I asked 5 days ago :)

> 1. What compelling reason do we have to upgrade Doxia in Maven  
> 2.1.0? I understand that there's a largish assortment of plugins  
> that cannot upgrade until Maven does...but what is in Doxia 1.1 that  
> we can't live without until the next release of Maven (by which time  
> - HOPEFULLY - Doxia would have been released and in the wild for  
> some time)?

For me, because it breaks the deadlock on the release and facilitates  
everything else moving forward rather than the split that occurred.

>
> 2. Is there a good reason why we can't publish a minimal set of  
> interfaces and exceptions that are shared between Maven and Doxia,  
> such that we could peg Maven to a version of that API and Doxia  
> could maintain compatibility with that API, and specific versions of  
> Doxia used in Maven could be a little more fluid?

This is already the case. We really only need the Sink and  
MavenReport. The original intent was that those interfaces wouldn't  
change, but Sink did. It needs to be decoupled, but for now, updating  
just the sink/logging api will facilitate plugins using new versions  
(and new doxia releases can be made without changing the sink/logging  
that is now bundled)

>
> For example, if the Site plugin were to instantiate the Doxia bits  
> and pass them through the Maven core to the report plugins...can we  
> make it so Maven core doesn't have much to do with it, and the site  
> plugin/report plugins can be the ones to respond to new Doxia  
> releases?? If we could agree on a minimal API artifact and just get  
> that released ASAP, it seems like we could upgrade to Doxia 1.1  
> after the core 2.1.0 release either through plugin-level deps or a  
> new release of the site plugin.

This is the ideal solution - I tried various iterations but it doesn't  
work in a backwards compatible way. Maybe some on-the-fly ASM wizardry  
could do it by creating the correct version of the sink interface at  
the time, but I think a better bet is to break compat in 3.0 and  
centre the sink handling in the site plugin instead as you say.

> If we really are stuck with this sort of lock-step release cycle,  
> isn't there something we can do right now, before releasing maven,  
> doxia, or what-have-you, that would improve (solve?) the situation  
> for next time?

I don't think it should be needed again if the API JARs are managed  
carefully. The key thing is that the Doxia release needs to start  
*right away* as originally suggested.

Cheers,
Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 2.1.0 and Doxia

Posted by Vincent Siveton <vi...@gmail.com>.
Hi John,

2009/3/2 John Casey <jd...@commonjava.org>:
> Hi,
>
> I know we've talked a bit about this already, but I'm still left with some
> questions. The most important of which is:
>
> What exactly is the plan for Doxia and Maven 2.1.0? Who's doing what to push
> this along?

As you probably know, the plan is here [1].
Doxia Team just have release 1.0 in February, and 1.1 is plan for this week.
I will start the release tomorrow morning if nobody already starts it.

> I'm looking at the recent history of our attempt to get a Maven 2.1.0
> release ready to go, and I see that we've been talking about including a new
> release of Doxia for quite some time now....but where is the release? It

Initially, Doxia 1.1 was planned to be included in Maven 2.0.10 but we
(Maven Team) decided to include it in Maven 2.1 (MNG-3602)

> looks like Doxia is still under development for 1.1, so I guess I'm just

All issues are fixes now [2] so not under development :)

> wondering:
>
> 1. What compelling reason do we have to upgrade Doxia in Maven 2.1.0? I
> understand that there's a largish assortment of plugins that cannot upgrade
> until Maven does...but what is in Doxia 1.1 that we can't live without until
> the next release of Maven (by which time - HOPEFULLY - Doxia would have been
> released and in the wild for some time)?

Maven 2.1 adds important features, Doxia too [3].
So, due these important features, IMHO Maven 2.1 should include Doxia 1.1.
If not included, we need to add Doxia 1.1 in Maven 2.2 which seems to
not be append due to Maven 3.

> 2. Is there a good reason why we can't publish a minimal set of interfaces
> and exceptions that are shared between Maven and Doxia, such that we could
> peg Maven to a version of that API and Doxia could maintain compatibility
> with that API, and specific versions of Doxia used in Maven could be a
> little more fluid?
>
> For example, if the Site plugin were to instantiate the Doxia bits and pass
> them through the Maven core to the report plugins...can we make it so Maven
> core doesn't have much to do with it, and the site plugin/report plugins can
> be the ones to respond to new Doxia releases?? If we could agree on a
> minimal API artifact and just get that released ASAP, it seems like we could
> upgrade to Doxia 1.1 after the core 2.1.0 release either through
> plugin-level deps or a new release of the site plugin.
>
> I'm probably naive, but why aren't we moving in this direction?

We probably could do it but you could also wait for one week more
without pain :)
If you have now a better idea to decouple Maven from Doxia, let's discuss!

> I'm venting because I'm a little frustrated that this conversation came up
> back in August and here we are talking about it again...and again, we have
> no released version of Doxia to consume. So, we're in a position of rushing
> out a release of Doxia so we can push an unproven dependency into Maven just
> in time for a release. Doesn't this seem like a terrible idea to anyone
> else? Doxia isn't a small system like plexus-utils or plexus-ant-factory;
> judging from the length of its recent release cycles, it's much more
> complicated.

Few people takes time to test Doxia 1.1 with Maven 2.1, maybe because
it depends on a particular site plugin [4].
I decided to include Doxia 1.1 (MNG-3602) in the build (r749465) so it
will be included in the 2.1 RC and, I hope, could be tested.

FYI MNG-3402 was a blocker issue but it is possible to shade Doxia in
the Maven report plugins to be backward compatible with 2.0.x [5]

> If we really are stuck with this sort of lock-step release cycle, isn't
> there something we can do right now, before releasing maven, doxia, or
> what-have-you, that would improve (solve?) the situation for next time?
>
> Sorry for the gruffness, but it doesn't seem like we're taking steps to fix
> the underlying situation between Maven and Doxia...

Doxia Team did tests to be *sure* that this integration doesn't break
site with Maven 2.1.

So I don't think we are stuck.

I hope this respond clarify your concerns.

Cheers,

Vincent

[1] http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
[2] http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13617&styleName=Html&projectId=10780&Create=Create
[3] http://maven.apache.org/doxia/whatsnew-1.1.html
[4] https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-doxia-1.1/
[5] http://maven.markmail.org/message/rc2r3efiffm26pac

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org