[JBoss JIRA] (JBTIS-598) Cannot install JBTIS in offline mode
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-598?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-598:
----------------------------------
Hey [~apodhrad]
If I do what you did I fail installing jbosstools-4.3.1.Beta2-updatesite-core with org.eclipse.jetty.websocket.api being not found. This does work for me:
This works for me:
0. Start with: eclipse-jee-mars-2-linux-gtk-x86_64.tar.gz
1. jbosstoolstarget-4.52.0.Beta2-SNAPSHOT.zip
2. jbosstools-4.3.1.Beta2-updatesite-core.zip
3. jbosstools-integration-stack-target-4.3.1.Beta1b-earlyaccess.zip # changed the name
4. jbosstools-integration-stack-4.3.0.Beta1-earlyaccess.zip
Does this work for you?
> Cannot install JBTIS in offline mode
> ------------------------------------
>
> Key: JBTIS-598
> URL: https://issues.jboss.org/browse/JBTIS-598
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Beta1
> Environment: Eclipse Mars-2 for JEE developers
> jbosstools-4.3.1.Beta2-updatesite-core.zip
> jbosstools-integration-stack-4.3.0.Beta1-earlyaccess.zip
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 4.3.0.CR1
>
>
> {code}
> Missing requirement: org.eclipse.bpmn2.modeler.core 1.2.3.Final-v20160226-1723-B97 requires 'bundle org.eclipse.emf.transaction 0.0.0' but it could not be found
> Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.jboss.tools.locus.sf.saxon [9.5.1,10.0.0)' but it could not be found
> Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.emf.compare.feature.group 2.1.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-608) Camel route viewer support for Java DSL
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-608?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-608:
--------------------------------------
I created a feature request jira on the FUSETOOLS project. This task is a rather complex one so it could take some time.
Meanwhile you can always launch the Java Context locally on your machine via "mvn camel:run" and then connect to the JMX process. In there you can edit the context running on your machine. That will basically give an XML export of your Java context which is then viewable in the editor.
> Camel route viewer support for Java DSL
> ----------------------------------------
>
> Key: JBTIS-608
> URL: https://issues.jboss.org/browse/JBTIS-608
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: Fuse IDE
> Affects Versions: 9.0.0.Beta1
> Reporter: Roger Hui
> Assignee: Lars Heinemann
>
> Currently, the fuse viewer can viewer and configure Camel route that are written in blueprint or spring XML. However, current there is no support for Java DSL.
> It would be nice to have the same viewer support for Java DSL. If not, a read only chart to demonstrate what the route looks like would be great.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-66) Create Identifier Completion Engine
by Ian Stewart-Binks (JIRA)
[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ]
Ian Stewart-Binks commented on ERT-66:
--------------------------------------
- Identifiers completion should also support CamelCase, i.e. if the identifier CamelCase exists and the user types in CC, CamelCase should be proposed.
- Identifiers that begin with an underscore should have a lower relevance than those that do not.
> Create Identifier Completion Engine
> -----------------------------------
>
> Key: ERT-66
> URL: https://issues.jboss.org/browse/ERT-66
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21970) Allow user to turn on/off showing console when output changes
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21970?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-21970.
-----------------------------------
Resolution: Done
Marking as resolved since [~rob.stryker] also cherry-picked the changes on the {{master}} branch of {{jbosstools-server}}.
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21970
> URL: https://issues.jboss.org/browse/JBIDE-21970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21625:
---------------------------------------
Trying the patch here: I get a bunch of errors as below:
{{code}}
!ENTRY org.eclipse.jdt.debug 4 125 2016-03-24 18:13:45.137
!MESSAGE Internal error logged from JDI Debug:
!STACK 0
org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 665.
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:187)
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:198)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:192)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:227)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:243)
at org.eclipse.jdi.internal.ThreadReferenceImpl.isSuspended(ThreadReferenceImpl.java:327)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.initialize(JDIThread.java:352)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.<init>(JDIThread.java:269)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.newThread(JDIDebugTarget.java:573)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createThread(JDIDebugTarget.java:549)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget$ThreadStartHandler.handleEvent(JDIDebugTarget.java:2012)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:152)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:100)
at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{{code}}
but then it finally worked !
I suspect that the error message occurred while the EAP server running on the pod was still starting (after the new triggered by the tooling to enable debugging).
> Server adapter: Enable debug mode on OpenShift servers
> ------------------------------------------------------
>
> Key: JBIDE-21625
> URL: https://issues.jboss.org/browse/JBIDE-21625
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21970) Allow user to turn on/off showing console when output changes
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21970?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21970:
---------------------------------------
cherry-picked the commit for {{jbosstools-openshift}} repo from {{jbosstools-4.3.x}} branch into {{master}} branch.
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21970
> URL: https://issues.jboss.org/browse/JBIDE-21970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21969:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21969
> URL: https://issues.jboss.org/browse/JBIDE-21969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21949:
----------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21949
> URL: https://issues.jboss.org/browse/JBIDE-21949
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years