This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

MANIFEST

 
Amruth Puppala
Ranch Hand
Posts: 295
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In general appContext/META-INF/MANIFEST.MF automatically created when we generate WAR file. So do we some times modify MANIFEST.MF? if yes why?
 
Martijn Verburg
author
Bartender
Posts: 3275
5
Eclipse IDE Java Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's usually for Meta Information such as the Vendor, the version number of your web app etc, see http://en.wikipedia.org/wiki/Manifest_file
 
Amruth Puppala
Ranch Hand
Posts: 295
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks
 
Rodrigo Vieira
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Manifest should be always edited, this file is used to create a classpath of your application, so you can write the reference of all yous libs there. It�s much better then put in the WEB-INF/lib because if you have more then one application using the same lib you are spending your hard disk. Also, creating a reference when you change the version of this lib, all of your applications will change as well without create new WAR.
[ August 04, 2008: Message edited by: Rodrigo Villelaaa ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic