[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2776:
-------------------------------------------
[~ldimaggio] this issue was waiting on QE ack - I took the liberty to set it to + since this is done and implemented. marking as resolved.
> Support quickstarts in OpenShift UI
> -----------------------------------
>
> Key: JBDS-2776
> URL: https://issues.jboss.org/browse/JBDS-2776
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.CR1
>
> Attachments: new-application-2.png
>
>
> OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI:
> !new-application-2.png!
> JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2776:
-----------------------------
CDW release: + (was: ?)
> Support quickstarts in OpenShift UI
> -----------------------------------
>
> Key: JBDS-2776
> URL: https://issues.jboss.org/browse/JBDS-2776
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
> Attachments: new-application-2.png
>
>
> OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI:
> !new-application-2.png!
> JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2840) Java 8
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2840?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-2840.
---------------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.GA)
Resolution: Done
all is done on dev side of this. resolving.
> Java 8
> ------
>
> Key: JBDS-2840
> URL: https://issues.jboss.org/browse/JBDS-2840
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, upstream
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Support for Java 8
> - The IDE running with Java 8 on all OS platforms
> - The capabilities in Eclipse Luna for code editing/support
> - EAP 6.3 with Java 8 (start, stop,deploy, debug, etc)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2838) OpenShift Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-2838.
---------------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.GA)
Resolution: Done
majority of this is now done.
quickstarts, menus and overall push/git workflow streamlined.
rest should be open as specific issues.
> OpenShift Usability
> -------------------
>
> Key: JBDS-2838
> URL: https://issues.jboss.org/browse/JBDS-2838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-293:
-------------------------------------------
The fix needed in spring IDE was to remove the Require-Bundle dependency on org.eclipse.core.runtime on the bundles that used javax and use Import-package instead (as far as I understood) - so thats worth a try. Problem is that these bundles seem to be runtime jars and not eclipse plugins we more easily can fix.
Maybe these jars are not needed anymore - [~lhein] thats for you to look at.
>From conversation with Martin in case these might match fuseide cases:
[16/07/14 09:58:39] Martin Lippert: regarding the javax stuff
[16/07/14 09:58:51] Martin Lippert: you need to take care of the package-use constraints as well
[16/07/14 09:59:22] Martin Lippert: if you are looking for the require-bundle dependencies in org.eclipse.core.runtime in combination with javax usages
[16/07/14 10:00:03] Martin Lippert: the org.springframework.web bundle was involved here in our case only because it imports javax stuff and has a package-use constraint defined for one of the packages that it exports
[16/07/14 10:00:08] Martin Lippert: and that we import somewhere else
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-293:
-------------------------------------------
The best description of this issue is at https://bugs.eclipse.org/bugs/show_bug.cgi?id=430458
and https://issues.jboss.org/browse/JBDS-2956
And this mail thread on equionox-dev: https://dev.eclipse.org/mhonarc/lists/equinox-dev/msg07755.html
I dont have time to digg into the full source at the moment but if you can isolate the plugins that causes it I suggest starting a thread on equinox-dev if there is an issue.
Also maybe [~snjeza] have an idea what root cause/fix is.
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17992) Show Tern Modules configuration under different preferences category
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17992?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17992:
----------------------------------------
Priority: Critical (was: Major)
> Show Tern Modules configuration under different preferences category
> --------------------------------------------------------------------
>
> Key: JBIDE-17992
> URL: https://issues.jboss.org/browse/JBIDE-17992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences.
> Should be possible by creating new category and assigning tern modules preference page class to it.
> Should test if it works with both original and new category visible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17889) Provide AngularJS Eclipse IDE through JBoss Central Early Access
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17889?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17889:
----------------------------------------
Priority: Blocker (was: Major)
> Provide AngularJS Eclipse IDE through JBoss Central Early Access
> ----------------------------------------------------------------
>
> Key: JBIDE-17889
> URL: https://issues.jboss.org/browse/JBIDE-17889
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> AngularJS Eclipse IDE have no frozen API to depend on, so we have to lock version avoid installation/update to newest version from external update. We also should make sure it works with tern bundles included into JBossTools target platform.
> Proposed name for new Feature/Bundle is org.jboss.tools.jst.angularjs.editor'.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18012) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18012?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18012:
--------------------------------------
Assignee: Daniel Azarov (was: Alexey Kazakov)
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [JST]
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18012
> URL: https://issues.jboss.org/browse/JBIDE-18012
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Daniel Azarov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [JST]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months