[JBoss JIRA] (JBIDE-13217) Execute permissions modified in new openshift projects causing action hoooks to not execute
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13217:
-------------------------------------------
Summary: Execute permissions modified in new openshift projects causing action hoooks to not execute
Key: JBIDE-13217
URL: https://issues.jboss.org/browse/JBIDE-13217
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Environment:
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Create and import new app - action_hooks x permissions gets reset.
iff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
causing /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
Failed to start jbossas-7
...but the server is started.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBIDE-13204) Download runtime for EAP gives NPE
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13204:
-------------------------------------------
Summary: Download runtime for EAP gives NPE
Key: JBIDE-13204
URL: https://issues.jboss.org/browse/JBIDE-13204
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Environment:
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
New EAP 6.0 server
Click download & install - nothing happens.
in error log:
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.runtime.DownloadRuntimeToWTPRuntime.getDownloadRuntimes(DownloadRuntimeToWTPRuntime.java:59)
at org.jboss.ide.eclipse.as.core.runtime.DownloadRuntimeToWTPRuntime.getDownloadRuntimes(DownloadRuntimeToWTPRuntime.java:45)
at org.jboss.ide.eclipse.as.ui.wizards.JBossASDownloadRuntimeFilter.accepts(JBossASDownloadRuntimeFilter.java:16)
at org.jboss.tools.runtime.ui.download.DownloadRuntimeViewerDialog.<init>(DownloadRuntimeViewerDialog.java:81)
at org.jboss.tools.runtime.ui.download.DownloadRuntimes.execute(DownloadRuntimes.java:26)
at org.jboss.ide.eclipse.as.ui.wizards.JBossRuntimeWizardFragment$DownloadAndInstallListener.widgetSelected(JBossRuntimeWizardFragment.java:381)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1531)
at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5807)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1093)
at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1085)
at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2538)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5493)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5557)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5002)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5151)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3616)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.wst.server.ui.internal.cnf.ServersView2$1.widgetSelected(ServersView2.java:116)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1531)
at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5807)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1093)
at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1085)
at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2538)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5493)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5557)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5002)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5151)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3616)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBIDE-12915) Kitchensink quickstart is missing .cheatsheet.xml
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-12915:
----------------------------------
Summary: Kitchensink quickstart is missing .cheatsheet.xml
Key: JBIDE-12915
URL: https://issues.jboss.org/browse/JBIDE-12915
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.0.0.Beta1
Reporter: Radim Hopp
Assignee: Snjezana Peco
Fix For: 4.0.0.CR1
After importing Kitchensink example from section "JBoss Developer Framework Quickstarts" in JBoss Central, user is prompted to
{noformat}Show '/jboss-as-kitchensink/.cheatsheet.xml' for further instructions{noformat}
but /jboss-as-kitchensink/.cheatsheet.xml does not exist.
Imported quickstart is named "kitchensink" instead of jboss-as-kitchensink and it has README.md instead of .cheatsheet.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBDS-2345) Create a JBDS parent pom
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2345:
------------------------------------
Summary: Create a JBDS parent pom
Key: JBDS-2345
URL: https://issues.jboss.org/browse/JBDS-2345
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Build
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 6.0.0.Beta1
Having a JBDS parent pom would be very comfortable. It would inherit from JBT parent pom, but would override some properties (such as local.site) and target-platform definitions.
This is currently done in configuration in Jenkins, so it requires lots of parameters to build. Having a parent pom would allow to build JBDS with the same required parameters as JBT.
It would also help to make the JBT parent pom cleaner: a lot of complexity in JBT parent pom comes from the fact that we want to be able to override everything since we use it for multiple purposes (JBT & JBDS).
A parent pom would move this complexity to another file (JBDS parent), and won't pollute JBT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBIDE-12551) Reset button in Convert to maven dependencies wizard is behaving weird
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-12551:
----------------------------------------
Summary: Reset button in Convert to maven dependencies wizard is behaving weird
Key: JBIDE-12551
URL: https://issues.jboss.org/browse/JBIDE-12551
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Alpha1
Reporter: Rastislav Wagner
Assignee: Fred Bricon
Fix For: 4.0.0.Alpha2
If I press Reset button in Convert to maven dependencies wizard during dependencies lookup then the status of already found dependencies is reset to "Unidentified dependency" and wizard continues in lookup but it wont bother with "reseted" dependencies anymore.
Another case: When lookup ends and then I press Reset button, status of all dependencies is changet to "Unidentified dependency" and lookup is not restarted. Then no dependencies are added to pom.xml
I would expect that pressing Reset button resets dependencies lookup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months