Getting ErrorID=-1 Publish skipped: No destination selected

[bwait]

Hi

Anyone know what might be causing this error? It is happening for HTML5 and PDF outputs. Below is the PDF example, the the HTML5 looks the same. We are building from a shell script using the command line interface.

The main project is using Target subfolders: Projects/Targets/Mobile-Targets/*
We are building only, not publishing to FTP or anything. The Targets do not enable Publishing - That is, in the target UI, Publishing > Destination > Publish is not checked.

Command:
MadCap Flare V9/Flare.app/madbuild.exe -project "gnsdk-all.flprj" -target "Mobile-Targets/OO-MobileDocsAndroidPDF" -log true

Output:
The output is being created and is written to gnsdk-all\Output\$USER$\Mobile-Targets\OO-MobileDocsAndroidPDF\GNSDK-for-Mobile-Android-Developers-Guide.pdf

However, we get this error message:

<LogEntry File="" Message="Publish skipped: No destination selected.
" LineIndex="-1" CharIndex="-1" Target="OO-MobileDocsAndroidPDF" ErrorID="-1" />

Ideas???

Thanks
-Brad

[LTinker68]

Is that error stopping anything? When you build using Flare, it will generate errors and warnings, but the warnings also appear on the Errors tab. I wonder if the ErrorID="-1" is how madbuild differentiates a warning from a real, full-stop error? I get warnings all the time because I have email addresses that aren't a standard format because it's a closed system and the email addresses aren't the standard public addresses. For example, an email address may appear as john.doe@abc.local. Every time I build my target (via the GUI, not madbuild), Flare displays a warning that the email address is not valid, but it doesn't stop the build. Try throwing in a weird email like that in a topic and build via madbuild and see if that email address throws a ErrorID="-1" message. If it does, then you know that line in the error log is a warning, and not a real OMG error.

[bwait]

Is that error stopping anything? When you build using Flare, it will generate errors and warnings, but the warnings also appear on the Errors tab. I wonder if the ErrorID="-1" is how madbuild differentiates a warning from a real, full-stop error? I get warnings all the time because I have email addresses that aren't a standard format because it's a closed system and the email addresses aren't the standard public addresses. For example, an email address may appear as john.doe@abc.local. Every time I build my target (via the GUI, not madbuild), Flare displays a warning that the email address is not valid, but it doesn't stop the build. Try throwing in a weird email like that in a topic and build via madbuild and see if that email address throws a ErrorID="-1" message. If it does, then you know that line in the error log is a warning, and not a real OMG error.

Thanks. I think you are right. The problem appears to be that the command-line build is attempting to "build and publish". But, since I had not set up any publish destinations or enabled publishing, it was giving a warning that looked like a more serious error. To test this, I set up and destination and enabled publishing, and the error went away. So, for now, we will ignore this error during our build process.

Does anyone know of a "build-only" command-line option, or a "don't publish" one?

Thanks
-Brad

[bwait]

Update on this command line publish error: MadCap should implement a -buildOnly command line option.

Problem: From my testing, running Flare from the command line automatically builds and publishes. There is no way from the command line to disable publishing. So, when you run a build process from the command line, you will get an error -1 Publish skipped if your Target did not specify a Destination.

Our process did not use the Publish/Destination feature because our build scripts publish the our software packages directly. The scripts copy the Flare output from the default /Output/<user>/<target-folder>/<target-name> to the package.

Workarounds: Set the build scripts to ignore the Flare error. Not a great solution. Or, implement the destinations feature and point your targets to them. This stops there error message, but of course publishes the two the destination and the default output folder. Not ideal in our case.

Conclusion: MadCap should implement a -buildOnly command line option.

[Msquared]

I use a batch target for building from the command line. This just means I can invoke MadBuild once, and specify the batch target that includes all the outputs for a particular product (I single source three different products from one set of content).

But one of the things you can do in a batch target is specify which targets you want to build, and which you want to publish. So you could create a single batch target, to build a single target (or more if you want), without publishing.