July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24653) include latest Windup built with Oxygen

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24653?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24653: ------------------------------- Fix Version/s: 4.5.0.AM2 > include latest Windup built with Oxygen > --------------------------------------- > > Key: JBIDE-24653 > URL: https://issues.jboss.org/browse/JBIDE-24653 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Fix For: 4.5.0.AM2 > > > Once [~jsteele] has it ready, update Central to include the latest Windup bits built with Oxygen. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24653) include latest Windup built with Oxygen

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24653: ---------------------------------- Summary: include latest Windup built with Oxygen Key: JBIDE-24653 URL: https://issues.jboss.org/browse/JBIDE-24653 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central-update Affects Versions: 4.5.0.AM2 Reporter: Nick Boldt Once [~jsteele] has it ready, update Central to include the latest Windup bits built with Oxygen. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform & Central to Oxygen.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24652: ------------------------------- Summary: update target platform & Central to Oxygen.0+ (was: update target platform to Oxygen.0+) > update target platform & Central to Oxygen.0+ > --------------------------------------------- > > Key: JBIDE-24652 > URL: https://issues.jboss.org/browse/JBIDE-24652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Fix For: 4.5.0.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform & Central to Oxygen.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24652?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24652: ---------------------------------- Assignee: Nick Boldt > update target platform & Central to Oxygen.0+ > --------------------------------------------- > > Key: JBIDE-24652 > URL: https://issues.jboss.org/browse/JBIDE-24652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform & Central to Oxygen.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24652: ------------------------------- Fix Version/s: 4.5.0.AM2 > update target platform & Central to Oxygen.0+ > --------------------------------------------- > > Key: JBIDE-24652 > URL: https://issues.jboss.org/browse/JBIDE-24652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform to Oxygen.0+

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24652: ---------------------------------- Summary: update target platform to Oxygen.0+ Key: JBIDE-24652 URL: https://issues.jboss.org/browse/JBIDE-24652 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.5.0.AM2 Reporter: Nick Boldt Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1137) Update Drools TP for Oxygen

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1137: --------------------------------- Summary: Update Drools TP for Oxygen Key: JBTIS-1137 URL: https://issues.jboss.org/browse/JBTIS-1137 Project: JBoss Tools Integration Stack Issue Type: Task Components: drools/ jBPM Affects Versions: 11.1.0.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 11.1.0.GA Update the Drools IS TP to 4.5.0.Final when available. Kris: Regarding the target platform, it's fine to update the community master to that (assuming it's a stable / released target platform, not a snapshot). We should have another community release by Aug hopefully ;) -- 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24651?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24651: ------------------------------------ [~fbricon] any comments ? > 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 > Components: webservices > Affects Versions: 4.4.4.Final > Environment: JBDS 10.4.0.GA > Reporter: Vsevolod Golovanov > Fix For: 4.5.x > > 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24651?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24651: ------------------------------- Component/s: webservices > 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 > Components: webservices > Affects Versions: 4.4.4.Final > Environment: JBDS 10.4.0.GA > Reporter: Vsevolod Golovanov > Fix For: 4.5.x > > 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24651?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24651: ------------------------------- Fix Version/s: 4.5.x > 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 > Fix For: 4.5.x > > 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

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