All information in this wiki is licensed under the Apache License, version 2.0. Please keep this in mind when you contribute.
- Scala and Maven
- Maven Day at Intuit (Thursday October 9th)
- Maven Patch Day
- Getting Started with Maven
- Maven Best Practice Guide
- Proposed Documentation
- Enterprise Maven
- Maven Skins
- Mini Guides
- Archived Docs
- Nexus Maven Repository Manager
- User Proposals
- Solving the Skinny Wars problem
- Using Maven to manage .NET projects
- OSS 计算技术
This wiki space is not for final documentation, but a workspace for creating it. If you think a document can be contributed back to the main site, please record that in JIRA. For discussions, ideas and design documents related to Maven, see the Maven space.
If you're a Java software developer that has worked in any type of team environment, you know that having a proper process is important to developing a quality product. You also know that rote methods can help maintain consistency and standardization among developers. Apache ANT provides most of this however Maven improves upon it in several areas. Maven takes some of that classpath and jar dependency frustrations out of the hands of the day-to-day developer. Most would agree that maintaining the project structure, dependencies, J2EE packaging, etc. is very difficult and when things are not structured correctly, applications cannot be built properly. Jars could be in the wrong place, be the wrong version, an XML file might be missing a descriptor, and a host of other project infrastructure issues can bring a project to stop. When this happens its sometimes difficult to determine where things went wrong. Maven is an excellent tool that solves most of these problems.