On Tue, 2003-10-14 at 14:08, Comtois, Pierre wrote:
I had same with 3.2.2 and Scott Stark of JBoss told me they shouldn't be
warnings and can be ignored.
I already changed these to DEBUG messages for 3.2.2 final
But this does mean that if you have a problem with manifests you'll
need to
I had same with 3.2.2 and Scott Stark of JBoss told me they shouldn't be
warnings and can be ignored.
Pierre Comtois
Business Acceleration Services, Solutions Consulting
45 O'Connor Street, Suite 500*Ottawa, Ontario K1P 1A4
Ph: 613-787-4649 * FAX: 613-567-6053 * E-Mail: [EMAIL
Ignore them as they are third party jars with inapproriate manifest classpath
references which are not relevant here.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Rich Reese wrote:
I get the following Warning messages when I start my JBoss
On Tue, 14 Oct 2003 09:11 am, Scott M Stark wrote:
Ignore them as they are third party jars with inapproriate manifest
classpath references which are not relevant here.
13:32:38,177 WARN [MainDeployer] The manifest entry in
It can if they are different versions or the classes use package protected access.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Brian Wallis wrote:
There does seem to be two copies of commons-logging.jar in jboss 3.2.2, one in
lib and
