[JBoss JIRA] (JBIDE-12465) Disable runtimes swtbot test plugin
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-12465?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-12465.
---------------------------------
Closing, nothing to do.
> Disable runtimes swtbot test plugin
> -----------------------------------
>
> Key: JBIDE-12465
> URL: https://issues.redhat.com/browse/JBIDE-12465
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: runtime-detection
> Affects Versions: 4.0.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Snjezana Peco
> Priority: Major
> Fix For: 4.0.0.Alpha1
>
>
> The swtbot test in runtimes (org.jboss.tools.runtime.as.ui.bot.test) has several problems.
> 1) It is improperly named. It is not just testing "as", it is also testing seam.
> 2) It is an all-encompassing UI test.
> 3) It is preventing the pushdown of runtimes from a top-level component to a low-level component. It's implied dependencies make the move impossible
> 4) As per max, QE has been instructed to find a new location for their swtbot tests.
> This plugin will be disabled immediately.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-13082) Add a reconnect button for MBean Explorer
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-13082?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-13082.
---------------------------------
Closing, nothing to do.
> Add a reconnect button for MBean Explorer
> -----------------------------------------
>
> Key: JBIDE-13082
> URL: https://issues.redhat.com/browse/JBIDE-13082
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jmx
> Affects Versions: 4.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.0.x
>
> Attachments: mbeans.png
>
>
> Now that JBIDE-12900 is done it is possible to disconnect and reconnect a jmx connection in MBean explorer. But this feature is well hidden - you need to right-click the server in the MBean Explorer and select Disconnect and then Connect again. It would be nice if this was more obvious - like a refresh button next to the button for New Connection.
> !mbeans.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[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, 5 months
[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, 5 months
[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, 5 months