Maven 2 & 3

MavenArtifactFilterManager needs to not filtering doxia-sink-api

Details

  • Number of attachments :
    1

Description

A plugin (like pdf-plugin) needs to use the most recent sink API and not the API embedded in maven.

Issue Links

This issue is related to:
MNG-3602 Schedule and release Doxia-1.1 Major Closed
This issue is depended upon by:
MSITE-299 Add Doxia logging support Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Siveton added a comment - - edited

An other solution could be to bump doxia-sink-api:1.0-beta-1 (when release done) in maven-reporting-api

Show
Vincent Siveton added a comment - - edited An other solution could be to bump doxia-sink-api:1.0-beta-1 (when release done) in maven-reporting-api
Hide
Permalink
Brian Fox added a comment -

should we just shade it then?

Show
Brian Fox added a comment - should we just shade it then?
Hide
Permalink
Brett Porter added a comment -

I don't think shading will work as the Sink interface is passed between core and plugin.

In doing this, there will be an implicit contract that the sink API can not have anything removed from it over time - though that's probably fair enough.

Show
Brett Porter added a comment - I don't think shading will work as the Sink interface is passed between core and plugin. In doing this, there will be an implicit contract that the sink API can not have anything removed from it over time - though that's probably fair enough.
Hide
Permalink
Brian Fox added a comment -

doxia-sink-api 1.0-beta-1 isn't released yet...

Show
Brian Fox added a comment - doxia-sink-api 1.0-beta-1 isn't released yet...
Hide
Permalink
Brian Fox added a comment -

Doxia isn't ready yet. See here: http://www.nabble.com/DOXIA---is-the-next-release-ready--tt16064480s177.html#a16064480

Show
Brian Fox added a comment - Doxia isn't ready yet. See here: http://www.nabble.com/DOXIA---is-the-next-release-ready--tt16064480s177.html#a16064480
Hide
Permalink
John Casey added a comment -

Pushing to 2.0.11 so we can have a smaller set of high-value issues to target for the next release (2.0.10).

Show
John Casey added a comment - Pushing to 2.0.11 so we can have a smaller set of high-value issues to target for the next release (2.0.10).
Hide
Permalink
John Casey added a comment -

Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.

Show
John Casey added a comment - Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.
Hide
Permalink
Brett Porter added a comment -

I believe we need to drop this from 2.1.0

Show
Brett Porter added a comment - I believe we need to drop this from 2.1.0
Hide
Permalink
Lukas Theussl added a comment -

This has been done in r783525, is the fix version correct?

Show
Lukas Theussl added a comment - This has been done in r783525, is the fix version correct?
Hide
Permalink
Olivier Lamy added a comment -

update fix version

Show
Olivier Lamy added a comment - update fix version
Hide
Permalink
Olivier Lamy added a comment -

I close it as it's done in trunk.
I will open a separate issue concerning site plugin with current trunk.

Show
Olivier Lamy added a comment - I close it as it's done in trunk. I will open a separate issue concerning site plugin with current trunk.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.