Other Ideas and Use Cases

Settings Management for Enterprise Deployments

Maven Settings Management

Dependency Comprehension

In our enterprise software reuse efforts, I have found that it can sometimes be troublesome to find the party accountable for a given artifact. In extreme cases the mater of accountability and support of published artifacts can be lost in the rush to meet business demands.

At the same time, the more thoughtful developer will be interested in getting to know the folks that produced the artifact that they may be using. Although maven project sites are intended to be this source of information, I've often found these sites going unpublished.

Therefore...

Consider decorating dependency information with the name of a developer who has the Role of lead and perhaps attempt to surface the social graph of developers not only the graph of artifact dependencies.

Flex Builder bridge

https://bugs.adobe.com/jira/browse/SDK-12730
Flex Builder Configuration API

Useful features will include:

• autogenerate maven project from Flex project settings as well as the inverse to autogenerate Flex Builder project settings from maven project, and keep them in sync
• automatic/ semi automatic uploading of flex libraries into local/remote repositories
• using swc/swf types of artifacts – the first step for this is fairly simple, just stop assuming that artifacts are jars, and give the option of working with an artifact of packaging swc or swf (defaulting to jar is fine, just allow an override)
• work with Adobe to allow Flex Builder to use a Maven classpath container, so project dependencies can be resolved from the local repository
• when files are modified in a project, kick off a maven build of all dependent projects, as well as a Flex Builder build of the dependent projects if necessary
• allow source lookup and asdoc (like javadoc) visibility of maven dependencies
• work with the existing Maven Flex plugins:
  • Flex-Mojos (prototyped)
  • Israfil
  • Serve Box

Archetype Filtering (implemented in 0.9.3)

See Archetype Filtering.

Strong OSGi integration

• automatic generation of bundle-relevant MANIFEST.MF snippets behind the scenes when trying to do a deploy. as soon as 'Run As...' bundle is chosen all dependencies should be added as bundle-classpath entries. then m2eclipse should pass bundle to eclipse OSGi runtime.

  Manuel, can you please elaborate on what "Run As..." mean for the OSGi bundle? Perhaps add a child page with some examples and use cases. EK

  When going for a new configuration and OSGi for maven-project is enabled, respective project should show up as a bundle, which you can register, resolve and start. As an example, see screenshot (maven project shows up in Workspace-bundle set).

!

• integration of maven-bundle plugin to fluently make an eclipse-outside build possible.

  you may want to take a look at Tycho, which is basically a comprehensive suite of Maven plugins for building osgi components and Eclipse RCP apps. EK

Integration with continuous integration servers

The Maven metadata for CI systems is limited to the system type and url. For example:

<ciManagement>
  <system>Hudson</system>
  <url>https://ci.sonatype.org/job/m2eclipse-with-e33/</url>
</ciManagement>

So, to map CI projects/jobs back to Maven artifacts one would have to read Maven poms from CI server.

Use cases and actions:

• materialize project from build server into the local workspace (implemented in c4e)
• for given Maven artifact (from popup menu, from Maven POM editor, etc)
  • run build
  • open build configuration
  • open build history
  • open build log

Foe example, here is how standard console, history, run actions could look like in the Maven POM editor UI: