I try to implement the following scenario.
My Eclipse project requires a set of JDBC drivers at runtime, which are not supposed to be present in compile classpath. Those drivers are stored in binary repository and must be accessed by artifact coordinates, so, other approaches like local file system are not an option.
Today our Eclipse projects are based on Ivy/IvyDE and the scenario above is quite easy to implement. There is dedicated project in our Eclipse workspace which is just kinda wrapper for the JDBC drivers of interest: those are included into IvyDE classpath container as project’s dependencies. Classpath container is exported and thus it’s just enough to add this project into debug/run configuration classpath. Two items are added then, project itself and its exported classpath container.
My problem is that I’m unable to implement the similar approach with Buildship. Although all necessary artifacts are declared as project’s runtime dependencies and “exported” with “whenMerged” hook, they do not become a part of debug configuration classpath when the project is included there. Container just do not appear in the entries list.
Is such an approach is possible with Buildship? Or is there a better way to implement this scenario?