You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2005/01/25 21:00:29 UTC
DO NOT REPLY [Bug 33243] New: -
Need a "meta data" facility.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33243>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33243
Summary: Need a "meta data" facility.
Product: Ant
Version: 1.7Alpha (nightly)
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Core
AssignedTo: dev@ant.apache.org
ReportedBy: alexeys@inventigo.com
After some discussion I want to propose a meta data facility to specify arbitrary
parameters to any ANT objects. The need for that appeared when I started to write
a parallel executor. Often (mostly with test targets) it is necessary to specify
that some targets should not be executed in parallel. One of the ways of
specifying mutexes is using global properties, but it is inconvenient. The better
way is to mark each target with a list of associated mutexes, but adding yet
another parameter into ANT core just for one executor does not make sense.
Instead meta data tags could be used. For example:
-- one level naming schema
<?META mutexes=�test�?>
<target name=�aaa-test�/>
-- two level naming schema
<?MUTEX names=�test�?>
<target name=�aaa-test�/>
The meta data could be accessed via additional Project API:
public MetaData getMetaData(Object o); // using identity map
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org