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 242941 - PATH_TO_WF_SERVER\WildFly\bin\standalone.conf.bat | was unexpected at this time
Summary: PATH_TO_WF_SERVER\WildFly\bin\standalone.conf.bat | was unexpected at this time
Status: RESOLVED DUPLICATE of bug 242661
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.0
Hardware: PC Windows 8 x64
: P2 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-16 12:59 UTC by reshi
Modified: 2014-03-16 13:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description reshi 2014-03-16 12:59:06 UTC
Product Version = NetBeans IDE 8.0 RC1 (Build 201402242200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_51
Runtime = Java HotSpot(TM) 64-Bit Server VM 24.51-b03

I've made a pure installation of NetBeans 8.0 RC1 on Windows 8 x64. Downloaded NetBeans plugin WildFly ApplicationServer version 1.0.10 from source 1393606785_org-netbeans-modules-javaee-wildfly.nbm . Then I downloaded from official JBoss WildFly site WildFly application server 8.0.0 Final. When I tried to run it I got following error:

standalone.conf.bat  
| was unexpected at this time

I was able to resolve this issue by disabling the usage of IDE proxy settings. (click services -> servers -> WildFly Application Server then right-click choose properties, choose platform in tab panel and uncheck the checkbox Use IDE proxy settings).
Comment 1 reshi 2014-03-16 13:01:24 UTC
I forgot to include my java version: 1.7.0 update 51.
Comment 2 ehsavoie 2014-03-16 13:39:24 UTC
You're proxy configuration is in the way.
Either remove proxy config at the netbeans level or use the version 1.0.10  of the plugin (which is available from  the dev update center).

*** This bug has been marked as a duplicate of bug 242661 ***