Document Maven How-Tos ---------------------- Key: JBIDE-12245 URL: https://issues.jboss.org/browse/JBIDE-12245 Project: Tools (JBoss Tools) Issue Type: Task Components: maven Affects Versions: 3.3.0.Final Reporter: Burr Sutter 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?

Document Maven How-Tos ---------------------- Key: JBIDE-12245 URL: https://issues.jboss.org/browse/JBIDE-12245 Project: Tools (JBoss Tools) Issue Type: Task Components: maven Affects Versions: 3.3.0.Final Reporter: Burr Sutter Assignee: Burr Sutter Fix For: 4.0.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?

Document Maven How-Tos ---------------------- Key: JBIDE-12245 URL: https://issues.jboss.org/browse/JBIDE-12245 Project: Tools (JBoss Tools) Issue Type: Task Components: maven Affects Versions: 3.3.0.Final Reporter: Burr Sutter Assignee: Burr Sutter Fix For: 4.0.x 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?