Seems like we need to keep what is there and just add what we have specified unless it is there in another way. Don't know if that is possible.
sandeep -----Original Message----- From: Charles N. Harvey III [mailto:[EMAIL PROTECTED] Sent: Thursday, April 29, 2004 12:08 PM To: Maven Users List Subject: Re: Eclipse Plugin Ideas Comments below. Kristopher Brown wrote: >Hi, > >I feel the eclipse plugin doesn't do what we need it to do. A few of >the issues are: > >1) .project file has entries for the eclipse checkstyle plugin, and >these get wiped out on regeneration. >2) .classpath file is able to generate workspace local dependencies, >however this is indicated in the pom rather than a manner that is >independent to the developers environment. This causes problems when >working with only a few projects as it generates local dependencies >which are not available [unless you go and remove them for the pom]. >3) additional classpath entries (added via the >maven.eclipse.classpath.include) in the .classpath file are only added >if there is a test source tree present. > >So, I've tried to come up with some solutions, and I'd like to hear >people's thoughts on them. > >1) Add something to the project.properties to specify the additional >buildCommands and natures that are used by the project. Seems fairly >simple for eclipse checkstyle plugin. Are there other >modifications/structure in .project to consider? > > "Natures" are added to the .project file. By default "Java Nature" is added to all projects. And the maven-eclipse-plugin adds that. But if I change my project to an AspectJ project it adds the "AspectJ Nature" to the .project file. This gets wiped out as well. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
