Hi David
Yes. I wrote 'optional', so it is obviously not Core.
Regards
Ed Willink
On 16/12/2013 07:17, David M Williams wrote:
I'm not sure if I
should laugh, or cry?
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.
From:
Ed Willink
<ed@xxxxxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>,
Date:
12/16/2013 01:36 AM
Subject:
Re:
[cross-project-issues-dev]
m2e ponders participation in luna
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi
There is a workaround for 'incubation' within mature projects.
New optional experimental functionality may be shipped in
examples plugins.
Regards
Ed Willink
On 16/12/2013 04:06, Igor Fedorenko wrote:
> Hello,
>
> I just pushed updated version of m2e 1.5 plan.xml to our
git
> repository [1]. 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
theme, we
> updated m2e to include maven 3.1.1 earlier this year and
there is
a
> 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
and
> 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
ee" epp
> package maintainers be willing to keep m2e in?
>
> [1]
> http://git.eclipse.org/c/www.eclipse.org/m2e.git/commit/?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07
>
> --
> Regards,
> Igor
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|