[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20904:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> automate publishing latest CI build to staging, then from staging to development (or stable)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20904
> URL: https://issues.jboss.org/browse/JBIDE-20904
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
>
> Suggestion:
> rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed.
> So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion.
> [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui...
> Examples of using a series of commands in parallel w/ a wait at the end:
> http://stackoverflow.com/questions/19543139/bash-script-processing-comman...
> {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code}
> echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $#
> {code}
> More discussion:
> {quote}
> [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions
> [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just:
> * add && after the 1st rsync in each loop
> * add & after the last one
> * put a wait after the last loop
> * give the big piece of code to procede directly to bash
> {quote}
> After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template.
> And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job.
> Scary, but much faster!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20845:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Unable to install breakpoint even if line number set to be generated
> --------------------------------------------------------------------
>
> Key: JBIDE-20845
> URL: https://issues.jboss.org/browse/JBIDE-20845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, upstream
> Affects Versions: 4.3.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha2
>
> Attachments: breakpoint-error.png, compiler-settings.png, html5-page.png, lineNumber.png
>
>
> I am unable to get breakpoints to work for a html5 project running on WildFly.
> I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error:
> Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes.
> Reason: Absent Line Number Information
> !breakpoint-error.png!
> I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has:
> org.eclipse.jdt.core.compiler.debug.lineNumber=generate
> This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same.
> I'm not really sure which component this should belong to, it looks like an upstream issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21384) Syntax errors reported on feedhenry.js file
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21384?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21384:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Syntax errors reported on feedhenry.js file
> -------------------------------------------
>
> Key: JBIDE-21384
> URL: https://issues.jboss.org/browse/JBIDE-21384
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.2.3.Final
> Environment: JBDS 9.0.0
> FeedHenry Cordova Light App with Ionic
> Mac OS X 10.11
> Reporter: Karel Piwko
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha2
>
> Attachments: feedhenry.js, Screen Shot 2015-12-23 at 19.00.36.png
>
>
> When a FeedHenry Cordova project is imported into JBDS, it reports 89 errors in JBDS in feedhenry.js file.
> {code}
> Description Resource Path Location Type
> Syntax error on token ":", = expected feedhenry.js /HelloCordova/www line 4099 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3475 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3499 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3512 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3694 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3752 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3906 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3916 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3958 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4030 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4042 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4063 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4076 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4213 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4274 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4777 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 8647 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10325 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10352 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10430 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10439 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10454 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10545 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10556 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10564 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10590 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3471 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3608 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3625 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3667 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3680 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3733 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3772 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3833 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3843 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3866 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4017 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4038 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4050 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4058 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4210 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4211 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4217 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4260 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4266 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4702 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4709 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4752 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4765 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6007 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6014 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6024 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6353 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10220 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10272 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10345 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10381 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10390 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10397 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10404 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10419 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10428 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10437 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10449 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3697 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3960 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4108 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4110 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4261 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4780 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 6354 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 8649 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10586 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "else BlockStatement" to complete IfStatement feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 1 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 3400 JavaScript Problem
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21201:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> TernError: No type found at the given position.
> -----------------------------------------------
>
> Key: JBIDE-21201
> URL: https://issues.jboss.org/browse/JBIDE-21201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: tern 1.1.0
> Reporter: Pavol Srna
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha2
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Click on 'user' text within <h:inputText> tag
> 4. Press F3 key
> {code}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21198:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> "Tern - Go to definition" hyperlink opens nothing
> -------------------------------------------------
>
> Key: JBIDE-21198
> URL: https://issues.jboss.org/browse/JBIDE-21198
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, jsp/jsf/xml/html-source-editing, upstream
> Affects Versions: 4.3.0.CR1
> Environment: JBDS 9.0.0.CR1-v20150912-1100-B100
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha2
>
>
> 1. Install AngularJS from JBoss Central (Enable Early Access)
> 2. Create JSF 1.2 Kick Start project
> 3. Open inputUserName.jsp in VPE
> 4. Click on 'user' text within <h:inputText> tag
> 5. Press F3 key
> ERROR: Nothing happened. User.java file should be opened in editor
> 6. Hover with mouse over the same text and push Ctrl key
> ASSERT: Menu with these tree actions appeared:
> * Tern - Go to definiton
> * Open User.java
> * Open 'User - demo'
> Action Open User.java opens User.java in editor
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21719:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21606:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Consider using java 8 for EAP 6.4 by default
> --------------------------------------------
>
> Key: JBIDE-21606
> URL: https://issues.jboss.org/browse/JBIDE-21606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha2
>
>
> Here's the problem that I just hit:
> I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime.
> Then on the project, I just Run -> Run on Server.
> The server started, but deployment failed on Unsupported version: 51.0
> Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6.
> So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months