You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by Mukul Gandhi <mu...@apache.org> on 2018/07/29 05:40:10 UTC
java project build question, in eclipse IDE
Hi all,
I apologize for cross posting to, two Xerces lists.
I need some help from the community here. Its an Eclipse question (Version:
Luna Release 4.4.0 Build id: 20140612-0600), while I'm working with Xerces
source code.
I've following three Java projects within my Eclipse workspace.
1) This project is the Xerces source code from the location,
https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/.
2) This project is the Xerces source code from the location,
https://svn.apache.org/repos/asf/xerces/java/trunk/.
3) This is my own application Java project, that simply does SAX and DOM
parsing with validation.
In the "Java Build Path" of project 3) mentioned above, I've specified
project 1) as dependency. Projects 1) & 2) build fine. But project 3) gives
me compilation error, that classes like javax.xml.validation.SchemaFactory
not found. Can someone please suggest, how I can fix this? I've also tried
starting Eclipse with option -clean, but that doesn't help. Its been 1-2
weeks, that I'm trying to solve this problem, but haven't found solution
yet :( I would be happy for any help.
I'm using JDK 1.4.2 within the mentioned Eclipse workspace.
--
Regards,
Mukul Gandhi
Re: [EXTERNAL] Re: java project build question, in eclipse IDE
Posted by Christophe Marchand <cm...@oxiane.com>.
I vote for Java 7 as a minimum for Xerces 2.12.xxx
There is still a lot of very old desktop computers with java 6 & swing
applications. And maintainers need strong arguments to migrate to recent
JDKs.
Removing support for pre-java 7 in Xerces will be a strong-enough argument.
Christophe
Le 30/07/2018 à 15:27, David Dillard a écrit :
>
> That sounds like a good idea. Testing on JDK 1.4, which has been EOL
> for years now, seems like a waste of time.
>
> Java 6 extended support ends this December, so either Java 6 or Java 7
> might be a good place to start.
>
> *From:* Mukul Gandhi [mailto:mukulg@apache.org]
> *Sent:* Monday, July 30, 2018 7:13 AM
> *To:* Elliotte Rusty Harold <el...@ibiblio.org>
> *Cc:* j-dev@xerces.apache.org; j-users@xerces.apache.org
> *Subject:* [EXTERNAL] Re: java project build question, in eclipse IDE
>
> On Mon, Jul 30, 2018 at 4:25 PM, Elliotte Rusty Harold
> <elharo@ibiblio.org <ma...@ibiblio.org>> wrote:
>
> I'm curious. Why do you need 1.4 and 1.3? Do you have customers
> using those?
>
> This needs to be understood correctly. Xerces can run on min JREs 1.4
> (if XSD 1.1 is needed) and 1.3 respectively. This doesn't mean, that
> Xerces cannot run on higher version JREs (I've personally tested, that
> Xerces 2.12.0 can run fine up to JDK 9).
>
> May be its time, we need to revisit the min JDK levels for
> Xerces. Michael Glavassevich needs to organize consensus on this.
>
>
>
> --
>
> Regards,
> Mukul Gandhi
>
RE: [EXTERNAL] Re: java project build question, in eclipse IDE
Posted by David Dillard <Da...@veritas.com>.
That sounds like a good idea. Testing on JDK 1.4, which has been EOL for years now, seems like a waste of time.
Java 6 extended support ends this December, so either Java 6 or Java 7 might be a good place to start.
From: Mukul Gandhi [mailto:mukulg@apache.org]
Sent: Monday, July 30, 2018 7:13 AM
To: Elliotte Rusty Harold <el...@ibiblio.org>
Cc: j-dev@xerces.apache.org; j-users@xerces.apache.org
Subject: [EXTERNAL] Re: java project build question, in eclipse IDE
On Mon, Jul 30, 2018 at 4:25 PM, Elliotte Rusty Harold <el...@ibiblio.org>> wrote:
I'm curious. Why do you need 1.4 and 1.3? Do you have customers using those?
This needs to be understood correctly. Xerces can run on min JREs 1.4 (if XSD 1.1 is needed) and 1.3 respectively. This doesn't mean, that Xerces cannot run on higher version JREs (I've personally tested, that Xerces 2.12.0 can run fine up to JDK 9).
May be its time, we need to revisit the min JDK levels for Xerces. Michael Glavassevich needs to organize consensus on this.
--
Regards,
Mukul Gandhi
RE: [EXTERNAL] Re: java project build question, in eclipse IDE
Posted by David Dillard <Da...@veritas.com>.
That sounds like a good idea. Testing on JDK 1.4, which has been EOL for years now, seems like a waste of time.
Java 6 extended support ends this December, so either Java 6 or Java 7 might be a good place to start.
From: Mukul Gandhi [mailto:mukulg@apache.org]
Sent: Monday, July 30, 2018 7:13 AM
To: Elliotte Rusty Harold <el...@ibiblio.org>
Cc: j-dev@xerces.apache.org; j-users@xerces.apache.org
Subject: [EXTERNAL] Re: java project build question, in eclipse IDE
On Mon, Jul 30, 2018 at 4:25 PM, Elliotte Rusty Harold <el...@ibiblio.org>> wrote:
I'm curious. Why do you need 1.4 and 1.3? Do you have customers using those?
This needs to be understood correctly. Xerces can run on min JREs 1.4 (if XSD 1.1 is needed) and 1.3 respectively. This doesn't mean, that Xerces cannot run on higher version JREs (I've personally tested, that Xerces 2.12.0 can run fine up to JDK 9).
May be its time, we need to revisit the min JDK levels for Xerces. Michael Glavassevich needs to organize consensus on this.
--
Regards,
Mukul Gandhi
Re: java project build question, in eclipse IDE
Posted by Mukul Gandhi <mu...@apache.org>.
On Mon, Jul 30, 2018 at 4:25 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
>
> I'm curious. Why do you need 1.4 and 1.3? Do you have customers using
> those?
This needs to be understood correctly. Xerces can run on min JREs 1.4 (if
XSD 1.1 is needed) and 1.3 respectively. This doesn't mean, that Xerces
cannot run on higher version JREs (I've personally tested, that Xerces
2.12.0 can run fine up to JDK 9).
May be its time, we need to revisit the min JDK levels for Xerces. Michael
Glavassevich needs to organize consensus on this.
--
Regards,
Mukul Gandhi
Re: java project build question, in eclipse IDE
Posted by Mukul Gandhi <mu...@apache.org>.
On Mon, Jul 30, 2018 at 4:25 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
>
> I'm curious. Why do you need 1.4 and 1.3? Do you have customers using
> those?
This needs to be understood correctly. Xerces can run on min JREs 1.4 (if
XSD 1.1 is needed) and 1.3 respectively. This doesn't mean, that Xerces
cannot run on higher version JREs (I've personally tested, that Xerces
2.12.0 can run fine up to JDK 9).
May be its time, we need to revisit the min JDK levels for Xerces. Michael
Glavassevich needs to organize consensus on this.
--
Regards,
Mukul Gandhi
Re: java project build question, in eclipse IDE
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
"I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK
1.4, and to develop for trunk we need JDK 1.3."
I'm curious. Why do you need 1.4 and 1.3? Do you have customers using those?
On Mon, Jul 30, 2018 at 2:06 AM, Mukul Gandhi <mu...@apache.org> wrote:
> On Sun, Jul 29, 2018 at 3:56 PM, Elliotte Rusty Harold <el...@ibiblio.org>
> wrote:
>>
>> Is there a reason you're still using 1.4.2?
>
>
> I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK 1.4, and
> to develop for trunk we need JDK 1.3.
>
>>
>> That's likely your issue.
>> javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
>
>
> You're right, and this solves my problem. When I provided explicitly the
> dependency xml-apis.jar (from XSD 1.1 branch's tools folder) to my project
> that was giving error, it worked.
> But I think, the problem I mentioned is likely an Eclipse IDE problem (I'm
> using the 2014 edition). I had given the XSD 1.1 project as a dependency to
> my own project, and this should have provided xml-apis.jar to my own
> project.
>
> Thanks for your help.
>
>
>
> --
> Regards,
> Mukul Gandhi
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: java project build question, in eclipse IDE
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
"I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK
1.4, and to develop for trunk we need JDK 1.3."
I'm curious. Why do you need 1.4 and 1.3? Do you have customers using those?
On Mon, Jul 30, 2018 at 2:06 AM, Mukul Gandhi <mu...@apache.org> wrote:
> On Sun, Jul 29, 2018 at 3:56 PM, Elliotte Rusty Harold <el...@ibiblio.org>
> wrote:
>>
>> Is there a reason you're still using 1.4.2?
>
>
> I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK 1.4, and
> to develop for trunk we need JDK 1.3.
>
>>
>> That's likely your issue.
>> javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
>
>
> You're right, and this solves my problem. When I provided explicitly the
> dependency xml-apis.jar (from XSD 1.1 branch's tools folder) to my project
> that was giving error, it worked.
> But I think, the problem I mentioned is likely an Eclipse IDE problem (I'm
> using the 2014 edition). I had given the XSD 1.1 project as a dependency to
> my own project, and this should have provided xml-apis.jar to my own
> project.
>
> Thanks for your help.
>
>
>
> --
> Regards,
> Mukul Gandhi
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: java project build question, in eclipse IDE
Posted by Mukul Gandhi <mu...@apache.org>.
On Sun, Jul 29, 2018 at 3:56 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
> Is there a reason you're still using 1.4.2?
I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK 1.4, and
to develop for trunk we need JDK 1.3.
> That's likely your issue.
> javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
You're right, and this solves my problem. When I provided explicitly the
dependency xml-apis.jar (from XSD 1.1 branch's tools folder) to my project
that was giving error, it worked.
But I think, the problem I mentioned is likely an Eclipse IDE problem (I'm
using the 2014 edition). I had given the XSD 1.1 project as a dependency to
my own project, and this should have provided xml-apis.jar to my own
project.
Thanks for your help.
--
Regards,
Mukul Gandhi
Re: java project build question, in eclipse IDE
Posted by Mukul Gandhi <mu...@apache.org>.
On Sun, Jul 29, 2018 at 3:56 PM, Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
> Is there a reason you're still using 1.4.2?
I'm member of Xerces dev team. To develop for XSD 1.1 we need JDK 1.4, and
to develop for trunk we need JDK 1.3.
> That's likely your issue.
> javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
You're right, and this solves my problem. When I provided explicitly the
dependency xml-apis.jar (from XSD 1.1 branch's tools folder) to my project
that was giving error, it worked.
But I think, the problem I mentioned is likely an Eclipse IDE problem (I'm
using the 2014 edition). I had given the XSD 1.1 project as a dependency to
my own project, and this should have provided xml-apis.jar to my own
project.
Thanks for your help.
--
Regards,
Mukul Gandhi
Re: java project build question, in eclipse IDE
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
Is there a reason you're still using 1.4.2? That's likely your issue.
javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
On Sun, Jul 29, 2018 at 1:40 AM, Mukul Gandhi <mu...@apache.org> wrote:
> Hi all,
> I apologize for cross posting to, two Xerces lists.
>
> I need some help from the community here. Its an Eclipse question (Version:
> Luna Release 4.4.0 Build id: 20140612-0600), while I'm working with Xerces
> source code.
>
> I've following three Java projects within my Eclipse workspace.
> 1) This project is the Xerces source code from the location,
> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/.
> 2) This project is the Xerces source code from the location,
> https://svn.apache.org/repos/asf/xerces/java/trunk/.
> 3) This is my own application Java project, that simply does SAX and DOM
> parsing with validation.
>
> In the "Java Build Path" of project 3) mentioned above, I've specified
> project 1) as dependency. Projects 1) & 2) build fine. But project 3) gives
> me compilation error, that classes like javax.xml.validation.SchemaFactory
> not found. Can someone please suggest, how I can fix this? I've also tried
> starting Eclipse with option -clean, but that doesn't help. Its been 1-2
> weeks, that I'm trying to solve this problem, but haven't found solution yet
> :( I would be happy for any help.
>
> I'm using JDK 1.4.2 within the mentioned Eclipse workspace.
>
>
>
>
> --
> Regards,
> Mukul Gandhi
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: java project build question, in eclipse IDE
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
Is there a reason you're still using 1.4.2? That's likely your issue.
javax.xml.validation.SchemaFactory wasn't added to the JDK until 1.5.
On Sun, Jul 29, 2018 at 1:40 AM, Mukul Gandhi <mu...@apache.org> wrote:
> Hi all,
> I apologize for cross posting to, two Xerces lists.
>
> I need some help from the community here. Its an Eclipse question (Version:
> Luna Release 4.4.0 Build id: 20140612-0600), while I'm working with Xerces
> source code.
>
> I've following three Java projects within my Eclipse workspace.
> 1) This project is the Xerces source code from the location,
> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/.
> 2) This project is the Xerces source code from the location,
> https://svn.apache.org/repos/asf/xerces/java/trunk/.
> 3) This is my own application Java project, that simply does SAX and DOM
> parsing with validation.
>
> In the "Java Build Path" of project 3) mentioned above, I've specified
> project 1) as dependency. Projects 1) & 2) build fine. But project 3) gives
> me compilation error, that classes like javax.xml.validation.SchemaFactory
> not found. Can someone please suggest, how I can fix this? I've also tried
> starting Eclipse with option -clean, but that doesn't help. Its been 1-2
> weeks, that I'm trying to solve this problem, but haven't found solution yet
> :( I would be happy for any help.
>
> I'm using JDK 1.4.2 within the mentioned Eclipse workspace.
>
>
>
>
> --
> Regards,
> Mukul Gandhi
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org