10 minutes demo of maven+mevenide for netbeans day 2006 in SF

prerequisites

Netbeans IDE (5.0 or 5.5 beta?)
Latest mevenide2 release (2.1.1)
Sources of maven and/or mevenide projects, for demo purposes.
A prepopulated local repository to make sure builds work and don't take long time.. the network can be possibly down. - TODO - (alternatively have a local fs based remote repository?)

walkthrough

Jason will talks about Maven features and philosophy first. TBD
We should think about ways of weaving the general talk and actual nb demo together.

Open single project

Note that the IDE integration completely replaces the Ant Layer in the IDE the whole project structure is backed up by Maven's POM.
Show the project's logical view.

For this we need a projects with

sources, test sources
some kind of resources
with compile time/runtime dependencies
possibly site or generated sources.
should have pom, settings file present. (profiles.xml also to be considered, probably only if jason talks about profiles)

Open multiproject

First open just the pom project. Show the modules structure of subprojects. Both in projects view and as graph. Open all of the subprojects. (we should do it beforehand as well, to have the parsing of jars phase short in the demo). Needs to be noted again that no imports are necessary, will work for any maven2 project out there.
Show how project's dependencies are interlinked pointing to other opened projects. Demonstrate with hyperlinks. Explain the difference between a Maven dependency and the Ant way of "jars, folders, libraries and projects on classpath". Dynamic resolution is the word.
Also point out that maven repository can hold sources and javadocs for artifacts and we can easily download them.

explain transitivity of dependencies. show graph of dependencies and how these are shown in the projects view. Talk about future features of easy searching and lookup of dependencies via the repository manager.

Building in the IDE.

Explain that IDE project building actions are mapped to maven goals. So building the project, creating javadoc or running tests is done though Maven as if this was done on command line. Every such action can be customized on a per project basis with reasonable defaults in place. The output is parsed and integrated so for example compilation errors are linked with the editor etc.

finals

show url for maven download, mevenide2 download, thank the audience, wait for the bravo exclamations and standing ovation