Home » Eclipse Projects » Oomph » Targlets: Do not inherit Targets
|
| Re: Targlets: Do not inherit Targets [message #1471687 is a reply to message #1471673] |
Thu, 13 November 2014 09:09   |
 Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Marco,
Comments below.
On 13/11/2014 10:00 AM, Marco Descher wrote:
> I am currently setting up Oomph for our project. Up to now, we used a
> .target. Now I added all the repos in this target file to a new
> targlet, which seems to work quite well.
>
> The problem however is, that within my targlet I reference an old
> update site of Eclipse http://download.eclipse.org/eclipse/updates/4.2
> which I have to use, but the target created by Oomph also inherits the
> Eclipse platform resp. site
> http://download.eclipse.org/eclipse/updates/4.4
That depends on the value of the eclipse.target.platform variable. It's
default value is None in which case it contributes an empty repository
list. Better would be if you don't duplicate the information about the
basic platform updates but rather structure your repository choices like
all the setups, so there choices for Mars, Luna, Kepler and so on so
that your project can be composed with other projects...
>
> So how may I tell oomph, not to inherit targlets, but only use the
> ones defined in my project?!
You can certainly set the variable to None, but I'd rather seem projects
be composeable and that won't be the case if there isn't some common
convention, so better if you use the same variable and the same
repository list names to add to the base repository choice. If all
setups do this, you could expect to compose then an have them
consistently induce a Mars, Luna, or Kepler TP...
>
> Thanks!
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | | | | | | |
| Re: Targlets: Do not inherit Targets [message #1471821 is a reply to message #1471790] |
Thu, 13 November 2014 11:08 |
Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Marco,
Comments below.
On 13/11/2014 11:36 AM, Marco Descher wrote:
> Hy,
>
> the thing is that I am using Oomph for a project, that builds an e4
> RCP based application. This application is currently built against the
> Juno target.
And will fail to build against a higher target because of very specific
upper bounds? That seems rare, but possible. E.g., EMF builds against
Eclipse 3.6 (or is it 3.5) but it's not a problem to resolve a TP that
contains Mars...
In any case, it sounds like you should provide a Juno choice, but I'm
not sure why/if it's necessary to exclude the ability to choose a higher
version of the TP... If that's really true, it implies that these
things would only run with Juno, would seem unfortunate.
> So oomph does not (officially) support working with a newer IDE than
> the target is (by forcing the IDE target onto the
> system)!?
I'm not sure what you're saying here... It's common that the TP is an
older version than the IDE itself.
> That isI still do not understand where to set the value "None" for
> realizing a fully IDE <-> Target decoupled dev evironment :( sorry
In the JDT.setup I set it to Mars in the Master stream, because it's the
only thing I tested and wanted feedback on the design before proceeding.
<?xml version="1.0" encoding="UTF-8"?>
<setup:Stream
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
name="master"
label="Master">
<setupTask
xsi:type="setup:VariableTask"
name="eclipse.target.platform"
value="Mars"
storageURI="scope://Workspace"/>
</setup:Stream>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Targlets: Do not inherit Targets [message #1473219 is a reply to message #1471821] |
Fri, 14 November 2014 12:45 |
Marco Descher
Messages: 197
Registered: October 2010
Location: Austria |
Senior Member |
|
|
Ed,
I really tried hard, and do now understand the way that eclipse.target.platform=None is supposed to work. It does however not work in my environment. Please have a look at this
Trying this, it ignores ALL my repository lists, even if I explicitely name my own None, just as you did in the Eclipse Platform part. On any other name I always get the IDE local update repo included which breakes with my .target requirements (-> see background part)
Background on my intentions
I understand all your thoughts on what would be better and should be done, but the fact is
- We develop an e4 based rcp app, built against a defined .target - this is no direct Eclipse project
- I want to have an up-to-date IDE while completely in development against the .target (currently built using Maven Tycho)
- I can not refer to the target file itself, hence I want to simply have the p2 repos in the target as repositories in Ooomph, but ONLY those!
- I want to introduce Ooomph, without currently being forced to change my back-end build system, hence I want to stick to the target!
I think that Oomph is great, and it will become even greater if I could create like a .setup file at the main repo view of my github project easily getting anyone to contribute - which is what I want to do for the Elexis project (https://github.com/elexis/elexis-3-core)
EDIT The screenshot is from another project I am trying to introduce Ooomph ... - same problem here 
[Updated on: Fri, 14 November 2014 12:46] Report message to a moderator |
|
|
| Re: Targlets: Do not inherit Targets [message #1473254 is a reply to message #1473219] |
Fri, 14 November 2014 13:16 |
Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Marco,
Comments from Christian suggested he had problems because he'd used
Oomph for a while and had variables stored in his user.setup that are
now normally stored in the workspace.setup... Perhaps that's an issue
for you?
On 14/11/2014 1:45 PM, Marco Descher wrote:
> Ed,
>
> I really tried hard, and do now understand the way that
> eclipse.target.platform=None is supposed to work. It does however not
> work in my environment. Please have a look at this
>
>
>
> Trying this, it ignores ALL my repository lists, even if I explicitely
> name my own None, just as you did in the Eclipse Platform part. On any
> other name I always get the IDE local update repo included which
> breakes with my .target requirements (-> see background part)
Perhaps there are things I should see that aren't making it to my
Thunderbird reader?
>
> Background on my intentions
> I understand all your thoughts on what would be better and should be
> done, but the fact is
>
>
> We develop an e4 based rcp app, built against a defined .target - this
> is no direct Eclipse project
There is a task to simply activate a .target file, which is slow and
horrible, but that's the nature of .target files.
> I want to have an up-to-date IDE while completely in development
> against the .target (currently built using Maven Tycho)
We use Maven Tycho for Oomph as well. We use annotations in the targlet
task to keep the .target file up-to-date (as well as various things like
keeping the pom.xmls updated)...
> I can not refer to the target file itself,
?
> hence I want to simply have the p2 repos in the target as repositories
> in Ooomph, but ONLY those!
Though it's clear that we're talking about one repository that you're
actually already specifying...
> I want to introduce Ooomph, without currently being forced to change
> my back-end build system, hence I want to stick to the target!
I'm not sure what this means. Perhaps you simply want to reuse your
..target an not use targlets...
>
>
> I think that Oomph is great, and it will become even greater if I
> could create like a .setup file at the main repo view of my github
> project easily getting anyone to contribute - which is what I want to
> do for the Elexis project (https://github.com/elexis/elexis-3-core)
That is what we've been doing for many projects, but with only the small
snippet of information you're providing, it's hard to give you
high-level feedback.
Perhaps you have a *.setup committed somewhere and I can have a look at
it the whole thing, and test it out, and then suggest how I would write
it if I were you...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | | |
Goto Forum:
Current Time: Sat Apr 27 04:19:19 GMT 2024
Powered by FUDForum. Page generated in 0.04339 seconds |
] 
Search
Help
Register
Login
Home
see comment above!
sorry