>> >>> To unsubscribe, e-mail: [hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=5848364&i=6>
>> >>> For additional commands, e-mail: [hidden email]
>> <http:///u
8364&i=6>
> >>> For additional commands, e-mail: [hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5848364&i=7>
> >>>
> >>>
> >>
> >
> > -------
Just writing for myself, I want to explain why I am pushing just a bit.
I can justify spending time on Maven because I can, amongst other
things, solve some practical problems for my colleagues. If we hit a
plugin issue, I can (usually) fix it, fix whatever other low-hanging
items are in the JIRA
I keep changing the method signatures from time to time if I discover
there's a better way.
Once released we shouldn't touch method signatures anymore.
It's a matter of rewriting plugins and testing to confirm that all works
as intended.
Robert
Op Sat, 10 Oct 2015 23:58:58 +0200 schreef Tib
What is unstable on it, any non-jira issues?
On Sat, Oct 10, 2015 at 11:31 PM, Robert Scholte
wrote:
> maven-common-artifact-filters shouldn't be a problem.
>
> but the API for maven-artifact-transfer isn't stable enough yet, so please
> don't.
>
> Robert
>
> Op Sat, 10 Oct 2015 21:05:56 +0200 s
maven-common-artifact-filters shouldn't be a problem.
but the API for maven-artifact-transfer isn't stable enough yet, so please
don't.
Robert
Op Sat, 10 Oct 2015 21:05:56 +0200 schreef Benson Margulies
:
maven-common-artifact-filters and maven-artifact-transfer, both 3.0.
Hi Benson,
On 10/10/15 9:05 PM, Benson Margulies wrote:
maven-common-artifact-filters
is depending on maven-shared-utils 0.7..it should be updated to 3.0.0
first...so atm not...
and maven-artifact-transfer, both 3.0.
No other dependencies..so i don't any impediment for this ...
Ki
maven-common-artifact-filters and maven-artifact-transfer, both 3.0.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
