[ https://issues.jboss.org/browse/JBDS-2759?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2759: ------------------------------------------- I think the basics usecases are: * Create a Maven project from scratch * Import an existing Maven Project And most likely importing is going to be what *majority* of users are doing. The content of this depends if we want to cover explaining how maven itself works or just focus on what is important in context of eclipse. My vote is mainly for focusing what is importing in context of eclipse and thus explain how maven integration in eclipse works - what is good and what is bad about it. I would explain how you can edit the pom.xml to add/change a dependency and when that is done explain the need to run Update project configuration. Then I would cover how to setup using an additional repository in settings.xml like maven.repository.redhat.com either manually or by using our maven repository dialog. Advanced how to: * cover how to enable autdownload of source and javadoc * usage of maven source lookup container (it somewhat automatces the autodownload) * explain maven lifecycles and how it can result in warnings/errors you as user don't really care or want to care about - in here explain how jboss tools and eclipse provides some autoconfiguration based on what plugins are useed and document the maven properties you can use to turn on/off this auto config such as enable hibernate, annotation processors, war projects etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)