January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2669: ------------------------------------------- I'm +1 based as already stated but would like to see the actual PR since i'm still not sure how big a change it will be hence why I would like to see the actual PR. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16345) General Palette improvements

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16345: ---------------------------------- Labels: new_and_noteworthy (was: ) > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.png!| > 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor > !PaletteDragAndDrop1.png! > !PaletteDragAndDrop2.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2669: -------------------------------------- +1 > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16309: ------------------------------------ PR 131 looks good except for use of jbosstools-upstream-repo property. Do you mean jbosstools-site-baseurl ? Similar issue in PR 186. > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16367: ---------------------------------------- > Yes, 400+ downloads of update site zips (and other files) per week. Wow. Then I shut up and close this bug as invalid. > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16355: ------------------------------------ I would prefer to link to a report like this one for all the JBT 4.1.1.* milestone issues: https://issues.jboss.org/secure/ConfigureReport.jspa?versions=12321748&ve... As generated from this page: https://issues.jboss.org/secure/ConfigureReport!default.jspa?projectOrFil... > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16367. ---------------------------------- Resolution: Rejected > Yes, 400+ downloads of update site zips (and other files) per week. Wow. Then I shut up and reject this request. > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16367: ------------------------------------ Yes, 400+ downloads of update site zips (and other files) per week. http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/ http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.0.x/ These are linked from here: http://www.jboss.org/tools/download/stable/4_1 http://www.jboss.org/tools/download/stable/4_0 We've been using SF since the early days in 2007. Curiously, we're still getting downloads of stuff from JBT 3.0 (2009) at a rate of 8 update site zips/week. http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools3.0.x/ And JBT 3.3.2 is still getting 60 dls/week: http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools3.3.x/ > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16367: ---------------------------------------- Akamai is good for people who consume those URL to fetch or install stuff. Is there anyone consuming the SF URLs of JBoss Tools? Do you have statistics? > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14768) Connection dialog: Inform users about invalid SSL certificates and allow them to accept/refuse them

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14768?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14768: ---------------------------------------- Priority: Critical (was: Major) > Connection dialog: Inform users about invalid SSL certificates and allow them to accept/refuse them > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-14768 > URL: https://issues.jboss.org/browse/JBIDE-14768 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Priority: Critical > Labels: connection_wizard > Fix For: 4.2.x > > > In JBIDE-10447 the openshift-java-client disabled the checks for SSL certificates since those prevented users from connecting to internal/private OpenShift instances: > {code:title=UrlConnectionHttpClient} > private HttpURLConnection createConnection(String userAgent, URL url) throws IOException { > HttpURLConnection connection = (HttpURLConnection) url.openConnection(); > if (isHttps(url) > && !doSSLChecks) { > HttpsURLConnection httpsConnection = (HttpsURLConnection) connection; > httpsConnection.setHostnameVerifier(new NoopHostnameVerifier()); > setPermissiveSSLSocketFactory(httpsConnection); > } > private boolean isHttps(URL url) { > return "https".equals(url.getProtocol()); > } > /** > * Sets a trust manager that will always trust. > * <p> > * TODO: dont swallog exceptions and setup things so that they dont disturb other components. > */ > private void setPermissiveSSLSocketFactory(HttpsURLConnection connection) { > try { > SSLContext sslContext = SSLContext.getInstance("SSL"); > sslContext.init(new KeyManager[0], new TrustManager[] { new PermissiveTrustManager() }, new SecureRandom()); > SSLSocketFactory socketFactory = sslContext.getSocketFactory(); > ((HttpsURLConnection) connection).setSSLSocketFactory(socketFactory); > } catch (KeyManagementException e) { > // ignore > } catch (NoSuchAlgorithmException e) { > // ignore > } > } > private static class PermissiveTrustManager implements X509TrustManager { > public X509Certificate[] getAcceptedIssuers() { > return null; > } > public void checkServerTrusted(X509Certificate[] chain, > String authType) throws CertificateException { > } > public void checkClientTrusted(X509Certificate[] chain, > String authType) throws CertificateException { > } > } > private static class NoopHostnameVerifier implements HostnameVerifier { > public boolean verify(String hostname, SSLSession sslSession) { > return true; > } > } > {code} > We should not simply disable these SSL checks but allow users to accept/refuse them via a dialog -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 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 January 2014