[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19792?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-19792.
-------------------------------
Resolution: Rejected
I will reject this issue. Please feel free to reopen with additional arguments if you feel there is still something we can do to help you.
> antlr packages and lib not exported in Hibernate Tools 4.0.1
> ------------------------------------------------------------
>
> Key: JBIDE-19792
> URL: https://issues.jboss.org/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
> 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.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1057) Fuse: Fix Project creation test
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-1057:
-----------------------------------
Summary: Fuse: Fix Project creation test
Key: JBTIS-1057
URL: https://issues.jboss.org/browse/JBTIS-1057
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.1.Final
Reporter: Tomáš Sedmík
Assignee: Tomáš Sedmík
Priority: Blocker
Fix For: 4.4.2.CR1
Timeout exceeded
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1056) Fuse: Fix regression tests
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-1056:
-----------------------------------
Summary: Fuse: Fix regression tests
Key: JBTIS-1056
URL: https://issues.jboss.org/browse/JBTIS-1056
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.1.Final
Reporter: Tomáš Sedmík
Assignee: Tomáš Sedmík
Priority: Blocker
Fix For: 4.4.2.CR1
Regression tests are failing
{code}
Failed tests:
RegressionTest.issue_1694:429 Problems view contains errors
Tests in error:
RegressionTest.issue_1115:188 » WaitTimeoutExpired Timeout after: 10 s.: widge...
RegressionTest.issue_1158:264 » CoreLayer No matching widget found with Matche...
RegressionTest.issue_2062:603 » WaitTimeoutExpired Timeout after: 300 s.: cons...
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24043) Upversion jbosstools-server in master and maintenance
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24043?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-24043.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
pushed it.
> Upversion jbosstools-server in master and maintenance
> -----------------------------------------------------
>
> Key: JBIDE-24043
> URL: https://issues.jboss.org/browse/JBIDE-24043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.4.AM1, 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM1, 4.5.0.AM1
>
>
> In maintenance:
> archives from 3.6.103 to 3.6.104
> jmx from 1.8.3 to 1.9.0 bc of API change
> wtp from 1.3.103 to 1.3.104
> AS from 3.2.3 to 3.2.4
> In Master
> archives from 3.6.103 to 3.6.110 to leave room in case of emergency
> jmx from 1.8.3 to 1.10.0 to leave room and also bc I expect further changes
> wtp from 1.3.103 to 1.3.110 to leave room in case of emergency
> AS from 3.2.3 to 3.3.0 because I expect API additions and new features
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24043) Upversion jbosstools-server in master and maintenance
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24043?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24043:
--------------------------------
Fix Version/s: 4.4.4.AM1
4.5.0.AM1
> Upversion jbosstools-server in master and maintenance
> -----------------------------------------------------
>
> Key: JBIDE-24043
> URL: https://issues.jboss.org/browse/JBIDE-24043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.4.AM1, 4.5.0.AM1
> Reporter: Rob Stryker
> Fix For: 4.4.4.AM1, 4.5.0.AM1
>
>
> In maintenance:
> archives from 3.6.103 to 3.6.104
> jmx from 1.8.3 to 1.9.0 bc of API change
> wtp from 1.3.103 to 1.3.104
> AS from 3.2.3 to 3.2.4
> In Master
> archives from 3.6.103 to 3.6.110 to leave room in case of emergency
> jmx from 1.8.3 to 1.10.0 to leave room and also bc I expect further changes
> wtp from 1.3.103 to 1.3.110 to leave room in case of emergency
> AS from 3.2.3 to 3.3.0 because I expect API additions and new features
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ERT-493) "org.eclipse.wst.jsdt.js.node" is requiring "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, and this is not into 4.6.2 build [EBZ#513341]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-493:
---------------------------------------
Summary: "org.eclipse.wst.jsdt.js.node" is requiring "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, and this is not into 4.6.2 build [EBZ#513341]
Key: ERT-493
URL: https://issues.jboss.org/browse/ERT-493
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Bundle "org.eclipse.wst.jsdt.js.node 1.0.0.v201608102114" requires exactly bundle "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, but this is not in the 4.6.2 GA build, the available version of this bundle into the 4.6.2 build is "0.5.0".
See the MANIFEST:
Manifest-Version: 1.0
Bundle-SymbolicName: org.eclipse.wst.jsdt.js.node;singleton:=true
Archiver-Version: Plexus Archiver
Built-By: genie.webtools
Require-Bundle: org.eclipse.ui,org.eclipse.core.runtime,org.eclipse.co
re.resources;bundle-version="[3.10.1,4.0.0)",org.eclipse.wst.jsdt.js.
common,org.eclipse.wst.jsdt.core,org.eclipse.debug.ui,org.eclipse.ui.
ide;bundle-version="[3.11.0,4.0.0)",org.eclipse.core.variables,org.ec
lipse.core.expressions,com.google.gson;bundle-version="[2.2.4,3.0.0)"
,org.eclipse.wst.jsdt.js.node.common,org.eclipse.debug.core,org.eclip
se.wst.jsdt.chromium.debug.core;bundle-version="0.4.0",org.eclipse.ws
t.jsdt.chromium;bundle-version="0.4.0",org.eclipse.wst.jsdt.chromium.
debug;bundle-version="0.4.0",org.eclipse.wst.jsdt.chromium.debug.ui;b
undle-version="[0.6.0,0.7.0)"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22382:
-------------------------------------
To avoid cluttering our jiras every sprint, I'll retarget this to 4.5.0.Final or something. Please ping / email me directly if the status here changes.
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Fix For: 4.5.0.Final
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years