May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.0.Alpha3 > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22305: ---------------------------------- Summary: automate process for fetching latest target platform mirrors Key: JBIDE-22305 URL: https://issues.jboss.org/browse/JBIDE-22305 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform, updatesite, upstream Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. Thus for webtools we might simply define: webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... and we'd end up with: http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3878) Devstudio shortcuts have outdated version in their names (again)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3878?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3878: ----------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Devstudio shortcuts have outdated version in their names (again) > ---------------------------------------------------------------- > > Key: JBDS-3878 > URL: https://issues.jboss.org/browse/JBDS-3878 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha2 > > > A while back we moved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3878) Devstudio shortcuts have outdated version in their names (again)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3878?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3878: ---------------------------------- Simpler PR: https://github.com/redhat-developer-tooling/developer-platform-install/pu... https://github.com/redhat-developer-tooling/developer-platform-install/pu... is still a reasonable approach but it's not working yet. > Devstudio shortcuts have outdated version in their names (again) > ---------------------------------------------------------------- > > Key: JBDS-3878 > URL: https://issues.jboss.org/browse/JBDS-3878 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha2 > > > A while back we moved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22177: --------------------------------------- @fbricon Adding a blocker to this issue that you discovered before. I don't know how this will affect other places where JBT consumes this code. Also, I don't know how to add this issue to the storyboard. Help me Obei`Fred... > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22177: --------------------------------------- Notes from my conversation with bparees regarding what 'oc new-app NAME' generally does. Note: openshift project matches docker username in a pullspec. User must have perms to this project in order to use image. ‘New-app’ roughly does the following given its arg: * Arg matches existing IS ** Ref existing IS * Arg matches image in public registry ** Create imagestream ref to arg * Arg matches only Image locally ** IS pointed to ref of image in project and need to push image to registry which means for JBT, since we are starting (potentially) with a local image and that image may or may not be pulled from a public registry should: # Check docker pull spec against project imagestreams and 'openshift' imagestreams and use that if there is a match # Create an IS to the pull spec with the 'username' modified to equal project name. inform user they need to push the image (until we can tag and push) and how. > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21408. ------------------------------- Since nobody seems to have experienced this since, I'm closing this. Unless [~mmalina] comes back from PTO and finds devstudio frozen again. > JBDS frozen and CPU at 100% after running overnight > --------------------------------------------------- > > Key: JBIDE-21408 > URL: https://issues.jboss.org/browse/JBIDE-21408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > Attachments: frozen_jbds_jstack.txt > > > Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure. > Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1772) Content Assist Issues (here will be found in 2.0.1 GA issues on content assist)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1772?page=com.atlassian.jira.plugin... ] Jan Richter closed JBIDE-1772. ------------------------------ Verified in 4.4.0.Alpha1. > Content Assist Issues (here will be found in 2.0.1 GA issues on content assist) > ------------------------------------------------------------------------------- > > Key: JBIDE-1772 > URL: https://issues.jboss.org/browse/JBIDE-1772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 2.0.1 > Reporter: Andrei Scherbovich > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > 2) After taglib declaration in jsp file if user enter "<" then moves the cursor before "<" and try to use content assist, it works not in proper way. Appears something like "f:actionListener type="" />/><" > 3) Not enough tags in content assist: > -- can't find <html> tag after taglib declaration in jsp file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-687) Update new project wizard tests for the new version of drools plugin

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-687?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-687. ----------------------------------- pushed to master > Update new project wizard tests for the new version of drools plugin > -------------------------------------------------------------------- > > Key: JBTIS-687 > URL: https://issues.jboss.org/browse/JBTIS-687 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: drools/ jBPM, QE > Affects Versions: 4.3.0.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-687) Update new project wizard tests for the new version of drools plugin

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-687?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-687: ------------------------------------ Affects Version/s: 4.3.0.Final > Update new project wizard tests for the new version of drools plugin > -------------------------------------------------------------------- > > Key: JBTIS-687 > URL: https://issues.jboss.org/browse/JBTIS-687 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: drools/ jBPM, QE > Affects Versions: 4.3.0.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016