I am having trouble with adding tools.jar to my classpath. I'm compiling against both the javadoc and apt APIs.
Tinkering with the bootclasspath or manually putting tools.jar into my local repository are both icky - they work for me but not for anybody else building the project. Since every jdk has tools.jar, could we not just have it recognised as a dependency something like this and have m2 glue it in from the jdk lib directory? <dependency> <groupId>sun.jdk</groupId> <artifactId>tools</artifactId> <type>jar</type> <scope>provided</scope> </dependency> On Sunday 31 July 2005 16:51, Kenney Westerhof wrote: > On Sun, 31 Jul 2005, Roman Bruggisser wrote: > > Hi, > > There aren't any. However it should be on the classpath if you use the > jdk. > > A better solution is to add it to the classpath at runtime. > See > http://svn.plexus.codehaus.org/trunk/plexus-components/plexus-compiler/plex >us-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compile >r/javac/JavacCompiler.java?rev=2369&view=markup for an example. > > -- Kenney > > > Hi > > > > > > > > I'm new to maven and I'm wondering if there is a way to add tools.jar to > > the classpath without placing it in the repository. > > > > Thanks for any ideas. > > > > > > > > Roman > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > --------------------------------------------------------------------- > 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]
