On Tue, Mar 27, 2012 at 9:48 AM, Andy Seaborne <[email protected]> wrote: > On 27/03/12 17:40, Andy Seaborne wrote: >> >> On 27/03/12 16:45, [email protected] wrote: >>> >>> Author: rvesse >>> Date: Tue Mar 27 15:45:38 2012 >>> New Revision: 1305876 >>> >>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev >>> Log: >>> Minor typo fix to error message in QueryEngineHttp >>> >>> Modified: >>> incubator/jena/Jena2/ARQ/trunk/.classpath >>> incubator/jena/Jena2/ARQ/trunk/.project >>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs >>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs >>> >>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java >>> >> >> Rob, this sets ARQ to be a m2e project. I guess that was unintended? >> >> May I revert it to a plain Eclispe project for now? >> >> Come the code reorg, when the projects can get their names aligned, we >> can try using m2e if the project cross-linking works for everyone (e.g. >> you need all the project open, I don't see how a quick bug version of >> one module works) >>
m2e works pretty well for me with cross-linking the various Jena projects. The key is to make sure you've specified the correct dependency versions to make Eclipse pick up the linking. It will also fall back to the jar in your repository if you close one of the dependency projects, or use a different version than the project you have open. > > > I also get m2e errors - the antrun plugin is "not covered by lifecycle > configuration" > You can fix that by using the QuickFix suggestion and ignoring that goal. That just means if you want that goal to run, you have to use the command line maven [1]. Below is a diff to apply that fix to ARQ. I've been debating checking this in for all the projects, as it will only affect those running m2e. -Stephen [1] m2e requires a "Lifecycle Mapping" be created for each Maven plugin that you want to use. This enforces that the plugin is working with Eclipse resources instead of directly with file handles. This is necessary for the plugin to play well with incremental compilation among other things. "Ignore" works well when it's not something that needs to be run a lot, and you can therefore do it manually if it is needed. The other option is "Execute", but that apparently is tricky. A bunch of info at [2]. [2] http://wiki.eclipse.org/M2E_plugin_execution_not_covered Index: pom.xml =================================================================== --- pom.xml (revision 1305481) +++ pom.xml (working copy) @@ -258,6 +258,39 @@ --> </plugins> + <pluginManagement> + <plugins> + <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.--> + <plugin> + <groupId>org.eclipse.m2e</groupId> + <artifactId>lifecycle-mapping</artifactId> + <version>1.0.0</version> + <configuration> + <lifecycleMappingMetadata> + <pluginExecutions> + <pluginExecution> + <pluginExecutionFilter> + <groupId> + org.apache.maven.plugins + </groupId> + <artifactId> + maven-antrun-plugin + </artifactId> + <versionRange>[1.6,)</versionRange> + <goals> + <goal>run</goal> + </goals> + </pluginExecutionFilter> + <action> + <ignore></ignore> + </action> + </pluginExecution> + </pluginExecutions> + </lifecycleMappingMetadata> + </configuration> + </plugin> + </plugins> + </pluginManagement> </build> <reporting>
