February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3322: -------------------------------------- Priority: Minor (was: Major) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3322: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.x) > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3285: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.x) > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): > {quote} > Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace". > We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough. > There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport. > There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point. > I invite you to give it a try, and to report issues here. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18008. ------------------------------------ > Nested jars prevent SonarQube/FindBugs from running > --------------------------------------------------- > > Key: JBIDE-18008 > URL: https://issues.jboss.org/browse/JBIDE-18008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, build, qa > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes). > Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1] > {code} > This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest > Also, the jvmmonitor bundles use nested jars. We should avoid that too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18750) Make CDI validation messages dependent on version

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18750?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18750. ------------------------------------ verified in JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Make CDI validation messages dependent on version > ------------------------------------------------- > > Key: JBIDE-18750 > URL: https://issues.jboss.org/browse/JBIDE-18750 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: cdi10.png, CDI12.png > > > All cdi validation messages in our tool now reference JSR-299, which is CDI 1.0. Validation of CDI 1.1 and 1.2 project should reference JSR-346, besides numbers of sections for many messages are changed. Even if in most cases wording of a message may remain the same, the necessity to provide relevant references requires separating messages for each version. That will also let change wording as needed. > The proposed solution to the task is such that in cases when a validation rule logic is the same through several versions, its implementation will not be affected other than by replacing MY_MESSAGE by MY_MESSAGE[versionIndex]. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3364: ------------------------------------------- What was done in JBDS-2456 if not include the sources ? What parts are we missing? > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19372) JBDS Central isn't sure if jst.angularjs feature is EA or not

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19372?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19372. --------------------------------------- Resolution: Rejected This works as expected. The whole point of Central is that we have some *stable* id's for connectors which depending on it is in community, product or earlyaccess status can give install different things depending on the context. *including* installing newer/different versions of what is already installed - in this case jst.angularjs normally just have our ionic js support but in early access we include anguljarjs eclipse tooling. Thus this is perfectly valid and expected. > JBDS Central isn't sure if jst.angularjs feature is EA or not > ------------------------------------------------------------- > > Key: JBIDE-19372 > URL: https://issues.jboss.org/browse/JBIDE-19372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Attachments: 001_jbds81-central-EA-disabled.png, 002_jbds81-central-EA-enabled.png > > > 1. Installed JBDS 8.0.0 > 2. Attempted to install *JBoss Hybrid Mobile Tools + CordovaSim* from the nightly site, http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.2.luna/ and as a result updated to 8.1.0.Beta1, as part of p2 remediation. But jst.angularjs feature was NOT installed, because the version available is still 3.6.1.Final and JBDS 8.1.0.Beta1 includes 3.6.2.Beta1. (Separate issue, see JBIDE-19370.) > 3. Now when I start up Central again, I can see the same *JBoss Hybrid Mobile Tools + CordovaSim* connector available, but it won't let me install the jst.angularjs feature. > 4. There's also the *AngularJS for Web Tools* connector, which attempts to install the same missing feature. But that one is supposed to be Early Access. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19189) NullPointerException in TablePropertiesBlock.doAdd

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19189?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19189: ----------------------------------- [~akazakov] Can you please take a look at the PR? > NullPointerException in TablePropertiesBlock.doAdd > -------------------------------------------------- > > Key: JBIDE-19189 > URL: https://issues.jboss.org/browse/JBIDE-19189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.2.Final > Environment: eclipse.buildId=4.4.1.M20140925-0400 > java.version=1.8.0_31 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE > Command-line arguments: -os win32 -ws win32 -arch x86_64 > Reporter: Michael Kolowicz > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > I want to develop a small prototype of a application. I have create a database on MySQL 5.6 on a remote server. They have only 1 table (It´s like a easy prototype). The table have a Id-column. > I using the eclipse 4.4.1 (on Windows 7 x64 - german), Hibernate 4.3.8, Hibernate Tools 4.0.0 (Final). > Installation is a fresh downloaded eclipse with all actual updates. In the application is added the JDBC for MySQL and the Hibernate-Core Files. > BTW: If i use Eclipse 4.3 with the same database, then the columns can be added an no error come up. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Anton Meller (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Anton Meller updated JBIDE-19376: --------------------------------- Attachment: 20150224_threaddump-1424762289905.tdump 20150225_threaddump-1424847077811.tdump 20150225_threaddump-1424847803263.tdump 20150226_threaddump-1424936318015.tdump The todays dump ("20150226_xxx") is from the current tools version (4.2.2.Final), the older three from the previous version I had installed, so the line numbers can differ. > Eclipse freezes at or short after startup > ----------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or short after startup

by Anton Meller (JIRA)

Anton Meller created JBIDE-19376: ------------------------------------ Summary: Eclipse freezes at or short after startup Key: JBIDE-19376 URL: https://issues.jboss.org/browse/JBIDE-19376 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 4.2.2.Final Environment: Eclipse Luna EE. Reporter: Anton Meller Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 February 2015