Thorsten Möller wrote:
> Am 23.09.2011 um 17:10 schrieb Paolo Castagna:
>
>> 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?
>
> The radical way of solving it...
>
> cd ~/.m2
> rm -rf *-javadoc.jar
>
> mvn eclipse:clean
> mvn eclipse:eclipse
>
>
> ... uff ;-)
Well, yeah... thanks! :-)
The problem is that you just need another project without the
<downloadJavadocs>false</downloadJavadocs> setting to re-populate
your Maven cache with *-javadoc.jar and you are again with absolute
paths in your .classpath files.
In any case, thanks for sharing your "radical" solution (which
is what I've been doing... until the above appens).
Anyway, not a big deal (everything still works, even with a non
existing path for a javadoc_location in the .classpath file).
And we have much more important things to improve/fix towards
making the first Apache Jena release.
Thanks.
Paolo
>
>
> Thorsten
>
>
>
>
>> 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
>
