Design, Patterns & Best Practices

Shows the unresolved issues sorted by number of votes

unresolved issues | resolved issues

Votes	T	Key	Summary	Fix Version/s	P	Status
26		MNG-2184	Possible problem with @aggregator and forked lifecycles	Issues to be reviewed for 3.x
21		MNG-612	implement conflict resolution techniques	3.x / Backlog
7		MNG-1425	best practices: the location of configuration files vs resources	Documentation Deficit
7		MNG-1468	best practices: version management in multi project builds	Documentation Deficit
4		MNG-1563	how to write integration tests	Documentation Deficit
4		MNG-41	best practices: site management	Documentation Deficit
4		MNG-1423	best practices: setting up multi-module build	Documentation Deficit
3		MNG-139	server definitions should be reusable - review use of repository IDs	Issues to be reviewed for 3.x
3		MNG-1950	Ability to introduce new lifecycles phases	3.x / Backlog
2		MNG-1867	deprecate system scope, analyse other use cases	3.2
1		MNG-2381	improved control over the repositories in the POM	3.2
1		MNG-5277	best practices: The Maven Way	Documentation Deficit
1		MNG-367	best practices: multi-user installation	Documentation Deficit
1		MNG-416	best practices: multiple profile deployments	Issues to be reviewed for 3.x
1		MNG-657	possible chicken and egg problem with extensions	Issues to be reviewed for 3.x
1		MNG-1441	Starting thinking about a proper distributed repository mechanism a la CPAN	Issues to be reviewed for 3.x
1		MNG-1569	Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare	3.2