RE: developing doclets with maven (revised)
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.orgmsgNo=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]
Re: developing doclets with maven (revised)
Maven defines tools.jar as a system property.
On Mon, 9 Aug 2004 07:54:39 +0100, Charles Daniels [EMAIL PROTECTED] wrote:
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.orgmsgNo=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]
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: developing doclets with maven (revised)
Hi Charles Dion,
Thanks for your recommendations!
Here's what I did:
In my project's build.properties:
maven.doccheck.tools.jar = ${tools.jar}
maven.jar.override = on
maven.jar.javadoc = ${maven.doccheck.tools.jar}
By default, it uses the tools.jar maven uses. In case you are running
it on Java 1.5, you can put the following in your
$HOME/build.properties:
maven.doccheck.tools.jar = /j2sdk1.4.2_04/lib/tools.jar
In Java 1.3 and before, it doesn't seem to compile anyways. Something
about the class version not being right.
Best regards,
-- Shinobu Kawai
On Mon, 9 Aug 2004 17:12:07 +1000
Dion Gillard [EMAIL PROTECTED] wrote:
Maven defines tools.jar as a system property.
On Mon, 9 Aug 2004 07:54:39 +0100, Charles Daniels [EMAIL PROTECTED] wrote:
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.orgmsgNo=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?
--
Shinobu Kawai [EMAIL PROTECTED], [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
