We've done quite a bit of debugging over the last several months,
and finally got our IP approvals for the various dependencies on
external tools (like Polyglot and LPG).

The preferences specification language has been enhanced
considerably (with support for new field types, and several
elements are now optional, with sensible defaults).

There is now a "presentation specification language" (more or
less bleeding-edge, which provides fairly concise and declarative
syntax for specifying token coloring, outlining, folding, and
label provider services. It's been a while since I worked on this,
but at last report it was generating sensible-looking working code.
Your mileage may vary.

We've tested this on Eclipse 3.3 and 3.4. We've not had time as
of yet to try it out on 3.5Mx, so any intrepid souls out there
that would like to try and post their experiences would be very
helpful. We've been developing on MacOS, Windows, and Linux, so
hopefully you'll find things working fairly well on these
platforms.

The update site houses not only IMP, but all of the other
features on which IMP depends (which previously you needed to
go to other update sites to retrieve):

- LPG
- Polyglot
- SDF + Box

Also, we've done a bit of reorganization of the features, so that
now the analysis-related code (the "Program DataBase", or PDB,
and friends) have been relocated to separate features.

Finally, as a quick heads-up, there are some minor breaking API
changes to PluginBase (derived classes need to define getLanguageID())
and a couple of other classes.

This system is a windows platform so it makes sense that the lpg install
didn't include the linux & macosx plugins; however, it seems that p2 now
believes that *all* os/arch-specific versions of the lpg.generator
plugins must be installed.

Is this a bug?

-- Nicolas.

Robert M. Fuhrer wrote:
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>

Great work! As my primary test, the new release works well under the Eclipse
3.5M5. The stability of this release has been much improved in my feeling.
hope imp will end incubation soon.

"Robert M. Fuhrer" <rfuhrer@watson.ibm.com>
??????:gnvqlr$7sf$1@build.eclipse.org...
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>
> --
> Cheers,
> -- Bob
>
> --------------------------------
> Robert M. Fuhrer
> Research Staff Member
> Programming Technologies Dept.
> IBM T.J. Watson Research Center
>
> IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
> X10: Productive High-Performance Parallel Programming (http://x10.sf.net)

"Robert M. Fuhrer" <rfuhrer@watson.ibm.com>
??????:gnvqlr$7sf$1@build.eclipse.org...
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>
> --
> Cheers,
> -- Bob
>
> --------------------------------
> Robert M. Fuhrer
> Research Staff Member
> Programming Technologies Dept.
> IBM T.J. Watson Research Center
>
> IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
> X10: Productive High-Performance Parallel Programming (http://x10.sf.net)

is this being looked at by anyone as it's been 3 months since Nicolas'
post now? Is there anything that I can do to help resolve this? If so,
please let me know either on this group or via a direct email.

> I installed IMP from the update site below; however, I get these errors
> when installing other features:
>
> Cannot complete the install because some dependencies are not satisfiable
> "lpg.generator.feature.group 2.0.16" requires
> "lpg.generator.linux_x86 [2.0.16]"
> "lpg.generator.feature.group 2.0.16" requires
> "lpg.generator.macosx_x86 [2.0.16]"
>
> This system is a windows platform so it makes sense that the lpg
> install didn't include the linux & macosx plugins; however, it seems
> that p2 now believes that *all* os/arch-specific versions of the
> lpg.generator plugins must be installed.

I don't think it has been committed to LPG, but the fix is to add the
correct os and arc attributes to those plugins in the feature.xml file
(which you could do on your local install if you so wished):

I've updated the feature manifests for the lpg.generator feature in
LPG 2.0.16 and 2.0.17 on the LPG update site. The changes have also
been checked into CVS HEAD on LPG's sourceforge repo.

I've also updated the copies of the lpg.generator feature on the IMP
update site.

Please post if you have good or bad experiences after these changes.

Thanks!

Robert M. Fuhrer wrote:
> Thanks, Jason! I had assumed that having the appropriate os/arch tags on
> the plugin fragments themselves was enough. Happy to be proven wrong,
> though, as this solves a long-standing problem.
>
> We've been busy with some bug triage, and have been sorting through the
> [many existing bugs, determining their current status. Needless to say,
> the install issues were/are high on the priority list.]
>
> I'll apply these fixes to the lpg.generator feature ASAP, and the next
> release of LPG will have the fixes.
>
> I'll also fix the 2.0.16 release (which is the latest one for which we
> have a proper CQ in place for IMP), and patch the update site.
>
> Again, many thanks Jason for pointing this out!
>
> Jason C Garcowski wrote:
>> Hello,
>>
>> I don't think it has been committed to LPG, but the fix is to add the
>> correct os and arc attributes to those plugins in the feature.xml file
>> (which you could do on your local install if you so wished):
>>
>> <plugin
>> id="lpg.generator.linux_x86"
>> download-size="0"
>> install-size="0"
>> os="linux"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>
>> <plugin
>> id="lpg.generator.macosx_x86"
>> download-size="0"
>> install-size="0"
>> os="macosx"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>
>> <plugin
>> id="lpg.generator.win32_x86"
>> download-size="0"
>> install-size="0"
>> os="win32"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>

Still no luck with the update site.
The LPG parser plugin installs but now I get the following error trying to
install the IMP IDE dev tools plugin (note the required lpg runtime
version which causes the error):

This system is a windows platform so it makes sense that the lpg install
didn't include the linux & macosx plugins; however, it seems that p2 now
believes that *all* os/arch-specific versions of the lpg.generator
plugins must be installed.

Is this a bug?

-- Nicolas.

Robert M. Fuhrer wrote:
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>

Great work! As my primary test, the new release works well under the Eclipse
3.5M5. The stability of this release has been much improved in my feeling.
hope imp will end incubation soon.

"Robert M. Fuhrer" <rfuhrer@watson.ibm.com>
??????:gnvqlr$7sf$1@build.eclipse.org...
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>
> --
> Cheers,
> -- Bob
>
> --------------------------------
> Robert M. Fuhrer
> Research Staff Member
> Programming Technologies Dept.
> IBM T.J. Watson Research Center
>
> IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
> X10: Productive High-Performance Parallel Programming (http://x10.sf.net)

"Robert M. Fuhrer" <rfuhrer@watson.ibm.com>
??????:gnvqlr$7sf$1@build.eclipse.org...
> Hi All,
>
> I've just posted a new release of IMP on our eclipse.org update
> site (at long last!). The update site location is:
>
> http://download.eclipse.org/technology/imp/updates
>
> We've done quite a bit of debugging over the last several months,
> and finally got our IP approvals for the various dependencies on
> external tools (like Polyglot and LPG).
>
> The preferences specification language has been enhanced
> considerably (with support for new field types, and several
> elements are now optional, with sensible defaults).
>
> There is now a "presentation specification language" (more or
> less bleeding-edge, which provides fairly concise and declarative
> syntax for specifying token coloring, outlining, folding, and
> label provider services. It's been a while since I worked on this,
> but at last report it was generating sensible-looking working code.
> Your mileage may vary.
>
> We've tested this on Eclipse 3.3 and 3.4. We've not had time as
> of yet to try it out on 3.5Mx, so any intrepid souls out there
> that would like to try and post their experiences would be very
> helpful. We've been developing on MacOS, Windows, and Linux, so
> hopefully you'll find things working fairly well on these
> platforms.
>
> The update site houses not only IMP, but all of the other
> features on which IMP depends (which previously you needed to
> go to other update sites to retrieve):
>
> - LPG
> - Polyglot
> - SDF + Box
>
> Also, we've done a bit of reorganization of the features, so that
> now the analysis-related code (the "Program DataBase", or PDB,
> and friends) have been relocated to separate features.
>
> Finally, as a quick heads-up, there are some minor breaking API
> changes to PluginBase (derived classes need to define getLanguageID())
> and a couple of other classes.
>
> --
> Cheers,
> -- Bob
>
> --------------------------------
> Robert M. Fuhrer
> Research Staff Member
> Programming Technologies Dept.
> IBM T.J. Watson Research Center
>
> IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
> X10: Productive High-Performance Parallel Programming (http://x10.sf.net)

is this being looked at by anyone as it's been 3 months since Nicolas'
post now? Is there anything that I can do to help resolve this? If so,
please let me know either on this group or via a direct email.

> I installed IMP from the update site below; however, I get these errors
> when installing other features:
>
> Cannot complete the install because some dependencies are not satisfiable
> "lpg.generator.feature.group 2.0.16" requires
> "lpg.generator.linux_x86 [2.0.16]"
> "lpg.generator.feature.group 2.0.16" requires
> "lpg.generator.macosx_x86 [2.0.16]"
>
> This system is a windows platform so it makes sense that the lpg
> install didn't include the linux & macosx plugins; however, it seems
> that p2 now believes that *all* os/arch-specific versions of the
> lpg.generator plugins must be installed.

I don't think it has been committed to LPG, but the fix is to add the
correct os and arc attributes to those plugins in the feature.xml file
(which you could do on your local install if you so wished):

I've updated the feature manifests for the lpg.generator feature in
LPG 2.0.16 and 2.0.17 on the LPG update site. The changes have also
been checked into CVS HEAD on LPG's sourceforge repo.

I've also updated the copies of the lpg.generator feature on the IMP
update site.

Please post if you have good or bad experiences after these changes.

Thanks!

Robert M. Fuhrer wrote:
> Thanks, Jason! I had assumed that having the appropriate os/arch tags on
> the plugin fragments themselves was enough. Happy to be proven wrong,
> though, as this solves a long-standing problem.
>
> We've been busy with some bug triage, and have been sorting through the
> [many existing bugs, determining their current status. Needless to say,
> the install issues were/are high on the priority list.]
>
> I'll apply these fixes to the lpg.generator feature ASAP, and the next
> release of LPG will have the fixes.
>
> I'll also fix the 2.0.16 release (which is the latest one for which we
> have a proper CQ in place for IMP), and patch the update site.
>
> Again, many thanks Jason for pointing this out!
>
> Jason C Garcowski wrote:
>> Hello,
>>
>> I don't think it has been committed to LPG, but the fix is to add the
>> correct os and arc attributes to those plugins in the feature.xml file
>> (which you could do on your local install if you so wished):
>>
>> <plugin
>> id="lpg.generator.linux_x86"
>> download-size="0"
>> install-size="0"
>> os="linux"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>
>> <plugin
>> id="lpg.generator.macosx_x86"
>> download-size="0"
>> install-size="0"
>> os="macosx"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>
>> <plugin
>> id="lpg.generator.win32_x86"
>> download-size="0"
>> install-size="0"
>> os="win32"
>> arch="x86"
>> version="2.0.16"
>> fragment="true"
>> unpack="false"/>
>>

Still no luck with the update site.
The LPG parser plugin installs but now I get the following error trying to
install the IMP IDE dev tools plugin (note the required lpg runtime
version which causes the error):