Hmm - sounds a little like overkill to me. How much time does it add to each build compared to one where the list of classes to generate stubs for are predefined? And how well does it scale to large codebases?
> From: Christian Andersson [mailto:[EMAIL PROTECTED] > > I've made a small rmic plugin for my own usage (with some help from > within here) > what it does is that it searches all compiled classes from your project, > and locates every class that implements the java.rmi.Remote interface, > the class cannot be an interface or abstract) it then calls rmic for all > of these classes, hence there is no need for a maven.rmi.classes > variable or anything... > > well it works for me atleast :-) > > /Christian Andersson > > Tim Anderson wrote: > > In a couple of projects I work on, I add a postGoal > > to java:compile to invoke rmic - from other posts, this seems > > to be a fairly common approach. > > > > Would it be worth adding support for this to the java plugin? > E.g (OTOH): > > > > <postGoal name="java:compile"> > > <j:if test="${context.getVariable('maven.rmi.classes') != null"> > > <rmic base="${maven.build.dest}" > > includes="${maven.rmi.classes}"> > > <classpath refid="maven.dependency.classpath"/> > > </rmic> > > </j:if> > > </postGoal> > > > > > > -Tim > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
