First thanks and second i would like to apologize, if my mail was too harsh.
Franz
Carlos Sanchez schrieb:
The reference API is under javax.xml.bind in
http://www.ibiblio.org/maven2/javax/xml/bind/ and sun implementation
under com.sun.xml.bind
On 8/11/06, Franz Fehringer <[EMAIL PROTECTED]> wr
Kohsuke is right, although old stuff may be under javax.xml and
com.sun.xml we see better fit under javax.xml.something and as they
manage com.sun.* they can do however they want there (and we are not
involved in this later case).
On 8/11/06, Kohsuke Kawaguchi <[EMAIL PROTECTED]> wrote:
Franz Fe
Franz Fehringer wrote:
Hello,
Are there any current activities for enabling JAXB2 support in Maven2?
In http://www.ibiblio.org/maven2/javax/xml/ there are jaxb-api jaxb-impl
jaxb-xjc, but they still contain only 2.0EA3.
Since 17. of july there is an additional subdirectory bind, but there
are
The reference API is under javax.xml.bind in
http://www.ibiblio.org/maven2/javax/xml/bind/ and sun implementation
under com.sun.xml.bind
On 8/11/06, Franz Fehringer <[EMAIL PROTECTED]> wrote:
I am not interested in "javax.xml instead of java.xml.bind", i am only
interested in a working (and curr
I am not interested in "javax.xml instead of java.xml.bind", i am only
interested in a working (and current) Maven2/JAXB2 combination (and a
fix for MNG-2305).
Greetings
Franz
Wayne Fay schrieb:
You should probably file the "javax.xml instead of java.xml.bind"
issue on JIRA under MEV if you
You should probably file the "javax.xml instead of java.xml.bind"
issue on JIRA under MEV if you actually expect someone to "fix" it.
Otherwise its just lots of talk on the Users list...
Wayne
On 8/11/06, Franz Fehringer <[EMAIL PROTECTED]> wrote:
IIUC the point was, that the groupId should
Yeah, I definitely agree that it should be under javax instead of com.sun --
but that's just because com.sun is supposedly reserved for Sun internal;
whereas javax is reserved for JCP-authorized extensions.
Regarding the proxy bit.. So it seems like the correct solution would be if
there is a wa
IIUC the point was, that the groupId should be javax.xml and not
java.xml.bind (the link given for this currently yields Application
error (Rails)) .
I reported the proxies/settings.xml error as MNG-2305.
Greetings
Franz
Malachi de Ælfweald schrieb:
Yeah, I definitely agree that it should b
Regarding the location (javax.xml.bind versus java.xml) i had a mail
sent by [EMAIL PROTECTED] in mind saying
.
.
.
Please note, that the policy for the groupId is "javax.xml" and "com.sun.xml" only. See
also http://www.mavenregistry.com/search/artifacts?hl=en&q=jsr173&btnG=Search+Registry
.
.
We should be using the latest version of JAXB, which is 2.0.2 as per the
website. Personally, I was not aware that the jars made it onto ibilio -- I
thought they were supposed to be hosted at java.net?
Out of curiousity, why would javax.xml.bind be incorrect for XML
Databinding?
Malachi
On 8/1
Hello,
Are there any current activities for enabling JAXB2 support in Maven2?
In http://www.ibiblio.org/maven2/javax/xml/ there are jaxb-api
jaxb-impl jaxb-xjc, but they still contain only 2.0EA3.
Since 17. of july there is an additional subdirectory bind, but there
are several things wrong/mi
11 matches
Mail list logo
