In front of a blog "Eclipse newspaper" the builder launch configuration could not being found "error resolution" describes the Eclipse report "the Builder launch Configur Ation could not being found "solution, according to that approach, found no error, but ant automatic construction is gone. This is unacceptable.
It seems that escape is not a problem to solve. So it is not very good to think that the "launch" of the "Eclipse" of the builder could not being found "wrong solution".
This article will show you how to do without removing ant's Auto-build when Wowza plug-in development (because Wowza Eclipse plugin development is ANT-built!). ) to resolve the Eclipse Wowza plug-in report "The Builder launch configuration could not being found" error. For Wowza Eclipse IDE support please refer to the steps of Eclipse installation/update Wowza IDE plug-in, the development of Wowza plugin can refer to the blog "Development of the first Wowza server extension application using Wowza IDE-Monitor Live channel" 。
1. Follow the steps described in the "Error resolution" of the "Eclipse newspaper", the builder launch configuration could not being found, after the completion of the project Builders such as:
The Eclipse Wowza project now has no automatic build capability.
2. Under Navigator View, under Edit Project, under the. project file, under the Projectdescription tab, add the following:
<natures><nature>com.wowza.wms.eclipse.sdk.WowzaMediaServerProNature</nature><nature> Org.eclipse.jdt.core.javanature</nature></natures>
Then Save: Project If the originalNatures definition, Delete--Since the report "The builder launch configuration could not be found" error, certainly not. The saved. Project files are as follows:
<?xml version= "1.0" encoding= "UTF-8"?><projectdescription><name>cloud-rts</name>< Comment></comment><projects></projects><buildspec><buildcommand><name> org.eclipse.jdt.core.javabuilder</name><arguments></arguments></buildcommand></ Buildspec><natures><nature>com.wowza.wms.eclipse.sdk.wowzamediaserverpronature</nature> <nature>org.eclipse.jdt.core.javanature</nature></natures></projectDescription>
3. In the package Explorer view, right-click the project name, select Properties menu, left menu tree, click Builders, click New ... button, pop-up Choose Configuration Type dialog box
4. Select Ant Builder and click the OK button to eject the Edit Configuration dialog box
5. Name uses Eclipse to give default New_builder (of course you can also customize other), Main page item under BuildFile Click Browse Workspace ... button, select the Build.xml under your project and click the OK button
Base Directory under Main page item click Browse Workspace ... button, select your project name, then click the OK button
Finally, click the Apply and OK button in the Edit Configuration dialog box to save
Discover that Ant's auto-build is back and has successfully solved "the builder launch configuration could not being found" error:
6. Add auto to the ant triggers of the. project file. The author's. Project file ends up as follows:
<?xml version= "1.0" encoding= "UTF-8"?><projectdescription><name>cloud-rts</name>< Comment></comment><projects></projects><buildspec><buildcommand><name> org.eclipse.jdt.core.javabuilder</name><arguments></arguments></buildcommand>< Buildcommand><name>org.eclipse.ui.externaltools.externaltoolbuilder</name><triggers>auto, Full,incremental,</triggers><arguments><dictionary><key>launchconfighandle</key> <value><project>/.externaltoolbuilders/new_builder.launch</value></dictionary></ Arguments></buildcommand></buildspec><natures><nature> Com.wowza.wms.eclipse.sdk.wowzamediaserverpronature</nature><nature> Org.eclipse.jdt.core.javanature</nature></natures></projectdescription>
