[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] juno m1 and indigo sr1
|
Source folder (i.e. src/main/java, etc) encoding is expected to be set
correctly in m2e 1.0 already and we plan to merge [1] for Indigo SR1. If
there are other scenarios when m2e does not properly manage source code
encoding you want addressed in SR1, please open new bugreport in
bugzilla and attach the patch in git-format-patch format.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=343927
--
Regards,
Igor
On 11-08-01 4:44 PM, Julien HENRY wrote:
Hi Igor,
What do you need to include MNGECLIPSE-1782 in next release of m2e? It seems there is already some code provided in the comments, but do you need a patch? I really miss this feature and I am ready to contribute for it.
Thanks
Julien
________________________________
De : Igor Fedorenko<igor@xxxxxxxxxxxxxx>
À : Maven Integration for Eclipse developers mailing list<m2e-dev@xxxxxxxxxxx>
Envoyé le : Lundi 1 Août 2011 13h41
Objet : [m2e-dev] juno m1 and indigo sr1
As discussed in [1], we are planning to maintain single development
stream both for Indigo SR and Juno work, which means we have about two
weeks left to produce m2e build for Indigo SR1 RC1 and Juno M1
(see [2]). With this in mind I went through m2e bugzilla backlog earlier
today and marked all bugzillas I believe are important and doable given
the time we still have left.
If you are working on a patch and would like to see this patch included
in Indigo SR1 build, please indicate so on the corresponding bugzilla so
we can better plan our time.
[1] http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00573.html
[2] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan
--
Regards,
Igor
_______________________________________________
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
