Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

This is a proposed release plan for Doxia and related pieces of Maven software.

Action

Developers

Date completed

Comments

Release 1.0-alpha-11 of Doxia, from the alpha branch

dennisl

2008-05-20

 

Update Site plugin to use 1.0-alpha-11 of Doxia

dennisl

2008-05-20

 

Update PIR plugin to use 1.0-alpha-11 of Doxia

dennisl

2008-05-20

 

Release version 1.0 of maven-doxia-tools, a shared component

vsiveton

2008-05-29

 

Use maven-doxia-tools 1.0 in the Site plugin

dennisl

2008-05-29

 

Use maven-doxia-tools 1.0 in the PIR plugin

vsiveton

2008-05-29

 

Release version 1.0.1 of maven-doxia-tools

dennisl

2008-06-14

 

Use maven-doxia-tools 1.0.1 in the Site plugin

dennisl

2008-06-14

 

Use maven-doxia-tools 1.0.1 in the PIR plugin

dennisl

2008-06-14

 

Release Site plugin 2.0-beta-7, to avoid having too large releases

dennisl

2008-07-02

 

Release PIR plugin 2.1

vsiveton

2008-07-28

 

Move the unresolved issues slated for 2.0-beta-7 to 2.0-beta-8 or later

dennisl

2008-05-20

 

Switch the Site plugin (2.0-beta-8-SNAPSHOT) to use Doxia 1.0-beta-1 SNAPSHOT

ltheussl

 

 

Switch the PIR plugin (2.2-SNAPSHOT) to use Doxia 1.0-beta-1 SNAPSHOT

vsiveton

 

 

Release Doxia 1.0-beta-1

ltheussl

 

 

Come up with a way to handle MNG-3402

 

 

Need to release Maven-2.0.10, see discussion

Release maven-reporting-impl using Doxia 1.0-beta-1

ltheussl

 

 

Release maven-doxia-tools using Doxia 1.0-beta-1

ltheussl

 

 

Release Site plugin 2.0-beta-8 using Doxia beta-1

dennisl

 

 

Release PIR plugin 2.2 using Doxia beta-1

vsiveton

 

 

Start collecting a list of issues that blocks a Doxia 1.0 release

ltheussl

 

 

Push that list down to 0

ltheussl

 

 

Release Doxia 1.0

vsiveton

 

 

Release Site plugin 2.0

dennisl

 

 

Feel free to attach your name to any of the actions above, if you are able to help with them.

sorting out Maven dependencies on Doxia

As seen in MNG-3402, Maven distributes a doxia-sink-api copy in its uber-jar: this is the main dependency between Maven and Doxia. Every API change in doxia-sink-api needs to be included in a Maven version before it can be used in a plugin (setting this Maven's version as prerequisite).

There are other more subtle dependencies in miscellaneous parts of Maven.

Doxia: doxia-sink-api

interface org.apache.maven.doxia.sink.Sink (since 1.0-alpha-6, no API change until 1.0-alpha-11)

deprecated interface org.codehaus.doxia.sink.Sink extends o.a.m.d.s.Sink (since 1.0-alpha-7)

interface org.apache.maven.doxia.sink.SinkFactory (since 1.0-alpha-9)

Maven Components: reporting-api

interface org.apache.maven.reporting.MavenReport#generate(org.codehaus.doxia.sink.Sink, Locale)

Maven [2.0.2;2.0.7] depends on doxia-sink-api 1.0-alpha-7
Maven 2.0.8 depends on doxia-sink-api 1.0-alpha-9
Maven 2.0.9 depends on doxia-sink-api 1.0-alpha-10, equivalent to alpha-9
Maven 2.0.10-RC depends on doxia-sink-api 1.0-alpha-11, equivalent to alpha-9

Maven Shared: reporting-impl

abstract class org.apache.maven.reporting.AbstractMavenReport implements MavenReport
             #generate(org.apache.maven.doxia.sink.Sink, SinkFactory, Locale)

Maven Plugins: maven-site-plugin

interface org.apache.maven.doxia.sink.SinkFactory (same as doxia-sink-api 1.0-alpha-9, to avoid Maven 2.0.8 as a prerequisite: see MSITE-368)

interface org.apache.maven.reporting.MavenMultiPageReport extends MavenReport
             #generate(org.apache.maven.doxia.sink.Sink, SinkFactory, Locale)

Question: shouldn't MavenMultiPageReport interface be included in reporting-api? and used in reporting-impl? As usual, it could stay copied in maven-site-plugin only to avoid prerequisite to a recent Maven version.

  • No labels