|Compile behaviour of OSGI DS annotation support [message #1803416]
||Thu, 28 February 2019 10:05
| Stefan Häusler
Registered: May 2013
since several years we are using OSGI Declarative services support for annotations inside Eclipse. First as a plugin installed to the IDE later when it was shipped by Eclipse Releases.
Since a while (dont know exactly since when, but we think it was not happening prio to Eclipse Neon), we are observing a changed behaviour in certain situations which hinders us a bit in our daily work.
Lets assume some @Reference set method input parameter class can not be found, then the DS plugin still seems to keep the XML file in sync with the code -> means it produces an invalid XML file (only shown with a warning).
Here it can be that the developer is even not responsible, its just happens when retrieving some changed artifacts from Target Platform or we switched to annother branch and the building process inside Eclipse shows issues temporarily.
Later when the build is finished it looks like that the DS XML file is not always made valid again.
In this case, the developer has to review exactly what he wants to commit and whether there is really some file which should not have been changed. This is already error prone when changes come all from his own. Sometimes, when the developer did a merge from trunk to branch, he may can not even distinguish where this change came from and will just commit.
So two questions:
- We think, the build behaviour of the DS annotation support changed since one of the latest eclipse versions. Are you aware of any changes and can elaborate whether this is true?
- How can it happen that sometimes the building process does not keep the XML file in sync (i can not make a real example here as it does seem to happen only in much more complex change scenarios, e.g. a switch between branches or target platform update).
Thanks in advance for your help,
Powered by FUDForum
. Page generated in 0.11954 seconds