I can't find anything searching nabble about whether it was considered a bad thing to write the cache files into ~/.m2/repository.
The problem I am finding is that you want to run "mvn eclipse:eclipse" when you have a new baseline and all your version numbers have changed. And often in this scenario you want to run "mvn clean" first, which deletes the download source/javadoc cache. Couldn't the cache files be placed into ~/.m2/repository like a lock file? e.g. say junit:junit:3.8.1 didn't have sources jars Then eclipse plugin could create a zero byte file called ~\.m2\repository\junit\junit\3.8.1\junit-3.8.1-sources.jar-not-available or something. And add a flag to force re-checking of source/javadoc availability. This way the not-available status is also shared across multiple projects. Thoughts? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
