March 2015 - jbosstools-issues - Jboss List Archives

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

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19345?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19345: -------------------------------------- Commit applied, aggregation will be visible when Final NN are added. > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19541) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19541?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19541. ------------------------------ Resolution: Done Verified in JBT 4.3.0.Alpha1 > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19541 > URL: https://issues.jboss.org/browse/JBIDE-19541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19541) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-19541: ---------------------------------- Summary: Arquillian should not be in JBT EA catalog Key: JBIDE-19541 URL: https://issues.jboss.org/browse/JBIDE-19541 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.2.2.Final Reporter: Radim Hopp Assignee: Nick Boldt Fix For: 4.2.3.Final, 4.3.0.Alpha1 In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19541) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19541?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-19541: ------------------------------- Fix Version/s: (was: 4.2.3.Final) > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19541 > URL: https://issues.jboss.org/browse/JBIDE-19541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-19038: ------------------------------- Fix Version/s: (was: 4.3.0.Alpha1) > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov commented on JBDS-3262: ---------------------------------------------- AFAIU deprecation means just announcing that Visual Editor for jsf will be removed into next release without any messages in JBDS > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[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)

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

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

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

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