[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Foundation 1.0

Hi Jeff,

This sounds interesting. How is this done?  e.g. I cannot install a "classic vm" on Mac but I can set the OSGi target platform to e.g. foundation 1.1. If this is done the language is syntax checked okay. However, I can still use any Class that is in the active VM.

Regards,

Wim







On Sat, Sep 19, 2009 at 5:03 PM, Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx> wrote:
You can also use the PDE API tools to catch this kind of thing.  you need a description of Foundation 1.0 (not sure if there is one but hope there is).  Then you set up the API tools to use that description and it should report to you that you are violating the constraint.

Jeff



On 14-Sep-09, at 10:11 AM, Scott Lewis wrote:

Hi Wim,

Wim Jongman wrote:
Hi,

This is fine for XML based responses but what about the old fashioned "we end with a period the rest is up to you" style communications... Don't answer, I will take a look at the StringUtils class and see if a replace of regex is feasible :-).

Putting the manifest on Foundation 1.0 did not catch the Regex classes. How can I instruct Eclipse to only take what is available in Foundation and not look at the other available classes in the JRE? Can I still install a JRE based on nothing but foundation?

The way to do this in Eclipse is to install a Foundation-1.0 (and/or 1.1)-compliant execution. There are some docs for this here [1]  (this link may be slightly old/out of date...I'm not sure...if others know of more up-to-date links for ees please provide them).

[1] http://wiki.eclipse.org/Execution_Environment


Wim

On Mon, Sep 14, 2009 at 1:59 AM, Scott Lewis <slewis@xxxxxxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxxxxxx>> wrote:

  Hi Wim,

  So far, we have made due with the utilities we've put on this
  class:  org.eclipse.ecf.core.util.StringUtils.

  We (intentionally) have not put a lot of xml parsing functionality
  into ECF core parts of ECF.  Rather we've used the
  XMLReader/XMLWriter services provided by the
  javax.xml.parsers.SAXParserFactory...which has implementations for
  Foundation 1.1 (from ercp) and JRE 1.4+ (in Equinox itself).

  Scott

  Wim Jongman wrote:

      Hi Scott,

      What do the ECF core modules use to parse data streams if not
      regex?

      Best regards,

      Wim

      On Mon, Sep 14, 2009 at 1:30 AM, Scott Lewis
      <slewis@xxxxxxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxxxxxx>
      <mailto:slewis@xxxxxxxxxxxxxxxxx
      <mailto:slewis@xxxxxxxxxxxxxxxxx>>> wrote:

         Hi Wim,


         Wim Jongman wrote:

             Hi,

             I have downgraded the NNTP code to Foundation 1.0 and
             everything compiles fine. I had to throw out loads of
      for(x y
             : z) code and also my generics which is a bloody shame
             especially for the model. But alright, running this
      code on my
             watch is a charming idea... However, I am using other stuff
             like stringbuilders and regex which only appeared in
      1.4. Do I
             have to throw this out as well or can these be added as
             libraries to the Foundation 1.0 platforms?


         Deploying them as libraries to add to Foundation 1.0 ees is
      not at
         all straightforward.   However, I would suggest that you move
         things down to as far as can be comfortably accomodated (e.g.
         either Foundation 1.1or to JRE 1.4).  Especially since ECF core
         (and indeed Equinox 3.5) depends upon Foundation 1.1 ee as
      minimum.

         Scott



             Best regards,

             Wim
                    ------------------------------------------------------------------------

             _______________________________________________
             ecf-dev mailing list
             ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
      <mailto:ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>>

             https://dev.eclipse.org/mailman/listinfo/ecf-dev

         _______________________________________________
         ecf-dev mailing list
         ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
      <mailto:ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>>

         https://dev.eclipse.org/mailman/listinfo/ecf-dev


      ------------------------------------------------------------------------

      _______________________________________________
      ecf-dev mailing list
      ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
      https://dev.eclipse.org/mailman/listinfo/ecf-dev


  _______________________________________________
  ecf-dev mailing list
  ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
  https://dev.eclipse.org/mailman/listinfo/ecf-dev


------------------------------------------------------------------------

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev