> On Apr 30, 2015, at 4:25 PM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> i would like to know if there are any objections to make a final release of
> the maven-eclipse-plugin ?
>
No objections to doing the release. Objection to calling it a final release.
:-)
Dan
> The reason is simply
Not that I'm aware of, but I can think of several steps:
- compile/runtime should not depend on maven-compat (the
plugin-testing-harness still requires it, so test-scope is still required,
though)
- consider testing with a Maven distribution without maven-compat
- use the major release to do
Do we have any wiki page describing the migration steps that would be
recommended to move a plugin from 2.2.1 deps to 3.x deps ?
I'm thinking *both* in terms of avoiding deprecations and "other" troubles
that may arise ?
Kristian
Hi,
i would like to know if there are any objections to make a final release
of the maven-eclipse-plugin ?
The reason is simply because it is the last plugin on the list which
misses the Maven 2.2.1 minimum
This could make our release map complete here...
as you can see here:
https://
My read is this work much like Github pages works. You have a repository with
your source and the rendered pages go into a branch. But nothing stops you from
having the source in one repo and just pushing the generated content to another
repo. This is currently how we do the M2Eclipse site. We h
Am 2015-04-30 um 00:31 schrieb Stephen Connolly:
http://bit.ly/1QLwWGS
(Source: https://twitter.com/planetapache/status/593535338074611712)
Wouldn't that imply always to clone a private copy of the entire repo
with autogerated stuff just to push changes back to the canonical repo?
Sounds li
