Custom setup task dependencies problem [message #1801668] |
Thu, 24 January 2019 13:20 |
Tim Sibirsky Messages: 9 Registered: October 2018 |
Junior Member |
|
|
Hello!
In our project, we have a custom Oomph Setup Task that performs some project-specific actions during the product installation. The problem is that both setup task and product use Google Guice plugins as dependencies, but with different versions (4.1.0 in task and 3.0.0 in product), and it totally breaks product.
So, are there any ways to not to install plugins that use setup task into the product? Our task has only BOOTSTRAP trigger, so it won't be used after product installations. Or maybe there are other ways to solve our problem without making any changes in product?
Thank you!
[Updated on: Thu, 24 January 2019 13:21] Report message to a moderator
|
|
|
|
Re: Custom setup task dependencies problem [message #1801887 is a reply to message #1801677] |
Tue, 29 January 2019 08:32 |
Tim Sibirsky Messages: 9 Registered: October 2018 |
Junior Member |
|
|
Sorry for keep waiting...
Yes, you have understood right. There are tasks that need to be installed in the installer to perform some specific logic, but they not needed in the installed product.
It seems that maybe installer really should not gather requirements from bootstrap-only tasks, but this question is opened for discussion, at least because I don't know if this approach will break something. Maybe it is a good idea to make installation of bootstrap-only tasks' dependencies as an optional action.
We have some ideas on how to overcome our problem, I will write if we find solution. But those ideas looks more like a bypass, not like real solution.
UPD: At Confirmation page, in P2 task I see all features from product setup file + features from out task.
[Updated on: Tue, 29 January 2019 09:01] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04191 seconds