October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Chunyun Chen edited comment on JBIDE-18696 at 10/29/14 11:10 PM: ----------------------------------------------------------------- 1. Tried below scenarios, all can be able to connect to devenv: 1). the "-Djsse.enableSNIExtension" is not in eclipse.ini , start Eclipse, then be able to connect to devenv; 2). the "-Djsse.enableSNIExtension=false" is added into eclipse.ini , restart Eclipse, then be able to connect to devenv; 3). the "-Djsse.enableSNIExtension=true" is added into eclipse.ini , restart Eclipse, then be able to connect to devenv. 2. The content of my ecliplse.ini: -startup plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile --launcher.appendVmargs -vmargs -Xms40m -Xmx512m -Djsse.enableSNIExtension=true ### only change this flag when testing. 3. Dose my Eclipse not read the eclipse.ini file ? is it possible? was (Author: cathat): 1. Tried below scenarios, all can be able to connect to devenv: 1). the "-Djsse.enableSNIExtension" is not in eclipse.ini , then be able to connect to devenv; 2). the "-Djsse.enableSNIExtension=false" is added into eclipse.ini , then be able to connect to devenv; 3). the "-Djsse.enableSNIExtension=true" is added into eclipse.ini , then be able to connect to devenv. 2. The content of my ecliplse.ini: -startup plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile --launcher.appendVmargs -vmargs -Xms40m -Xmx512m -Djsse.enableSNIExtension=true ### only change this flag when testing. 3. Dose my Eclipse not read the eclipse.ini file ? is it possible? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Attachments: jdk_cmd.png, jdk_eclipse.png, jre.png, quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Chunyun Chen edited comment on JBIDE-18696 at 10/29/14 11:09 PM: ----------------------------------------------------------------- 1. Tried below scenarios, all can be able to connect to devenv: 1). the "-Djsse.enableSNIExtension" is not in eclipse.ini , then be able to connect to devenv; 2). the "-Djsse.enableSNIExtension=false" is added into eclipse.ini , then be able to connect to devenv; 3). the "-Djsse.enableSNIExtension=true" is added into eclipse.ini , then be able to connect to devenv. 2. The content of my ecliplse.ini: -startup plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile --launcher.appendVmargs -vmargs -Xms40m -Xmx512m -Djsse.enableSNIExtension=true ### only changed this flag when testing. 3. Dose my Eclipse not read the eclipse.ini file ? is it possible? was (Author: cathat): 1. Tried below scenarios, all can be able to connect to devenv: 1). the "-Djsse.enableSNIExtension" is not in eclipse.ini , then be able to connect to devenv; 2). the "-Djsse.enableSNIExtension=false" is added into eclipse.ini , then be able to connect to devenv; 3). the "-Djsse.enableSNIExtension=true" is added into eclipse.ini , then be able to connect to devenv. 2. The content of the ecliplse.ini: -startup plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile --launcher.appendVmargs -vmargs -Xms40m -Xmx512m -Djsse.enableSNIExtension=true ### only changed this flag when testing. 3. Dose my Eclipse not read the eclipse.ini file ? is it possible? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Attachments: jdk_cmd.png, jdk_eclipse.png, jre.png, quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Chunyun Chen commented on JBIDE-18696: -------------------------------------- 1. Tried below scenarios, all can be able to connect to devenv: 1). the "-Djsse.enableSNIExtension" is not in eclipse.ini , then be able to connect to devenv; 2). the "-Djsse.enableSNIExtension=false" is added into eclipse.ini , then be able to connect to devenv; 3). the "-Djsse.enableSNIExtension=true" is added into eclipse.ini , then be able to connect to devenv. 2. The content of the ecliplse.ini: -startup plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile --launcher.appendVmargs -vmargs -Xms40m -Xmx512m -Djsse.enableSNIExtension=true ### only changed this flag when testing. 3. Dose my Eclipse not read the eclipse.ini file ? is it possible? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Attachments: jdk_cmd.png, jdk_eclipse.png, jre.png, quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16695: ---------------------------------- Labels: new_and_noteworthy (was: ) > Add marker/quick fix if test contains non static deployment method > ------------------------------------------------------------------ > > Key: JBIDE-16695 > URL: https://issues.jboss.org/browse/JBIDE-16695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-3200: --------------------------------------- [~mmalina] - yep, I can update the docs regarding this. What is the situation on Windows? If the user right-clicks the .jar on Windows, what is the option the user needs to click - is it open or run? > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: LATER > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17923) Support CDI 1.2

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-17923: ----------------------------------------------- A useful link for diff between 1.1 and 1.2 https://docs.jboss.org/cdi/spec/1.2/cdi-spec-diff.html Diffs that require implementation in JBoss CDI Tools: 1. The set of bean defining annotations for the 'annotated' bean discovery mode is changed. (2.5, 12.4.1) 2. An array type is not a legal bean type if its component type is not a legal bean type. (2.2.1, 3.3, 3.4) 3. Clarification: An observer method will be notified of an event if the event object is assignable to the observed event type, and if the _set of_ observed event qualifiers _is a subset of all_ the event qualifiers of the event. (10 - we have to check if we interpreted specs 1.0 and 1.1 in that way) 4. Section 'Firing events' (10.3) looks totally rewritten, but comparing old 10.3 to new 10.2, I have found only that previous 'or the @Any qualifier may be used, allowing the application to specify qualifiers dynamically' changed to 'or the application may specify qualifiers dynamically' (both cases imply that there are no other specified qualifiers). Probably, that does not influence what we implemented for resolving event qualifiers, but we have to check it. > Support CDI 1.2 > --------------- > > Key: JBIDE-17923 > URL: https://issues.jboss.org/browse/JBIDE-17923 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.2.0.Beta3 > Reporter: Fred Bricon > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > CDI 1.2 spec was released on april 14th, 2014 : http://www.cdi-spec.org/news/2014/04/14/CDI-1_2-released/ > Apparently, minor things went in, but I assume some validation rules will need to be updated, along adding a CDI 1.2 Facet -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18713) Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18713: --------------------------------- Priority: Major (was: Critical) > Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-18713 > URL: https://issues.jboss.org/browse/JBIDE-18713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Final > Environment: RHEL6 > Oracle JDK 1.7 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Fix For: 4.2.1.Final > > Attachments: Screenshot-127-0-0-1.png, Screenshot-localhost.png, ticket-monster.war > > > See the attached screenshots - I am seeing a consistent pattern where browsersim cannot open a URL that specifies localhost, such as: > http://localhost:8080/ticket-monster/mobile.html > But it is able to open a URL for the same page, if it specifies 127.0.0.1, such as: > http://127.0.0.1:8080/ticket-monster/mobile.html > See the attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18713) Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18713: -------------------------------------- Yes - this is seen with the EAP server embedded in JBDS 8.0 (EAP 6.3.0). Yes - this is seen with the SWT web engine and the JavaFX web engine. > Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-18713 > URL: https://issues.jboss.org/browse/JBIDE-18713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Final > Environment: RHEL6 > Oracle JDK 1.7 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.1.Final > > Attachments: Screenshot-127-0-0-1.png, Screenshot-localhost.png, ticket-monster.war > > > See the attached screenshots - I am seeing a consistent pattern where browsersim cannot open a URL that specifies localhost, such as: > http://localhost:8080/ticket-monster/mobile.html > But it is able to open a URL for the same page, if it specifies 127.0.0.1, such as: > http://127.0.0.1:8080/ticket-monster/mobile.html > See the attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18713) Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18713: -------------------------------------- The ticketmonster project (created by following the user guide) is attached to the JIRA in a .war file. > Browsersim is refusing to open pages on localhost - but will open the pages on 127.0.0.1 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-18713 > URL: https://issues.jboss.org/browse/JBIDE-18713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Final > Environment: RHEL6 > Oracle JDK 1.7 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.1.Final > > Attachments: Screenshot-127-0-0-1.png, Screenshot-localhost.png, ticket-monster.war > > > See the attached screenshots - I am seeing a consistent pattern where browsersim cannot open a URL that specifies localhost, such as: > http://localhost:8080/ticket-monster/mobile.html > But it is able to open a URL for the same page, if it specifies 127.0.0.1, such as: > http://127.0.0.1:8080/ticket-monster/mobile.html > See the attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17180: -------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.x) > Disable custom deployment settings for remote servers without management port exposed > ------------------------------------------------------------------------------------- > > Key: JBIDE-17180 > URL: https://issues.jboss.org/browse/JBIDE-17180 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > JBIDE-13445 added the possibility to use custom deploy dir on remote server. > {quote} > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. > {quote} > We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014