May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18829) Add BPMN2 and teiid to tracked usage tooling components

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18829?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18829. ------------------------------ Verified in JBDS 9.0.0.Alpha2. Closing. > Add BPMN2 and teiid to tracked usage tooling components > ------------------------------------------------------- > > Key: JBIDE-18829 > URL: https://issues.jboss.org/browse/JBIDE-18829 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19697: --------------------------------------------- If oomph records anything about usage that is a bug since I did open this bug back in february to get that fixed. https://bugs.eclipse.org/bugs/show_bug.cgi?id=459455 > 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-19758) when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /static/releases for archiving

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19758: ---------------------------------- Summary: when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /static/releases for archiving Key: JBIDE-19758 URL: https://issues.jboss.org/browse/JBIDE-19758 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.2.3.Final Reporter: Nick Boldt Seems somewhere between 4.2.x and 4.3.x we stopped moving /builds/staging/jbosstools-4.2.x.Final-* folders into /static/releases/ Need to fix that (by hand) and ensure we don't forget to do this for any future 4.2.x releases (if any happen). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- I guess the bug is coupled with browser initialization. Basically, if one roll up visual/source tab the content would appear - https://youtu.be/-hGYMD8UBL8 > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-431. ------------------------------ Fix Version/s: 4.2.3.CR1a-TP Resolution: Done > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > Assignee: Paul Leacu > Fix For: 4.2.3.CR1a-TP > > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3431: ------------------------------------- [~mhusnain], I believe the conclusion here was to use EAP 6.x for JBDS 8.0 and 8.1, instead of listing EAP 6.0, 6.1, 6.2, 6.3, 6.4. Can you use that? But I have one concern here. [~mmusaji], you say we can't say JBDS 6 supports EAP 6.x now, because EAP 6.4 will surely not work (there were some changes in EAP 6.1 requiring a new server adapter). But isn't that exactly what we're doing with JBDS 8 now? We will say we support JBDS 8.1 with EAP 6.x. But then if hypothetically there is EAP 6.5 that requires some changes a year from now when JBDS 9 is already out, saying JBDS 8.1 supports EAP 6.x will no longer be true. But perhaps we can deal with such situation if it really happens. Another possibility is to use .x only for currently newest versions and once we have a new version, we can retrospectively specify the exact version numbers for JBDS 8.1 to reflect the reality at the time. > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3433?page=com.atlassian.jira.plugin.... ] Martin Malina resolved JBDS-3433. --------------------------------- Resolution: Duplicate Issue Sorry, this is already covered in JBDS-3431. > 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)

10 years, 11 months

1
0
0 / 0

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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-423: ---------------------------------- I'm actually talking about both connector IDs and category IDs. Here's the issue - lets look at Fuse. Here's the released Fuse connector: {code}  <connectorDescriptor categoryId="com.jboss.jbds.central.discovery.integration-stack.bundle" groupId="com.jboss.jbds.central.discovery.integration-stack.bundle-fuse" certificationId="com.jboss.jbds.discovery.certification.supported" kind="task" license="Free, EPL" provider="JBoss by Red Hat" siteUrl="${jboss.discovery.site.integration-stack.url}" name="JBoss Fuse Development" description="Tools related to integrating software components that work with Apache ServiceMix, ActiveMQ and Camel - support for Fuse." id="jboss.integration-stack.bundle.fuse"> <iu id="org.fusesource.ide.camel.editor.feature"/> <iu id="org.fusesource.ide.core.feature"/> <iu id="org.fusesource.ide.fabric8.feature"/> <iu id="org.fusesource.ide.jmx.feature"/> <iu id="org.fusesource.ide.server.extensions.feature"/> <icon image32="images/jbds_icon32.png"> </icon> <overview url="http://fusesource.com/products/fuse-ide/"> </overview> </connectorDescriptor> {code} Here is the EA connector: {code}  <connectorDescriptor categoryId="com.jboss.jbds.central.discovery.integration-stack.ea.bundle" groupId="com.jboss.jbds.central.discovery.integration-stack.ea.bundle-fuse" certificationId="com.jboss.jbds.discovery.certification.earlyaccess" kind="task" license="Free, EPL" provider="JBoss by Red Hat" siteUrl="${jboss.discovery.site.integration-stack.url}" name="JBoss Fuse Development" description="Tools related to Fuse Tooling data mapping and transformation." id="jboss.integration-stack.bundle.fuse.ea"> <iu id="org.jboss.tools.fuse.transformation.feature"/> <icon image32="images/jbds_icon32.png"> </icon> <overview url="http://devstudio.redhat.com/"> </overview> </connectorDescriptor> {code} The particular relevant info is the connector ID (jboss.integration-stack.bundle.fuse, jboss.integration-stack.bundle.fuse.ea) and the category ID. Since the connector content is different between EA and released (Fuse tooling has components of both EA and released), if a user were to enable early access with the same connector ID they would only see the EA Fuse content (the released content is not visible). If they have different IDs then both are selectable. The only proxy wizard we have is for Fuse and that sits on the released side. Since the released side IDs are not changed future updates will work okay. The unique situation I have is having production connectors in both EA and released. > 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)

10 years, 11 months

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 commented on JBIDE-18508: ------------------------------------- So the underlying problem is events sent went reopening projects are not sorted per project dependency. So the EAR is configured first, then the EJB. Given we're still on the same workspace lock, no other events are sent, to tell the EAR that EJB has been imported. This needs to be fixed in m2e, but that will require delicate tuning, because projects dependency needs to be fully loaded when the events are sent, which can only happen ... after some events were sent. Typical chicken-egg problem. Given the workaround is simply to force project configuration update, I'll punt that issue for a while. > 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)

10 years, 11 months

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 edited comment on JBIDE-18508 at 5/4/15 10:16 AM: -------------------------------------------------------------- So the underlying problem is events sent when reopening projects are not sorted per project dependency. So the EAR is configured first, then the EJB. Given we're still on the same workspace lock, no other events are sent, to tell the EAR that EJB has been imported. This needs to be fixed in m2e, but that will require delicate tuning, because projects dependency needs to be fully loaded when the events are sent, which can only happen ... after some events were sent. Typical chicken-egg problem. Given the workaround is simply to force project configuration update, I'll punt that issue for a while. was (Author: fbricon): So the underlying problem is events sent went reopening projects are not sorted per project dependency. So the EAR is configured first, then the EJB. Given we're still on the same workspace lock, no other events are sent, to tell the EAR that EJB has been imported. This needs to be fixed in m2e, but that will require delicate tuning, because projects dependency needs to be fully loaded when the events are sent, which can only happen ... after some events were sent. Typical chicken-egg problem. Given the workaround is simply to force project configuration update, I'll punt that issue for a while. > 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)

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