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 classes will be distributed with 3.x. Not
sure what you guys are planning for 3.x.
There were never any doxia classes distributed with any version of
maven, that's not the issue.
doxia-sink and yes it is an issue. This particular issue aside.
Well that's exacly the point about MNG-3402. The only place where a doxia class is
referenced in maven 2.x core is MavenReport in reporting-api, but the Sink there
is the old codehaus Sink. This interface, apart from getting deprecated, has not
changed since I don't know when. So even though the MavenArtifactFilterManager
puts the maven Sink in front in your class path, the class is never actually
referenced.
The problem is (was) that maven 2.x is filtering the doxia version
(MNG-3402), which makes it impossible for plugins to use their own
(updated) version of doxia (usecase: pdf plugin). The development of
doxia was hindered not by it's coupling to maven, but by maven
refusing any update to doxia.
The that immediately presents the problem we have. If doxia is hindered
by Maven not updating then it's not really and independent project used
by anyone.
I think you misunderstood me or maybe I misunderstand you. I did not say "doxia is
hindered by Maven not updating", I said "...by maven refusing any update to
doxia". The current site plugin on trunk is still using doxia 1.0 which is
effectively more than a year old now and has seen only few changes the year before
that. Doxia 1.1 was released 3 months ago and since then we've solved 47 issues
for 1.1.1. It would be released by now if it wasn't for those new Apache
requirements. Together with the ~100 issues solved in 1.1, this makes ~150 solved
issues that current maven site users are still waiting for.
Why is it a problem that doxia is "not really and independent project used by
anyone"? Does doxia have any different status than, say, wagon, surefire,
archetype...?
But anyway, I'm happy that all this will be no issue in 3.x :)
Nope.
Yes, really, I am happy...
Doxia will truly be an independent project and will survive or die
based on the value provided reporting implementation created with it.
Not sure how to parse that and again, don't know what you mean with "independent
project"?
-Lukas
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.
-Lukas
[1] http://www.nabble.com/MNG-3402-tt17207692.html
[email protected] wrote:
Author: olamy
Date: Wed Jun 10 21:30:40 2009
New Revision: 783525
URL: http://svn.apache.org/viewvc?rev=783525&view=rev
Log:
don't filter doxia-sink-api. users will be still able to run : mvn
site:site
Modified:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultArtifactFilterManager.java
Modified:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultArtifactFilterManager.java
URL:
http://svn.apache.org/viewvc/maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultArtifactFilterManager.java?rev=783525&r1=783524&r2=783525&view=diff
==============================================================================
---
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultArtifactFilterManager.java
(original)
+++
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultArtifactFilterManager.java
Wed Jun 10 21:30:40 2009
@@ -54,7 +54,7 @@
artifacts.add( "classworlds" );
artifacts.add( "plexus-classworlds" );
artifacts.add( "commons-cli" );
- artifacts.add( "doxia-sink-api" );
+ //artifacts.add( "doxia-sink-api" );
artifacts.add( "jsch" );
artifacts.add( "maven-artifact" );
artifacts.add( "maven-artifact-manager" );
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
the course of true love never did run smooth ...
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
