September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25045) no items in in http://download.jboss.org/jbosstools/oxygen/stable/updates/

by Stefan Cordes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25045?page=com.atlassian.jira.plugi... ] Stefan Cordes updated JBIDE-25045: ---------------------------------- Description: Update Site does no longer have artifacts. http://download.jboss.org/jbosstools/oxygen/stable/updates/ => brocken (There are no categorized items). (see !2017-09-15 12_21_06-Install.png|thumbnail! ) http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ => works well. http://download.jboss.org/jbosstools/oxygen/development/updates/ => works well. Please re-publish. was: Update Site does no longer have artifacts. http://download.jboss.org/jbosstools/oxygen/stable/updates/ => brocken (There are no categorized items). http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ => works well. http://download.jboss.org/jbosstools/oxygen/development/updates/ => works well. Please re-publish. > no items in in http://download.jboss.org/jbosstools/oxygen/stable/updates/ > -------------------------------------------------------------------------- > > Key: JBIDE-25045 > URL: https://issues.jboss.org/browse/JBIDE-25045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Environment: Eclipse Java EE IDE for Web Developers. > Version: Oxygen Release (4.7.0) > Build id: 20170620-1800 > Reporter: Stefan Cordes > Attachments: 2017-09-15 12_20_31-Install.png, 2017-09-15 12_20_45-Install.png, 2017-09-15 12_21_06-Install.png > > > Update Site does no longer have artifacts. > http://download.jboss.org/jbosstools/oxygen/stable/updates/ > => brocken (There are no categorized items). (see !2017-09-15 12_21_06-Install.png|thumbnail! ) > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > => works well. > http://download.jboss.org/jbosstools/oxygen/development/updates/ > => works well. > Please re-publish. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24945) Central: refactor integration tests for use with RedDeer 2.0

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24945?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-24945: ------------------------------------- Assignee: Josef Kopriva (was: Vojtech Prusa) > Central: refactor integration tests for use with RedDeer 2.0 > ------------------------------------------------------------ > > Key: JBIDE-24945 > URL: https://issues.jboss.org/browse/JBIDE-24945 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.1.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24893) Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24893?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24893: ------------------------------- Fix Version/s: 4.5.x > Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24893 > URL: https://issues.jboss.org/browse/JBIDE-24893 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-platform, server > Affects Versions: 4.5.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Rob Stryker > Priority: Optional > Fix For: 4.5.x > > > Hi, > I believe that eclipse development with wildfly is quite cumbersome at the moment of defining a new wildfly domain runtime, in particular in regard to the resutilng "open launch configurations". > When we consider what happens with weblogic domains, they normally all have a dedicated bin/ folder. > I do the same thing when a create a fresh new wildfly domain, i enrich it with an additional bin/ folder where I pump in scripts to start/stop etc.. the domain. > Where in particular, the start script is created with properties like java options that matter to our deployments. > Weblogic start plugin uses the startWeblogic.cmd in the bin folder. > Naturally, this does not happen on Wildfly because the concept for the bin scripts is different. They are generic and domain independent. > But It would in any case be very nice, if it were possible to have some sort of convention that when the eclipse plugin looks at a stand alone domain, it could at least hunt for some sort of configuration file, such as an .eclipse_launch_parameters config, to override the default settings. > If such a mechanism would exist, i could enhance my create domain logic to pump into such a configuration file the same setting that is use in my start wildfly scripts.bat.sh. > As it stands, every time I create a new runtime I need to open the configuration page. > Go to the launch configurations, remove the heap settings. > And then go to my startup domain scripts, search for the java opts that I care about, and copy them over. > This is quite time wasteful. > It would be extremely helpful to be able to dodge point and click configuration, once I tell wildfly where the folder for my stand alone domain is located. > Many thanks for taking into consideration this enhancement request for widlfly eclipse plugin. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24893) Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24893?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24893: ---------------------------------- Assignee: Rob Stryker (was: Tomaz Cerar) > Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24893 > URL: https://issues.jboss.org/browse/JBIDE-24893 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-platform, server > Affects Versions: 4.5.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Rob Stryker > Priority: Optional > > Hi, > I believe that eclipse development with wildfly is quite cumbersome at the moment of defining a new wildfly domain runtime, in particular in regard to the resutilng "open launch configurations". > When we consider what happens with weblogic domains, they normally all have a dedicated bin/ folder. > I do the same thing when a create a fresh new wildfly domain, i enrich it with an additional bin/ folder where I pump in scripts to start/stop etc.. the domain. > Where in particular, the start script is created with properties like java options that matter to our deployments. > Weblogic start plugin uses the startWeblogic.cmd in the bin folder. > Naturally, this does not happen on Wildfly because the concept for the bin scripts is different. They are generic and domain independent. > But It would in any case be very nice, if it were possible to have some sort of convention that when the eclipse plugin looks at a stand alone domain, it could at least hunt for some sort of configuration file, such as an .eclipse_launch_parameters config, to override the default settings. > If such a mechanism would exist, i could enhance my create domain logic to pump into such a configuration file the same setting that is use in my start wildfly scripts.bat.sh. > As it stands, every time I create a new runtime I need to open the configuration page. > Go to the launch configurations, remove the heap settings. > And then go to my startup domain scripts, search for the java opts that I care about, and copy them over. > This is quite time wasteful. > It would be extremely helpful to be able to dodge point and click configuration, once I tell wildfly where the folder for my stand alone domain is located. > Many thanks for taking into consideration this enhancement request for widlfly eclipse plugin. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24784) Investigate Docker test failure during provisioning of RHEL7

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24784?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24784. --------------------------------- Resolution: Done Closing, probably due to network issues. > Investigate Docker test failure during provisioning of RHEL7 > ------------------------------------------------------------ > > Key: JBIDE-24784 > URL: https://issues.jboss.org/browse/JBIDE-24784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.1.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24901) Rework connection selection in Deploy DeployDockerImageTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24901?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24901: ---------------------------------- Fix Version/s: 4.5.1.AM3 > Rework connection selection in Deploy DeployDockerImageTest > ----------------------------------------------------------- > > Key: JBIDE-24901 > URL: https://issues.jboss.org/browse/JBIDE-24901 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.1.AM3 > > > Rework connection selection in test DeployDockerImageTest, because it has hard coded values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24933) Add ITest for editing the oc location when creating/editing a connection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24933?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24933: ---------------------------------- Fix Version/s: 4.5.1.AM3 > Add ITest for editing the oc location when creating/editing a connection > ------------------------------------------------------------------------ > > Key: JBIDE-24933 > URL: https://issues.jboss.org/browse/JBIDE-24933 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Labels: connection_wizard, integration_tests, openshift_v3 > Fix For: 4.5.1.AM3 > > > https://issues.jboss.org/browse/JBIDE-24802 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24784) Investigate Docker test failure during provisioning of RHEL7

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24784?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24784: ---------------------------------- Fix Version/s: 4.5.1.AM2 > Investigate Docker test failure during provisioning of RHEL7 > ------------------------------------------------------------ > > Key: JBIDE-24784 > URL: https://issues.jboss.org/browse/JBIDE-24784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.1.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24947) Openshift: refactor integration tests for use with RedDeer 2.0

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24947?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24947: ---------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > Openshift: refactor integration tests for use with RedDeer 2.0 > -------------------------------------------------------------- > > Key: JBIDE-24947 > URL: https://issues.jboss.org/browse/JBIDE-24947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24681: ---------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Josef Kopriva > Fix For: 4.5.1.AM3 > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017