facebook

ant build.xml has error File Not Found

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 11 posts - 16 through 26 (of 26 total)
  • Author
    Posts
  • #241007 Reply

    diamonddog
    Member

    Say how do i find a good book on learning myeclipse? one that would speed my learning curve?

    #241009 Reply

    Riyad Kalla
    Member

    Actually most everything is under our Documentation section here: http://www.myeclipseide.com/ContentExpress-display-ceid-67.html

    Also some visual tours of older versions are available in our Tutorials and Demos section: http://www.myeclipseide.com/ContentExpress-display-ceid-16.html

    Also don’t forget an excellent resource for many detailed tutorials here, they have been kind enough to base many of them around MYEclipse: http://www.laliluna.de/tutorials.html

    There isn’t a book persay that covers MyEclipse, but a few Eclipse books that have been published have briefly covered MyEclipse or given us a nod which has been great, but not an entire book just yet.

    #242611 Reply

    sofistek
    Participant

    @support-rkalla wrote:

    Keith,
    Close the files, open the properties for the build.xml file, mark it as Derived, click OK, then right click on the project and rebuild it. That should stop the validator from trying to validate it.

    I have the same problem; using an entity, pointing at an existing file, causes a “file not found” validation error, when there is no error. I can’t use the workaround mentioned since setting the Derived property disables all of the team functions, apart from Apply Patch.

    The build file works fine when running the ant build inside or outside of eclipse, so there is no actual problem with the file. This only shows up as a problem with MyEclipse, not with raw eclipse. Is a fix being worked on?

    (In my case, the entity points to a file that is in a directory parallel to the current directory – actually in another eclipse project. e.g. “file:../OtherProject/OtherFile.xml” – it is a valid and existing file. However, I’ve tried copying the included file to the same directory as the build file, and changing the entity definition accordingly; validation still comes up with an error.)

    Tony

    #242651 Reply

    sofistek
    Participant

    I was swayed by the actual validation error shown on the ant editor. Even though the validation claims that the file, pointed to by the entity, can’t be found, the editor has, in fact, found it and incorporated the properties contained in it. This can be seen from the build file outline view. (I have entities to define files that separate out common properties and targets for many build files.)

    As I say, the apparent validation error doesn’t show up in a plain vanilla version of eclipse (without myEclipse) but both that version and the one with myEclipse show an error in the log when starting the ant editor. I don’t know if this is connected with the problem. The error is:

    !ENTRY org.eclipse.ant.ui 4 120 2005-12-05 16:36:16.754
    !MESSAGE Error logged from Ant UI:
    !STACK 0
    org.eclipse.jface.text.BadLocationException
    at org.eclipse.jface.text.AbstractLineTracker.getLineDelimiter(AbstractLineTracker.java:350)
    at org.eclipse.jface.text.AbstractDocument.getLineDelimiter(AbstractDocument.java:807)
    at org.eclipse.ant.internal.ui.model.AntModel.getLastCharColumn(AntModel.java:1037)
    at org.eclipse.ant.internal.ui.model.AntModel.computeOffsetUsingPrefix(AntModel.java:1008)
    at org.eclipse.ant.internal.ui.model.AntModel.computeOffset(AntModel.java:997)
    at org.eclipse.ant.internal.ui.model.AntModel.addComment(AntModel.java:1436)
    at org.eclipse.ant.internal.ui.editor.utils.ProjectHelper$LexHandler.comment(ProjectHelper.java:475)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.comment(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.comment(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanComment(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.eclipse.ant.internal.ui.editor.utils.ProjectHelper.parse(ProjectHelper.java:568)
    at org.eclipse.ant.internal.ui.editor.utils.ProjectHelper.parse(ProjectHelper.java:642)
    at org.eclipse.ant.internal.ui.model.AntModel.parseDocument(AntModel.java:312)
    at org.eclipse.ant.internal.ui.model.AntModel.reconcile(AntModel.java:260)
    at org.eclipse.ant.internal.ui.model.AntModel.getProjectNode(AntModel.java:1378)
    at org.eclipse.ant.internal.ui.model.AntModel.getProjectNode(AntModel.java:1388)
    at org.eclipse.ant.internal.ui.editor.text.AntFoldingStructureProvider.updateFoldingRegions(AntFoldingStructureProvider.java:88)
    at org.eclipse.ant.internal.ui.editor.AntEditor.projectionEnabled(AntEditor.java:1355)
    at org.eclipse.jface.text.source.projection.ProjectionViewer.fireProjectionEnabled(ProjectionViewer.java:480)
    at org.eclipse.jface.text.source.projection.ProjectionViewer.enableProjection(ProjectionViewer.java:528)
    at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1418)
    at org.eclipse.ant.internal.ui.editor.AntEditor$StatusLineSourceViewer.doOperation(AntEditor.java:301)
    at org.eclipse.ant.internal.ui.editor.AntEditor.createPartControl(AntEditor.java:1096)
    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609)
    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552)
    at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:283)
    at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:126)
    at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
    at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
    at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:391)
    at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1102)
    at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1051)
    at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1256)
    at org.eclipse.ui.internal.PartStack.add(PartStack.java:442)
    at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:109)
    at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
    at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:212)
    at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:202)
    at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:758)
    at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:665)
    at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:628)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2360)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295)
    at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287)
    at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2249)
    at org.eclipse.ui.ide.IDE.openEditor(IDE.java:371)
    at org.eclipse.ui.ide.IDE.openEditor(IDE.java:334)
    at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:251)
    at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:131)
    at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
    at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:169)
    at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:153)
    at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:222)
    at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:198)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:296)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:869)
    at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:741)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
    at org.eclipse.core.runtime.Platform.run(Platform.java:783)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
    at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:739)
    at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:968)
    at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1067)
    at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:243)
    at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:238)
    at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:277)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
    at org.eclipse.core.launcher.Main.run(Main.java:973)
    at org.eclipse.core.launcher.Main.main(Main.java:948)

    It would sure be nice to get rid of the false indicator of a validation error, though it doesn’t seem to affect the functionality at all.

    Tony

    #242652 Reply

    Riyad Kalla
    Member

    Tony can you give us an example of the snippet of code you are using in your build file to reference the external XML? The reason this likely doesn’t happen with plain Eclipse is that Eclipse does not ship an XML validator, we do. So if our XML validator is running on the ant build file, it is barfing on the external entity reference which is a filed bug we have in our system.

    Additionally we have filed the ability to exclude specific files and directories from validation without using the dervied property. Both of these issues do not have an ETA yet, but both would help work around the erroneous errors you are seeing, sorry for the trouble in the interm.

    #242664 Reply

    sofistek
    Participant

    @support-rkalla wrote:

    Tony can you give us an example of the snippet of code you are using in your build file to reference the external XML?

    Here is a sample build file that causes the problem.

    <?xml version=”1.0″?>
    <!DOCTYPE project [
    <!ENTITY properties SYSTEM “file:../appBuild/properties.xml”>
    ]>
    <project name=”myProject” default=”all” basedir=”.”>

    <target name=”init”>
    <tstamp>
    <format property=”startTime” pattern=”dd-MM-yyyy hh:mm:ss aa” unit=”hour”/>
    </tstamp>
    <echo message=”started at ${startTime}”/>

    <property name=”appName” value=”${ant.project.name}”/>
    <property name=”war” value=”${appName}.war”/>
    <property name=”ear” value=”${appName}.ear”/>
    <property name=”jar” value=”${appName}.jar”/>

    &properties;

    <property file=”../appBuild/develop.properties”/>

    <mkdir dir=”${assemble.war}”/>
    <mkdir dir=”${assemble.ear}”/>
    <mkdir dir=”${assemble.jar}”/>
    <mkdir dir=”${assemble.wls.war}”/>

    </target>

    <!– And so on –>
    </project>

    Note that the file ../appBuild/properties.xml exists and is picked up by the Ant editor, with no problem. You’re right, it’s the XML validation that fails (I tried it as a normal XML file, not an Ant build file). It looks like this is a bug to me, so a work around is probably not appropriate.

    #242688 Reply

    Riyad Kalla
    Member

    Agreed, this is a bug. Validation is not honoring that relative path, although IIRC absolute paths should work. I am filing the issue now.

    NOTE: I just did some testing locally and it seems for me absolute paths are not working, can you get them to work on your end?

    #242720 Reply

    sofistek
    Participant

    @support-rkalla wrote:

    Agreed, this is a bug. Validation is not honoring that relative path, although IIRC absolute paths should work. I am filing the issue now.

    NOTE: I just did some testing locally and it seems for me absolute paths are not working, can you get them to work on your end?

    Thanks for that.

    Yes, I can confirm that absolute paths are fine, for me. I’m working on Windows and putting an absolute path in the entity definition got rid of the validation error. This is not a suitable workaround, of course, since the same project is loaded by different people who may have different directory locations.

    Tony

    #242722 Reply

    Riyad Kalla
    Member

    We understand Tony that this workaround is “crappy” at best, sorry for the inconvenience.

    #246631 Reply

    sofistek
    Participant

    Hi,

    I just wondered if a fix for this is close? I downloaded the latest release but still get the problem.

    Thanks,
    Tony

    #246648 Reply

    Riyad Kalla
    Member

    Tony,
    No work was done on this yet.

Viewing 11 posts - 16 through 26 (of 26 total)
Reply To: ant build.xml has error File Not Found

You must be logged in to post in the forum log in