October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3553: -------------------------------------- > substring completion is just one of many, right? > Can someone outline the features we get beyond it ? Yes. There are: - % of most used calls for: Call Completion, Constructor Completion, Override Completion - Subtypes Completion (disabled by default) - Subwords Completion - Chain Completion (e.g. getA().foo().setB().doSomeOtherStuff() etc.) - Adaptive Template Completion (inserts group of methods) - Mylyn Completion The full list of features is here: https://www.eclipse.org/recommenders/manual/ > last I checked the big feature of code recommenders was about showing the % of the likelihood of a completion being relevant for a given situation - afaik that only works for SWT/Eclipse platform code. Not for Java/JavaEE in general. Can anyone confirm ? That's true. Afaik you have to provide your own remote model if you want to extend it. For example Mars by default includes http://download.eclipse.org/recommenders/models/mars only. It's mostly about SWT stuff only. > The coderecommenders rely on a remote DB to be updated and I believe thre might also be data sent to coderecommenders or eclipse - is that part of the default code recommender suggested here ? if yes, how does that affect our online/offline story (if at all) ? Afaik Eclipse downloads the models listed in the model repositories view. So you probably should be online to download them. Don't know if you can pre-download them and include in the installation and use them as a cache. > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- I see that unzip area for all our recent builds seem empty. Since the zip gets to Nexus, it's not a Tycho issue, but a Nexus one. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ So the last time that we had successfully deployed to Nexus and the unzip plugin fired to create the unpacked site was on *Thu Nov 13 09:33:23 EST 2014* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... Not sure why deployment continues but unzipping does not. --- Found a way to push to Nexus snapshots using a classifier to define the BUILD_ALIAS... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... ends up with: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... instead of https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... However, there's nothing in the unzip area: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The issue I foresee with this approach is that there will not be a predictable URL for that zip, or the URL would still be the same, without the BUILD_ALIAS, still colliding in case we have same Maven versions on multiple branches. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21022: ----------------------------------- Assignee: Snjezana Peco > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 2:03 PM: -------------------------------------------------------------- Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308 was (Author: nickboldt): Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* [INFO] freemarker.site .................................... SUCCESS [ 4.587 s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21012 at 10/26/15 2:02 PM: -------------------------------------------------------------- Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Run locally: {code} mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_* [INFO] freemarker.site .................................... SUCCESS [ 4.587 s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ {code} Results: * site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar * site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308 was (Author: nickboldt): Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix. https://github.com/jbosstools/jbosstools-freemarker/pull/54 Next I need to see if this works in Jenkins/Nexus... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308 > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-508: ---------------------------------- Looks good! Did you also want to merge your content into the JBT 4.3.0.Final composite sites, so we have simpler URLs in ide-config.properties and fewer URLs showing up in Eclipse? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20764: ------------------------------------------ In a 1st batch we'll try to implement "oc rsync" for incremental deployment. The [PR|https://github.com/openshift/origin/pull/4787] for "oc rsync" unveils the details of the implementation. It's using rsync if the client OS is linux, *tar* on windows. An exemplary usage can be read here: https://github.com/openshift/origin/blob/master/docs/generated/oc_by_exam... > Create Server Adapter for OpenShift 3 applications > -------------------------------------------------- > > Key: JBIDE-20764 > URL: https://issues.jboss.org/browse/JBIDE-20764 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: server adapter wizard.bmml, server adapter wizard.png > > > get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed. > Server status= matching deployment pod status > Possible menus: > - Start/Stop > - Show Web Console > - Port Forwarding > - Stream logs > [~maxandersen] can you think of anything else? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015