This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 64432 - Unable to use "arch" target if building against binary NB build harness
Summary: Unable to use "arch" target if building against binary NB build harness
Status: CLOSED DUPLICATE of bug 61231
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-15 14:08 UTC by iformanek
Modified: 2005-11-04 13:01 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-09-15 14:08:56 UTC 
I am building my modules against the harness contained in the binary NB builds.
I was not able to figure out how to specify tej DTD and Arch-api-questions.xml 
reference in my arch.xml, since the DTD and questions files are contained in 
the tasks.jar.

Per Jarda's request filing this into IZ.
Comment 1 iformanek 2005-09-15 14:18:00 UTC 
When I manually put the DTD and questions xml file and specify them 
explicitely, further problem arises with the Arch.dtd reference to xmhtml1-
strict.dtd, the build fails with error:

arch:
D:\Dev\toolscvs.sfbay\cvs-profiler\build\netbeans\harness\common.xml:420: File 
D:\Dev\toolscvs.sfbay\cvs-profiler\profiler\modules\profiler-main\arch\arch-
profiler.xml cannot be parsed: D:\Dev\libs\external\dtds\xhtml1-20020801
\DTD\xhtml1-strict.dtd (The system cannot find the path specified)
        at org.netbeans.nbbuild.Arch.execute(Arch.java:150)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at org.apache.tools.ant.helper.DefaultExecutor.executeTargets
(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run
(BridgeImpl.java:234)
        at org.apache.tools.ant.module.run.TargetExecutor.run
(TargetExecutor.java:283)
        at org.netbeans.core.execution.RunClassThread.run
(RunClassThread.java:125)
Caused by: java.io.FileNotFoundException: D:\Dev\libs\external\dtds\xhtml1-
20020801\DTD\xhtml1-strict.dtd (The system cannot find the path specified)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at java.io.FileInputStream.<init>(FileInputStream.java:66)
        at sun.net.www.protocol.file.FileURLConnection.connect
(FileURLConnection.java:70)
        at sun.net.www.protocol.file.FileURLConnection.getInputStream
(FileURLConnection.java:161)
        at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity
(XMLEntityManager.java:973)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
(XMLEntityManager.java:905)
        at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
(XMLEntityManager.java:843)
        at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.startPE
(XMLDTDScannerImpl.java:686)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.skipSeparator
(XMLDTDScannerImpl.java:2065)
        at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls
(XMLDTDScannerImpl.java:2027)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExternalSubset
(XMLDTDScannerImpl.java:319)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dis
patch(XMLDocumentScannerImpl.java:1030)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocum
ent(XMLDocumentFragmentScannerImpl.java:368)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
(XML11Configuration.java:834)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
(XML11Configuration.java:764)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
(XMLParser.java:148)
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse
(DOMParser.java:250)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse
(DocumentBuilderImpl.java:292)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
        at org.netbeans.nbbuild.Arch.execute(Arch.java:138)
        ... 11 more
Comment 2 Jaroslav Tulach 2005-09-15 15:52:17 UTC 
I can think only of writing EntityResolver. It will help with arch.dtd, but 
not with the xhtml problem. Jesse what is your suggestion?
Comment 3 Jesse Glick 2005-09-15 18:43:32 UTC 
Could use a web location for the DTD, I guess.

Probably should be marked for 'future'.

Isn't this a dupe, BTW?
Comment 4 pzajac 2005-09-19 12:31:37 UTC 
Yes it is duplicate ..
Comment 5 pzajac 2005-09-19 12:33:06 UTC 

*** This issue has been marked as a duplicate of 61231 ***
Comment 6 Tomas Danek 2005-11-04 13:01:30 UTC 
yes, ver. dup./closed