If they are true examples, those example
components could just be omitted without loss of core functionality, right?
Even then, I guess I've not read the
guide lines that say "incubating examples" can be released without
an "incubating" label (since "incubating" refers to
a project, not a component?).
I hope this "workaround" is
not simply a way to "work around the release rules" established
by the Eclipse Foundation ...
since I think we all know what that
means ... after all, as committers, don't we agreed to abide by those rules?
But, I'm sure Ed meant something else
than the way I am reading it.
Ed Willink <ed@xxxxxxxxxxxxx>
Cross project issues
12/16/2013 01:36 AM
m2e ponders participation in luna
There is a workaround for 'incubation' within mature projects.
New optional experimental functionality may be shipped in examples plugins.
On 16/12/2013 04:06, Igor Fedorenko wrote:
> I just pushed updated version of m2e 1.5 plan.xml to our git
> repository . I will let technology pmc and other eclipse powers
> decide if this is good enough for m2e to stay in simultaneous release.
> Also, in line with our "use latest released maven" recurring
> updated m2e to include maven 3.1.1 earlier this year and there is
> 50/50 chance will update to maven 3.1.2, provided it is released before
> luna ip deadline. Problem is, maven 3.1.x includes Eclipse Aether
> Eclipse Sisu binaries, both currently under incubation as eclipse
> technology project.
> My questions are
> Can m2e get an exception to ship incubating components in a mature
> project on the grounds that m2e includes released maven version, which
> just happens to include eclipse incubating project binaries?
> If m2e has to go back to incubation, will "java" and "java
> package maintainers be willing to keep m2e in?
> cross-project-issues-dev mailing list