[
https://issues.apache.org/jira/browse/IVY-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakari Maaranen updated IVY-855:
--------------------------------
Description:
Ivy uses XML attributes all too often. Many information elements, especially
potential multiline text items should be possible to specify as XML elements
instead of attributes.
Probably the best examples are various description-items, e.g. module
configuration descriptions. Currently one must specify: {{<conf name="example"
description="WENDY" />}}
It would be better to do it like so:
{{<conf name="example">}}
{{ <description>}}
{{ WELCOME TO MIAMI BEACH.}}
{{ HAVE A NICE DAY!}}
{{ </description>}}
{{</conf>}}
At least potentially long data elements like descriptions should be made
sub-elements instead of attributes. Of course both could be allowed like Ant
often does.
This should also be promoted as a design principle, and not just an individual
bug. Always supports XML element notation when some information element is
potentially long, multiline, or structural. Both the attribute and the element
notation should be supported when an item can be either small or large
(multiple lines / structured).
was:
Ivy uses XML attributes all too often. Many information elements, especially
potential multiline text items should be possible to specify as XML elements
instead of attributes.
Probably the best examples are various description-items, e.g. module
configuration descriptions. Currently one must specify: {{<conf name="example"
description="WENDY" />}}
It would be better to do it like so:
{{<conf name="example">
<description>
WELCOME TO MIAMI BEACH.
HAVE A NICE DAY!
</description>
</conf>}}
At least potentially long data elements like descriptions should be made
sub-elements instead of attributes. Of course both could be allowed like Ant
often does.
This should also be promoted as a design principle, and not just an individual
bug. Always supports XML element notation when some information element is
potentially long, multiline, or structural. Both the attribute and the element
notation should be supported when an item can be either small or large
(multiple lines / structured).
Just fixed some cosmetic probs with the wiki-notation...
> Overuse of XML attributes where subelements would be more appropriate
> ---------------------------------------------------------------------
>
> Key: IVY-855
> URL: https://issues.apache.org/jira/browse/IVY-855
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-beta-2
> Reporter: Sakari Maaranen
> Priority: Minor
>
> Ivy uses XML attributes all too often. Many information elements, especially
> potential multiline text items should be possible to specify as XML elements
> instead of attributes.
> Probably the best examples are various description-items, e.g. module
> configuration descriptions. Currently one must specify: {{<conf
> name="example" description="WENDY" />}}
> It would be better to do it like so:
> {{<conf name="example">}}
> {{ <description>}}
> {{ WELCOME TO MIAMI BEACH.}}
> {{ HAVE A NICE DAY!}}
> {{ </description>}}
> {{</conf>}}
> At least potentially long data elements like descriptions should be made
> sub-elements instead of attributes. Of course both could be allowed like Ant
> often does.
> This should also be promoted as a design principle, and not just an
> individual bug. Always supports XML element notation when some information
> element is potentially long, multiline, or structural. Both the attribute and
> the element notation should be supported when an item can be either small or
> large (multiple lines / structured).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
