May 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-19792?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-19792. --------------------------------- Closing, nothing to do. > antlr packages and lib not exported in Hibernate Tools 4.0.1 > ------------------------------------------------------------ > > Key: JBIDE-19792 > URL: https://issues.redhat.com/browse/JBIDE-19792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Final > Environment: Eclipse Luna SR2 > Reporter: Bastian Ulke > Assignee: Koen Aers > Priority: Major > Fix For: 4.3.x > > Attachments: B82_MANIFEST.MF, B95_MANIFEST.MF > > > I am currently working on an Eclipse-Plugin that is built on top of the > Hibernate Tools project. For example, I am using the following statements > to get the AST of a named query: > {code} > try { > HqlParser parser = HqlParser.getInstance(statementString); > parser.statement(); > } catch (RecognitionException | TokenStreamException e) { > e.printStackTrace(); > } > AST statementAst = parser.getAST(); > {code} > For this to work well with Hibernate Tools Version 4.0.0, I added bundle > org.hibernate.eclipse.libs as required bundle to my plug-in configuration > (which resolved to > org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far). > However, I now updated to Hiberate Tools 4.0.1 > (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I > have now is that the following imports cannot be resolved: > import antlr.RecognitionException; > import antlr.TokenStreamException; > import antlr.collections.AST; > The problem seems to arise from the fact, that in the new version's > MANIFEST.MF, the antlr... packages are not exported and > lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any > more (I reformatted both MANIFEST.MFs, that you can find attached, to allow > a convenient comparison). After manually adding the antlr-related entries > to the new version's MANIFEST.MF, my code works pretty well again. > I agree, that internal libraries should generally not be exported. However, > org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites? > (By the way, I'd be fine with integrating another library into my project. > However, I tried to manally add antlr-2.7.6.jar as library to > my project, which solved the compilation error, but yields a > java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by > org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-18570?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-18570. --------------------------------- Closing, nothing to do. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.redhat.com/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Priority: Major > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-19039?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-19039. --------------------------------- Closing, nothing to do. > Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19039 > URL: https://issues.redhat.com/browse/JBIDE-19039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, upstream > Affects Versions: 4.2.2.Final > Reporter: Pavol Srna > Assignee: Snjezana Peco > Priority: Major > Fix For: LATER > > Attachments: forge-scaffold-window.png, other-wizard.png > > > Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard. > You can see on the screenshots how it looks when you have your monitor in portrait orientation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14099) CLONE - Project Archives incorrectly loading saved .packages

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-14099?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-14099. --------------------------------- Closing, nothing to do. > CLONE - Project Archives incorrectly loading saved .packages > ------------------------------------------------------------ > > Key: JBIDE-14099 > URL: https://issues.redhat.com/browse/JBIDE-14099 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.0.2.Final > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15687) For JBIDE 4.1.1.Beta1: Code Freeze + Branch [JST]

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-15687?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-15687. --------------------------------- Closing, nothing to do. > For JBIDE 4.1.1.Beta1: Code Freeze + Branch [JST] > ------------------------------------------------- > > Key: JBIDE-15687 > URL: https://issues.redhat.com/browse/JBIDE-15687 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.1.1.Beta1 > > > For JBIDE 4.1.1.Beta1 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Beta1 > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.31.0.Final # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.31.1.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Beta1x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Beta1x > git push origin jbosstools-4.1.1.Beta1x > {code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17666) memory usage keeps growing even on processes that does nothing

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-17666?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-17666. --------------------------------- Closing, nothing to do. > memory usage keeps growing even on processes that does nothing > -------------------------------------------------------------- > > Key: JBIDE-17666 > URL: https://issues.redhat.com/browse/JBIDE-17666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Max Andersen > Assignee: Rob Stryker > Priority: Major > Fix For: 4.2.x > > > I noticed that when enabling the timeline graphs the memory usage just seem to constantly increase with every poll. even for apps that does nothing. > Seems like we are not freeing memory in the agent or something ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13720) Add JBoss Portal Platform (JPP) 6.0.0 to downloadable runtimes

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-13720?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-13720. --------------------------------- Closing, nothing to do. > Add JBoss Portal Platform (JPP) 6.0.0 to downloadable runtimes > -------------------------------------------------------------- > > Key: JBIDE-13720 > URL: https://issues.redhat.com/browse/JBIDE-13720 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Reporter: Peter Palaga > Assignee: Max Andersen > Priority: Major > > Please post downloadId here when fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13780) Create" New and Noteworthy" for 4.0.1.Final

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-13780?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-13780. --------------------------------- Closing, nothing to do. > Create" New and Noteworthy" for 4.0.1.Final > ------------------------------------------- > > Key: JBIDE-13780 > URL: https://issues.redhat.com/browse/JBIDE-13780 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: help > Affects Versions: 4.0.1.Final > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Major > Fix For: 4.0.1.Final > > > [Fixed issues|https://issues.jboss.org/issues/?filter=12318972] to document. > Affected components are: > - JBoss AS > - Archives > - Struts > - Maven -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3549) Providing APIs for getting the output message of the jboss server through WTP server adaptor

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-3549?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-3549. -------------------------------- Closing, nothing to do. > Providing APIs for getting the output message of the jboss server through WTP server adaptor > --------------------------------------------------------------------------------------------- > > Key: JBIDE-3549 > URL: https://issues.redhat.com/browse/JBIDE-3549 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: LATER > Reporter: Denny Xu > Assignee: Rob Stryker > Priority: Major > Fix For: LATER > > > Rob, I am trying to develop a Test UI for ESB service, I would like to have APIs to get the console output of a running server so that I can show the result message on TestUI page after a Test action is executed. > since there might be a lot of application running on the server, and there maybe a lots of outputs during a period , so if we can only get the output of a specified application, that would be better. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-13340?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-13340. --------------------------------- Closing, nothing to do. > An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13340 > URL: https://issues.redhat.com/browse/JBIDE-13340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.0.Final > Environment: Windows 7 > Eclipse Juno 64 bit > Jdk 1.7 64 bit > Reporter: andrea tomassi > Assignee: Rob Stryker > Priority: Major > Labels: jboss > Fix For: LATER > > Attachments: Img0.png, Img2.png, img1.png > > > 1) Install JBoss Tools version 4.0 (Juno) > 2) Create a new workspace > 3) Select Java EE Eclipse perspective > 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final) > 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options) > 5) Click with right mouse button on the server, than select "Add and Remove...". > 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0) > 7) Create a Dynamic Web Project (default options) > 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1) > 9) Click again with right mouse button on the server, than select "Add and Remove...". > 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 2020