James Mao wrote:
>> And my project has been moved to ANT, it's just simple to get things
>> done. Maven is too....
>
> I know, tell me about it. I'm thinking about doing "101 things I hate
> about Maven".
>
> Actually finding 101 problems might not be too difficult...
>
> The worst part is that despite all those issues, sometimes Maven is
> the best tool for the job!
One thing i don't like it is that i really don't know which jar has been
loaded in the classpath, i'm trying to print the classpath in the
runtime, what i got is "classworld.jar" what the hell is that?
in ANT, i CAN, it's very clear, which xmlparser i'm using, it's just
easy to debug.
And ANT is faster then maven, it don't need to parse the pom and
dependent pom...
I've create a MANT project, which can manage/download the dependencies
just like maven, i also generalize a set of ant build files which
include all the common targets, like
compile/test/install/get.dependencies/jar/ etc.
I don't know why we still need Maven? Maybe i should get more
tutorial/lessons/consultant about maven, but i don't need with ANT,
it's so simple
Cheers,
James.
>
>>
>> Cheers,
>> James.
>>
>>>
>>> On 2/3/07, *James Mao* <james.mao_at_iona.com
>>> <mailto:james.mao_at_iona.com>> wrote:
>>>
>>> Hi,
>>>
>>> I encounter a very strange problem with jaxb2 UTF-8 support,
>>> I'm using JAXB 2.0.3, jdk 1.5.0_10-b03, the xml is in utf-8
>>> encoding.
>>>
>>> The problem is:
>>>
>>> if the node or attribute contains *three* Chinese characters, the
>>> unmarshall will fail with the exception message:
>>>
>>> [org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8
>>> sequence.]
>>> at
>>>
>>> javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException
>>>
>>> (AbstractUnmarshallerImpl.java:315)
>>> at
>>>
>>> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:476)
>>>
>>>
>>> at
>>>
>>> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0
>>> (UnmarshallerImpl.java:198)
>>> at
>>>
>>> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:167)
>>>
>>> at
>>>
>>> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java
>>>
>>> :137)
>>> at
>>>
>>> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:184)
>>>
>>>
>>> If add another Chinese character (*four* Chinese characters), the
>>> unmarshall works just fine.
>>>
>>> I don't know if it's a known issue in jaxb2? or maybe it's a bug
>>> in the
>>> xml parser used by Jaxb2?
>>>
>>> Trying to upgrade to JAXB2 2.1.2, but seems the version is not
>>> uploaded
>>> to the maven2 repository yet, any plan to upload the latest
>>> version?
>>>
>>>
>>> Thanks,
>>> James.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
>>> <mailto:users-unsubscribe_at_jaxb.dev.java.net>
>>> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>>> <mailto:users-help_at_jaxb.dev.java.net>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
>> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>>
>>
>
>