Out of curiosity, why are you prefer m-e-p plugin over IDE support?
For example, m2eclipse [1] can import Maven projects without running intermediate commands and it does cache if source artifacts are present or not (among bunch of other things). regards, Eugene [1] http://m2eclipse.codehaus.org/ baerrach wrote: > > 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? > -- View this message in context: http://www.nabble.com/m-eclipse-p%3A-use-%7E-.m2-repository-for-cache-files--tp19566246p19574791.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
