On 07/02/2013 10:03 AM, Matthew Adams wrote:
On Tue, Feb 5, 2013 at 9:57 AM, Ron Wheeler
<[email protected]
<mailto:[email protected]>> wrote:
[snip]
We do make a single jar for each group in the group POM and put
that in the Tomcat lib at run time.
This just keeps the clutter down.
It makes sure that we get the same versions of everything with
which we did the builds of the wars, without having to deal with
70+ jar files.
[snip]
Unsure how well this fits in with OSGi.
Me neither, but I would like to hear anyone's opinion.
Well, I can tell you that wouldn't work well in OSGi. OSGi places a
formal boundary around bundles, which are jars, only with OSGi
metadata in their META-INF/MANIFEST.MF. It'd be pretty crazy to try
to export everything properly from uberjars like these.
At an abstract level, these would be "provided" in the same way that the
JVM or Tomcat functionality is provided.
Thanks for the comment. I will read your references and if you find the
other link, that would be most appreciated.
It is an area that I have not had a chance to explore so I appreciate
your effort to get me started.
Ron
I think a better solution would be to use OSGi plans or libraries,
which is kind of targeting the ease-of-use problem. See
http://www.eclipse.org/virgo/documentation/virgo-documentation-3.6.0.RELEASE/docs/virgo-user-guide/htmlsingle/virgo-user-guide.html#concepts.grouping,
although I think it's documented better elsewhere (and I can't find it
right now).
-matthew
--
mailto:[email protected]
skype:matthewadams12
googletalk:[email protected]
<mailto:googletalk%[email protected]>
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
