[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Ah, OK. I'm trying to get rid of it and was just wondering if you guys were actually using it. This does speak back to our need to make the IDE for C/C++ Developers on Linux and the IDE for C/C++ Linux Developers the same thing ;)
:D
> -----Original Message-----
> From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Jeff Johnston
> Sent: Thursday, November 10, 2011 4:57 PM
> To: epp-dev@xxxxxxxxxxx
> Subject: Re: [epp-dev] Juno M3...
>
> It was specified in our linuxtools feature.xml for epp and may have just been
> listed along with all cdt features at some time. I am trying to have it removed
> but I can't check in the change.
>
> -- Jeff J.
>
> On 11/10/2011 02:22 PM, Schaefer, Doug wrote:
> > Wrong list, but Jeff, what are you using the p2 feature for?
> >
> >> -----Original Message-----
> >> From: epp-dev-bounces@xxxxxxxxxxx
> >> [mailto:epp-dev-bounces@xxxxxxxxxxx]
> >> On Behalf Of Jeff Johnston
> >> Sent: Thursday, November 10, 2011 2:20 PM
> >> To: epp-dev@xxxxxxxxxxx
> >> Subject: Re: [epp-dev] Juno M3...
> >>
> >> Hi Markus,
> >>
> >> I sent another patch to you for Linux tools as the CDT has not
> >> included the p2 feature and that is breaking our build because it is listed as
> an import.
> >>
> >> Regards,
> >>
> >> -- Jeff J.
> >>
> >> On 11/10/2011 10:16 AM, Markus Knauer wrote:
> >>> Fine with me... I am just asking to get an overview of the status
> >>> and maybe there are issues that need to be addressed.
> >>>
> >>> Thanks,
> >>> Markus
> >>>
> >>> On 10 November 2011 13:35, Daniel Wiehl<Daniel.Wiehl@xxxxxxxxx
> >>> <mailto:Daniel.Wiehl@xxxxxxxxx>> wrote:
> >>>
> >>> Hi Markus____
> >>>
> >>> __ __
> >>>
> >>> Unfortunately, we will not be ready for M3, but will give our very
> >>> best to be ready for M4. That is because right now, we are
> >>> migrating to the compatibility layer of E4.____
> >>>
> >>> __ __
> >>>
> >>> Best Regards,____
> >>>
> >>> Daniel ____
> >>>
> >>> __ __
> >>>
> >>> __ __
> >>>
> >>> __ __
> >>>
> >>> *Von:*epp-dev-bounces@xxxxxxxxxxx
> >>> <mailto:epp-dev-bounces@xxxxxxxxxxx>
> >>> [mailto:epp-dev-bounces@xxxxxxxxxxx
> >>> <mailto:epp-dev-bounces@xxxxxxxxxxx>] *Im Auftrag von *Markus
> >> Knauer
> >>> *Gesendet:* Mittwoch, 9. November 2011 09<tel:2011%2009>:47
> >>> *An:* EPP Developer Mailing List
> >>> *Betreff:* Re: [epp-dev] Juno M3...____
> >>>
> >>> __ __
> >>>
> >>> Most packages are building, but not the LinuxTools and the Scout
> >>> packages. Both define requirements that are not yet contributed to
> >>> the Simultaneous Release repository.
> >>>
> >>> What's the status and outlook here? Any plans to change this for M3?
> >>> Or would it be possible to remove some dependencies in order to
> >>> build them with a reduced functionality (if this makes sense)?
> >>>
> >>> Thanks,
> >>> Markus____
> >>>
> >>> On 7 November 2011 20<tel:2011%2020>:28, Markus Knauer
> >>>
> <mknauer@xxxxxxxxxxxxxxxxx<mailto:mknauer@xxxxxxxxxxxxxxxxx>>
> >>> wrote:____
> >>>
> >>> ...maybe you've seen that I updated the configurations and enabled
> >>> the Hudson jobs for the EPP builds towards Juno M3. If you are
> >>> interested in early builds please check the juno.epp-xyz-builds on
> >>> Hudson
> >>>
> (https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/)
> >>> and the packages at
> >>> http://build.eclipse.org/technology/epp/epp_build/juno/download/.
> >>>
> >>> Thanks,
> >>> Markus
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> epp-dev mailing list
> >>> epp-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/epp-dev
> >>
> >> _______________________________________________
> >> epp-dev mailing list
> >> epp-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/epp-dev
> > _______________________________________________
> > epp-dev mailing list
> > epp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/epp-dev
>
> _______________________________________________
> epp-dev mailing list
> epp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/epp-dev
