Jump to: navigation, search

Difference between revisions of "What's in IAM"

 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{backlink|IAM}}
 
{{backlink|IAM}}
= What's in 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 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/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]
Line 10: Line 9:
 
   
 
   
  
== Core ==
+
= Core =
  
=== Direct import of Maven 2 projects ===
+
== Direct import of Maven 2 projects ==
  
 
[[Image:Import_wizard.png]]
 
[[Image:Import_wizard.png]]
  
=== Maven suggestions in the XML editor ===
+
== New project wizard from Maven Archetypes ==
  
When editing pom.xml files, values for the GroupId, PackageId and Version tags when adding a dependency are available.
+
Wizard for creation of new projects using the archetype mechanism
  
[[Image:PomXmlSuggestion.png]]
+
We also provide an [http://code.google.com/p/q4e/wiki/Archetype2ArchetypeProvider Archetype Provider for the Archetype Catalog format] to plug other archetype sources
  
This feature uses the Open Artifact Search Framework outlined below.  
+
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.  
  
=== Always updated dependencies ===
+
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.  
 
No need to mvn install the dependencies on the workspace when running maven goals. The most current version is always used.  
Line 32: Line 37:
 
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 ===
+
== 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 43:
 
[[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.
 
  
Several implementations are bundled with the install so you can use it out of the box.
+
= Editors =
  
[[Image:SearchEngines.png]]
+
== Form based POM editors ==
  
=== [http://code.google.com/p/q4e/wiki/DevelopingMojos Resolve Maven Mojos from the Workspace] ===
+
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.
  
It is possible to have maven mojo projects on the workspace and haven them used by q4e.  
+
Settings.xml editor
  
=== [http://code.google.com/p/q4e/wiki/Archetype2ArchetypeProvider New Archetype Provider for the Archetype Catalog format] ===
+
== Maven suggestions in the XML editor ==
  
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.  
+
When editing pom.xml files, values for the GroupId, PackageId and Version tags when adding a dependency are available.  
  
This format is used to register an internal catalog by default, which replaces the wiki provider (although it can still be manually added).  
+
[[Image:PomXmlSuggestion.png]]
  
 +
This feature uses the Open Artifact Search Framework outlined below.
  
=== 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
+
= Search =
  
== Tooling ==
+
== Archiva search integration ==
  
=== [http://code.google.com/p/q4e/wiki/DependencyGraphViewer Dependency Viewer] ==
+
[[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]]
 
[[Image:Dependency_viewer.png]]
  
=== [http://code.google.com/p/q4e/wiki/DependencyAnalysis Dependency Analysis] ==
+
== [http://code.google.com/p/q4e/wiki/DependencyAnalysis Dependency Analysis] ==
  
[[Image:Dependency_analysis.png]]
+
[[Image:Dependency_analysis.gif]]
  
  
== WTP support ==
 
  
=== J2EE Project Dependencies management ===
+
= 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 82: Line 99:
 
[[Image:J2eeDependencies.png]]
 
[[Image:J2eeDependencies.png]]
  
All your dependencies in the workspace will be available when running the project on a J2EE server.  
+
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]] ==
+
= [[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.

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.


Core

Direct import of Maven 2 projects

Import wizard.png

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.

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.

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.

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.

SearchEngines.png


Tooling

Dependency Viewer

Dependency viewer.png

Dependency Analysis

Dependency analysis.gif


WTP support

J2EE Project Dependencies management

Automatic synchronization of J2EE project dependencies from maven dependencies for war projects.

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 pom can be checked out in the workspace using their scm information.

IAMBuckminster MaterializeDependenciesDialog.png

This is available in the Maven 2 context menu for the project.