June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20067) Unable to add second server of the same type via runtime detection.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20067?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20067: ------------------------------------- > I have tried this scenario with wildfly 8.2, wildfly 9, wildfly-web 9. You haven't told me if it works properly for these versions or if its broken for all of them ;) Please try to include a bit more information to aid in a faster response. > Unable to add second server of the same type via runtime detection. > ------------------------------------------------------------------- > > Key: JBIDE-20067 > URL: https://issues.jboss.org/browse/JBIDE-20067 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > > When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't. > I saw no error, when I tried to add them at once. It must be done one after another to see the error. > I have tried this scenario with wildfly 8.2, wildfly 9, wildfly-web 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20083) Bad asciidoc -> html rendering for menu:: macros

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20083?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-20083. ----------------------------------------- Resolution: Done this is now enabled globally. I'm 99.99% sure we had it enabled globally before but I can't find that in the logs - so either i'm wrong or it was removed in a bad push force ;/ > Bad asciidoc -> html rendering for menu:: macros > ------------------------------------------------- > > Key: JBIDE-20083 > URL: https://issues.jboss.org/browse/JBIDE-20083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta2 > > > See on http://tools.jboss.org/blog/2015-05-28-port-monitoring.html, the menu is poorly rendered: > {{code}} > menu:Window[Preferences > Run/Debug > TCP/IP Monitor]. > {{code}} > while it's fine on GitHub: https://github.com/jbosstools/jbosstools-website/blob/7936a01c03ceecc45bd... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20096) creating eap-simple from templates and show in browser tries to open 'eap.local'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20096: --------------------------------------------- we can't expect users to do this manually for every template. Does openshift template system not have access to what the url will actually be ? > creating eap-simple from templates and show in browser tries to open 'eap.local' > -------------------------------------------------------------------------------- > > Key: JBIDE-20096 > URL: https://issues.jboss.org/browse/JBIDE-20096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Critical > > not sure what is to "blame" here but creating app from https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v3beta1) results in app getting created but show in browser wants me to go to "eap.local" which pretty sure that is not something that exist from the outside. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3463: ------------------------------------------- can you attach the installconfig.xml ? I would say it shouldn't allow any install the UI one wouldn't. > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20024: --------------------------------------------- we don't have access to the p2 install statistics so that is a mute point. The bugs above describe why we can't use a single jboss tools entry. > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > New Eclipse Marketplace problems: > * all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 > * 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- [~mickael_istria] putting more generic text that wont help IMO. [~jtyrrell] UX were involved and sales and PM teams was invited to comment. This issue would not be here if we actually had a release of Fuse tooling to use with JBDS 8 and then with JBDS 8.1 when it came out That was the plan to start with. Out of my team control. We will find a way to fix this for JBDS 9 and tell users to use JBDS 7 or 8 as needed. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18912: ------------------------------------- So, I thought I could finally replicate. Nothing was happening. The files were copied, but no deployment. Then I realized I didn't check the "Expose management port" in the server editor. Once I did that, everything worked fine. However, I do notice an area for improvement: when the management port is not exposed, the error message is swallowed and not presented to the user. This is obviously bad, as it gives no info for the user to pass on to us. I'll commit a fix that adds logging of the exception, but, again, I genuinely cannot replicate ;) > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-14341. ------------------------------------ Resolution: Rejected > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14341: ------------------------------------- Comment: was deleted (was: OpenShift v2 is being replaced with OpenShift v3 which is replacing v2 cartridges with docker and different build strategies (sti etc.).) > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14341: ------------------------------------------ OpenShift v2 is being replaced with OpenShift v3 which is replacing v2 cartridges with docker and different build strategies (sti etc.). > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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