May 2015 - jbosstools-dev - Jboss List Archives

Improvement for the N&N "Related JIRA" macro in the website

by Xavier Coulon

Hello, FYI, I just fixed https://issues.jboss.org/browse/JBIDE-19588 <https://issues.jboss.org/browse/JBIDE-19588> and took the opportunity to improve the "related_jira" macro that we use to link a N&N entry to one or more issues in JIRA. You may now include the title of the issue in the brackets as below: related_jira::JBIDE-19113[Update of wildfly jars] This will render as follow in the web page: "Related JIRA: JBIDE-19113 - Update of wildfly jars <https://issues.jboss.org/browse/JBIDE-19113>" If you don't specify any attribute in the macro, the link title will just be the issue number. Best regards, /Xavier

9 years, 7 months

1
0
0 / 0

If you are still hesitating whether to buy medications at our pharmacy, read our testimonials!

by New-Canadian-Meds

Miler to know about parlors for individualized programs james actually. Publicist, so awesome, is costly liang, et al pastor. Me ds 0f or 0M en Vi Ci Ci Le Pr ag al al vi op ra is is tr ec S a ia of t Ta bs $0 $1 $2 $2 $0 .9 .6 .5 .5 .4 9 5 0 0 5 Me ds 3f or 2W om en Ac Cl De Fe Fe om om fl ma ma pl id uc le le ia an C V ia ia li gr s a $1 $0 $1 $1 $0 .7 .4 .2 .1 .7 5 5 5 1 2 24 Fa On An /7 st ly on c w r ym us or el ou to ld ia s me wi bl de r de e li su s su ve pp hi pp ry or pp li t in er g s S V N 1 pe is o 00 ci a, pr % al Ma es Au i st cr th nt er ip en er ca ti ti ne rd on c t ,E r Me pr ch eq ds ic ec ui es k re d >> Enter Here

9 years, 7 months

1
0
0 / 0

Java 8 experiement for JBoss Tools 4.3/Developer studio 9

by Max Rydahl Andersen

Hey, We are going to make Java 8 required for upcoming Beta1. To see what kind of reaction we will get on moving to Java 8. This does *not* mean you should add Java 8 features to the codebase. We will still compile with Java 7 where we can, as we might be required to support Java 7 before GA. Thus don't get too excited - but at least be happy users will run with a faster Java with better memory management! /max http://about.me/maxandersen

9 years, 7 months

3
6
0 / 0

ACTION REQUIRED: Update target platform 4.50.0.Beta1-SNAPSHOT to Mars M7

by Nick Boldt

Here is a proposal for a change to the JBoss Tools and Red Hat JBoss Developer Studio 4.50.0.Beta1-SNAPSHOT target platforms. https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ It consists in the following change(s): * JBIDE-19776: Create and use Mars M7 target-platform p2diff reports: https://issues.jboss.org/secure/attachment/12389427/jbosstools.p2diff.txt https://issues.jboss.org/secure/attachment/12389428/jbdevstudio.p2diff.txt Please review the above PR(s), as it will be applied as soon as possible. You can use the following to build & test the target-platform locally against your component(s). Build target-platform: cd jbosstools-target-platforms/jbosstools/multiple git checkout https://github.com/jbosstools/jbosstools-target-platforms/pull/142/ mvn clean install Or, without hub: cd jbosstools-target-platforms/jbosstools/multiple git fetch origin pull/142/head && git checkout FETCH_HEAD mvn clean install Try with just built target-platform: $ cd /path/to/your/component $ mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT -Pmultiple.target -- If you want to perform a scripted install of the entire target platform into your local Eclipse or JBDS instance, you can now do so with this script: https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... Usage is documented in the above script, and in this README: https://github.com/jbosstools/jbosstools-target-platforms/tree/master#upd... -- -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

9 years, 7 months

5
7
0 / 0

ACTION REQUIRED: Can we move up to requiring JUnit 4.12 instead of 3.8? (4.50.0.Beta1-SNAPSHOT target platform w/ Mars M7)

by Nick Boldt

The following projects have plugins or features which depend on JUnit 3.8. Can they be changed to use JUnit 4.12, which is the version included in the latest 4.50.0.Beta1-SNAPSHOT target platform and Mars M7? * base * bpel * central * forge * hibernate * javaee * jst * portlet * vpe Or do we need to find a way to include JUnit 3.8 as well as JUnit 4.12? Details here: https://issues.jboss.org/browse/JBIDE-19836 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

9 years, 7 months

4
6
0 / 0

antlr packages and lib not exported in Hibernate Tools 4.0.1

by Bastian Ugimachi

Dear all, 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: try { HqlParser parser = HqlParser.getInstance(statementString); parser.statement(); } catch (RecognitionException | TokenStreamException e) { e.printStackTrace(); } AST statementAst = parser.getAST(); 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. My question is thus: (a) Do you consider this to be a bug in the realease of Hibernate Tools 4.0.1? (b) If yes for (a): Do you have an idea when this issue could be solved? (c) If no for (a): Which alternative solution would you suggest? I mean, manually editing the MANIFEST.MF of realeased plug-ins is not quite the best practice, is it? 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 Any advice? Thanks! Bastian

9 years, 7 months

3
5
0 / 0

ACTION REQUIRED: 1 issue with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBIDE-19819 https://issues.jboss.org/browse/JBIDE-19819 Summary: Installing JBT 4.3.0.Alpha2 on eclipse Mars M6 breaks icons Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 14:03:27.958188 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

9 years, 7 months

1
0
0 / 0

Where can I download jboss messaging 1.4.7.GA?

by Rajkumar Rajaratnam

Hi, Can someone please tell me how to download jboss messaging 1.4.7.GA pre built binaries? Thanks. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com

9 years, 7 months

2
1
0 / 0

Some updates on new terminal

by Rob Stryker

Hi All: So I've discovered by more code-browsing that the new tm terminal view makes their internal viewer public API. This should easily allow someone like Lars to use the viewer and embed it into their own view. I havent' yet discovered if their public API is sufficient for Lars to simply call and open a specific connection type in the existing view. I have learned, however, that o.e.remote does not plan to use their view, but rather will use the viewer itself and create 'consoles' out of it... via IConsoleManager and the associated UI. You can find their code in git://git.eclipse.org/gitroot/ptp/org.eclipse.remote.git in the bundles/org.eclipse.remote.console/ folder. I've also opened bugs to ensure that this plugin at least has public API to open a console for a given o.e.remote IRemoteConnection object, which I've just had accepted. https://bugs.eclipse.org/bugs/show_bug.cgi?id=467350#add_comment Either way, whether Lars in the future wants to make his servers exposable via o.e.remote and implement an IRemoteCommandShellService (which I haven't investigated how easy this part is yet, but I suspect its not difficult) or if he wants to simply keep his view but change the implementation to use the new public API viewers inside, it should work as expected. There's enough code in existence now that provide PoCs and should make converting his console fairly easy. It would be really nice if Lars had a Mars branch and TP available, though. But it seems he won't get that far for quite a while, so I took the lead on making sure API was sufficient. Does anyone else depend on the terminal situation other than Lars? It'd be great if specific usecases could be laid out for how it's being used right now and what fucntionality is needed in future impls. - Rob Stryker

9 years, 7 months

3
4
0 / 0

Sprint #3 closed, Sprint #4 started ...

by Max Rydahl Andersen

Heya, Closed Sprint #3 this morning. https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=641&view=report... 21 issues done, 49+ issues not done. Either our sprints are too short or jiras too big :) I've started Sprint #4 with end date June 5th, which is 3 weeks from now - the day after code freeze for Beta1. That at least tries to fixe the "sprints are too" short issue. Let's not put stuff on the sprints if we can't make them happen. Thanks, /max http://about.me/maxandersen

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev May 2015