October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ] Karel Piwko commented on JBIDE-18699: ------------------------------------- Ahh, I haven't noticed these are two different installations. Now looking at the description, it does not same the same thing. Is there a chance that icon or title could be different to make this less confusing while keeping id the same? > Angular.js is present in both supported and Early Access > -------------------------------------------------------- > > Key: JBIDE-18699 > URL: https://issues.jboss.org/browse/JBIDE-18699 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0.GA > Reporter: Karel Piwko > Assignee: Max Rydahl Andersen > Attachments: early-access.png, no-early-access.png > > > If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access. > However, it is in supported as well. I guess only Arquillian should pop up in early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ] Karel Piwko updated JBIDE-18699: -------------------------------- Issue Type: Feature Request (was: Bug) > Angular.js is present in both supported and Early Access > -------------------------------------------------------- > > Key: JBIDE-18699 > URL: https://issues.jboss.org/browse/JBIDE-18699 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0.GA > Reporter: Karel Piwko > Assignee: Max Rydahl Andersen > Attachments: early-access.png, no-early-access.png > > > If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access. > However, it is in supported as well. I guess only Arquillian should pop up in early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12384) Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12384?page=com.atlassian.jira.plugi... ] Paul Leacu resolved JBIDE-12384. -------------------------------- Fix Version/s: (was: 4.0.0.Alpha1-SOA) Resolution: Out of Date Issue is out of date - please escalate if this requires immediate attention. > Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error > ------------------------------------------------------------------------- > > Key: JBIDE-12384 > URL: https://issues.jboss.org/browse/JBIDE-12384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform, runtime-detection > Affects Versions: 3.3.1.Final > Environment: MacOS Mountain Lion with Eclipse 4.2 (Juno). > Reporter: Robb Greathouse > Assignee: Paul Leacu > -- 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 Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18713: ------------------------------------------------ Len, I download ticketmonster from github, import demo project, run it on wildfly 8.1 and everything is fine. > 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 Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18713: ------------------------------------- [~ldimaggio] is it reproducible on RHEL for both JavaFX and SWT web engines? > 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 Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18713?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18713: ------------------------------------- [~ldimaggio], not reproducible on windows with *jboss-kitchensink-html5-mobile* project > 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 commented on JBIDE-17180: ------------------------------------- Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=449183 for a small bug relating to server editor parts and their displayed error messages > 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.x > > > 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

[JBoss JIRA] (TOOLSDOC-547) OpenShift How To: Develop an Existing OpenShift Online App

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-547?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-547: -------------------------------------------- Hi [~aakanksha_writer] and [~mmurray], Please find the article for peer review at: https://docs.google.com/a/redhat.com/document/d/1GQmZvunNDPnpHytNKLEt2C2T... Thanks, Supriya > OpenShift How To: Develop an Existing OpenShift Online App > ---------------------------------------------------------- > > Key: TOOLSDOC-547 > URL: https://issues.jboss.org/browse/TOOLSDOC-547 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Split Work with Existing OS Applications article into two articles. This article will contain the Importing an Existing OpenShift Online Application to the IDE section. -- 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 commented on JBIDE-17180: ------------------------------------- Experiencing following stacktrace: {code} !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$RadioClickedCommand.execute(JBossDeploymentOptionsComposite.java:581) at org.eclipse.wst.server.ui.internal.command.ServerCommand.execute(ServerCommand.java:39) at org.eclipse.wst.server.ui.internal.editor.GlobalCommandManager.executeCommand(GlobalCommandManager.java:345) at org.eclipse.wst.server.ui.internal.editor.ServerResourceCommandManager.execute(ServerResourceCommandManager.java:54) at org.jboss.ide.eclipse.as.ui.editor.DeploymentPage.execute(DeploymentPage.java:117) at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.radioSelected(JBossDeploymentOptionsComposite.java:486) at org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$2.widgetSelected(JBossDeploymentOptionsComposite.java:288) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) {code} > 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.x > > > 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

[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 commented on JBIDE-17180: ------------------------------------- Just a note: The workflow for this issue is to have a server configured as remote + fs/shell operations. > 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.x > > > 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