how do we deal with dependencies while developing plugins?

[andy-berry-dev]

discussion started with @leggetter and @dchambers

---

when developing a plugin in Eclipse you need to add brjs-core.jar and all of its dependencies to the classpath for src and tests. to do this you select all the jars in the libs dir and add them.

if we add a new dependency, or change a dependency that list changes so the classpath has to be updated - this might happen every time we release. can we fix this?

possible solutions:

• ignore the problem, how often do we think this will realisticly be a problem?
• use a fat jar
• find a way to add a directory rather than individual jars to the classpath

[mikes-c]

Adding a directory instead of individual jars to the classpath:

java -cp ".:../lib/*"

[andy-berry-dev]

'java -cp ".:../lib/*"": via command line yes, but in Eclipse is very different. You cant seem to add a directory, only individual files in a directory.

[leggetter]

I only had to add brjs-core.jar and jsap-2.1.jar in order to create a CommandPlugin using the ArgsParsingCommandPlugin abstract helper class.

Really wasn't a lot of effort to do that.