Note that there are some explanatory texts on larger screens.

plurals
  1. POWrestling with Eclipse-modified .classpath in a Mixed Windows/Mac Team Environment
    primarykey
    data
    text
    <p>I'm using Eclipse on a small development environment where one developer has a Windows PC and the other has a MacBook. We share code using a subversion repository, and use Maven as an "External Tool" (not using the m2e plugin).</p> <p>We each have an M2_REPO variable that has been working great for resolving paths to .jar files on our two systems. Recently, however, I ran a command to tell Maven to pull down sources and javadocs.</p> <pre class="lang-sh prettyprint-override"><code>mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true </code></pre> <p>Since then, I see some very Windows-centric references in my .classpath that are a nuissance to my Mac-using friend.</p> <pre class="lang-xml prettyprint-override"><code>&lt;classpathentry kind="var" path="M2_REPO/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar" sourcepath="M2_REPO/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4-sources.jar"&gt; &lt;attributes&gt; &lt;attribute value="jar:file:/C:/Users/John/.m2/repository/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4-javadoc.jar!/" name="javadoc_location"/&gt; &lt;/attributes&gt; &lt;/classpathentry&gt; </code></pre> <p>Even after having removed the downloadSources and downloadJavadocs parameters, and verified that they're false in my plugin configuration for maven-eclipse-plugin, deleted my .classpath file, and reran <code>mvn eclipse:eclipse</code> I still see those unwanted references placed into my .classpath file.</p> <p>Has anyone found a good working solution to this problem? Have I overlooked some setting that tells Maven to use the M2_REPO variable in its references to javadoc files?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload