Brett Porter wrote:
On 14/01/2008, at 5:20 PM, Trygve Laugstøl wrote:
Brett Porter wrote:
Hi,
I just wanted to point out I made a couple of changes:
- changed the model format (classpath elements are grouped by type to
be more conducive to being read by modello) - this impacts the
descriptor file format
Got an example?
- switched to a stax reader/writer generated by modello to avoid
needing to maintain the reader/writer by hand (I needed to add some
other fields as well)
Where was this changed? The point by reading the file by hand was to
not add any dependencies outside the JDK.
oops... commit didn't go through but mail did, and then I walked away a
few hours, hehe. I did a bunch of stuff offline :)
Any objections?
Personally, I don't quite understand why there is a descriptor file
anyway just yet - maybe someone can provide some insight on it's use
cases?
Some of the configurations are so huge that it was easier to have it
an external file. In addition stuff like automatic updates of systems
was planned so then you need a descriptor of the current system.
Ok... it seemed all the configurations were being mirrored in the POM
configuration so I was confused :)
Yes, it probably is. The idea is to separate the core appassembler code
from the Maven plugin. The Maven plugin optionally read a file from
disk, merge in the stuff from the plugin configuration and pass it on to
the requested generators. I would like to split out the core code from
the plugin code someday, hopefully before a 1.0 release.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
