[JBoss JIRA] (TOOLSDOC-301) Document Maven How-Tos
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-301?page=com.atlassian.jira.plug... ]
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)
11 years, 6 months
[JBoss JIRA] (TOOLSDOC-301) Document Maven How-Tos
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-301?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-301:
-------------------------------------
Fix Version/s: (was: 4.2.0.Beta1)
Epic Name: Maven How-Tos
> 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
>
> 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)
11 years, 6 months
[JBoss JIRA] (TOOLSDOC-343) NeedInfo: Disabling validation to remove/reduce false warnings
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-343?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-343.
--------------------------------------
Resolution: Out of Date
> NeedInfo: Disabling validation to remove/reduce false warnings
> --------------------------------------------------------------
>
> Key: TOOLSDOC-343
> URL: https://issues.jboss.org/browse/TOOLSDOC-343
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: User Guide - JSF Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
>
> I came across: http://docs.jboss.org/tools/whatsnew/jst/jst-news-3.3.0.M5.html
> It states:
> 1) JSF @FacesConverter validation: faces converter validation is an issue in eclipse
> 2) Configuring Problem Severity via Quick Fix: problems if you use CDI programatically or you use CDI components that are not detectable by the tooling
> *Are these instances of validation still issues?*
> I tested (1) with <f:converter converterID="test"></f:converter> and didn't get any error or warning messages so thought it might be fixed in eclipse. Not sure how to test CDI yet (haven't got to that chapter!).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months