[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-301) Document Maven How-Tos

[Michelle Murray (JIRA)]

     [ https://issues.jboss.org/browse/TOOLSDOC-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Murray updated TOOLSDOC-301:
-------------------------------------
    Issue Type: Epic  (was: Task)


> Document Maven How-Tos
> ----------------------
>
>                 Key: TOOLSDOC-301
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-301
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Epic
>          Components: User Guide - Maven Tools
>    Affects Versions: 3.3.0.Final
>            Reporter: Burr Sutter
>            Assignee: Michelle Murray
>             Fix For: 4.2.0.Beta1
>
>
> Maven is "black magic" to the average developer and this task intends to capture the key scenarios that should be documented and/or tooling improved:
> 1) Why is THIS dependency needed? What specific component is using it?
> 2) Where did THIS dependency come from?  What repository?
> 3) How can I work offline, off the net?  How do I know an artifact that I am reaching for is not on my local machine? Not on my local network?
> 4) Since a property, determines the BOM and the BOM determines the versions of each included dependency, how can I trace those versions, see what is being used?
> 5) Often my local .m2/repository collects a "bad" artifact, how can I detect that and clean it up?



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)