July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20164) webtools server adapter installation UI is non-informative

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20164 at 7/2/15 11:13 AM: ------------------------------------------------------------- These three commits are in build B803, which is available here [1]. JBIDE-20164: https://github.com/jbosstools/jbosstools-server/commit/6ba6d30c6c10d8ec51... JBIDE-20173: https://github.com/jbosstools/jbosstools-server/commit/97df8fbf994ac0e88d... JBIDE-20170: https://github.com/jbosstools/jbosstools-server/commit/a4ce07ab623a48acc0... [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ or http://download.jboss.org/jbosstools/updates/nightly/mars/ So, I installed Eclipse 4.5, then opened this file: eclipse/plugins/org.eclipse.wst.server.discovery_1.0.701.v201505261810.jar!/serverAdapterSites.xml And changed this: {code} - <site url="http://download.jboss.org/jbosstools/updates/webtools/mars/"/> + <site url="http://download.jboss.org/jbosstools/updates/nightly/mars/"/> {code} So then: !install-jbossas-connector-from-nightly.png! And these features are freshly installed: {code} cd eclipse/features; find . -maxdepth 1 -mmin -10 | sort ./org.eclipse.jdt_3.11.0.v20150603-2000 ./org.eclipse.jst.web_core.feature_3.7.0.v201506041749 ./org.eclipse.jst.web_ui.feature_3.7.0.v201506041749 ./org.jboss.ide.eclipse.archives.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.archives.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.jmx.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.server.rse.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.archives.scanner.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.jmx.feature_1.7.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.runtime.core.feature_3.1.0.Beta2-v20150626-1605-B757 ./org.jboss.tools.stacks.core.feature_1.2.0.Beta2-v20150626-1605-B757 {code} was (Author: nickboldt): These three commits are in build B803, which is available here [1]. JBIDE-20164: https://github.com/jbosstools/jbosstools-server/commit/6ba6d30c6c10d8ec51... JBIDE-20173: https://github.com/jbosstools/jbosstools-server/commit/97df8fbf994ac0e88d... JBIDE-20170: https://github.com/jbosstools/jbosstools-server/commit/a4ce07ab623a48acc0... [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ or http://download.jboss.org/jbosstools/updates/nightly/mars/ So, I installed Eclipse 4.5, then opened this file: eclipse/plugins/org.eclipse.wst.server.discovery_1.0.701.v201505261810.jar!/serverAdapterSites.xml And changed this: - <site url="http://download.jboss.org/jbosstools/updates/webtools/mars/"/> + <site url="http://download.jboss.org/jbosstools/updates/nightly/mars/"/> So then: !install-jbossas-connector-from-nightly.png! And these features are freshly installed: {code} cd eclipse/features; find . -maxdepth 1 -mmin -10 | sort ./org.eclipse.jdt_3.11.0.v20150603-2000 ./org.eclipse.jst.web_core.feature_3.7.0.v201506041749 ./org.eclipse.jst.web_ui.feature_3.7.0.v201506041749 ./org.jboss.ide.eclipse.archives.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.archives.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.jmx.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.server.rse.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.archives.scanner.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.jmx.feature_1.7.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.runtime.core.feature_3.1.0.Beta2-v20150626-1605-B757 ./org.jboss.tools.stacks.core.feature_1.2.0.Beta2-v20150626-1605-B757 {code} > webtools server adapter installation UI is non-informative > ---------------------------------------------------------- > > Key: JBIDE-20164 > URL: https://issues.jboss.org/browse/JBIDE-20164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: install-jbossas-connector-from-nightly.png, Install_New_Extension_and_New_Server.png > > > When using the "download additional adapters" for JBoss Tools it has a few issues. > a) shows "null" for vendor > b) does not actually say it is for WildFly nor EAP servers > c) (idea) should we add OpenShift to this ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20164) webtools server adapter installation UI is non-informative

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20164: ------------------------------- Attachment: install-jbossas-connector-from-nightly.png These three commits are in build B803, which is available here [1]. JBIDE-20164: https://github.com/jbosstools/jbosstools-server/commit/6ba6d30c6c10d8ec51... JBIDE-20173: https://github.com/jbosstools/jbosstools-server/commit/97df8fbf994ac0e88d... JBIDE-20170: https://github.com/jbosstools/jbosstools-server/commit/a4ce07ab623a48acc0... [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ or http://download.jboss.org/jbosstools/updates/nightly/mars/ So, I installed Eclipse 4.5, then opened this file: eclipse/plugins/org.eclipse.wst.server.discovery_1.0.701.v201505261810.jar!/serverAdapterSites.xml And changed this: - <site url="http://download.jboss.org/jbosstools/updates/webtools/mars/"/> + <site url="http://download.jboss.org/jbosstools/updates/nightly/mars/"/> So then: !install-jbossas-connector-from-nightly.png! And these features are freshly installed: {code} cd eclipse/features; find . -maxdepth 1 -mmin -10 | sort ./org.eclipse.jdt_3.11.0.v20150603-2000 ./org.eclipse.jst.web_core.feature_3.7.0.v201506041749 ./org.eclipse.jst.web_ui.feature_3.7.0.v201506041749 ./org.jboss.ide.eclipse.archives.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.archives.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.jmx.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.ide.eclipse.as.server.rse.integration.feature_3.1.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.archives.scanner.feature_3.6.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.jmx.feature_1.7.0.Beta2-v20150701-2155-B803 ./org.jboss.tools.runtime.core.feature_3.1.0.Beta2-v20150626-1605-B757 ./org.jboss.tools.stacks.core.feature_1.2.0.Beta2-v20150626-1605-B757 {code} > webtools server adapter installation UI is non-informative > ---------------------------------------------------------- > > Key: JBIDE-20164 > URL: https://issues.jboss.org/browse/JBIDE-20164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: install-jbossas-connector-from-nightly.png, Install_New_Extension_and_New_Server.png > > > When using the "download additional adapters" for JBoss Tools it has a few issues. > a) shows "null" for vendor > b) does not actually say it is for WildFly nor EAP servers > c) (idea) should we add OpenShift to this ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20092: ------------------------------------------ [~mmalina] filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=471655 which sounds like exactly the same issue as we have here. > Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works) > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20092 > URL: https://issues.jboss.org/browse/JBIDE-20092 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png > > > using https://console.stg.openshift.com as server > the retrieve link does nothing if clicked. > Only if I use "enter" on the keyboard does it actually show a browser. > Steps: > # ASSERT: make sure that you're using MacOS > # EXEC: launch new connection wizard, > # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen > # EXEC: hit "retrieve" link > !retrieve-token-link.png! > Result: > Nothing happens -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20092: ------------------------------------- Affects Version/s: 4.3.0.Beta2 Forum Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=471655 > Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works) > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20092 > URL: https://issues.jboss.org/browse/JBIDE-20092 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Labels: connection_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png > > > using https://console.stg.openshift.com as server > the retrieve link does nothing if clicked. > Only if I use "enter" on the keyboard does it actually show a browser. > Steps: > # ASSERT: make sure that you're using MacOS > # EXEC: launch new connection wizard, > # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen > # EXEC: hit "retrieve" link > !retrieve-token-link.png! > Result: > Nothing happens -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19598: ------------------------------------ So with this change any of the 17 builds would trigger a rebuild of the JBT core & coretests aggregates. But today, we can collect changes into fewer respins using the composite site job (which spins at intervals rather than for EVERY upstream commit). The composite job ALSO does an install test to verify that everything can be installed into the current version of Eclipse. That job has been failing since we moved the target platform to use Eclipse Mars R (RC4/SR0) because it was using RC2 to do the install. (I fixed that yesterday and the job's back to blue/yellow.) So... that's a GOOD thing. It caught the fact that we can't install JBT 4.3.0.Beta2-SNAPSHOT bits onto RC2 because of the incompatible target platforms (p2 director installs can't do remediation). Losing this test, IMHO, would be bad. The overhead/maintenance is minimal. Causing many more aggregate builds to fire doesn't seem like a good thing. Why do we want to go back to something we specifically STOPPED doing a few years ago? -- Today, we run all the project builds based on SCM change, then fire the aggregates based on a composite site build. When we want to build the whole stack, we use a buildflow job. This achieves a balance of: * fairly frequent aggregate respins (every 3 hours, with re-checks every 30 mins if the attempt to build failed due to missing content) * light Jenkins slave load (composite job is faster and eats less time/disk space than 2 aggregate builds, which also have to suck down source zips from Github) https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... We used to have a cascade of jobs, linked together in their logical build order, then fired the aggregates based on a composite site build. We removed the inter-job linking to make maintenance easier (this was replaced by a buildflow job in 7.0). http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... Before that, we had all the jobs cause aggregates to fire (using a cascade of jobs, linked together in their logical build order). This was better than the old way, but harder to maintain as component job deps changed (more things depending on Base or Server, for example). So for 6.0 I added the composite install job. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... Before that, we had all the projects firing the aggregate in no particular order, with no inter-job linking. This caused build failures and ate a lot of slave resources. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... --- I guess my question, ultimately, is "what are we trying to solve by switching to a new model of job aggregation?" This JIRA doesn't actually state the problem we're trying to fix; it only says "we could use this plugin to remove the need for 1 job". Is the job so bad that its maintenance burden behooves its removal? > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-457) Spin a new community stack with the latest Luna TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-457?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-457. ------------------------------ Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/commit/30de52c... > Spin a new community stack with the latest Luna TP > -------------------------------------------------- > > Key: JBTIS-457 > URL: https://issues.jboss.org/browse/JBTIS-457 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 4.2.3.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.3.Beta1 > > > Create a new JBTIS 4.2.3.Beta1 community-only release with the latest JBTIS TP 4.2.6.Final. Teiid Designer wants to use it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20100: ---------------------------------------- 1) currently, we only have one connector existing in regular and early-access, so the result would be the same list as when Early-Access is enabled, +1 (the regular version of this connector). No bug change for a big benefit that early-access content is visible immediately. 2) In that case. I don't see how adding "connectors" to show that Fuse & others currently don't work with JBT/JBDS is helpful for users. Note that the user-story in the description doesn't mention at all the need for "advertising connector". > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15388?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15388: ------------------------------------ We kind of already have this now as a shell wrapper to call maven deploy. Suggestion to migrate it to mojo in JBIDE-20177 > Compute whether to publish or not based on output signature rather than commits > ------------------------------------------------------------------------------- > > Key: JBIDE-15388 > URL: https://issues.jboss.org/browse/JBIDE-15388 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: LATER > > > [Assuming we already have reproducible qualifiers...] > Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication. > However there are some case not correctly supported: > * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen > * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it. > instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19598: ---------------------------------------- Currently SCM chnage will republish content and then require a new aggregate, so this case doesn't change with the "Build other project (extended)". This is the story of JBIDE-15388. > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20175) JBT update site returns 404 Not Found

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20175?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20175. ------------------------------ Just FYI, http://download.jboss.org/jbosstools/updates/snapshots/mars/ and http://download.jboss.org/jbosstools/updates/nightly/mars/ contain the same content (one's a symlink to the other). Link is fixed on http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html so closing. > JBT update site returns 404 Not Found > ------------------------------------- > > Key: JBIDE-20175 > URL: https://issues.jboss.org/browse/JBIDE-20175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: page.png > > > The JBT nightly update site http://download.jboss.org/jbosstools/mars/development/nightly does not point to a valid repository and returns code 404 Not found. This URL is listed on the JBT Downloads page > http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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