[JBoss JIRA] (JBIDE-21080) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21080:
----------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.Beta1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21286) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21286:
-------------------------------------
Summary: Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
Key: JBIDE-21286
URL: https://issues.jboss.org/browse/JBIDE-21286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Marián Labuda
Assignee: Fred Bricon
Priority: Minor
Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-20531:
---------------------------------------
Yeah, that's right. Maybe it is just my personal feeling that it looks strange. If you are ok with current UX, I can accept it.
> Expose additional service ports from deploy docker image wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-20531
> URL: https://issues.jboss.org/browse/JBIDE-20531
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: docker
> Fix For: 4.3.1.Beta1
>
> Attachments: Service and routing page.png, service port edit dialog.png
>
>
> Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image
> * Also only remove those which were added
> * Only reset those which are defaults
> * Edit via double click
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20508) Makes workflow to modify application based on OS v3 templates user friendly
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20508?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20508.
---------------------------------
Closing.
> Makes workflow to modify application based on OS v3 templates user friendly
> ---------------------------------------------------------------------------
>
> Key: JBIDE-20508
> URL: https://issues.jboss.org/browse/JBIDE-20508
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 4.3.1.Beta1
>
>
> Currently if user wants to modify an existing application based on a template with source code, user has to fork a repo containing source code, copy URL of a fork and paste it into template parameter SOURCE_CODE_URL. This is a bit unfriendly work flow from my point of view, because it requires several steps:
> 1) At first user has to know an URL of a source code for a template. Intuitively user would go through New Application Wizard to Template Parameters wizard page and check value of SOURCE_CODE_URL parameter.
> 2) Fork a repository containing source code - it requires switching to browser and go to the repository web page and fork repo.
> 3) Copy a URL of user's source code repo (its easier to use SSH url git@github.com:user/repo.git to avoid filling in credentials for a github account)
> plus importing an application, making changes, commit and push.
> Would it be possible to create a fork and use user specific URL automatically? E.g. show a dialog to enter github username and tooling would via git API fork the repo and put the user specific source code URL into wizard page as template parameter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21279) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21279?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-21279:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [Arquillian]
> --------------------------------------------------------
>
> Key: JBIDE-21279
> URL: https://issues.jboss.org/browse/JBIDE-21279
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Arquillian]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (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.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), 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.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 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 Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20747:
----------------------------------------
[~dgolovin]: Installation-tests using install-grinder are testing the p2 consistency of our target-platform, main update-site and Central. It doesn't check that things work well after installation, it just checks that things are installed. What it does and check is partly documented on the job page.
This kind of issue is made possible because p2 does not support the "capability" definition while resolving dependencies ( https://dev.eclipse.org/mhonarc/lists/p2-dev/msg05417.html ), so it can for example install org.eclipse.jetty.websocket.servlet without installing the bundle providing the necessary capability. Then loading jetty.websocket fails at runtime, and by consequence, everything that depends on it fails to load.
[~ldimaggio] You tried against current 4.3.1/9.1.0, right? This failure is about master
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-20747:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-20747:
-----------------------------------
Affects Version/s: 4.4.0.Alpha1
(was: 4.3.0.CR1)
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features.txt, plugins.txt
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-21202:
--------------------------------------
Assignee: Fred Bricon
> Central is stuck on "Loading JBoss Central" when offline
> --------------------------------------------------------
>
> Key: JBIDE-21202
> URL: https://issues.jboss.org/browse/JBIDE-21202
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.Beta2
>
>
> When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up:
> {noformat}
> Unable to open /resources/jbosstools-central-webpage.zip
> Can't find embedded central zip
> {noformat}
> even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system.
> In JBDS 9.0.0.GA Central can be loaded without issues when offline.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21233:
----------------------------------------
I believe our current approach with a composite to really control what is enabled for user at installation works fine and make the release-train specific URL useless. So overall, +1 for that change, although I didn't look into details.
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months