Maven Board Report - 18 January 2006

Goings on

ApacheCon was a good experience for many of the Maven developers. We chatted with OSGi folks about how Maven might be used utilzed by OSGi developers. We chatted with Jeff McAffer of the Eclipse PDE team and discussed how some Maven technologies might be integrated into Eclipse in particular their Update Manager. We also chatted with some Cocoon developers about trying to help them convert their build over to Maven 2.x.

Activity in the community has been steadily increasing. We have one of the most active mailing lists (if not the most right now: would be cool to link in Ken's page here) and we are attempting to answer users questions by capturing them in a FAQ document which we want to process and turn into static documentation. We're experimenting with parsing content right now of Confluence i.e. making static sites from a Wiki.

We have been working on a new Development Process for the Maven project which we hope to flesh out over the next release, create some automated tools for, and share with other projects that use Maven to try and help with a process of development, documenting and releasing.

We have been experimenting with some automation tools for issue management and documentation creation. We have created a little Jira Ruby Gem for automating some aspects of our issue management. We're also working on a patch server and submission tools which will take patches and documentation from users directly from the Maven 2.x CLI and create JIRA issues and stow the patch somewhere we can easily process it.
We are also working on trying to setup a structure where all our Maven plug-ins get some sort of review for the time of the Board report because that gives some visilbility to outside observers like the Board but it also helps us keep track of plug-in status. We don't have a clear way of dealing with this right now but we hope to automate something by the next board report.

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Data cannot be retrieved due to an unexpected error. View these issues in Jira

Error rendering macro 'jiraissues'

Macro params are invalid

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Data cannot be retrieved due to an unexpected error. View these issues in Jira

Error rendering macro 'jiraissues'

Macro params are invalid

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Data cannot be retrieved due to an unexpected error. View these issues in Jira

Error rendering macro 'jiraissues'

Macro params are invalid