April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19696) Rename of an exception class does not work properly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19696?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19696: ----------------------------------- Sprint: Sprint #2 April 2015 > Rename of an exception class does not work properly > --------------------------------------------------- > > Key: JBIDE-19696 > URL: https://issues.jboss.org/browse/JBIDE-19696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > When I try to rename an exception class RenamableException to RenamableException2, I get batch.RenamableException2enamableException in job XML file instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19696) Rename of an exception class does not work properly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19696?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19696: -------------------------------------- Assignee: Daniel Azarov > Rename of an exception class does not work properly > --------------------------------------------------- > > Key: JBIDE-19696 > URL: https://issues.jboss.org/browse/JBIDE-19696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > When I try to rename an exception class RenamableException to RenamableException2, I get batch.RenamableException2enamableException in job XML file instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19696) Rename of an exception class does not work properly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19696?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19696: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Rename of an exception class does not work properly > --------------------------------------------------- > > Key: JBIDE-19696 > URL: https://issues.jboss.org/browse/JBIDE-19696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Priority: Critical > Fix For: 4.3.0.Beta1 > > > When I try to rename an exception class RenamableException to RenamableException2, I get batch.RenamableException2enamableException in job XML file instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19689) Add isWarning to JobUtils

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19689?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19689: ----------------------------------- Issue Type: Task (was: Feature Request) > Add isWarning to JobUtils > ------------------------- > > Key: JBIDE-19689 > URL: https://issues.jboss.org/browse/JBIDE-19689 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19689) Add isWarning to JobUtils

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19689?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19689: ----------------------------------- Sprint: Sprint #2 April 2015 > Add isWarning to JobUtils > ------------------------- > > Key: JBIDE-19689 > URL: https://issues.jboss.org/browse/JBIDE-19689 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19689) Add isWarning to JobUtils

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19689?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19689: ----------------------------------- Component/s: common/jst/core > Add isWarning to JobUtils > ------------------------- > > Key: JBIDE-19689 > URL: https://issues.jboss.org/browse/JBIDE-19689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19695) Annoying message "Be sure, may be you also should rename setter methods to avoid compilation problems."

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19695?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19695: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Annoying message "Be sure, may be you also should rename setter methods to avoid compilation problems." > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19695 > URL: https://issues.jboss.org/browse/JBIDE-19695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.3.Final > Reporter: Clovis Seragiotto > Fix For: 4.3.0.Beta1 > > Attachments: after installation.png, renaming a get method.png, Version chosen.png > > > When renaming a get-method in Eclipse, the warning "Be sure, may be you also should rename setter methods to avoid compilation problems." is displayed. > It should be possible to turn this warning off (and the sentence should be fixed). > By Googling the message, I found: > JBoss Tools SVN: r40216 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core. > That is why I suppose the right component is seam. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19694: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Angular Explorer doesn't show anything > -------------------------------------- > > Key: JBIDE-19694 > URL: https://issues.jboss.org/browse/JBIDE-19694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Beta1 > > > # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source > # Checkout step-12 branch of imported project > # Open Angular Explorer > # Open index.html file of angular-phonecat project > ERROR: Angular Explorer is empty. It should contain angular controllers and modules > Was working fine with JBDS 8.1.0.GA and the same project configuration -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-429: -------------------------------- Summary: JBDSIS 8.0.2 component updates Key: JBTIS-429 URL: https://issues.jboss.org/browse/JBTIS-429 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 8.0.1.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 8.0.2.GA Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-416: ---------------------------------- Hey [~mhusnain] - I should have generated this in your Jira. Is there any way to get this paragraph into the 8.0.1.GA release notes? If not then just comment as such and I'll close it. > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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