Sounds good. The only caution I'd exercise is that I think one of
them introduces POM elements - I'm not sure if we want them into 2.0.8.
If we do add them, that's fine though I'm not entirely sure what the
current situation is with Maven reading POMs from the repository with
elements it doesn't understand (I think it safely ignores them, just
need to test).
One other thing to consider is whether it is easier to use the StAX
modello plugin instead of xpp3. Probably not until 2.1 since we'd
want to disentangle xpp3 from a number of other places, but just
throwing it out there.
Side note, I went through the issues in 2.0.8 and voted too, but I
didn't have any 'must be in 2.0.8' issues that I felt compelled raise.
On 22/06/2007, at 7:39 AM, Jason van Zyl wrote:
It seems like there are many problems with encoding that could be
easily solved with a couple tweaks to modello, specifically the
reader and writing so I've scheduled these for 2.0.8. There some
patches for these and hopefully Herve will work his magic with his
suggested fix. I like the idea of borrowing the idea from the Rome
IO utils to find the right encoding by default. That could easily
be integrated into modello. Herve if you need access to Modello we
can set you up.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
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]
