[JBoss JIRA] (JBIDE-21839) Cannot connect to Karaf via JMX
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21839?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21839:
-------------------------------------
So generally, trying to gain JMX access to some processes that secure their JMX doesn't always work with the standard connectors or the local processes connectors. This is why we've added the category for servers: they usually are better at setting credentials, using the right (sometimes internal) API, and other details.
[~lhein] Can you verify this? What tasks does your Karaf server jmx connection perform that the standard one probably isn't doing?
> Cannot connect to Karaf via JMX
> -------------------------------
>
> Key: JBIDE-21839
> URL: https://issues.jboss.org/browse/JBIDE-21839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> Reporter: Tomáš Sedmík
> Assignee: Rob Stryker
> Attachments: out.ogv
>
>
> I'm unable to connect to Apache Karaf runtime via JMX Navigator --> Local Processes (see attached video)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19738:
--------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.x)
> Failed runtime download offers no error message
> -----------------------------------------------
>
> Key: JBIDE-19738
> URL: https://issues.jboss.org/browse/JBIDE-19738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.1.AM3
>
>
> While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22807:
-----------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.AM2)
> Could not install bundle. A bundle is already installed with the name xxx
> -------------------------------------------------------------------------
>
> Key: JBIDE-22807
> URL: https://issues.jboss.org/browse/JBIDE-22807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Environment: Fedora 24, x86_64
> devstudio:
> Version: 10.0.1.AM2
> Build id: AM2-v20160720-1632-B5674
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.1.AM3
>
>
> Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio)
> Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message).
> This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22855?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22855:
---------------------------------------
That would a field I would expect to be un-editable; from my experience there are many of these and the server silently ignores them. I assume its a conscience decision to error on fields only that do not pass the validations. Also, I believe their is a conscience decision to not be able to edit pod definitions at all unless (maybe) you are a cluster-admin. Pods are controlled by replication controllers and that is the mechanism by which pods are created. If you wish to change a pod, then you should be editing its replication controller/deployment config/deployment.
I don't think this is a bug and should be resolved as such.
> Editing pod's json - strange behavior
> -------------------------------------
>
> Key: JBIDE-22855
> URL: https://issues.jboss.org/browse/JBIDE-22855
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Dmitry Bocharov
> Priority: Minor
> Fix For: 4.4.x
>
> Attachments: editing_pod_json.webm
>
>
> It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
Okay - I can look at the progress bar later - can we get this first one pushed?
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBTIS-654:
-------------------------------------
It seems runtime install is not included into overall progress as for example EAP, primarily because we are not building installer with IzPack but just replacing and adding resources to DevStudio jar installer. Number of included packages stays the same as it was set during IzPack build. It is not critical for this issue IMO, can be fixed after we done with this one,
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-20512) Hitting enter next to an FTL constructs doesn't indent the line
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20512?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20512:
--------------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.x)
Assignee: Alexey Kazakov (was: Denis Golovin)
Resolution: Done
> Hitting enter next to an FTL constructs doesn't indent the line
> ---------------------------------------------------------------
>
> Key: JBIDE-20512
> URL: https://issues.jboss.org/browse/JBIDE-20512
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.AM3
>
>
> When hitting enter when the cursor only has plain text next to it, the newly started line copies its indentation as expected. But if the cursor is directly before or after an FTL construct ({{$\{x\}}}, {{<#assign x = 1>}}, etc.) then after hitting enter the indentation will be 0. The most common case of running into this is hitting enter after an indented newly entered FTL construct, as then you will have to indent manually before you start typing the next line.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22856) TP does not allow to run RedDeer UI tests
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22856:
----------------------------------
Summary: TP does not allow to run RedDeer UI tests
Key: JBIDE-22856
URL: https://issues.jboss.org/browse/JBIDE-22856
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 4.4.1.AM2
Reporter: Jeff MAURY
Fix For: 4.4.1.AM3
The TP does not allow to run RedDeer UI tests. When launching such a test, the following error is shown:
{code:shell}
!ENTRY org.eclipse.osgi 4 0 2016-07-29 16:46:32.581
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "org.jboss.reddeer.ui.reddeertestapplication" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.ant.ui.antRunner, org.eclipse.datatools.connectivity.console.profile.StorageFileEditor, org.eclipse.e4.ui.workbench.swt.E4Application, org.eclipse.e4.ui.workbench.swt.GenTopic, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.jdt.core.JavaIndexer, org.eclipse.pde.build.Build, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.legacytestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication, org.eclipse.swtbot.eclipse.core.swtbottestapplication, org.eclipse.ui.ide.workbench, org.eclipse.wst.jsdt.core.JavaCodeFormatter, org.eclipse.wst.server.preview.preview, org.eclipse.xsd.ecore.importer.XSD2GenModel.
at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months