You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kenney Westerhof <fo...@gods.nl> on 2006/07/24 16:58:52 UTC
Reporting / Doxia / site api change
Hi there,
I've stumbled upon a problem I need some assistance with.
I've got an API change for maven-reporting: adding a SinkFactory
parameter to the generate( Sink, Locale ) method. It allows a plugin
to produce multiple pages.
However, this API change is tied to the maven-site-plugin and
maven-project-info-reports-plugin (because they use the new
maven-reporting api/impl dependencies).
First I tried adding an interface containing the new method,
leaving the old one intact. This works. However, once that interface
has to go and be merged with the original interface, dropping the
deprecated 2-arg generate method. So adding a new interface is only
postponing the problem I'm facing now:
The site plugin uses the new API, but existing reporting plugins may not.
If the site plugin is released, it will render a set of reporting plugins
unusable (AbstractMethodError/NoSuchMethodException).
This means that all reporting plugins are tied to the site plugin's
version. It's also the case with the recent doxia changes: there's
no longer a 'createSink' method in the Renderer interface, so when the
site plugin upgrades it's dependency on doxia past 1.0-alpha-7, we run
into trouble.
We could synchronize the release of the site plugin with releases of all
other reporting plugins, even those on mojo.c.o. However, there will
no doubt be problems when users have fixed versions for plugins in their
poms.
What to do..?
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Reporting / Doxia / site api change
Posted by Brett Porter <br...@apache.org>.
I'm a little unsure why this is, but would need to take a closer look.
I thought the situation was that they were tied to the sink/reporting
API versions in the Maven core, and not the site plugin, and that
reports were executed from isolated plugin containers. I could be wrong.
Can we get this on the 2.1 design list? Even though it is sort of a
plugin issue, it is worth having on the radar in case the core can
provide the necessary services.
- Brett
On 25/07/2006 12:58 AM, Kenney Westerhof wrote:
> Hi there,
>
> I've stumbled upon a problem I need some assistance with.
>
> I've got an API change for maven-reporting: adding a SinkFactory
> parameter to the generate( Sink, Locale ) method. It allows a plugin
> to produce multiple pages.
>
> However, this API change is tied to the maven-site-plugin and
> maven-project-info-reports-plugin (because they use the new
> maven-reporting api/impl dependencies).
>
> First I tried adding an interface containing the new method,
> leaving the old one intact. This works. However, once that interface
> has to go and be merged with the original interface, dropping the
> deprecated 2-arg generate method. So adding a new interface is only
> postponing the problem I'm facing now:
>
> The site plugin uses the new API, but existing reporting plugins may not.
> If the site plugin is released, it will render a set of reporting plugins
> unusable (AbstractMethodError/NoSuchMethodException).
>
> This means that all reporting plugins are tied to the site plugin's
> version. It's also the case with the recent doxia changes: there's
> no longer a 'createSink' method in the Renderer interface, so when the
> site plugin upgrades it's dependency on doxia past 1.0-alpha-7, we run
> into trouble.
>
> We could synchronize the release of the site plugin with releases of all
> other reporting plugins, even those on mojo.c.o. However, there will
> no doubt be problems when users have fixed versions for plugins in their
> poms.
>
> What to do..?
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org