May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-439) Add XMLBeans to TP

by Keith Babo (JIRA)

Keith Babo created JBTIS-439: -------------------------------- Summary: Add XMLBeans to TP Key: JBTIS-439 URL: https://issues.jboss.org/browse/JBTIS-439 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: Fuse IDE, target-platform Affects Versions: 4.3.0.Alpha1 Reporter: Keith Babo Fix For: 4.3.0.Alpha1 Fuse Data Transformation tooling relies on XMLBeans to generate an XML schema from an XML instance document in order to support the generation of model classes for XML source/target. We currently bundle xmlbeans inside the data transformation plugin within Fuse IDE. *Project page/sources:* http://xmlbeans.apache.org/ *Version:* 2.6.0 (no hard requirement on this specific version that I know of) *License and owner:* ALv2 *Original p2 repo:* unknown *JBoss mirror:* unknown *Include Sources:* Yes *Affected projects:* Fuse IDE *Include in JBDS:* unknown *Type of dependency:* unknown *non-p2 repository:* https://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/2.6.0/xmlbean... Looks like there is a prior version of xmlbeans in Orbit already: http://download.eclipse.org/tools/orbit/downloads/drops/R20150124073747/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-438) Add JAXB XJC to TP

by Keith Babo (JIRA)

[ https://issues.jboss.org/browse/JBTIS-438?page=com.atlassian.jira.plugin.... ] Keith Babo updated JBTIS-438: ----------------------------- Fix Version/s: 4.3.0.Alpha1 > Add JAXB XJC to TP > ------------------ > > Key: JBTIS-438 > URL: https://issues.jboss.org/browse/JBTIS-438 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: Fuse IDE, target-platform > Reporter: Keith Babo > Fix For: 4.3.0.Alpha1 > > > Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). > We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. > *Project page/sources:* https://jaxb.java.net/ > *Version:* 2.2.7 (no hard requirement on this specific version that I know of) > *License and owner:* CDDL v1.1 and GPL v2 > *Original p2 repo:* unknown > *JBoss mirror:* unknown > *Include Sources:* Yes > *Affected projects:* Fuse IDE > *Include in JBDS:* unknown > *Type of dependency:* unknown > *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-438) Add JAXB XJC to TP

by Keith Babo (JIRA)

Keith Babo created JBTIS-438: -------------------------------- Summary: Add JAXB XJC to TP Key: JBTIS-438 URL: https://issues.jboss.org/browse/JBTIS-438 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: Fuse IDE, target-platform Reporter: Keith Babo Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. *Project page/sources:* https://jaxb.java.net/ *Version:* 2.2.7 (no hard requirement on this specific version that I know of) *License and owner:* CDDL v1.1 and GPL v2 *Original p2 repo:* unknown *JBoss mirror:* unknown *Include Sources:* Yes *Affected projects:* Fuse IDE *Include in JBDS:* unknown *Type of dependency:* unknown *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19457) implement wtp servertools integration with "launchbar"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19457?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19457. --------------------------------- Resolution: Rejected Duplicate of JBIDE-19711 > implement wtp servertools integration with "launchbar" > ------------------------------------------------------- > > Key: JBIDE-19457 > URL: https://issues.jboss.org/browse/JBIDE-19457 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > The launchbar is a new concept introduced in CDT (with no cdt deps) that allows for a more extensible and faster launching experience. > This should integrate with the run as -> Run on server APIs to enhance synnergy and other cool buzzwords. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19697. --------------------------------- Resolution: Rejected As far as I can tell, this is not a bug ;) Please feel free to re-open if I've completely misread the comment history. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: pref-recorder.png, preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19770) linux distro not tracked reliable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19770?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-19770 at 5/11/15 4:55 PM: ----------------------------------------------------------------- I think I now know the reason of this weird data. The Unknown distro is actually *not linux* system for most cases. We had this bug from the very beginning. We do not check OS at all when defining the User Defined Value. If no linux distro is found then we report it's as Unknown. Check this out: 1. There is a big number of unset value for last 3 years (92%). But if you check the JBT version of all unset values then you see that all of them are old JBT releases when we didn't have that distro detection: [Link1|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] And BTW, do you see it keeps declining (new versions are being released and are not reporting unset values). 2. If you take a look at the last 30 days only then you see that "unset" value is just ~ 9% (they must come from the old versions as well). But the majority (82%) is Unknown: [Link2|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] 3. OK. Let's see what OS actually reports these Unknown linux distros. 99,82% of them are Windows & Linux. And just 0.15% of "Unknown Linux Disrto" are actually Linux: [Link3|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] I will fix this issue, so Unknown value will be reported only for Linux system. was (Author: akazakov): I think I now know the reason of this weird data. The Unknown distro is actually *not linux* system for most cases. We had this bug from the very beginning. We do not check OS at all when defining the User Defined Value. If no linux distro is found then we report it's as Unknown. Check this out: 1. There is a big number of unset value for last 3 years (92%). But if you check the JBT version of all unset values then you see that all of them are old JBT releases when we didn't have that distro detection: [Link1|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] 2. If you take a look at the last 30 days only then you see that "unset" value is just ~ 9% (they must come from the old versions as well). But the majority (82%) is Unknown: [Link2|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] 3. OK. Let's see what OS actually reports these Unknown linux distros. 99,82% of them are Windows & Linux. And just 0.15% of "Unknown Linux Disrto" are actually Linux: [Link3|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] I will fix this issue, so Unknown value will be reported only for Linux system. > linux distro not tracked reliable > --------------------------------- > > Key: JBIDE-19770 > URL: https://issues.jboss.org/browse/JBIDE-19770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > user defined value is not set in ~50% of cases of linux users. > https://www.google.com/analytics/web/?hl=en#report/content-pages/a1764536... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19770) linux distro not tracked reliable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19770?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19770: ---------------------------------------- I think I now know the reason of this weird data. The Unknown distro is actually *not linux* system for most cases. We had this bug from the very beginning. We do not check OS at all when defining the User Defined Value. If no linux distro is found then we report it's as Unknown. Check this out: 1. There is a big number of unset value for last 3 years (92%). But if you check the JBT version of all unset values then you see that all of them are old JBT releases when we didn't have that distro detection: [Link1|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] 2. If you take a look at the last 30 days only then you see that "unset" value is just ~ 9% (they must come from the old versions as well). But the majority (82%) is Unknown: [Link2|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] 3. OK. Let's see what OS actually reports these Unknown linux distros. 99,82% of them are Windows & Linux. And just 0.15% of "Unknown Linux Disrto" are actually Linux: [Link3|https://www.google.com/analytics/web/?hl=en#report/content-pages/a1...] I will fix this issue, so Unknown value will be reported only for Linux system. > linux distro not tracked reliable > --------------------------------- > > Key: JBIDE-19770 > URL: https://issues.jboss.org/browse/JBIDE-19770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > user defined value is not set in ~50% of cases of linux users. > https://www.google.com/analytics/web/?hl=en#report/content-pages/a1764536... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- Also check if its replicatable on other operating systems please ;) thanks > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19776: ------------------------------------- I suppose anything's possible, but it would be pretty foolish to allow our users to only get HALF of the new terminal feature. > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ Can't you use a telnet or ssh terminal to connect to localhost? > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015