Bugs item #609132, was opened at 2002-09-13 15:58
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=609132&group_id=22866
Category: Build System
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Ulrich Romahn (diggermaus)
Assigned to: Jason Dillon (user57)
Summary: Can't compile with Sun JDK 1.4.1rc-b19
Initial Comment:
I checked out the tagged version 'JBoss_3_2_0_1' on
Linux and are trying to compile it with Sun's latest JDK.
After some time, I am getting the following error
messages which leads to an abort of ant:
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:621:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
if (moduleStack[i].module != null) {
^
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:622:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
methods =
moduleStack[i].module.getClass().getMethods();
^
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:636:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
moduleStack[i].module =
constructor.newInstance(args);
^
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:638:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
methods =
moduleStack[i].module.getClass().getMethods();
^
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:651:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
methods[mIndex].invoke(moduleStack[i].module, initArgs);
^
/home/uroma/java_dev/src/jboss-all/security/src/main/javax/security/auth/login/LoginContext.java:665:
cannot resolve symbol
symbol : variable module
location: class
javax.security.auth.login.AppConfigurationEntry
(moduleStack[i].module,
args)).booleanValue();
All error messages suggest that the method 'module' in
class AppConfigurationEntry does not exist.
It compiles and runs fine with Sun's JDK1.3.1.
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2002-10-04 09:40
Message:
Logged In: YES
user_id=175228
LoginContext is not going to change. The change was to
disable compilation of these classes under 1.4 vms as the
change is not needed with these. Look at the
security/build.xml file for the changes.
----------------------------------------------------------------------
Comment By: Matthew Munz (mattmunz)
Date: 2002-10-04 07:41
Message:
Logged In: YES
user_id=340814
Scott,
I am still having this problem. I took a look at the cvs
history for LoginContext, and it hasn't changed. What did
you do to fix this? I'm happy to check in my patch (very
simple), I just don't know what the rules are for modifying files
under the org.javax.* domain.
- Matt
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2002-09-24 12:52
Message:
Logged In: YES
user_id=175228
This has already been fixed in all Branch_3_0, Branch_3_2
and head.
----------------------------------------------------------------------
Comment By: Matthew Munz (mattmunz)
Date: 2002-09-24 12:31
Message:
Logged In: YES
user_id=340814
I have written and am currently using a patch for this defect.
This class (LoginContext) starts with a comment that says
that it is Sun-licensed. As such, I am not sure if JBoss
should be applying the patch, or if Sun should.
Could a knowledgeable JBoss developer please comment on
this situation? Should I commit my patch, or should I submit
it to Sun, or both, or what?
- Matt
----------------------------------------------------------------------
Comment By: Oskari Kettunen (aok)
Date: 2002-09-14 08:01
Message:
Logged In: YES
user_id=558871
Hello,
I've had the same problem, I faintly recollect someone
suggesting on the devel-list that the javax.security stuff
shouldn't be compiled on j2sdk1.4.1
So, my workaround (in building cvs HEAD) has been:
rm -rf security/src/main/javax
as far as I can tell, it works just fine.
The bug's been around for a while now, apparently a fix isn't
very high on the list or the solution is more complicated than
it seems.
Oskari Kettunen
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=609132&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
