Well, to be absolutely clear, to fix that issue I might need to make bigger
changes (incl. public methods) as there should probably be some design
changes. The patch is not complete.
But I'd like this discussion to be generic and not specific to this issue.
/Anders
On Tue, Jan 29, 2013 at 3:59
+1
And the patch is a signature change on a private method so not a real issue.
2013/1/29 Anders Hammar :
> Just want to check what the general opinion is about changing method
> signatures of Plexus component interfaces in our plugins for a minor
> version release.
>
> In a perfect world it would
+1 on changing. no one is forced to upgrade.
On Jan 29, 2013, at 1:19 PM, Anders Hammar wrote:
> Just want to check what the general opinion is about changing method
> signatures of Plexus component interfaces in our plugins for a minor
> version release.
>
> In a perfect world it would be aweso
Just want to check what the general opinion is about changing method
signatures of Plexus component interfaces in our plugins for a minor
version release.
In a perfect world it would be awesome to always keep backwards
compatibility and at least never do any changes unless a major version. But
as
