August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24573) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24573: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.x) > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-24573 > URL: https://issues.jboss.org/browse/JBIDE-24573 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.4.4.Final > Environment: windows 7 eclipse neon maven > Reporter: stefano canu > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > Attachments: pfi-test.zip, pom.xml > > > I 'm tryng to deploy to wildfly 10 an ear project (maven) composed by one war and one jar (ejb) project, but the ear deployed with eclipse wildfly connector is different form one present in the target foleder, library in web-inf lib is missing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24573) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24573?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24573: ------------------------------- Sprint: devex #136 August 2018 > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-24573 > URL: https://issues.jboss.org/browse/JBIDE-24573 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.4.4.Final > Environment: windows 7 eclipse neon maven > Reporter: stefano canu > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > Attachments: pfi-test.zip, pom.xml > > > I 'm tryng to deploy to wildfly 10 an ear project (maven) composed by one war and one jar (ejb) project, but the ear deployed with eclipse wildfly connector is different form one present in the target foleder, library in web-inf lib is missing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (an other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24787: ---------------------------------- Assignee: Andre Dietisheim (was: Dmitrii Bocharov) > Wildfly (an other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.1.AM1 > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (an other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24787: ------------------------------- Sprint: devex #136 August 2018 > Wildfly (an other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.1.AM1 > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4410: -------------------------------- Sprint: devex #136 August 2018 > DevSuite 1.4 Installer indicate download size during choice selection > --------------------------------------------------------------------- > > Key: JBDS-4410 > URL: https://issues.jboss.org/browse/JBDS-4410 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.x > > > During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late. > The two use cases I see for this: > # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later. > # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V. > Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4411) DevSuite 1.4 installer display required disk space

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4411: -------------------------------- Sprint: devex #136 August 2018 > DevSuite 1.4 installer display required disk space > --------------------------------------------------- > > Key: JBDS-4411 > URL: https://issues.jboss.org/browse/JBDS-4411 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 11.x > > > DevSuite 1.4 installer (online) should display the disk space requirements which should include the calculation for both the downloads and the unpacked/installed files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22613: ------------------------------- Sprint: devex #123 November 2016, devex #136 August 2018 (was: devex #123 November 2016) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.1.AM1 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4302) Component should declare dependencies in requirements-.json

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4302?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4302: -------------------------------- Fix Version/s: 11.0.0.GA (was: 11.x) > Component should declare dependencies in requirements-.json > ----------------------------------------------------------- > > Key: JBDS-4302 > URL: https://issues.jboss.org/browse/JBDS-4302 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.GA > > > Current implementation for dependencies validation is hardcoded and was originally implemented for static set of components. It should part of components configuration in requirements.json file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4302) Component should declare dependencies in requirements-.json

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4302?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4302. --------------------------------- Resolution: Done > Component should declare dependencies in requirements-.json > ----------------------------------------------------------- > > Key: JBDS-4302 > URL: https://issues.jboss.org/browse/JBDS-4302 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.GA > > > Current implementation for dependencies validation is hardcoded and was originally implemented for static set of components. It should part of components configuration in requirements.json file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4302) Component should declare dependencies in requirements-.json

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4302?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4302: -------------------------------- Sprint: devex #135 July 2017 > Component should declare dependencies in requirements-.json > ----------------------------------------------------------- > > Key: JBDS-4302 > URL: https://issues.jboss.org/browse/JBDS-4302 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.GA > > > Current implementation for dependencies validation is hardcoded and was originally implemented for static set of components. It should part of components configuration in requirements.json file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 August 2017