-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#175 fixed #242
#175 fixed #242
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least one test case must be added that uses this functionality, to the files in com.btc.serviceidl.test/.../good, and this must also be included in the serviceidl-integrationtests.
YT: Right, we need some tests. That should be done within the ticket PRINS-4407 in the one of the next sprints. @huttenlocher extended the ticket.
I am not quite sure how the ODB project generation can be controlled, i.e. how I would run a generation on something that has an ID field, but not ODB project should be generated. Maybe the pre-defined project sets need to be updated?
YT: @GerrietReents suggested to use -projectSet parameter (with odb value) to specify the necessity of using ODB. However it requires to support of multivalued parameter, something like api|server|odb. New ticket should be open for this purpose.
...erviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeTopLevelProjectFileGenerator.xtend
Outdated
Show resolved
Hide resolved
...erviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeTopLevelProjectFileGenerator.xtend
Outdated
Show resolved
Hide resolved
...erviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeTopLevelProjectFileGenerator.xtend
Outdated
Show resolved
Hide resolved
...erviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeTopLevelProjectFileGenerator.xtend
Outdated
Show resolved
Hide resolved
com.btc.serviceidl/src/com/btc/serviceidl/generator/cpp/prins/OdbProjectGenerator.xtend
Outdated
Show resolved
Hide resolved
com.btc.serviceidl/src/com/btc/serviceidl/generator/cpp/TypeResolver.xtend
Outdated
Show resolved
Hide resolved
com.btc.serviceidl/src/com/btc/serviceidl/generator/DefaultGenerationSettingsProvider.xtend
Outdated
Show resolved
Hide resolved
...btc.serviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeModuleStructureStrategy.xtend
Outdated
Show resolved
Hide resolved
...btc.serviceidl/src/com/btc/serviceidl/generator/cpp/cmake/CMakeModuleStructureStrategy.xtend
Outdated
Show resolved
Hide resolved
The PR cannot be merged before all of these points have been solved. |
Maybe the failing integration tests are due to inconsistent conan packages, since there have been several build failures on the CAB jenkins over the last days due to http://jira.e-konzern.de/browse/BOPINFRA-582 |
Probably yes, just now I checked out the master branch and tried to run the integration tests, same tests are failing also with "master". There is probably something wrong in the "lastest" package dependencies. I get linker errors in almost all projects for elementary classes like BTC::ServiceComm::API::InvalidReplyReceivedyException etc. which are correctly referenced in CMake files and not touched by last commits. |
Yes, we keep one eye on this, however we will not be able provide an integration test in this sprint. Instead, we will provide new integration tests along with new tests for #186; this is planned as Jira issue PRINS-4407. We need also to check whether all conditions are fulfilled, at least to clarify: does @yury-trofimov has permissions to commit to Bitbucket repository bitbucket.e-konzern.de/scm/btccabcom/serviceidl-integrationtests.git |
com.btc.serviceidl/src/com/btc/serviceidl/generator/cpp/prins/OdbProjectGenerator.xtend
Outdated
Show resolved
Hide resolved
com.btc.serviceidl/src/com/btc/serviceidl/generator/cpp/prins/OdbProjectGenerator.xtend
Outdated
Show resolved
Hide resolved
The serviceidl-integrationtests now work again in general, however some test cases are still failing.
The test case interface-query-raises-exception is also failing with a different problem:
|
Nice, we can then investigate those problems locally until everything is working. We will tackle this as soon as possible today. |
Now all integration tests are green. To address conditional ODB generation, I created the new issue #244, since this functionality goes beyond the scope of #175 (= "make ODB compatible with CMake" - this basic requirement is now implemented). To address extension of integration tests, we already created the issue PRINS-4407. So for our part, we consider this ticket as solved. |
I am sorry, but it is not possible to merge this, since it changes the behaviour for existing uses. This is an implicit constraint of the compatibility of versions. In addition, integration tests for the new functionality are still missing, as mentioned above. |
We could merge this PR, if you change the behaviour to disable ODB generation by default now, and address conditional activation (and integration tests) in a later PR. |
Done. By default, ODB-based projects will not be generated (so previous behavior is still guaranteed). I introduced a new command line option value for OPTION_PROJECT_SET to force ODB generation, if desired. |
Thanks for restoring the default behaviour. I rebased the branch and squashed some commits to conform with the contribution guidelines , and I will open a new PR for that branch on your behalf, and close this one. However, the addition of integration tests must still be done in a timely manner, also for the changes of #238. Please provide these by December 14th, otherwise I consider reverting the changes in the master again, until the integration test extensions are provided. This is essential to avoid maintain the quality of the Service IDL generators. On the one hand, I cannot judge if your additions work without such tests, but what is even more important is that no one can judge with reasonable effort if future changes break these new features. |
See #246 |
please to review