done
[EMAIL PROTECTED] wrote:
Enter 'em in Jira, that's the easiest way to keep track.
My take on most of the stuff below is that it is mostly a by product of
extending BaseObject, and the properties, though valid maybe meaningless.
We should make sure the xsd documents the meaningful stuff onl
Enter 'em in Jira, that's the easiest way to keep track.
My take on most of the stuff below is that it is mostly a by product of
extending BaseObject, and the properties, though valid maybe meaningless.
We should make sure the xsd documents the meaningful stuff only.
--
dIon Gillard, Multitask C
Cool. There seems to be a pattern of the base POM classes extending
BaseObject, which has name and id properties, but not necessarily
declaring same in XSD or docs. Which is better to follow - code, XSD,
docs (my gut sez go with the code)? Here are the inconsistencies I find:
*Organization -
AFAIK,
comments is missing from the XSD and should be present.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jeffrey Bonevich <[EMAIL PROTECTED]> wrote on 30/11/2003 01:41:44 PM:
> I am working on the POM editor for mevenide's Eclipse plugin. Hoping
I am working on the POM editor for mevenide's Eclipse plugin. Hoping
someone in the know could answer this question:
The License class has properties: name, distribution, url, and comments.
Comments is not discussed in the reference docs, nor is it in the
current version of the XSD for maven'
