Bug 33862 - rmic always builds with jdk1.5
Summary: rmic always builds with jdk1.5
Status: RESOLVED FIXED
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: nightly
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on: 40342
Blocks:
  Show dependency tree
 
Reported: 2005-03-05 16:58 UTC by Roland Bergler
Modified: 2008-02-22 12:18 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Bergler 2005-03-05 16:58:32 UTC 
I'm using the default settings for the rmic task with jdk1.5.
<rmic> always compiles, because the tasks expects the sun rmic to generate
skeleton classes, which it doesnt't do since 1.5. 

     [rmic] Verify has been turned on.
     [rmic] kam\janet\connector\RemoteDataProcessorImpl.class added as
kam/janet/connector/RemoteDataProcessorImpl_Skel.class doesn't exist.
...
     [rmic] RMI Compiling 5 classes to ...
     [rmic] Using SUN rmic compiler
     [rmic] Compilation arguments:
     [rmic] '-d'
     [rmic] '...'
     [rmic] '-classpath'
     [rmic] '...'
Comment 1 Steve Loughran 2005-03-07 14:04:58 UTC 
I am looking at this. I think the default behaviour of rmic has changed, 

It used to be -vcompat, now it is -v1.2; hence the effect.

if you set stubversion="compat" you get the old behaviour. I am going to change
Ant1.7 to make this the default.
Comment 2 Steve Loughran 2005-03-07 16:19:51 UTC 
Fixed in CVS_HEAD; modified default behaviour to be -vcompat. 

Now, if other rmic impls dont recognise -vcompat we have a problem; need more
testing here...

Also, should we pass the stubversion down to the options as is if not
recognised. Currently anything other than 1.1 or 1.2 is viewed as '-vcompat', it
would be more flexiblt to say 1.1, 1.2, compat or *whatever*, so if rmi 1.3
comes along, the task is ready.