Hi James,
I noticed that you had to patch in the source/target versions for the
compiler plugin - I'll work that into the next update on the Jenkins
plugin parent pom so its not required in future.
Thanks. My current target is to package git plugin. I have some of its other
dependencies
in my pipeline, so I'll wait for your next update.
Still what bothers me a bit is the fact that created *.hpi files have libraries
they depend on
bundled inside /WEB-INF/lib/ directories, so
a) the plugin archives are unnecessary huge
b) we are duplicating libraries in the system
c) whenever a library is updated, we have to rebuild and reupload the
affected Jenkins plugin to
let it use this new version (probably the biggest drawback I see)
Have you already investigated a possibility if the plugins can reference jars
installed
for example in /usr/share/java?
For now, as a first step, it's fine to have the libs bundled, but maybe in a
longer term
something should be done with it.
Cheers
Jakub
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f397a1c.4080...@ktknet.cz
