August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20416) Include JBDS source zip on tools.jboss.org download page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20416?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20416: ------------------------------- Fix Version/s: 4.3.0.Beta2 > Include JBDS source zip on tools.jboss.org download page > -------------------------------------------------------- > > Key: JBIDE-20416 > URL: https://issues.jboss.org/browse/JBIDE-20416 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > I noticed, that the sources zip is not available for download for JBDS 9.0.0.Beta2: > http://tools.jboss.org/downloads/devstudio/mars/9.0.0.Beta2.html#zips > There are only two files there: > Update site (including sources) bundle of JBoss Developer Studio (507MB) > Target Platform for JBoss Developer Studio (452MB) > Whereas the JBoss.org Products page contains the source zip: > http://www.jboss.org/products/devstudio/download/ > Stand-alone Installer > Update Site Zip > JBoss Central Zip > Source Zip > Also, the JBoss Tools download page on tools.jboss.org does include the source zip: > http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Beta2.html#zips > Update site (including sources) bundle of all JBoss Core Tools > Sources zip of all JBoss Core Tools > Stand-alone BrowserSim > Release Notes > I understand that the sources are in the update site zip, too. But I wonder if there is any reason for this inconsistency. I can't think of any. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20416) Include JBDS source zip on tools.jboss.org download page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20416?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20416: ------------------------------------ In the past the sources zip contained only the sources of JBDS (not its JBT pieces too). So it was of value only to people who wanted to build JBDS from source but who didn't have access to the jbdevstudio-product github repo. Since the sources zip [1] is linked from https://www.jboss.org/products/devstudio/download/ for JBDS 9 Beta2, we should probably add it to tools.jboss.org too, for consistency. PR: https://github.com/jbosstools/jbosstools-website/pull/452 [1] http://www.redhat.com/j/elqNow/elqRedir.htm?ref=http://www.jboss.org/down... > Include JBDS source zip on tools.jboss.org download page > -------------------------------------------------------- > > Key: JBIDE-20416 > URL: https://issues.jboss.org/browse/JBIDE-20416 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > I noticed, that the sources zip is not available for download for JBDS 9.0.0.Beta2: > http://tools.jboss.org/downloads/devstudio/mars/9.0.0.Beta2.html#zips > There are only two files there: > Update site (including sources) bundle of JBoss Developer Studio (507MB) > Target Platform for JBoss Developer Studio (452MB) > Whereas the JBoss.org Products page contains the source zip: > http://www.jboss.org/products/devstudio/download/ > Stand-alone Installer > Update Site Zip > JBoss Central Zip > Source Zip > Also, the JBoss Tools download page on tools.jboss.org does include the source zip: > http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Beta2.html#zips > Update site (including sources) bundle of all JBoss Core Tools > Sources zip of all JBoss Core Tools > Stand-alone BrowserSim > Release Notes > I understand that the sources are in the update site zip, too. But I wonder if there is any reason for this inconsistency. I can't think of any. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Rastislav Wagner reassigned JBIDE-19910: ---------------------------------------- Assignee: Rastislav Wagner > Add w3 schemes to XML catalog > ----------------------------- > > Key: JBIDE-19910 > URL: https://issues.jboss.org/browse/JBIDE-19910 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.3.0.CR1 > > > We should add w3 schemes which are used in our quickstarts/examples to XML catalog because: > 1) w3 servers are intentionally slow > 2) it seems that wsdl validator does no caching of previously downloaded schemes > I will take a look at examples and list schemes here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20001?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20001 at 8/5/15 8:55 AM: ------------------------------------------------------------------ [~sspeiche] thx for confirming. merged and pushed to upstream/master was (Author: adietish): merged and pushed to upstream/master > Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-20001 > URL: https://issues.jboss.org/browse/JBIDE-20001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Steve Speicher > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Screen Shot 2015-06-09 at 10.35.54 AM.png > > > The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers. > Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3 > An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20143) use SHA256 instead of SHA1 when digesting zips and jars

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20143?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-20143. ------------------------------- Verified and CSP content test changed accordingly. > use SHA256 instead of SHA1 when digesting zips and jars > ------------------------------------------------------- > > Key: JBIDE-20143 > URL: https://issues.jboss.org/browse/JBIDE-20143 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > CSP & GoldenGate uses SHA256 digests, so we should use that instead of SHA1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20001?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20001: ------------------------------------------ merged and pushed to upstream/master > Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-20001 > URL: https://issues.jboss.org/browse/JBIDE-20001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Steve Speicher > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Screen Shot 2015-06-09 at 10.35.54 AM.png > > > The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers. > Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3 > An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account

by Steve Speicher (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20001?page=com.atlassian.jira.plugi... ] Steve Speicher commented on JBIDE-20001: ---------------------------------------- Sounds right to me > Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-20001 > URL: https://issues.jboss.org/browse/JBIDE-20001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Steve Speicher > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Screen Shot 2015-06-09 at 10.35.54 AM.png > > > The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers. > Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3 > An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3327) Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3327?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3327. ---------------------------- Assignee: Misha Ali (was: Michelle Murray) Closing since done. Changed assignee to Misha, not Michelle. > Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0 > -------------------------------------------------------- > > Key: JBDS-3327 > URL: https://issues.jboss.org/browse/JBDS-3327 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Misha Ali > Fix For: 9.0.0.Beta2 > > > We have been testing primarily on Yosemite (and Mavericks) for some time and there's no reason why not include Yosemite. > This is the JBDS support matrix doc: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20203) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20203?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20203: ------------------------------------------ merged and pushed to upsteam/master > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-20203 > URL: https://issues.jboss.org/browse/JBIDE-20203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [OpenShift]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20332) [Bower] Better user experience when running 'Bower Update' on a default bower.json file

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20332?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20332: ------------------------------------- [~psrna], I have fixed it with JBIDE-20319. Console view will be shown on every "Bower Update" launch (once it will be executed console title will change to smth. like "<terminated> Bower Update") > [Bower] Better user experience when running 'Bower Update' on a default bower.json file > --------------------------------------------------------------------------------------- > > Key: JBIDE-20332 > URL: https://issues.jboss.org/browse/JBIDE-20332 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > > Running 'Run As -> Bower Update' on a default bower.json (that one created by Bower Init wizard' results in no visible action. That is under my opinion a bad user experience. I personally have hit 'Run as' 3 times to be sure something has started. > I suggest, that we show the console, with something like 'bower update terminated' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015