|
> From: Mark Phippard > > If you are using a Studio 5.x IDE and WAS Express or WAS 5.x as your test > environment, then there is also a setting in the Project properties of > your web application where you can specify another Java project in your > workspace as a "Library project". > (...) > have to constantly export it to test. However, when you do a live > deployment, you still need to package it as a JAR under the /WEB-INF/lib > folder. This was what I was starting to believe, although I was sure it was just me. That's too bad. There should be an option to deploy as a JAR - you should be able to define a JAR file as "internal" to the project and then simply be able to add packages and/or classes to it. It should not require an extra project to deploty a JAR file. If a large part of my code is stable, it makes sense to JAR it up; every text on JIT compilers says that the more things are JAR'd the better the optimization decisions the compiler can make. This JAR file can still be local to my project. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.