Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "What's in IAM"
Line 1: | Line 1: | ||
{{backlink|IAM}} | {{backlink|IAM}} | ||
− | |||
You can see a list of some of the features below. There are also slides available presented at different conferences. | You can see a list of some of the features below. There are also slides available presented at different conferences. | ||
Line 10: | Line 9: | ||
− | + | = Core = | |
− | + | == Direct import of Maven 2 projects == | |
[[Image:Import_wizard.png]] | [[Image:Import_wizard.png]] | ||
− | + | == Maven suggestions in the XML editor == | |
When editing pom.xml files, values for the GroupId, PackageId and Version tags when adding a dependency are available. | When editing pom.xml files, values for the GroupId, PackageId and Version tags when adding a dependency are available. | ||
Line 24: | Line 23: | ||
This feature uses the Open Artifact Search Framework outlined below. | This feature uses the Open Artifact Search Framework outlined below. | ||
− | + | == Always updated dependencies == | |
No need to mvn install the dependencies on the workspace when running maven goals. The most current version is always used. | No need to mvn install the dependencies on the workspace when running maven goals. The most current version is always used. | ||
Line 32: | Line 31: | ||
This means that you can modify a project on your workspace and use it in the surefire tests of a different one depending on it. Instantly. | This means that you can modify a project on your workspace and use it in the surefire tests of a different one depending on it. Instantly. | ||
− | + | == Profile activation/deactivation == | |
The profile view allows for quickly enabling and disabling profiles when running maven. | The profile view allows for quickly enabling and disabling profiles when running maven. | ||
Line 38: | Line 37: | ||
[[Image:ProfilesView.png]] | [[Image:ProfilesView.png]] | ||
− | + | == Open Artifact Search Framework == | |
New extension points allow third parties to develop and register search engines for their indexing solution. | New extension points allow third parties to develop and register search engines for their indexing solution. | ||
Line 46: | Line 45: | ||
[[Image:SearchEngines.png]] | [[Image:SearchEngines.png]] | ||
− | + | == [http://code.google.com/p/q4e/wiki/DevelopingMojos Resolve Maven Mojos from the Workspace] == | |
It is possible to have maven mojo projects on the workspace and haven them used by q4e. | It is possible to have maven mojo projects on the workspace and haven them used by q4e. | ||
− | + | == [http://code.google.com/p/q4e/wiki/Archetype2ArchetypeProvider New Archetype Provider for the Archetype Catalog format] == | |
The archetype catalog xml format used by the archetype 2.0 plug-in can now be used with q4e for selecting an archetype in the New Maven Project wizard. | The archetype catalog xml format used by the archetype 2.0 plug-in can now be used with q4e for selecting an archetype in the New Maven Project wizard. | ||
Line 57: | Line 56: | ||
− | + | == Form based POM editors == | |
Edit POM files in a form based editor that synchronizes automatically to the pom.xml file in both directions. Also allows you to see the parent POM and the effective POM. | Edit POM files in a form based editor that synchronizes automatically to the pom.xml file in both directions. Also allows you to see the parent POM and the effective POM. | ||
Line 63: | Line 62: | ||
Settings.xml editor | Settings.xml editor | ||
− | + | = Tooling = | |
− | + | == [http://code.google.com/p/q4e/wiki/DependencyGraphViewer Dependency Viewer] = | |
[[Image:Dependency_viewer.png]] | [[Image:Dependency_viewer.png]] | ||
− | + | == [http://code.google.com/p/q4e/wiki/DependencyAnalysis Dependency Analysis] = | |
[[Image:Dependency_analysis.png]] | [[Image:Dependency_analysis.png]] | ||
− | + | = WTP support = | |
− | + | == J2EE Project Dependencies management == | |
Automatic synchronization of J2EE project dependencies from maven dependencies for war projects. | Automatic synchronization of J2EE project dependencies from maven dependencies for war projects. | ||
Line 85: | Line 84: | ||
− | + | = [[IAM Buckminster Integration]] = | |
Dependencies declared in a workspace project <tt>pom</tt> can be checked out in the workspace using their ''scm'' information. | Dependencies declared in a workspace project <tt>pom</tt> can be checked out in the workspace using their ''scm'' information. |
Revision as of 15:06, 7 May 2009
< To: IAM
You can see a list of some of the features below. There are also slides available presented at different conferences.
- Eclipse IAM, Maven Integration For Eclipse. ApacheCon EU 2009 March 26th 2009 by Carlos Sanchez
- Eclipse IAM. EclipseCon 2009 March 26th 2009 by Mike Poindexter
Contents
- 1 Core
- 1.1 Direct import of Maven 2 projects
- 1.2 Maven suggestions in the XML editor
- 1.3 Always updated dependencies
- 1.4 Profile activation/deactivation
- 1.5 Open Artifact Search Framework
- 1.6 Resolve Maven Mojos from the Workspace
- 1.7 New Archetype Provider for the Archetype Catalog format
- 1.8 Form based POM editors
- 2 Tooling
- 3 = Dependency Viewer
- 4 = Dependency Analysis
- 5 WTP support
- 6 IAM Buckminster Integration
Core
Direct import of Maven 2 projects
Maven suggestions in the XML editor
When editing pom.xml files, values for the GroupId, PackageId and Version tags when adding a dependency are available.
This feature uses the Open Artifact Search Framework outlined below.
Always updated dependencies
No need to mvn install the dependencies on the workspace when running maven goals. The most current version is always used.
This means that you can modify a project on your workspace and use it in the surefire tests of a different one depending on it. Instantly.
Profile activation/deactivation
The profile view allows for quickly enabling and disabling profiles when running maven.
Open Artifact Search Framework
New extension points allow third parties to develop and register search engines for their indexing solution.
Several implementations are bundled with the install so you can use it out of the box.
Resolve Maven Mojos from the Workspace
It is possible to have maven mojo projects on the workspace and haven them used by q4e.
New Archetype Provider for the Archetype Catalog format
The archetype catalog xml format used by the archetype 2.0 plug-in can now be used with q4e for selecting an archetype in the New Maven Project wizard.
This format is used to register an internal catalog by default, which replaces the wiki provider (although it can still be manually added).
Form based POM editors
Edit POM files in a form based editor that synchronizes automatically to the pom.xml file in both directions. Also allows you to see the parent POM and the effective POM.
Settings.xml editor
Tooling
= Dependency Viewer
= Dependency Analysis
WTP support
J2EE Project Dependencies management
Automatic synchronization of J2EE project dependencies from maven dependencies for war projects.
All your dependencies in the workspace will be available when running the project on a J2EE server.
IAM Buckminster Integration
Dependencies declared in a workspace project pom can be checked out in the workspace using their scm information.
This is available in the Maven 2 context menu for the project.