• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

skinny ear files similar to skinny war files

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been wondering, with all the continuous integration which is quite popular nowadays, it is a waste of space to build 40-50 MB ear files where most of it are external dependencies. Is it such a bad idea to have a separate configuration for your project in jboss (other than minimal, default and all) and maintain the external dependencies in the lib folder of this custom configuration folder instead of inside the war/ear file. What are the cons in such an approach. With maven we can make sure that the correct versions of the jars are always synced with the jboss lib folder on each build. Any thoughts?
 
author
Posts: 3285
13
Mac OS X Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I moved this to Jboss as Jboss's classloading can make this 'interesting' dependent on what version of Jboss you are using....
 
JavaMonitor Support
Posts: 251
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It makes your EARs and WARs depend on server configuration. For you that may be fine, but I sometimes port stuff between app servers.

Also, it enforces the precise same version of every dependency, barring webapps to run a new version of something for a while before the rest is ported over.

Both arguments say the same thing: you increase the number of things that have to be precisely right for your app to work.
 
reply
    Bookmark Topic Watch Topic
  • New Topic