|
ArtifactResolution
Resolving maven artifacts from the workspace
IntroductionResolving artifacts from the workspace allow you to work on two levels:
Compiling with eclipseIf project_a has a dependency on project_b and both are on your workspace under q4e control, project_a buildpath will be updated to use project_b. This feature is a must for any developer, so there is no need to mvn install after every change on project_a just to work with project_b in Eclipse. Compiling with mavenSometimes you just need to use maven. But (starting with q4e 0.5.0) you can still use the projects on your workspace. You can't still avoid calling mvn install. In few words... if you need to execute a goal on any project, use Maven 2 > Execute goal on the project's context menu and you'll save the step of installing to the repository.
Watch this screencast to see it in action The long storyNot every maven mojo supports running from the workspace. Most notably, plug-ins that fork execution and/or require the presence of jar files will fail. Starting in 0.7.0, Q for Eclipse will automatically package the workspace artifacts when the plug-ins involved in the current build require it. Note that nothing is installed in the repository at this point. We would be glad to work with maven plug-in authors to help them support working from the workspace with Q for Eclipse. |
