[JBoss JIRA] (JBIDE-19747) IllegalArgumentException when creating new batch job xml file
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19747?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19747.
-----------------------------------
Verified JBDS 9.0.0.beta1
> IllegalArgumentException when creating new batch job xml file
> -------------------------------------------------------------
>
> Key: JBIDE-19747
> URL: https://issues.jboss.org/browse/JBIDE-19747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta1
>
>
> 1. File->New->Batch->Job XML File
> 2. Click on any project (root folder):
> {code}
> java.lang.IllegalArgumentException: Path must include project and resource name: /BatchTestProject
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069)
> at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201)
> at org.jboss.tools.batch.ui.internal.wizard.NewJobXMLCreationWizard$WizardNewBeansXMLFileCreationPage.validatePage(NewJobXMLCreationWizard.java:367)
> at org.eclipse.ui.dialogs.WizardNewFileCreationPage.handleEvent(WizardNewFileCreationPage.java:687)
> at org.eclipse.ui.internal.ide.misc.ResourceAndContainerGroup.handleEvent(ResourceAndContainerGroup.java:369)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2560)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2486)
> at org.eclipse.ui.internal.ide.misc.ContainerSelectionGroup.containerSelectionChanged(ContainerSelectionGroup.java:190)
> at org.eclipse.ui.internal.ide.misc.ContainerSelectionGroup$1.selectionChanged(ContainerSelectionGroup.java:277)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19947:
------------------------------------------
[~deshuai] [~mlabuda] JBoss Tools now as a whole requires JDK8, there's no way around it. As for OpenShift there's no way around jdk8 either since the bundle org.jboss.tools.foundation.core it relies on requires jdk8 propagating the requirement up the tree.
The only question that remains for me is how we'd prevent users using jdk7 from updating. [~nickboldt] any ideas?
> OpenShift v3 plugin can't work after update
> -------------------------------------------
>
> Key: JBIDE-19947
> URL: https://issues.jboss.org/browse/JBIDE-19947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Ma Deshuai
> Attachments: error1.jpg, error2.jpg, error3.jpg
>
>
> Description of problem:
> After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse.
> Version-Release number of selected component (if applicable):
> Eclipse: mars
> Jdk: 1.7
> OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825
> How reproducible:
> Always
> Steps to Reproduce:
> 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/
> 2.Restart eclipse and open "OpenShift Explorer"
> Actual results:
> 2.Open "OpenShift Explorer" with error
> Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView
> Expected results:
> 2.Open "OpenShift Explorer" corectly
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-19971:
-------------------------------------
Summary: OSE v2 prompts user to enter kerberos credentials from command line while importing an application
Key: JBIDE-19971
URL: https://issues.jboss.org/browse/JBIDE-19971
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Priority: Blocker
Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
Prompt from CLI looks like:
Kerberos username [mlabuda]:
Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19970) Unable to download products (EAP, ...)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-19970:
----------------------------------
Summary: Unable to download products (EAP, ...)
Key: JBIDE-19970
URL: https://issues.jboss.org/browse/JBIDE-19970
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.3.0.Beta1
Reporter: Radim Hopp
Priority: Critical
It's impossible to download products via download runtime wizard.
It tries to download it but after few seconds error dialog just flashes and no error in error log is recorded.
After capturing the process on video and pausing it when the error dialog pops up, I figured it says that the downloaded file is not properly formated zip file.
The file it downloads just contains html page:
{noformat:title=➜ ~ cat temp/jboss-eap-6.4.0.GA.zip }
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>JBoss Community</title>
<style type="text/css">
body {
margin: 230px 0 0 0;
text-align: center;
font-family: 'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
font-size:15px;
background: #e6e7e8 url(http://design.jboss.org/jbossorg/code/jbossorg_3_0/images/errorbkg.png) no-repeat top center;
}
.wrappper {
width:600px;
margin: auto;
text-align: left;
line-height: 20px;
}
h2 {
color:#424242;
display:block;
font-family:Myriad Pro,Helvetica,Arial,sans-serif;
font-size:25px;
font-weight:normal;
letter-spacing:-0.03em;
margin-top:5px;
}
</style>
</head>
<body>
<div class="wrappper" >
<h2>Cookies disabled</h2>
<p>The download requires cookies to be enabled in your web browser.</p>
<p>Please, enable cookies and reload the page.</p>
</div>
</body>
</html>
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19951:
---------------------------------------
Beta1x branch has been created here:
https://github.com/jbosstools/jbosstools-integration-tests/tree/jbosstool...
PR to move master to 4.3.0.Beta2-SNAPSHOT parent pom is here:
https://github.com/jbosstools/jbosstools-integration-tests/pull/997
[~nickboldt] do you think I also need to upversion our plugins now? In the past we only did it when we moved to the next version of JBoss Tools, e.g. from 4.2.x to 4.3.x. Please let me know.
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-19951
> URL: https://issues.jboss.org/browse/JBIDE-19951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18974) Latest Ionic app based on tabs template is not shown on HTM5 Preview
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18974?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18974.
-------------------------------
Verified with JBDS 9.0.0.Beta1-v20150605-2014-B34
> Latest Ionic app based on tabs template is not shown on HTM5 Preview
> --------------------------------------------------------------------
>
> Key: JBIDE-18974
> URL: https://issues.jboss.org/browse/JBIDE-18974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Fedora 20 Linux x86_64
> OpenJDK 7
> SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta1
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot1.png, screenshot2.png
>
>
> The app works fine in internal browser, bit not in HTML5 Preview (see image screenshot1.png below).
> The same issue when I open external browser form preview. But after a while Refresh in external browser finally shows the page (see screenshot2.png below).
> After that it appears in preview as well.
> !screenshot1.png!
> !screenshot2.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
){kind=link}