+1, with the "later date" being driven by need or request. I was
initially looking at doing the same thing with the simple XML parser,
before I figured out how to use some of the less-commonly used features
of the parser.
Randall Hauch wrote:
Very good question. The project information and dependency
management
aspects, I believe, are the most useful. Maybe we could start small
and get that kind of stuff working, and then enhance it at a later date?
Thoughts? Please weigh in, everyone.
Randall
On Jun 15, 2008, at 3:25 PM, Michael Trezzi wrote:
> Hello,
> I am creating a schema for the Maven2 POM sequencer, however I see
> that the POM syntax is HUGE and contains tons of things. I just want
> to ask what are your opinions what should be sequenced. There are
> basically 2 options:
>
> a) everything (basically mirroring the XML structure)
> b) only a subset for which I would probably take: groupId,
> artifactId, version, name, description, url, licenses, dependencies
> (all metadata excluding exclusions)
>
> Thanks in advance for your opinions.
>
> Michael Trezzi
>
> _______________________________________________
> dna-dev mailing list
> dna-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/dna-dev
_______________________________________________
dna-dev mailing list
dna-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/dna-dev