Hi Thorsten
Thorsten Möller wrote:
> Am 23.09.2011 um 16:18 schrieb Paolo Castagna:
>
>>> - <classpathentry kind="var"
>>> path="M2_REPO/com/hp/hpl/jena/iri/0.8/iri-0.8.jar"
>>> sourcepath="M2_REPO/com/hp/hpl/jena/iri/0.8/iri-0.8-sources.jar">
>>> - <attributes>
>>> - <attribute
>>> value="jar:file:/home/castagna/.m2/repository/com/hp/hpl/jena/iri/0.8/iri-0.8-javadoc.jar!/"
>>> name="javadoc_location"/>
>>> - </attributes>
>>> - </classpathentry>
>> If someone knows how to avoid that (i.e. absolute paths in the .classpath
>> file) I'd love to find out.
>
> Well, there is almost no need to attach the javadoc jar if the source jar is
> attached these days. Since you use Eclipse, Eclipse provides on-the-fly
> rendering JavaDoc like views from the sources. Try Eclipse' Javadoc view;
> similar for tooltips.
Yes. I agree.
> You might also want to turn off this for the Eclipse Maven plugin [1].
Yep.
We have this in the LARQ's pom.xml [1] file, for example:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.8</version>
<configuration>
<buildOutputDirectory>${project.build.directory}/classes-eclipse</buildOutputDirectory>
<downloadSources>true</downloadSources>
<downloadJavadocs>false</downloadJavadocs>
<useProjectReferences>false</useProjectReferences>
</configuration>
</plugin>
However, if the javadoc jar is in your local Maven cache, it will appear in your
.classpath every time you type mvn eclipse:eclipse.
Do you know how I can avoid that?
Paolo
[1] https://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/pom.xml
>
> Thorsten
>
> [1]
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#downloadJavadocs
