Apologies in advance for any newbie mistakes, bad assumptions, etc. We'd love to utilize a JAR repository in our environment (either via Maven or Ruper), but all of the proposals I've seen so far center around putting the version number in the JAR file name. Is this the only way of accomplishing this?
I see quite a few problems with changing the JAR file name with each new version, particularly within a J2EE environment. For example, changing the file name for an EJB client JAR would require updating all of the Manifest files of other EJBs that depended on that client JAR. Changing the name of an EJB JAR in the repository would also mean re-setting/adding/configuring the EJB in WebLogic (not sure if other J2EE containers are dependent on file names). Making these changes would not scale well, and quickly grow cumbersome in a large IT shop with many different components (EJBs, WARs, etc), each with their own internal version number, being promoted to various testing environments each day. Ideally, from my standpoint, different versions of a JAR would be separated into different directories - versioning information would also be embedded (and accessible) in the JAR's manifest file. Is this possible with Maven? Has anyone else raised this issue, looking at it, or already resolved it? Thanks, Kyle _____ Kyle Adams | Java Developer | Gordon Food Service | 616-717-6162 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
