Home » Eclipse Projects » Oomph » component.def dependencies cached?
| component.def dependencies cached? [message #1700458] |
Thu, 02 July 2015 17:00  |
|
Hi
I started to use component.def in projects that are not bundles nor
features, and I use them as a kind of "root" features, i.e., they
specify dependencies on other projects (possibly containing other
component.def). I have the impression that Oomph caches dependencies
for such component.def since if I modify such files, and try to rerun
the targlet task, even on a brand new workspace, oomph keeps on using
the old dependencies... is that correct? What's the best way, in case,
to clean such cache? Or am I missing something?
thanks in advance
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
| Re: component.def dependencies cached? [message #1700463 is a reply to message #1700458] |
Thu, 02 July 2015 17:51  |
|
Am 02.07.2015 um 19:00 schrieb Lorenzo Bettini:
> Hi
>
> I started to use component.def in projects that are not bundles nor
> features, and I use them as a kind of "root" features, i.e., they
> specify dependencies on other projects (possibly containing other
> component.def). I have the impression that Oomph caches dependencies
> for such component.def since if I modify such files, and try to rerun
> the targlet task, even on a brand new workspace, oomph keeps on using
> the old dependencies... is that correct?
It must be correct if your problem description is correct :P
But I really don't remember that we cache that data explicitely. A couple things you can try to narrow down the problem:
1) Check that the targlet task is really triggered, considered needed, checked on the confirmation page and finally
executed.
2) Please paste the relevant log output (select the targlet task and the relevant log part is selected, too).
3) Delete all p2 profiles for *that* workspace (they have names like
C__develop_cdo_ws-dc38723c3ee234fa85ecb766bce6a3c3be8984db.profile).
4) Rename the .metadata\.plugins\org.eclipse.oomph.targlets.core directory
Do you have the chance to (remote) debug this problem? Interesting places for breakpoints are:
1) org.eclipse.oomph.targlets.internal.core.TargletContainer.resolveUnits(IProgressMonitor)
2) org.eclipse.oomph.targlets.internal.core.TargletContainer.updateProfile(String, String, String, IProgressMonitor)
3) org.eclipse.oomph.targlets.internal.core.TargletContainer.analyzeWorkspaceIUs(EList<Requirement>, SubMonitor)
With all this let's see if we can pin the problem...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> What's the best way, in case,
> to clean such cache? Or am I missing something?
>
> thanks in advance
> Lorenzo
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: component.def dependencies cached? [message #1700472 is a reply to message #1700463] |
Thu, 02 July 2015 18:36 |
|
On 02/07/2015 19:51, Eike Stepper wrote:
> Am 02.07.2015 um 19:00 schrieb Lorenzo Bettini:
>> Hi
>>
>> I started to use component.def in projects that are not bundles nor
>> features, and I use them as a kind of "root" features, i.e., they
>> specify dependencies on other projects (possibly containing other
>> component.def). I have the impression that Oomph caches dependencies
>> for such component.def since if I modify such files, and try to rerun
>> the targlet task, even on a brand new workspace, oomph keeps on using
>> the old dependencies... is that correct?
> It must be correct if your problem description is correct :P
no doubt ;)
I'm sure I had also deleted the workspace and the eclipse installation,
but I hadn't thought about profiles for that workspace (and I hadn't
tried to give the workspace another name)... the targlet was
effectively triggered.
I managed to have it working by changing the root dependency in the
targlet, and then changing it back again. I did that before reading
your answer and now I can't seem to reproduce it. If that happens
again, I'll try to use your suggestions and let you know.
Thanks!
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
Goto Forum:
Current Time: Sat Dec 07 03:29:23 GMT 2024
Powered by FUDForum. Page generated in 0.02433 seconds |
] 
Search
Help
Register
Login
Home
