If you were working for a company which required that their software run on
JDK6 and when you ask the developers whether they have extensively tested
the software on JDK 6, and the answer is, yes, the continuous integration
system runs that, but we developers mostly test it with JDK5, would you be
Axis2 web console component contains some JSP and HTML errors and deprecated
tag names.
---
Key: AXIS2-4980
URL: https://issues.apache.org/jira/browse/AXIS2-4980
Proj
[
https://issues.apache.org/jira/browse/AXIS2-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ying Andrews updated AXIS2-4980:
Attachment: core.patch
I have fixed these minor issues in the attached patch. The patch will make t
I don't see any empirical evidence that would support the claim that
Axis2 is not sufficiently tested with Java 1.6. How do you come to
that conclusion?
Andreas
On Wed, Mar 16, 2011 at 08:21, Afkham Azeez wrote:
> If you were working for a company which required that their software run on
> JDK6
The Ant release notes say this:
"Ant no longer ships with Apache Xerces-J or the XML APIs but relies
on the Java runtime to provide a parser and matching API versions."
It's for the very same reason that we removed Xerces from our
distributions; it is simply not necessary to include it because th
I agree with Andreas here. I work on commercial software and we always build
on a minimum JDK (happens to be 5 at the moment) and we always claim support
for that version and above. I do not think that there is any hesitation for
consumers of open source software to take a release that support
On Thu, Mar 17, 2011 at 2:33 AM, Andreas Veithen
wrote:
> I don't see any empirical evidence that would support the claim that
> Axis2 is not sufficiently tested with Java 1.6. How do you come to
> that conclusion?
>
What percentage of developers build/test Axis2 on a regular basis on Java
1.6? A
