October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3190) Wrong update sites in JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3190?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3190: -------------------------------------- The development site should not appear on a GA candidate. This is caused by this file https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.2.x/... which requires an update to use GA instead of development. I'm going to update this file manually and create a respin-c of JBDS. [~nickboldt] As this is a step which is pretty easy to forget, we need to set up some automation or a rule that would prevent us from forgetting that. > Wrong update sites in JBDS > -------------------------- > > Key: JBDS-3190 > URL: https://issues.jboss.org/browse/JBDS-3190 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Blocker > Labels: respin-c > Fix For: 8.0.0.CR2 > > > There are wrong update sites defined in JBDS: > http://i.imgur.com/Y5l3rdy.png -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3190) Wrong update sites in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3190?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3190: -------------------------------------- Labels: respin-c (was: ) > Wrong update sites in JBDS > -------------------------- > > Key: JBDS-3190 > URL: https://issues.jboss.org/browse/JBDS-3190 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Blocker > Labels: respin-c > Fix For: 8.0.0.CR2 > > > There are wrong update sites defined in JBDS: > http://i.imgur.com/Y5l3rdy.png -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18665: ------------------------------------- Labels: application_wizard (was: ) Workaround Description: manually correct the application name, remove non-alphanumeric characters (*ticket-monster* -> *ticketmonster*) Workaround: Workaround Exists > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: 4.3.x > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18665: ------------------------------------- Priority: Minor (was: Major) > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.3.x > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3190) Wrong update sites in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3190?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3190: -------------------------------------- Fix Version/s: 8.0.0.CR2 Assignee: Mickael Istria > Wrong update sites in JBDS > -------------------------- > > Key: JBDS-3190 > URL: https://issues.jboss.org/browse/JBDS-3190 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR2 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Blocker > Fix For: 8.0.0.CR2 > > > There are wrong update sites defined in JBDS: > http://i.imgur.com/Y5l3rdy.png -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3190) Wrong update sites in JBDS

by Radim Hopp (JIRA)

Radim Hopp created JBDS-3190: -------------------------------- Summary: Wrong update sites in JBDS Key: JBDS-3190 URL: https://issues.jboss.org/browse/JBDS-3190 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 8.0.0.CR2 Reporter: Radim Hopp Priority: Blocker There are wrong update sites defined in JBDS: http://i.imgur.com/Y5l3rdy.png -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-538) If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-538?page=com.atlassian.jira.plug... ] Konstantin Marmalyukov commented on TOOLSDOC-538: ------------------------------------------------- Issue can be resolved because this case was documented in https://github.com/jbosstools/jbosstools-website/pull/248. Please mark this issue as resolved cause I have no rights to do it. > If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-538 > URL: https://issues.jboss.org/browse/TOOLSDOC-538 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Affects Versions: 4.2.0.CR2 > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Critical > Fix For: 4.2.0.Final > > > If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine > The issue is that if a RHEL user installs these packages: > java-1.7.0-oracle-1.7.0 > java-1.7.0-oracle-devel-1.7.0 > It may appear as though the full JDK has been installed as the "devel" package installs javac - however, the JavaFx libraries are not installed. As a result, the user cannot specify JavaFx as the browser engine in the BrowserSim preferences. (See attached screenshot.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3189) AngularJS for Web Tools cannot be installed

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBDS-3189?page=com.atlassian.jira.plugin.... ] Lucia Jelinkova commented on JBDS-3189: --------------------------------------- Also Arquillian and Maven Packaging Configurator plugins have in Central CR2 version. > AngularJS for Web Tools cannot be installed > ------------------------------------------- > > Key: JBDS-3189 > URL: https://issues.jboss.org/browse/JBDS-3189 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.CR2 > Environment: JBDS 8.0.0.CR2b > Reporter: Rastislav Wagner > Assignee: Mickael Istria > Priority: Blocker > Fix For: 8.0.0.CR2 > > > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74) > Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt 3.6.0.Final-v20141016-0045-B76) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt 3.6.0.CR2-v20141003-2041-B74) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141017-1111-B314) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.Final-v20141016-0045-B76] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314) > To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141017-1111-B314] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.CR2-v20141003-2041-B74] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.CR2-v20141003-2041-B74) > To: org.jboss.tools.jst.jsdt [3.6.0.CR2-v20141003-2041-B74] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.Final-v20141016-0045-B76) > To: org.jboss.tools.jst.jsdt [3.6.0.Final-v20141016-0045-B76] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10777) Use Sonar for Code Quality Analysis

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10777?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-10777: ---------------------------------------- Sorry, I meant JBIDE-17991 > Use Sonar for Code Quality Analysis > ----------------------------------- > > Key: JBIDE-10777 > URL: https://issues.jboss.org/browse/JBIDE-10777 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 3.1.2 > Environment: any > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Minor > Fix For: LATER > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Sonar provides a very powerful tool to get report about tests, code coverage, and static analysis in a project (errors, duplications...). It is easy to use, there is a nice integration with Maven and Hudson/Jenkins. It provides reporting tools for everything existing in the Java world, and more. > Adding Sonar to Hudson really helps to make code better. > http://www.sonarsource.org/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18665: ------------------------------------- Estimated Difficulty: Low > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 October 2014