July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4448: ------------------------------------- The reason for DevStudio installation failure is installing DevSuite 1.4.0.GA over devsuite 1.3.0.GA. Could you also look at /Applications/DevelopmentSuite/developer-studio/studio/configuration for log files? > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Bob Davis updated JBDS-4448: ---------------------------- Attachment: install.log > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Bob Davis commented on JBDS-4448: --------------------------------- [^install.log] Here you go. Thanks. Bob > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4448: ------------------------------------- [~rpdavis] could you attach install.log from target installation folder? > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4448: ----------------------------------- Assignee: Denis Golovin > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24651) JAX-RS support (Facet) not installed for JAR projects, that are packaged into WAR's WEB-INF/lib

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24651?page=com.atlassian.jira.plugi... ] Vsevolod Golovanov updated JBIDE-24651: --------------------------------------- Description: {quote}Put REST webresource in a war project - m2e adds JAX-RS support to the project. Put REST webresource in a jar project, that is deployed in a war - m2e does not add JAX-RS support to the project. As JAX-RS 2.0 spec says in 2.3.2 Servlet: "A JAX-RS application is packaged as a Web application in a .war file. The application classes are packaged in WEB-INF/classes or WEB-INF/lib and required libraries are packaged in WEB-INF/lib. See the Servlet specification for full details on packaging of web applications." That means you can have REST webresources in jars, that are deployed in a war. Such jars are web fragments in servlet terms. The reproducer is attached. The war project receives the relevant facets: Dynamic Web Module and JAX-RS. The jar-ui project receives the Web Fragment Module facet, but no JAX-RS.{quote} This is a quote from an analogous [m2e-wtp issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=519228]. I'm not sure if there is anything to be done at JBT side of things, or if this is a strictly m2e-wtp issue. I see two relevant JBT specifics: jboss' repackaged jax-rs spec api and the JAX-RS/JAX-RS Support thingy in project properties. I've attached a jboss-specific reproducer here, that uses jboss' repackaged jax-rs spec api. It shows both JAX-RS Support not being enabled and JAX-RS facet not being added to a jar web fragment project. was: {quote}Put REST webresource in a war project - m2e adds JAX-RS support to the project. Put REST webresource in a jar project, that is deployed in a war - m2e does not add JAX-RS support to the project. As JAX-RS 2.0 spec says in 2.3.2 Servlet: "A JAX-RS application is packaged as a Web application in a .war file. The application classes are packaged in WEB-INF/classes or WEB-INF/lib and required libraries are packaged in WEB-INF/lib. See the Servlet specification for full details on packaging of web applications." That means you can have REST webresources in jars, that are deployed in a war. Such jars are web fragments in servlet terms. The reproducer is attached. The war project receives the relevant facets: Dynamic Web Module and JAX-RS. The jar-ui project receives the Web Fragment Module facet, but no JAX-RS.{quote} This is a quote from an analogous [m2e-wtp issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=519228]. I'm not sure if there is anything to be done at JBT side of things, or if this is a strictly m2e-wtp issue. I see two relevant JBT specifics: jboss' repackaged jax-rs spec api and the JAX-RS/JAX-RS Support thingie in project properties. I've attached a jboss-specific reproducer here, that uses jboss' repackaged jax-rs spec api. It shows both JAX-RS Support not being enabled and JAX-RS facet not being added to a jar web fragment project. > JAX-RS support (Facet) not installed for JAR projects, that are packaged into WAR's WEB-INF/lib > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24651 > URL: https://issues.jboss.org/browse/JBIDE-24651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.4.4.Final > Environment: JBDS 10.4.0.GA > Reporter: Vsevolod Golovanov > Attachments: m2e-jax-rs-activation-jboss-ex.zip > > > {quote}Put REST webresource in a war project - m2e adds JAX-RS support to the project. > Put REST webresource in a jar project, that is deployed in a war - m2e does not add JAX-RS support to the project. > As JAX-RS 2.0 spec says in 2.3.2 Servlet: > "A JAX-RS application is packaged as a Web application in a .war file. The application classes are packaged in WEB-INF/classes or WEB-INF/lib and required libraries are packaged in WEB-INF/lib. See the Servlet specification for full details on packaging of web applications." > That means you can have REST webresources in jars, that are deployed in a war. Such jars are web fragments in servlet terms. > The reproducer is attached. > The war project receives the relevant facets: Dynamic Web Module and JAX-RS. > The jar-ui project receives the Web Fragment Module facet, but no JAX-RS.{quote} > This is a quote from an analogous [m2e-wtp issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=519228]. I'm not sure if there is anything to be done at JBT side of things, or if this is a strictly m2e-wtp issue. I see two relevant JBT specifics: jboss' repackaged jax-rs spec api and the JAX-RS/JAX-RS Support thingy in project properties. > I've attached a jboss-specific reproducer here, that uses jboss' repackaged jax-rs spec api. > It shows both JAX-RS Support not being enabled and JAX-RS facet not being added to a jar web fragment project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24651) JAX-RS support (Facet) not installed for JAR projects, that are packaged into WAR's WEB-INF/lib

by Vsevolod Golovanov (JIRA)

Vsevolod Golovanov created JBIDE-24651: ------------------------------------------ Summary: JAX-RS support (Facet) not installed for JAR projects, that are packaged into WAR's WEB-INF/lib Key: JBIDE-24651 URL: https://issues.jboss.org/browse/JBIDE-24651 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.4.4.Final Environment: JBDS 10.4.0.GA Reporter: Vsevolod Golovanov Attachments: m2e-jax-rs-activation-jboss-ex.zip {quote}Put REST webresource in a war project - m2e adds JAX-RS support to the project. Put REST webresource in a jar project, that is deployed in a war - m2e does not add JAX-RS support to the project. As JAX-RS 2.0 spec says in 2.3.2 Servlet: "A JAX-RS application is packaged as a Web application in a .war file. The application classes are packaged in WEB-INF/classes or WEB-INF/lib and required libraries are packaged in WEB-INF/lib. See the Servlet specification for full details on packaging of web applications." That means you can have REST webresources in jars, that are deployed in a war. Such jars are web fragments in servlet terms. The reproducer is attached. The war project receives the relevant facets: Dynamic Web Module and JAX-RS. The jar-ui project receives the Web Fragment Module facet, but no JAX-RS.{quote} This is a quote from an analogous [m2e-wtp issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=519228]. I'm not sure if there is anything to be done at JBT side of things, or if this is a strictly m2e-wtp issue. I see two relevant JBT specifics: jboss' repackaged jax-rs spec api and the JAX-RS/JAX-RS Support thingie in project properties. I've attached a jboss-specific reproducer here, that uses jboss' repackaged jax-rs spec api. It shows both JAX-RS Support not being enabled and JAX-RS facet not being added to a jar web fragment project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1136) Sync with JBT 4.5.0.AM1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1136?page=com.atlassian.jira.plugin... ] Paul Leacu closed JBTIS-1136. ----------------------------- Fix Version/s: 11.0.0.AM1 Resolution: Done > Sync with JBT 4.5.0.AM1 > ----------------------- > > Key: JBTIS-1136 > URL: https://issues.jboss.org/browse/JBTIS-1136 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 11.0.0.AM1 > > > Sync with JBT 4.5.0.AM1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24650) Modify tooling UI to invoke command to retrieve the Docker registry

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24650: ---------------------------------- Summary: Modify tooling UI to invoke command to retrieve the Docker registry Key: JBIDE-24650 URL: https://issues.jboss.org/browse/JBIDE-24650 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk Affects Versions: 4.5.0.AM1 Reporter: Jeff MAURY Fix For: 4.5.x -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24649) Modify CDK server adapter to retrieve Docker registry

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24649: ---------------------------------- Summary: Modify CDK server adapter to retrieve Docker registry Key: JBIDE-24649 URL: https://issues.jboss.org/browse/JBIDE-24649 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk Affects Versions: 4.5.0.AM1 Reporter: Jeff MAURY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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