Home » Eclipse Projects » Oomph » How to inherit a project from another in a different setup file
| How to inherit a project from another in a different setup file [message #1428982] |
Mon, 22 September 2014 16:32  |
|
Hi,
My use case:
I want to provide a public .setup file and a private one. The private one will inherits everything from the public one and also add references to some internal resources (such as Sonar, CI builds).
I tried to specify the "Logical Project Container" but not action from the container has been executed.
is it something supported? If yes, how can I handle it?
Regards,
Aurélien Pupier - Red Hat
Senior Software Engineer in Fuse Tooling team
|
|
|
| Re: How to inherit a project from another in a different setup file [message #1428998 is a reply to message #1428982] |
Mon, 22 September 2014 16:58  |
 Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Aurelien,
Comments below.
On 22/09/2014 6:32 PM, Aurelien Pupier wrote:
> Hi,
>
> My use case:
> I want to provide a public .setup file and a private one. The private
> one will inherits everything from the public one
What specifically will it inherit?
> and also add references to some internal resources (such as Sonar, CI
> builds).
What do you mean specifically by "adding references"?
>
> I tried to specify the "Logical Project Container" but not action from
> the container has been executed.
That's only used in the outline preview. At runtime, the project must
be contained somewhere.
I'm wondering if it's actually necessary to contain the private project
in the public project. I.e., what does that buy you verses having two
separate projects and simply specifying a stream from each? (That's
what we've been doing.)
>
> is it something supported?
No, it's not...
> If yes, how can I handle it?
I'm wondering why you actually need it. (I imagine this is primarily
an issue of sharing variables, but I could be missing the point.)
>
> Regards,
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: How to inherit a project from another in a different setup file [message #1429012 is a reply to message #1428998] |
Mon, 22 September 2014 17:29 |
|
Hi Ed,
thanks for your very fast answers!
> My use case:
> I want to provide a public .setup file and a private one. The private
> one will inherits everything from the public one
What specifically will it inherit?
It will inherits everything which is not related to our internal Sonar instance and Jira. So same working sets, same projects, same Preferences, all P2 directors from the public one.
I'm wondering if it's actually necessary to contain the private project
in the public project. I.e., what does that buy you verses having two
separate projects and simply specifying a stream from each? (That's
what we've been doing.)
Ok I understand, you simply ask to install two projects.
My idea was to provide a single one for the company developers too.
I'm wondering why you actually need it. (I imagine this is primarily
an issue of sharing variables, but I could be missing the point.)
Effectively if we need to share variables it might an issue. Currently, I don't have this use case.
So currently, the only thing is that it would be easier for my company developers if they a single project instead of two to import. Anyway, I think that we can live without it.
Regards and thanks again for your answers
Aurélien Pupier - Red Hat
Senior Software Engineer in Fuse Tooling team
|
|
|
| Re: How to inherit a project from another in a different setup file [message #1429023 is a reply to message #1429012] |
Mon, 22 September 2014 17:44 |
Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Aurelien,
Comments below.
On 22/09/2014 7:29 PM, Aurelien Pupier wrote:
> Hi Ed,
>
> thanks for your very fast answers!
>
>> My use case:
>> I want to provide a public .setup file and a private one. The private
>> one will inherits everything from the public one
> What specifically will it inherit?
>
> It will inherits everything which is not related to our internal Sonar
> instance and Jira. So same working sets, same projects, same
> Preferences, all P2 directors from the public one.
Well, if you choose the stream for your public project, you will get all
those. None of these are a reason why another project would needs to be
contained...
>
> I'm wondering if it's actually necessary to contain the private
> project in the public project. I.e., what does that buy you verses
> having two separate projects and simply specifying a stream from each?
Exactly. Ease of selection I supposed, but the project page remembers
your last selection so that's not a big win...
> (That's what we've been doing.)
> Ok I understand, you simply ask to install two projects.
Yep.
> My idea was to provide a single one for the company developers too.
>
>
> I'm wondering why you actually need it. (I imagine this is primarily
> an issue of sharing variables, but I could be missing the point.)
> Effectively if we need to share variables it might an issue.
> Currently, I don't have this use case.
That would be the strongest concern...
> So currently, the only thing is that it would be easier for my company
> developers if they a single project instead of two to import. Anyway,
> I think that we can live without it.
One thing I've considered is creating dependencies between streams so
you can basically specify "if this stream is selected, this other stream
should also be selected automatically", but it's all complicated enough
already that we'd need stronger use cases...
>
> Regards and thanks again for your answers
You're welcome.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Goto Forum:
Current Time: Fri Apr 26 22:05:48 GMT 2024
Powered by FUDForum. Page generated in 0.03677 seconds |
] 
Search
Help
Register
Login
Home
