Recent changes to issues

#20 Build failed out of the box

Nils Cordes — Sun, 10 Apr 2016 12:39:12 -0000

status: open --> accepted
assigned_to: Nils Cordes

Build failed out of the box

Jeff Rancier — Sun, 10 Apr 2016 00:47:00 -0000

Ticket 20 has been modified: Build failed out of the box
Edited By: Nils Cordes (cordbhkj)
Status updated: u'open' => u'accepted'
Owner updated: None => u'cordbhkj'

Build failed out of the box

Jeff Rancier — Sun, 10 Apr 2016 00:47:00 -0000

I created the project per the PDF instructions and can even build the sample. I tried to track down the properties file, but that was fruitless. Is this a dead project? I'm running:

Version: Mars.2 Release (4.5.2)

BUILD FAILED
C:\Users\Jeff Rancier\eclipse_workspace\DocBook\build.xml:7: Cannot find C:\Users\Jeff Rancier\eclipse_workspace\DocBook\${net.sourceforge.dep4e.resources}\ant\docbook_5-0.xml imported from C:\Users\Jeff Rancier\eclipse_workspace\DocBook\build.xml

Call build.xml from Java code

liu xue — Sat, 17 Oct 2015 21:08:36 -0000

Hello,

I would like to call build.xml file from a Java program. I am new Ant user. I found a sample code below:

        File buildFile = new File("build.xml");
        Project p = new Project();
        p.setUserProperty("ant.file", buildFile.getAbsolutePath());
        DefaultLogger consoleLogger = new DefaultLogger();
        consoleLogger.setErrorPrintStream(System.err);
        consoleLogger.setOutputPrintStream(System.out);
        consoleLogger.setMessageOutputLevel(Project.MSG_INFO);
        p.addBuildListener(consoleLogger);

        try {
            p.fireBuildStarted();
            p.init();
            ProjectHelper helper = ProjectHelper.getProjectHelper();
            p.addReference("ant.projectHelper", helper);
            helper.parse(p, buildFile);
            p.executeTarget(p.getDefaultTarget());
            p.fireBuildFinished(null);
        } catch (BuildException e) {
            p.fireBuildFinished(e);
        }

But it gives me an error message as

BUILD FAILED
F:\workspace\Eclipse-Playground\de.itesys.xslt.docbook\build.xml:7: Cannot find F:\workspace\Eclipse-Playground\de.itesys.xslt.docbook\${net.sourceforge.dep4e.resources}\ant\docbook_5-0.xml imported from F:\workspace\Eclipse-Playground\de.itesys.xslt.docbook\build.xml

Total time: 0 seconds

Therefore I would like to know what is the right way to call build.xml file. Thank you.
In the attachment you can find an example project from DEP4E.

#18 New Docbook 5.0 File wizard fails to open when used in a git shared Docbook project.

Thierry MASSON — Thu, 15 Oct 2015 21:29:06 -0000

Ok, been playing with source code a bit tonight, and the bug does not occur with the latest source.

Some defensive code:

fileLocation = "";

has been added to NewDocBook50FileWizardPage#init method and the IllegalArgumentException is not raised anymore.

Issue can be closed, sorry for the noise :s, my bad.

Regards,

Thierry MASSON

New Docbook 5.0 File wizard fails to open when used in a git shared Docbook project.

Thierry MASSON — Thu, 15 Oct 2015 12:45:09 -0000

Downloaded dep4e from marketplace (2014.8.0 version) and started to use it (tested on Luna, eclipse.buildId=4.4.1.M20140925-0400, java.version=1.8.0_25, win 7 x64)

I shared my Docbook project on git (because our documentation project is large enough to involve some team work). By sharing the project on git, the project location is NOT located in the current workspace anymore (points at my local git working directory).

Since this move, the New Docbook file 5.0 file wizard does not work anymore on this project (the dialog is not showing).

Exception stacktrace follows :
java.lang.IllegalArgumentException: Argument cannot be null
at org.eclipse.swt.SWT.error(SWT.java:4422)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
at org.eclipse.swt.widgets.Text.setText(Text.java:2249)
at net.sourceforge.dep4e.plugin.perspective.docbook.wizards.NewDocBook50FileWizardPage.initContents(NewDocBook50FileWizardPage.java:157)
at net.sourceforge.dep4e.plugin.perspective.docbook.wizards.NewDocBook50FileWizardPage.createControl(NewDocBook50FileWizardPage.java:118)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:178)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:759)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:622)
at org.eclipse.jface.window.Window.create(Window.java:435)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:123)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
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.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

Regards,

Thierry MASSON

#3 xi:include is tagged as error on validate

Nils Cordes — Sat, 02 May 2015 18:45:03 -0000

The DocBook V5.0 schema distribution does not contain the file "xi.xsd". To fix it the missing file was added and the xml catalog contribution was reworked.
This fix will become part of the next release.

#14 Validate against a folder - not listing which XML file has errors

Nils Cordes — Sat, 02 May 2015 18:44:24 -0000

It seems that the indication of warnings and errors does not work correctly in the view "Navigator".
To fix it the perspective DEP4E was changed to use the view "Project Explorer" instead of the view "Navigator" by default.
This fix will become part of the next release.

#16 [FEATURE REQUEST] Make dep4e resources available for command-line builds

sdruskat — Mon, 27 Apr 2015 20:35:36 -0000

Great news! Can you make an approximate prediction when the new release will be available? Thanks!

#14 Validate against a folder - not listing which XML file has errors

Nils Cordes — Mon, 27 Apr 2015 18:17:31 -0000

assigned_to: Nils Cordes