April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- Max, there is a PR with latest updates - https://github.com/jbosstools/jbosstools-versionwatch/pull/1 > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19190: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-versionwatch/pull/1 > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-19605: ------------------------------------------- Interesting. I wonder then if we need the bundle at all? > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19605: --------------------------------------- [~bfitzpat], No, the https://github.com/jbosstools/jbosstools-webservices/blob/master/plugins/... only defines {{String}} constants that are later used to match specific class names, but the JAX-RS tooling does not depend on the {{javax.servlet}} bundle. > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-416: ---------------------------------- Thanks Misha - looks good to me. [~apodhrad] - what do you think? > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19708: -------------------------------- Component/s: server > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19708: ----------------------------------- Assignee: Rob Stryker > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3408: ---------------------------------- I'll try to reproduce with one of the latest builds here http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18348. ------------------------------ Resolution: Done Done: JBIDE-19708. Closing this one. > Add support for WildFly 9 > ------------------------- > > Key: JBIDE-18348 > URL: https://issues.jboss.org/browse/JBIDE-18348 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > > Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS. > I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue. > Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow. > Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3408: ---------------------------------- This might be a consequence of one or more of the update sites within the JBDS installer not having had its associate sites scrubbed out (to remove all feature.xml refs to upstream URLs at eclipse.org or jboss.org). If so, might be a dupe of what caused JBDS-3423. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 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 April 2015