| Re: [m2e-dev] kepler m1 candidate build (aka juno sr1 release candidate) |
I think all/many extras in [1] already use [1,2] range.
[1] http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/
--
Regards,
Igor
On 12-08-21 10:04 AM, Marcel Schutte wrote:
I do want to give m2e 1.2 a try, but my other plugins prevent me from
installing it. It might be a lack of know how from my side, but
currently plugins like m2e-wtp, m2e connector for build helper and
several others cannot be installed because they state that they are
compatible with m2e [1.0.0,1.2.0) which excludes 1.2.0
Testing m2e 1.2 on its own is not really an option for me, I need them
all before I can do a meaningful regression test.
Is there a way around this, or is it up to the individual plugin
maintainers to update their version range? A relation question: is it
really necessary to be this restrictive in version ranges? Why can't for
instance m2e-wtp state compatibility with [1.0.0,2.0.0) ?
Regards, Marcel
On Tue, Aug 21, 2012 at 1:52 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx<mailto:igor@xxxxxxxxxxxxxx>> wrote:
Friendly reminder, kepler m1 is this coming Friday. If you don't test
and don't report problems you find, currently staged candidate build
1.2.0.20120819-2129 will become m2e 1.2 release.
--
Regards,
Igor
On 12-08-17 11:10 PM, Igor Fedorenko wrote:
I've just uploaded m2e 1.2.0.20120818-0226 to [1]. This is out
current
kepler m1 candidate build. You can see full list of fixes in
this build
in [2], but the big change is of course workspace-level lifecycle
mapping configuration. Kudos to Andrew Eisenberg from VMWare for
driving
this work to completion.
There appears to be a recent regression in archetyper support
tracked as
bug 387521, so we may have another build early next week, but
unless new
regressions are found, I do not expect any other changes before
final
kepler m1 build is declared. We also plan to contribute the same
build
to juno sr1, so it will likely be our official m2e 1.2 release
(I guess
I need to start doing the paperwork already).
Please test m2e 1.2 and provide feedback either here or in m2e
bugzilla.
[1] http://download.eclipse.org/__technology/m2e/milestones/1.2
<http://download.eclipse.org/technology/m2e/milestones/1.2>
[2]
https://bugs.eclipse.org/bugs/__buglist.cgi?list_id=2652291&__query_format=advanced&product=__m2e&target_milestone=Kepler%__20M1
<https://bugs.eclipse.org/bugs/buglist.cgi?list_id=2652291&query_format=advanced&product=m2e&target_milestone=Kepler%20M1>
--
Regards,
Igor_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
--
Fotografie
http://schutte.name/
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev