Right of course, but the core idea is that XML doesn't drive the
format or structure of data. It should tell you guys something that
negative reactions to Maven like Buildr use the colon notation.
Maven itself prints out dependencies using the colon notation when you
run the dependency plugin and when you turn on debug info.
On Feb 12, 2008, at 9:18 AM, nicolas de loof wrote:
Your example just demonstrate the issue with String formated :
<time>23:22:22.003</time>
or
<time>11PM:22:22.003</time>
or
<time>21:22:22.003 UTC</time>
???
The "native" format for time (in computer world) is number of ms since
01/01/1970 .. so its un non-formated binary type
The equivalent XML element should be something like
<time format="xx" timezone="yy">23:22:22.003</time>
2008/2/12, Tim O'Brien <[EMAIL PROTECTED]>:
On Feb 12, 2008, at 3:58 AM, Benjamin Bentmann wrote:
For example, we'd can group groupId/artifactId/version into one
attribute
like this:
<dependency artifact="org.apache.maven:maven-project:
2.0.8" [...] />
Please don't do this. This would require another parsing step after
the XML
parsing and introduces further error sources. Use XML to structure
the data,
not some proprietary format. Third-party tools dealing with the POM
will
also appreciate a proper/pure XML representation of the project
model.
Consider for instance the pain such string aggregates would cause
for XSLT
processing of the POM. Merging different pieces of data into a
single string
is in general a bad idea.
Couldn't disagree more. Certain data has a native format. Consider
something like a 24 hour time. Is:
<time>23:22:22.003</time>
an "undue burden" on different parsers? No, this is reasonable.
This would be unreasonable:
<time hour="23" minute="22" second="22" millis="003"/>
The idea that we have to design data around parsers means that you
sacrifice usability and readability.
I'd take it one step further than Emmanuel:
<dependencyGroup root="org.apache.maven">
<dependency artifact="maven-project:2.0.8"/>
<dependency artifact="continuum:continuum-model:1.1"/>
</dependencyGroup>
Should be:
<dependGroup root="org.apache.maven">
maven-project:2.0.8
continuum:continuum-model:1.1
</dependGroup>
XSLT can tokenize strings just fine.
Besides, this thread is about improving user experience with the
POM. Now,
if one needs to declare a dependency with groupId, artifactId,
version,
classifier, type and scope can you remember the proper order for all
those
elements when putting them into a single string? As for me, the
answer is
"No".
Regards,
Benjamin Bentmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
