2008/4/28 David Leangen <[EMAIL PROTECTED]>: > > Hi, Stuart. > > > However, I am still getting lots of compiler warnings, and any > > changes I > > make to my .classpath file are being overwritten. > > > > ideally you shouldn't need to change the classpath, > > can you list the changes you're making that aren't in > > the generated .classpath file? > > Well, for one I'm trying to exclude certain files from the classpath. In > other words, I'm trying to influence the line: > > <classpathentry excluding="**/*.java" kind="src" > path="src/main/resources"/> > > in the .classpath file. I add <excludes> entry to the config in my pom, > but it does not influence the .classpath file at all. >
looks like this option appeared in the recently released 2.5 maven-eclipse-plugin (see MECLIPSE-79) whereas the pax-plugin currently extends 2.4, so an update would be needed to support this. The other thing is that I'm trying to use a more precise version of the > JRE container (as suggested by the warning in Eclipse). > > So this: > <classpathentry kind="con" > path="org.eclipse.jdt.launching.JRE_CONTAINER"/> > > Should be this: > > <classpathentry kind="con" > path="org.eclipse.jdt.launching.JRE_CONTAINER/ > org.eclipse.jdt.internal.debug.ui.launcher.St > andardVMType/J2SE-1.5"/> > > This entry is getting added, but so is the one above. I guess the one > above always gets added, so the Eclipse warning never goes away. > > I'm also guess that this isn't a very important problem, but it still > seems inconsistent to me... > this one should be straightforward to fix - unless it's also fixed in 2.5 in which case upgrading the dependency will also fix this problem. > also the whole idea of generating .project / .classpath > > files, is that they should be working out-of-the-box and > > not require further changes - otherwise you'd need to > > commit them to svn for other developers, which kind-of > > defeats the point of generating them... > > Yes, understood. > > Until now, I always just hand crafted, then committed these files. I had > no problems working this way, but the model is now changed. > > Just like you say, if these are re-generated each time, then they need > to work out of the box. Any additional config must be provided in the > pom file so it is generated and added at build time. > > > Are the issues I mention above related to the pax plugin, the felix > plugin, or the maven plugin? In other words, can you tell me where I > need to file a JIRA issue? > the pax-plugin (which extends the maven-eclipse-plugin) because it's responsible for creating the .project / .classpath files - you could try raising issues for the maven-eclipse-plugin but they tend to ask for patches and testcases before fixing issues, and there can be a long wait between releases (which is why we currently extend the plugin) OPS4J JIRA, project: PAXCONSTRUCT, component: maven-pax-plugin > Thanks! > David > > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Stuart
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
