July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3484) Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3484?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3484: -------------------------------- Priority: Blocker (was: Major) > Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3484 > URL: https://issues.jboss.org/browse/JBDS-3484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Currently org.jboss.tools.jst.js.feature with bower integration available only from jbosstools aggregated p2 repository. > This is very desired feature for javascript development and should be included into into JBDS installer, BYOE feature and JBDS p2 repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3484) Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3484?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3484: -------------------------------- Fix Version/s: 9.0.0.Beta2 > Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3484 > URL: https://issues.jboss.org/browse/JBDS-3484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Currently org.jboss.tools.jst.js.feature with bower integration available only from jbosstools aggregated p2 repository. > This is very desired feature for javascript development and should be included into into JBDS installer, BYOE feature and JBDS p2 repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19963: --------------------------------------- released to 4.3.0.Beta2 branch > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19963: --------------------------------------- It should be in Beta2, because it is a blocker. > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20300) As a user I would like to hot deploy my application to shorten the development cycle

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20300: ------------------------------------- Summary: As a user I would like to hot deploy my application to shorten the development cycle Key: JBIDE-20300 URL: https://issues.jboss.org/browse/JBIDE-20300 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill As a developer, it would be nice to compile locally and sync the changes with an existing deployment of my application to shorten my code/test/deploy cycle. I'm not sure how feasible this is in v3. * There may be a way to copy changed files to a running pod, but these changes would be lost if the pod is bounced unless there is persistent storage * Where do the files get copied to? How do find this information out? An agreed location based on an annotation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill edited comment on JBIDE-19178 at 7/17/15 2:13 PM: ---------------------------------------------------------------- Conversation with [~maxandersen] suggested: * Modify current tree view to have limited depth ** Maybe service (route) -> pod which represents an application ** limited info in the tree view * Tabbed Properties view when you click on an 'app' ** Each tab is a resource type for a specific 'app' ** Maybe a properties tab view for projects or even connections that displays essentially what we show now for the raw view * Add a way to flip between current impl and new impl? Would we need this if we have the tabbed view design? was (Author: jcantrill): Conversation with [~maxandersen] suggested: * Modify current tree view to have limited depth ** Maybe service (route) -> pod which represents an application ** limited info in the tree view * Tabbed Properties view when you click on an 'app' ** Each tab is a resource type for a specific 'app' ** Maybe a properties tab view for projects or even connections that displays essentially what we show now for the raw view > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add logical view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19178: ---------------------------------- Summary: Explorer: Add logical view to OpenShift v3 explorer (was: Explorer: Add "Pipeline" view to OpenShift v3 explorer) > Explorer: Add logical view to OpenShift v3 explorer > --------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19178: --------------------------------------- Conversation with [~maxandersen] suggested: * Modify current tree view to have limited depth ** Maybe service (route) -> pod which represents an application ** limited info in the tree view * Tabbed Properties view when you click on an 'app' ** Each tab is a resource type for a specific 'app' ** Maybe a properties tab view for projects or even connections that displays essentially what we show now for the raw view > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20299) JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20299?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20299: ------------------------------- Summary: JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml (was: JBDS central discovery site contains jbosstools-directory.xml and devstudio-directory.xml) > JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20299 > URL: https://issues.jboss.org/browse/JBIDE-20299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Critical > > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > contains an extra jbosstools-directory.xml file (and an extra jbosstools-earlyaccess.properties file, too). > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 > [TXT] compositeContent.xml 17-Jul-2015 13:38 868 > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 > [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - > {code} > But the EA site does not: > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 1.1K > [TXT] compositeContent.xml 17-Jul-2015 13:38 1.1K > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [ ] devstudio-earlyaccess.properties 12-May-2015 23:22 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - {code} > So for some reason we're mixing JBT content into the JBDS Central Discovery site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20299) JBDS central discovery site contains jbosstools-directory.xml and devstudio-directory.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20299?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20299 at 7/17/15 1:54 PM: ------------------------------------------------------------- Similar problem... http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... {code} [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 [TXT] compositeContent.xml 17-Jul-2015 13:38 868 [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K [DIR] plugins/ 17-Jul-2015 13:38 - {code} yet the JBT Central Discovery site is fine. was (Author: nickboldt): Similar problem... http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... {code} [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 [TXT] compositeContent.xml 17-Jul-2015 13:38 868 [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K [DIR] plugins/ 17-Jul-2015 13:38 - {code} > JBDS central discovery site contains jbosstools-directory.xml and devstudio-directory.xml > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20299 > URL: https://issues.jboss.org/browse/JBIDE-20299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Critical > > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > contains an extra jbosstools-directory.xml file (and an extra jbosstools-earlyaccess.properties file, too). > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 > [TXT] compositeContent.xml 17-Jul-2015 13:38 868 > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 > [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - > {code} > But the EA site does not: > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 1.1K > [TXT] compositeContent.xml 17-Jul-2015 13:38 1.1K > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [ ] devstudio-earlyaccess.properties 12-May-2015 23:22 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - {code} > So for some reason we're mixing JBT content into the JBDS Central Discovery site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015