On Thu, 19 Jun 2008, Markus Umefjord wrote:
What I mean was: try to remove legacyMode - and leave jdkComplianceLevel
to 5.0.
If you get an error message about "jdkComplianceLevel is an unknown
attribute" - then you have to upgrade.
For upgrades:
Try turning off antivirus (at least Norman antivirus is brainf***ed and
may very well corrupt WAS on upgrades).
Are you running from within RAD? RADs integrated testenv lags updates from
the "normal" standalone WAS package.
I'm running 6.1.0.15 (base-install/externally from RAD) - you could try
that version as well.
Right, but removing the <jdkCompianceLevel>-tag does not change anything (it
should default to 5.0, but apparently not).
I'm trying this on a WAS 6.1.0.2, so if I could get the latest fixpack
installed things might change. Unfortunately the IBM Update Installer
software (6.1.0.17) is broken on Windows, so I'm kind of stuck here... Any
ideas on that?
Sure
This parameter (complianceLevel) was introduced by IBM in FP7 - see the
faq #1: http://mojo.codehaus.org/was6-maven-plugin/faq.html
and also
http://mojo.codehaus.org/was6-maven-plugin/ejbdeploy-mojo.html#jdkCompliance
Level
So either remove the legacyMode flag - or if running on a WAS version
which handles it - set the compliance level.
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
