On Jan 26, 2006, at 1:06 PM, Aaron Mulder wrote:
On 1/26/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
How about we just eliminate the single string from? In most cases,
you shouldn't need the parentId anyway, and in the cases you do, you
simply use this:
<parent>
<groupId>geronimo</groupId>
<artifactId>foo</artifactId>
</parent >
-dain
P.S., I think we should make "car" the default type and allow it to
be optional.
Except, we currently allow you to specify abitrary configIds. So you
can declare a configId of "foo" or "foo/bar", and then it's not clear
what an import would look like if you tried to use the split-up syntax
to refer to that configId.
I agree that it is not clear, and I think that is a big problem. If
we switch to an explicitly separated maven format, there will be no
confusion.
Also, parentId is currently an attribute which we can't decompose as
easily. Granted we could just eliminate parentId in favor of <import>
(which as far as I can tell does the same thing), but we still have to
figure out what to do about the above. I'm not super-thrilled with
telling people that they must write every plan using the
configId="group/artifact/version/type" syntax.
I agree that forcing as strict string model is to complex. I see two
possible solutions. Split up string as attributes:
<configuration groupId="myCompany" artifactId="myAppName"
version="1.0">
Traditional maven style:
<configuration>
<groupId>myCompany</groupId>
<artifactId>myApplication</artifactId>
<version>1.0<version>
Regardless of the option we choose, I think all three parts should be
optional with the following defaults:
groupId: Unspedified or ""
artifactId: filename without extension
version: international timestamp in one of the following formats
2006-01-26-1326
200601261326
SNAPSHOT-2006-01-26-1326
SNAPSHOT-200601261326
-dain
Can we say "there are configIds with 3 slashes and there are all other
configIds" and "if you don't have 3 slashes then you only use
artifactId to refer to it, otherwise you must use at least groupId and
artifactId and may use version and type"?
I'm not sure about making "car" the default since we also use these
same elements for dependencies, which are most naturally of type
"jar". Though I guess there's no reason we can't have different
defaults for "import" than for "dependency" and "include".
Thanks,
Aaron
