Re: [Woden] Moving to Java 5 and dropping woden-qname module

+1 If any Woden consumer has a hard dependency on Java 1.4 please speak up now. Lawrence From: Sagara Gunathunga To: dev@ws.apache.org Date: 05/17/2011 08:45 AM Subject: [Woden] Moving to Java 5 and dropping woden-qname module Hi devs, Since some of the projects moving to Java 6 this is

Re: [Woden] Moving to Java 5 and dropping woden-qname module

Not from me. Moving up to Java5 makes complete sense and removing stuff that causes conflicts and issues is always good. :-) Dan On Tuesday, May 17, 2011 8:43:53 AM Sagara Gunathunga wrote: > Hi devs, > > Since some of the projects moving to Java 6 this is a very late > discussion to have

Build failed in Jenkins: woden-trunk #148

See Changes: [sagara] Added SNAPSHOT versions of dependencies. -- [...truncated 3 lines...] U pom.xml At revision 1104308 Found mavenVersion 2.0.9 from file jar:file:/home/hudson/tools

Build failed in Jenkins: woden-trunk » Woden - OM #148

See -- [INFO] [INFO] Building Woden - OM [INFO]task-segment: [clean, install] [INFO]

[jira] [Commented] (XMLSCHEMA-3) DefaultURIResolver doesn't resolve JAR style URLs properly

[ https://issues.apache.org/jira/browse/XMLSCHEMA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034749#comment-13034749 ] geoff day commented on XMLSCHEMA-3: --- thanks for the update guys, when can i expect vers

[Woden] Moving to Java 5 and dropping woden-qname module

Hi devs, Since some of the projects moving to Java 6 this is a very late discussion to have :) BTW these are the two modification I suggest for Woden. 1.) Moving to support Java 5 officially. 2.) With above change no need to keep woden-qname module that has single class (QName ). Earlier there