[OPENIDM-10118] Allow the openidm-launcher to use the bundles directory as its class path instead of /openidm/bin Created: 01/Feb/18 Updated: 29/Nov/18 Resolved: 29/Nov/18 |
|
| Status: | Closed |
| Project: | OpenIDM |
| Component/s: | Module - OSGi Container / Framework integration |
| Affects Version/s: | OpenIDM 6.0.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jason Lemay | Assignee: | Katie Gonzalez |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | TechnicalDebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Story Points: | 5 |
| Description |
|
When openidm-launcher bootstraps the osgi framework it uses the openidm/bin directory as its classpath instead of the bundles directory. This causes a few of the dependencies to be added to both the bundles directory and the openidm/bin directory. We should see if it is possible for the launcher to use the bundles directory instead of the openidm/bin directory. This would remove the need to ship these duplicate dependencies. |
| Comments |
| Comment by Katie Gonzalez [ 10/Apr/18 ] |
|
This needs to be revisited because it should have been resolved in 6.0 through: & |
| Comment by Brendan Miller [ 29/Nov/18 ] |
|
Closing in deference to present workaround that builds classpath in startup.sh to initiate launcher properly. |