-library-path vs -include-libraries

[Logan Allred]

We noticed the latest plugin broke our automation build. I tracked it
down to the removal of -include-libraries.

Obviously, I can work around this with extraParameters, but it brings
up an interesting question:

What is the correct maven way of handling different types of library
dependencies? Java doesn't allow you to link jars differently that I
know of, so doesn't have a concept of different link types (sort of
similar to static vs dynamic in C, maybe?)

-library-path will only include the parts of the .swc that are
actually used in your application, which is normally what is desired

-include-libraries will include the entire swc whether your code
actually uses it or not, which AFAIK is only used in a few instances,
like some automation builds (anyone else need -include-libraries?)

So, if we list the -include-libraries swc in the dependencies section
should we have a special scope ("included"? "included-swc"? "include-
library"?)?

Or should we have a separate configuration section of the plugin for
included-libraries, and if so, can they reference the dependency from
the dependencies section using coordinates, or do we only declare it
in the configuration section?

Logan

[Christian Edward Gruber]

Yeah, tricky. I'm not sure how to handle it, except to have a section
in config for "included deps" which would pull those dependencies from
the list and use included rather than library-path, but only on
those. It's a bit verbose, but you can't dynamically add scopes, as
I understand it.

I think there's an issue posted for this, but I am not sure. Feel
free to create an issue on the issue tracker for precisely this, if
it's not already there.

Christian.