September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18181) Errors when hibernate.cfg.xml not at classpath root

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18181?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18181: --------------------------------------------- this patch definitely looks more like it. I say apply it and we'll see if other issues are found. > Errors when hibernate.cfg.xml not at classpath root > --------------------------------------------------- > > Key: JBIDE-18181 > URL: https://issues.jboss.org/browse/JBIDE-18181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599, Hibernate 4.1.12 > Reporter: Luke Maurer > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > If a project keeps its hibernate.cfg.xml anywhere besides the root of the classpath, Hibernate Tools will not recognize it. In the Hibernate Configurations tree, expanding either Session Factory or Database gives an error ending in “/hibernate.cfg.xml not found”. (The Configuration subtree appears to work.) > As a workaround, if I go into the directory holding WEB-INF/classes (i.e. where compiled Java bytecode goes) and symlink hibernate.cfg.xml there, it seems to work. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3009) use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3009?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-3009. ---------------------------- I searched jbosstools-base and jbdevstudio-product for devstudio.jboss.com with no success. Supposing this was resolved correctly. Closing. > use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3009 > URL: https://issues.jboss.org/browse/JBDS-3009 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 8.0.0.CR1 > > Attachments: ssl-enabled-for-filemgmt-but-at-what-cost.png > > > use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates) > Affected files: *.xml, *.inf, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18246) Hyperlink navigation based on Name Binding doesn't work

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18246?page=com.atlassian.jira.plugi... ] Radoslav Rábara commented on JBIDE-18246: ----------------------------------------- Hi [~xcoulon], the problem is that I don't have the same behaviour. It works in JBDS 8.0.0 Beta3 but not in CR1. > Hyperlink navigation based on Name Binding doesn't work > ------------------------------------------------------- > > Key: JBIDE-18246 > URL: https://issues.jboss.org/browse/JBIDE-18246 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18246_screenshot.png, JBIDE-18246_screenshot2.png > > > Hyperlink navigation based on Name Binding doesn't work. Ctrl (or cmd) + click on annotation, which is annotated with @NameBinding, doesn't open pop-up with navigation between appropriate classes. > See http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta1.html... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18246) Hyperlink navigation based on Name Binding doesn't work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18246?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18246: ---------------------------------- Attachment: JBIDE-18246_screenshot.png JBIDE-18246_screenshot2.png [~rrabara], {{Ctrl}} or {{Cmd}} + {{mouse hover}} on the custom name binding annotation on a type opens the dialog. Do you have the same behaviour ? OTOH, there is no such navigation when {{Ctrl}} or {{Cmd}} + {{mouse hover}} on the {{@NameBinding}} annotation. Is it the problem you wanted to report ? > Hyperlink navigation based on Name Binding doesn't work > ------------------------------------------------------- > > Key: JBIDE-18246 > URL: https://issues.jboss.org/browse/JBIDE-18246 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18246_screenshot.png, JBIDE-18246_screenshot2.png > > > Hyperlink navigation based on Name Binding doesn't work. Ctrl (or cmd) + click on annotation, which is annotated with @NameBinding, doesn't open pop-up with navigation between appropriate classes. > See http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta1.html... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-297) Update JBTIS TP and composites for BPMN2 Modeler

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-297?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-297. ------------------------------ Resolution: Done Picked up latest SwitchYard 2.0.0. https://github.com/jbosstools/jbosstools-integration-stack/commit/a390a30... > Update JBTIS TP and composites for BPMN2 Modeler > ------------------------------------------------ > > Key: JBTIS-297 > URL: https://issues.jboss.org/browse/JBTIS-297 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPMN2 > Affects Versions: 4.2.0.Alpha7-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Alpha8-TP > > > Update the JBTIS TP 4.2.0.Alpha8 with > http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1... >  > - <unit id="org.eclipse.bpmn2.modeler.feature.feature.group" version="1.0.2.201402102317"/> > - <unit id="org.eclipse.bpmn2.modeler.jboss.runtime.feature.feature.group" version="1.0.2.201402102317"/> > - <repository location="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1..."/> > + <unit id="org.eclipse.bpmn2.modeler.feature.group" version="1.1.0.201408072130"/> > + <unit id="org.eclipse.bpmn2.modeler.runtime.jboss.feature.group" version="1.1.0.201408072130"/> > + <repository location="http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1..."/> > org.eclipse.bpmn2.modeler.feature is now org.eclipse.bpmn2.modeler and > org.eclipse.bpmn2.modeler.jboss.runtime.feature is now org.eclipse.bpmn2.modeler.runtime.jboss > Then have SwitchYard build its 2.0.0.Alpha3 and create the JBTIS Alpha2 release. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18004) Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18004?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18004: --------------------------------------------- okey- but I would discourage IMO since it would make the action users would need to do behave differently than what the cheatsheet is doing... > Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18004 > URL: https://issues.jboss.org/browse/JBIDE-18004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > > The name of the command to be executed should be accepted as a parameter so that it can be directly launched from an Eclipse cheatsheet, instead of merely guiding the user to the quick access menu. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3139: ------------------------------------------- [~mickael_istria] what unit do you mean to move ? normal central should have angularjs with ionic, early access ionnic+angularjs for eclipse > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18128: ------------------------------------- Just an update, but nothing found yet. When i import the project as a maven project, I see no .java files, and so no .class files either. I've verified I have m2e-wtp installed. The pom.xml has the following error: {code} Failure to transfer org.codehaus.mojo:aspectj-maven-plugin:pom:1.5 from https://repository.jboss.org/nexus/ content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of jboss-plugins has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.mojo:aspectj-maven-plugin:pom:1.5 from/to jboss-plugins (https://repository.jboss.org/nexus/ content/groups/public): Connect to squid.corp.redhat.com:3128 [squid.corp.redhat.com/10.68.5.41] failed: Connection refused {code} This seems strange to me, because my network connection setting in eclipse is set to "direct", so proxy is not enabled. Also, the imported project does not have any wtp facets or natures installed on it, and is not deployable to the server at all. Not sure what's going on here. I'll ask someone else to replicate. > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Attachments: jboss-test.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3139: -------------------------------------- Actually, it seems like angularjs is required for 'normal' discovery (not only earlyaccess), so this unit needs to be moved the jbtcentraltarget instead of jbtearlyaccesstarget. > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15825?page=com.atlassian.jira.plugi... ] Radoslav Rábara edited comment on JBIDE-15825 at 9/3/14 9:36 AM: ----------------------------------------------------------------- Reopening - doesn't work in JBDS 8.0.0 CR1-v20140831-0335-B201 was (Author: rrabara): Doesn't work in JBDS 8.0.0 CR1-v20140831-0335-B201 > JAX-RS problems don't show up after target runtime is set > --------------------------------------------------------- > > Key: JBIDE-15825 > URL: https://issues.jboss.org/browse/JBIDE-15825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > JAX-RS problems don't show up after target runtime is set on project that was created with target runtime set to <None>. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014