atom feed23 messages in org.apache.ant.userrmic, javac, and packaging for deploy...
FromSent OnAttachments
schmittOct 17, 2000 7:13 am 
Stefan BodewigOct 17, 2000 7:30 am 
Dino ValenteOct 17, 2000 8:19 am 
Stefan BodewigOct 17, 2000 8:34 am 
Craig R. McClanahanOct 17, 2000 8:44 am 
George McKInneyOct 17, 2000 8:44 am 
Mahlen MorrisOct 17, 2000 8:51 am 
Stefan BodewigOct 17, 2000 8:52 am 
Dino ValenteOct 17, 2000 9:06 am 
Stefan BodewigOct 17, 2000 9:21 am 
Craig R. McClanahanOct 17, 2000 9:55 am 
Dan SmithOct 17, 2000 10:11 am 
Chris ToddOct 17, 2000 5:24 pm 
Chris ToddOct 17, 2000 6:11 pm 
Diane HoltOct 17, 2000 10:48 pm 
Stefan BodewigOct 17, 2000 11:50 pm 
Stefan BodewigOct 18, 2000 12:53 am 
Stefan BodewigOct 18, 2000 1:10 am 
Stefan BodewigOct 18, 2000 1:34 am 
Douglas GuptillOct 18, 2000 1:48 pm 
Stefan BodewigOct 19, 2000 4:30 am 
Dino ValenteOct 20, 2000 7:55 am 
Stefan BodewigOct 20, 2000 7:58 am 
Subject:rmic, javac, and packaging for deployment question
From:Chris Todd (chr@christophertodd.com)
Date:Oct 17, 2000 6:11:18 pm
List:org.apache.ant.user

I hope you will forgive me if this is a stupid question; I am still learning java, RMI, and Ant. I am pondering how to handle the following situation: I have a CVS tree with several sub-directories, each of which contain some files that need to be rmic'd and some that only need to be javac'd. After compilation, I want to jar the resulting classes for deployment to two different targets (client and server). I guess the thing i would most appreciate suggestions on is how to separate the files that need to be rmic'd from the files that only need to be javac'd. From there, running javac, rmic, and jar seems pretty straight forward.

BTW, if "reorganize your CVS tree so all of your rmi classes are in the same directory" is the best answer, that is perfectly acceptable; I had thought of that (it is a pretty obvious solution), but I was just wondering if Ant had some filter, property, or task magic it could perform. :-)