Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "What's in IAM"
(Add screenshot) |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| 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 which are more up to date than this page. | |
| − | + | * [http://www.slideshare.net/carlossg/eclipse-iam-maven-integration-for-eclipse Eclipse IAM, Maven Integration For Eclipse. ApacheCon EU 2009] March 26th 2009 by [http://www.carlossanchez.eu/ Carlos Sanchez] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | * [http://www.slideshare.net/mpoindexter/iam-eclipsecon-2009-1005873 Eclipse IAM. EclipseCon 2009] March 26th 2009 by Mike Poindexter | |
| − | + | ||
| − | + | = Core = | |
| − | == | + | == Direct import of Maven 2 projects == |
| − | + | [[Image:Import_wizard.png]] | |
| + | == New project wizard from Maven Archetypes == | ||
| + | |||
| + | Wizard for creation of new projects using the archetype mechanism | ||
| + | |||
| + | We also provide an [http://code.google.com/p/q4e/wiki/Archetype2ArchetypeProvider Archetype Provider for the Archetype Catalog format] to plug other archetype sources | ||
| + | |||
| + | The archetype catalog xml format used by the archetype 2.0 plug-in can now be used to select 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). | ||
| + | |||
| + | == [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. | ||
| + | |||
| + | == Always updated dependencies == | ||
| + | |||
| + | No need to mvn install the dependencies on the workspace when running maven goals. The most current version is always used. | ||
| + | |||
| + | [[Image:DependencyPackaging.png]] | ||
| + | |||
| + | 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. | ||
| + | |||
| + | [[Image:ProfilesView.png]] | ||
| + | |||
| + | |||
| + | |||
| + | = Editors = | ||
| + | |||
| + | == 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 | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | [[Image:PomXmlSuggestion.png]] | ||
| + | |||
| + | This feature uses the Open Artifact Search Framework outlined below. | ||
| + | |||
| + | |||
| + | |||
| + | = Search = | ||
| + | |||
| + | == Archiva search integration == | ||
| + | |||
| + | [[Archiva_Search_Integration]] find real time what's available in your Archiva repository | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | [[Image:SearchEngines.png]] | ||
| + | |||
| + | |||
| + | |||
| + | = Tooling = | ||
| + | |||
| + | == [http://code.google.com/p/q4e/wiki/DependencyGraphViewer Dependency Viewer] == | ||
| + | |||
| + | [[Image:Dependency_viewer.png]] | ||
| + | |||
| + | == [http://code.google.com/p/q4e/wiki/DependencyAnalysis Dependency Analysis] == | ||
| + | |||
| + | [[Image:Dependency_analysis.gif]] | ||
| + | |||
| + | |||
| + | |||
| + | = WTP support = | ||
| + | |||
| + | == J2EE Project Dependencies management == | ||
| + | |||
| + | Automatic synchronization of J2EE project dependencies from maven dependencies for war projects. | ||
| + | |||
| + | [[Image:J2eeDependencies.png]] | ||
| + | |||
| + | All your dependencies in the workspace will be available when running the project on a J2EE server. | ||
| + | |||
| + | == WAR / EAR Support == | ||
| + | |||
| + | Eclipse IAM supports WAR and EAR projects, including deployment to application servers, war overlay,... See [[IAM_WTP_support]] for details. | ||
| + | |||
| + | = [[IAM Buckminster Integration]] = | ||
| + | |||
| + | Dependencies declared in a workspace project <tt>pom</tt> can be checked out in the workspace using their ''scm'' information. | ||
| + | |||
| + | [[Image:IAMBuckminster_MaterializeDependenciesDialog.png | center]] | ||
| + | |||
| + | This is available in the ''Maven 2'' context menu for the project. | ||
[[Category:IAM]] | [[Category:IAM]] | ||
Latest revision as of 11:24, 27 August 2010
< To: IAM
You can see a list of some of the features below. There are also slides available presented at different conferences which are more up to date than this page.
- 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
Core
Direct import of Maven 2 projects
New project wizard from Maven Archetypes
Wizard for creation of new projects using the archetype mechanism
We also provide an Archetype Provider for the Archetype Catalog format to plug other archetype sources
The archetype catalog xml format used by the archetype 2.0 plug-in can now be used to select 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).
Resolve Maven Mojos from the Workspace
It is possible to have maven mojo projects on the workspace and haven them used by q4e.
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.
Editors
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
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.
Search
Archiva search integration
Archiva_Search_Integration find real time what's available in your Archiva repository
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.
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.
WAR / EAR Support
Eclipse IAM supports WAR and EAR projects, including deployment to application servers, war overlay,... See IAM_WTP_support for details.
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.