My suggestion would be your second solution. Then each developer need only define the property tools.jar in his/her build.properties file. Although, you may want to consider using a version number in the property name (e.g., tools14.jar) just in case a developer also wants to point to version 1.3 for some other project. This way they can have two distinct properties that they can put in ~/build.properties.
> -----Original Message----- > From: Shinobu Kawai [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 6:45 AM > To: Maven Users List > Subject: developing doclets with maven (revised) > > > > Hi! > > I'm looking for a good way to develop doclets using maven. During > compilation, I need the Javadoc API, but I'm probably going to give up > putting the Javadoc 1.4 API in ibiblio. > cf. > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] he.org&msgNo=22207 Now I'm looking for alternatives. Right now, I can think of two solutions: 1. Make the jar myself (or use tools.jar) and put it in the local repository or a private remote repository. Of course, I need tell other developers that their repositories have to be manually added. 2. Use the maven.jar.override property and point the dependency to such a jar file. I can expect this to work anywhere as long as maven is running under the right version of java. maven.jar.override = on maven.jar.javadoc = ${tools.jar} Any suggestions? or other alternatives? Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED], [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]
