Eclipse Community Forums: Oomph » Assign project streams to product versions

Help

Home

Home » Eclipse Projects » Oomph » Assign project streams to product versions

Show: Today's Messages :: Show Polls :: Message Navigator

Assign project streams to product versions [message #1721700]

Fri, 29 January 2016 10:05

Oliver Libutzki

Messages: 40
Registered: September 2011

Member

Hi,

is there a way to define which project streams are compatible with product versions.

Background: We use Xtext to provide some DSLs which are part of our Product. Everytime we have changes in the DSLs we provide a new Product version.

Each stream of our project is pinned to a specific version of the Product in order to ensure the DSL compatibility.

Is there a way to configure the relationship from the Project Stream to the Product version?

It would be great if the installer just provides project streams which are compatible with the chosen Product version.

Thanks for your answer!

Kind regards
Oliver

Report message to a moderator

Re: Assign project streams to product versions [message #1721706 is a reply to message #1721700]

Fri, 29 January 2016 10:21

Ed Merks

Messages: 33141
Registered: July 2009

Senior Member

Oliver,

Comments below.

On 29.01.2016 11:05, Oliver Libutzki wrote:
> Hi,
>
> is there a way to define which project streams are compatible with
> product versions.
No.
>
> Background: We use Xtext to provide some DSLs which are part of our
> Product. Everytime we have changes in the DSLs we provide a new
> Product version.
I see.
>
> Each stream of our project is pinned to a specific version of the
> Product in order to ensure the DSL compatibility.
>
> Is there a way to configure the relationship from the Project Stream
> to the Product version?
>
> It would be great if the installer just provides project streams which
> are compatible with the chosen Product version.
I wonder if a different approach wouldn't work okay... I.e., focus on
defining your project stream so that it can work with the Platform
Product, which is basically an Eclipse IDE with nothing specific
installed. Then your project definition itself can ensure that it
spells out all the specific things it wants installed into a bare bones
IDE. At least with your Xtext example, that should work quite well
because the latest Xtext can install into Neon, Mars, or other older
versions of the IDE...
>
> Thanks for your answer!
>
> Kind regards
> Oliver

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Assign project streams to product versions [message #1721998 is a reply to message #1721706]

Tue, 02 February 2016 08:06

Oliver Libutzki

Messages: 40
Registered: September 2011

Member

Ed Merks wrote on Fri, 29 January 2016 05:21

I wonder if a different approach wouldn't work okay... I.e., focus on
defining your project stream so that it can work with the Platform
Product, which is basically an Eclipse IDE with nothing specific
installed. Then your project definition itself can ensure that it
spells out all the specific things it wants installed into a bare bones
IDE. At least with your Xtext example, that should work quite well
because the latest Xtext can install into Neon, Mars, or other older
versions of the IDE...

That's a great idea... thanks, Ed.

Report message to a moderator

Previous Topic:	Default value for unsigned content?
Next Topic:	command line

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 22:12:19 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter