March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-594) Offline Install does not mention the Target Platform zip

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-594?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-594: --------------------------------------- This JIRA will be closed when the update site (https://devstudio.jboss.com/updates/8.0/) is updated to contain the GA .zip files: Two .zip files are provided for installing JBoss Developer Studio BYOE in offline mode, namely an Update archive and a Target Platform archive. Both of these .zip files are necessary for a successful install and they can be downloaded from https://devstudio.jboss.com/updates/8.0/ under Offline Install. > Offline Install does not mention the Target Platform zip > -------------------------------------------------------- > > Key: TOOLSDOC-594 > URL: https://issues.jboss.org/browse/TOOLSDOC-594 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.2.2.Final > Environment: Build Name: 22661, Install Red Hat JBoss Developer Studio-8.0 > Build Date: 25-11-2014 14:18:18 > Topic ID: 41914-716354 [Latest] > Reporter: Nick Boldt > Assignee: Michelle Murray > Priority: Blocker > Fix For: 4.2.3.Final > > > Title: Install JBoss Developer Studio BYOE when Offline > Describe the issue: > See JBDS-3361. User cannot install from JBDS zip alone because some eclipse dependencies are unavailable in that zip. > > Suggestions for improvement: > TP zip should be linked from CSP, jboss.org, and devstudio.redhat.com. > Doc (in CSP and on access.redhat.com) should tell users about the target platform zip, too. > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3364: ------------------------------------ Verified in GA build: tree -L 3 . ├── devstudio │ └── product │ ├── features │ ├── installer │ ├── p2-director │ ├── plugins │ ├── pom.xml │ ├── README.md │ ├── results │ ├── site │ └── sources ├── jboss-devstudio-8.1.0.GA-v20150327-1349-B467-installer-src.zip └── jbosstools ├── aerogear_Final-v20150325-0456-B90_9789322aa94b2409bd360c0d0e364fef72c97ce9 │ ├── cordova │ ├── cordovasim │ ├── feedhenry │ ├── pom.xml │ ├── README.md │ └── site ├── aggregate │ ├── component-site │ ├── hibernatetools-site │ ├── pom.xml │ ├── README.building.txt │ ├── README.installation.txt │ ├── site │ └── webtools-site ├── arquillian_Final-v20141209-0427-B81_0718cfb99cb1b1265819ce125f6672d9b741843d │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── base_Final-v20150325-0456-B99_4240d036287b0c892515cecc0e6e3f234137ad84 │ ├── common │ ├── foundation │ ├── pom.xml │ ├── README.md │ ├── runtime │ ├── site │ ├── stacks │ └── usage ├── browsersim_Final-v20150324-2137-B57_2b43e367cbe1bae36cb8364e7c5dca21031b425a │ ├── features │ ├── plugins │ ├── pom.xml │ ├── products │ ├── README.md │ └── site ├── central_Final-v20150325-0325-B120_1d1f58cb3c6fc405653889cf472dc2cccb2f2346 │ ├── central │ ├── examples │ ├── maven │ ├── pom.xml │ ├── README.md │ └── site ├── forge_Final-v20150324-2247-B98_633cd9986d54e547d77822c4e286a2f3f4c57312 │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── freemarker_Final-v20141209-0743-B10_122ec093384398084a63cd058a1e1671f641c0d1 │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── hibernate_Final-v20150324-2307-B95_be0b90692795fc9bc7532af45586f78649b0999e │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ ├── sampleprojects │ └── site ├── javaee_Final-v20150325-0431-B95_86d74ad8fce1a9bc1eb1957502f406c1ed1d3ca9 │ ├── cdi │ ├── jsf │ ├── pom.xml │ ├── README.md │ ├── seam │ └── site ├── jbosstools-cleanup.sh ├── jst_Final-v20150325-0257-B112_180b7c816d460e4e30c5fd14b8b05caf5cd0c7ea │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── livereload_Final-v20141016-1313-B72_f1a8e6845274a9446614c267c398d863c26fa76c │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── openshift_Final-v20150203-0337-B74_39bba292ef5e16001058dcee772833c166cfdb7a │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── portlet_Final-v20141209-0339-B20_4eec888e7045ab1413934670cbdcdf7a11447b52 │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site ├── publish.sh ├── README.md ├── server_Final-v20150325-0035-B129_d6491efc29a0dac8c9de2ac0d51d292ac15a48cd │ ├── archives │ ├── as │ ├── jmx │ ├── pom.xml │ ├── README.md │ ├── site │ └── wtp ├── vpe_Final-v20150325-0347-B93_2980df9e9abac59194c7922bca0b3246c94e312e │ ├── features │ ├── plugins │ ├── pom.xml │ ├── README.md │ └── site └── webservices_Final-v20150324-2159-B84_1aa0d8958a4ffb767d329656977cf9c68bfdb6c0 ├── features ├── plugins ├── pom.xml ├── README.md └── site 89 directories, 41 files > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3364. ------------------------------ > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19042. --------------------------------- > Cannot login via Openshift Explorer on Openshift "Can not verify User" > ---------------------------------------------------------------------- > > Key: JBIDE-19042 > URL: https://issues.jboss.org/browse/JBIDE-19042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.x > Environment: Win7, jdk7, Openshift Online > Reporter: Stylianos Koussouris > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.2.Final > > Attachments: CannotVerifyUser.JPG > > > Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive > Unknown error, can not verify user > and in the log > !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113) > at com.openshift.internal.client.RestService.request(RestService.java:151) > at com.openshift.internal.client.RestService.request(RestService.java:107) > at com.openshift.internal.client.RestService.request(RestService.java:100) > at com.openshift.internal.client.RestService.request(RestService.java:81) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19501) Cutted text on features page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19501?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19501. --------------------------------- > Cutted text on features page > ---------------------------- > > Key: JBIDE-19501 > URL: https://issues.jboss.org/browse/JBIDE-19501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Environment: Win 7, Firefox 36.0.1 > Reporter: Konstantin Marmalyukov > Assignee: Xavier Coulon > Fix For: 4.2.3.Final > > Attachments: 19501_1.png, 19501_2.png, 19501_3_Chrome.png, Screenshot 2015-03-24 13.12.13.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19345) allow NN to be filtered/redefined for NN

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19345: --------------------------------------- commit that resolves the issue: https://github.com/jbosstools/jbosstools-website/commit/f64ee34825013d295... > allow NN to be filtered/redefined for NN > ---------------------------------------- > > Key: JBIDE-19345 > URL: https://issues.jboss.org/browse/JBIDE-19345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.3.Final, 4.3.0.CR1 > > > there been examples of auto aggregation of NN be a hit or miss for how much it makes sense in the release. > For example: > Beta1: Added a few components to the Ionic Palette: <c1> <c2> <c3> > Beta2: Added a few components to the Ionic: <c4> <c5> > Alexey Kazakov: But in the final verision I would like to have: Added new components: <c1>,...<c5>. > One suggestion been to have ability to rewrite the full NN version at final but I just know that will kill us becase it is going to be a pain to copy/paste right. > Alternative suggestion is: > A) during rendering of the "final" aggregation set a asciidoc variable (i.e. "finalnn") allowing us to use asciidoc conditionals like > {code} > ifndef::finalnn[] > This piece of news was only relevant for Beta1 > endif::finalnn[] > {code} > See: http://mrhaki.blogspot.ch/2014/08/awesome-asciidoc-using-conditional.html > B) allow to add a .Final newnoteworthy adoc to use as place to write the aggregated news ..note, these should still be merged with the former NN's. so you only need to write the sections that are actually different. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-18595. -------------------------------- Closed as resolved and also follow-up JIRA is closed. > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa, upstream > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 4.2.3.Beta1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-15609. -------------------------------- This was resolved in VW 0.4, closing > versionwatch should ignore when there's a folder & jar which are identical > -------------------------------------------------------------------------- > > Key: JBIDE-15609 > URL: https://issues.jboss.org/browse/JBIDE-15609 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Optional > Fix For: 4.2.2.Final > > > A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. > Now, the vwatch tool complains when there's a folder and a jar present. > Two possible solutions to this come to mind: > a) ignore this - do not report as *{color:red}a problem{color}* > b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19495) Remove erroneously added OpenShift v3 plugins from jbosstools-4.2.x

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19495?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19495. --------------------------------- Verified. Branch 4.2.x does not contains v3 plugin anymore. > Remove erroneously added OpenShift v3 plugins from jbosstools-4.2.x > ------------------------------------------------------------------- > > Key: JBIDE-19495 > URL: https://issues.jboss.org/browse/JBIDE-19495 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.3.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.3.CR1 > > > in the commit for JBIDE-19122 (which bumped branch to 2.6.2) I erroneously included the stubs for the v3 OpenShift plugins (empty plugin directories with a .project file): > * org.jboss.tools.openshift.core > * org.jboss.tools.openshift.ui > * org.jboss.tools.openshift.client > * org.jboss.tools.openshift.common.core > * org.jboss.tools.openshift.common.ui > See https://github.com/adietish/jbosstools-openshift/commit/ac9596eb19efb07cb... > There's no harm since they're not included in the features nor in the build but we have to remove those again. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3347) Is installer/src/config/resources/images/logo.png even used?

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3347?page=com.atlassian.jira.plugin.... ] Jiri Peterka closed JBDS-3347. ------------------------------ Closing, nothing to verify. > Is installer/src/config/resources/images/logo.png even used? > ------------------------------------------------------------ > > Key: JBDS-3347 > URL: https://issues.jboss.org/browse/JBDS-3347 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 8.1.0.Beta1, 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > [~dgolovin] - there's one reference [1] to this file [2] in the installer sources but we didn't update it for JBDS 8 (the new logo treatment = red on white instead of white on red) so I'm guessing it's a dead file. > Can we just remove it? That would be more fun that getting James to design a new one for JBDS 9, and updating it for JBDS 8.1, too. :) > [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... > [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 March 2015