[jbosstools-issues] [JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious
[
https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-16343:
-------------------------------------
The thing is this feature is not linked/tied to Maven. It can take *any* classpath
container aka classpath library (gradle, ivy, junit, whatever ...) and extract its jars.
Calling them dependencies doesn't fit either as it should have a more generic name
(jars? classpath entries?).
Burr : the term "library" here corresponds to what you see in Eclipse's
Project Properties > Java Build Path > Libraries > Add Library... So it's
completely coherent.
"Materialize Libraries" is not obvious
--------------------------------------
Key: JBIDE-16343
URL: https://issues.jboss.org/browse/JBIDE-16343
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: maven
Affects Versions: 4.2.0.Alpha1
Reporter: Mickael Istria
Assignee: Fred Bricon
Fix For: 4.2.x
While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that
"Materialize Libraries" is not a clear name for what it does.
Why not renaming it to "Copy libraries into Project..." or "Turn into
Libraries inside project..." ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira