May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3433) Add EAP 6.4 to support matrix for JBDS 8.1

by Martin Malina (JIRA)

Martin Malina created JBDS-3433: ----------------------------------- Summary: Add EAP 6.4 to support matrix for JBDS 8.1 Key: JBDS-3433 URL: https://issues.jboss.org/browse/JBDS-3433 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: documentation Affects Versions: 8.1.0.GA Reporter: Martin Malina Assignee: Misha Ali Last week, [~mmusaji] suggested we add EAP 6.4 to the support matrix: {quote} Reading [1], I think this needs to be changed so that 8.0 and 8.1.0 list different supported EAP versions? Misha, can you update it based on the answers to the following? - Does JBDS 8.0 support EAP 6.4.0? I don't believe EAP 6.4.0 was tested against JBDS 8.0.0 - EAP 6.4.0 should be listed under supported EAP versions for JBDS 8.1.0 Thanks Mus [1] https://access.redhat.com/articles/427493 {quote} I conducted testing of EAP 6.4 with JBDS 8.1 and found no issues, so I believe we can go ahead and add 6.4 to the document. But in my opinion we don't have to distinguish JBDS 8.0 and 8.1 - there were no changes made to support 6.4, it works exactly the same way like 6.3, using the same EAP 6.1+ server adapter. So I think we're fine just adding 6.4 to JBDS 8.0/8.1 in the document. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18508: -------------------------------- Fix Version/s: LATER (was: 4.3.x) > EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening > ------------------------------------------------------------------------------------- > > Key: JBIDE-18508 > URL: https://issues.jboss.org/browse/JBIDE-18508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.1.2.Final > Reporter: Marek Schmidt > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: LATER > > Attachments: seam-restbay-src.zip > > > EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening > 0. setup the redhat techpreview/all maven repository > 1. Import the (attached) project as Maven project > 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3) > 3. Close all 4 subprojects of the restbay project > 4. reopen all the restbay projects > 5. now the application will automatically redeploy > 6. this redeployment will result in a failure. > If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3408: ------------------------------------------- two things: 1) great its "just" the stas 2) sucks that the stats are reporting as if they are JBoss Tools 9.0's, with no job_name - seems we are missing something in our p2 metadata to actually make that url proper and possibly(?) report to devstudio.redhat.com instead ? > 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: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > 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)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-434) Some features are duplicated on Update Site in site.xml

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-434?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-434. ------------------------------ Fix Version/s: 4.2.2.CR1 8.0.1.CR1 Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/commit/dee6b6a... > Some features are duplicated on Update Site in site.xml > ------------------------------------------------------- > > Key: JBTIS-434 > URL: https://issues.jboss.org/browse/JBTIS-434 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.2.2.Final > Environment: JBDSIS 8.0.2.ER1 > Reporter: Tomáš Sedmík > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.2.2.CR1, 8.0.1.CR1 > > > Runtime detectors in _site.xml_ on Update Site are duplicated see: > http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... > {code} > ... > <feature id="org.jboss.tools.runtime.drools.detector.feature" url="features/org.jboss.tools.runtime.drools.detector.feature_6.2.0.Final.jar" version="6.2.0.Final"> > <category name="BusinessLogic"/> > <category name="SOADev"/> > <category name="SOADev5"/> > </feature> > <feature id="org.jboss.tools.runtime.esb.detector.feature" url="features/org.jboss.tools.runtime.esb.detector.feature_1.5.530.Final-v20150310-1957-B70.jar" version="1.5.530.Final-v20150310-1957-B70"> > <category name="SOADev5"/> > </feature> > <feature id="org.jboss.tools.runtime.jbpm.detector.feature" url="features/org.jboss.tools.runtime.jbpm.detector.feature_4.5.200.Final-v20130815-1941-B2008.jar" version="4.5.200.Final-v20130815-1941-B2008"> > <category name="SOADev"/> > <category name="SOADev5"/> > </feature> > ... >  > <feature id="org.jboss.tools.runtime.drools.detector.feature"/> > <feature id="org.jboss.tools.runtime.esb.detector.feature"/> > <feature id="org.jboss.tools.runtime.jbpm.detector.feature"/> > ... > {code} > IMHO there should be only one entry for one feature -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-423: ------------------------------------------- Just to be clear, are you talking about connector ids or category id's ? multiple connection id we *cannot* live with - it will break the proxy wizards unless you also want to maintain them. multiple category ID's we can live with, but I think we should fix that issue instead of working around it. Do you know *why* it happens ? afaik you should just not declare the category twice. > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19752) Update mylyn UI test method names to better integrate with Polarion

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19752?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-19752. -------------------------------- PR merged and closed - closing the JIRA. > Update mylyn UI test method names to better integrate with Polarion > ------------------------------------------------------------------- > > Key: JBIDE-19752 > URL: https://issues.jboss.org/browse/JBIDE-19752 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19752) Update mylyn UI test method names to better integrate with Polarion

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19752?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-19752. ---------------------------------- Resolution: Done > Update mylyn UI test method names to better integrate with Polarion > ------------------------------------------------------------------- > > Key: JBIDE-19752 > URL: https://issues.jboss.org/browse/JBIDE-19752 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19697: ---------------------------------- Attachment: pref-recorder.png I tried to verify if (with default settings) new instance of Eclipse will ask users about usage tracking or not. First odd thing is that the Preference Recorder preference page already contains the usage preferences: !pref-recorder.png! How did it get there I don't know - it's a new Eclipse, new workspace and I wiped ~/.eclipse beforehand. Anyway, it's not checked, so it should not be recorded. I installed JBT, restarted Eclipse, and the usage window popped up. The I repeated this a second time - new eclipse, new workspace, installed JBT, restarted. And... surprise, surprise ... it asked me again if I want to report usage. So that looks fine. > 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)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-19704: --------------------------------------- JBDS 8.1.0.CR1 build ID B449: Tried both,JSF and HTML5 support, and I had empty pane under "Preview" tab but there was a content under "Visual/Source" tab. > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.0.Beta1 > > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-433) MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-433?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-433: -------------------------------- Assignee: Paul Leacu > MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1 > ------------------------------------------------- > > Key: JBTIS-433 > URL: https://issues.jboss.org/browse/JBTIS-433 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Current build of JBDS-IS 8.0.2.ER1 contains MASTER build of Fuse tooling, namely 7.3.0.v20150428-1634-H488-MASTER. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 1 month

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