January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21066) Extra step in opening terminal in git perspective?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21066: ----------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.x) > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20535) wildfly-bmt quickstart fails with unsupported content validation error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20535: ------------------------------------- [~snjeza] Most of these bugs are only replicatable in the 9.x branch. The 10.x branch seems to have removed most of their descriptors entirely, preferring annotation. > wildfly-bmt quickstart fails with unsupported content validation error > ---------------------------------------------------------------------- > > Key: JBIDE-20535 > URL: https://issues.jboss.org/browse/JBIDE-20535 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Snjezana Peco > Fix For: 4.3.x, 4.4.0.Alpha1 > > > Importing the above quickstart fails validation with the following (cryptic) error: > The persistence.xml file does not have supported content for this JPA platform. > Stack-overflow on a similar topic: http://stackoverflow.com/questions/3701901/eclipse-does-not-recognize-con... > Link to bugzilla from 2008 that claims issue is fixed: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251323 > I have absolutely no idea how to fix this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20538?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20538: ------------------------------------- There are no errors in the 10.x stream of the quickstarts, because there are no longer ejb descriptor files ;) In the 9.x stream, this still fails. However, adding the followign to the namespace declarations seems to fix the primary error: {code} http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd {code} This fix is courtesy of Keith Chong, over at https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 > wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error > --------------------------------------------------------------------- > > Key: JBIDE-20538 > URL: https://issues.jboss.org/browse/JBIDE-20538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Labels: xml_validation_schema_error > Fix For: 4.4.0.Alpha1 > > > Root cause here seems to be that the xsd on the web url http://www.jboss.org/schema/jbossas/jboss-ejb3-spec-2_0.xsd has a schemaLocation=jboss-ejb3-2_0.xsd relative path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20538?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20538: ------------------------------------- I don't see any errors in this quickstart anymore (?) Anyone else able to verify? > wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error > --------------------------------------------------------------------- > > Key: JBIDE-20538 > URL: https://issues.jboss.org/browse/JBIDE-20538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Labels: xml_validation_schema_error > Fix For: 4.4.0.Alpha1 > > > Root cause here seems to be that the xsd on the web url http://www.jboss.org/schema/jbossas/jboss-ejb3-spec-2_0.xsd has a schemaLocation=jboss-ejb3-2_0.xsd relative path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20540) Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20540: ------------------------------------- Upstream closed the issue last month. It seems they added the following to our namespace declaration in our example xml file, but made no changes to any schema at all. {code} http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd {code} So it seems our examples might be missing this? > Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd > ---------------------------------------------------------------- > > Key: JBIDE-20540 > URL: https://issues.jboss.org/browse/JBIDE-20540 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) Extra step in opening terminal in git perspective?

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21066: --------------------------------------- The issue has been fixed in the master and the 4.0.0_mars_bugfix branch of the org.eclipse.tm.terminal.git project (Aug 11, 2015). JBT includes the 4.0.0.201505101440 version of this plugin (http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...) so that the fix isn't included in the JBT target platform. > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21533) Create New and Noteworthy for 4.3.1.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21533?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21533: -------------------------------------- Assignee: Alexey Kazakov > Create New and Noteworthy for 4.3.1.Beta2 > ----------------------------------------- > > Key: JBIDE-21533 > URL: https://issues.jboss.org/browse/JBIDE-21533 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21584) Forge is missing default values in some wizards

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21584?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21584: ----------------------------------------- That is a consequence of the stacks support. I'll fix it and release Forge 3.0.0.Beta4 > Forge is missing default values in some wizards > ------------------------------------------------ > > Key: JBIDE-21584 > URL: https://issues.jboss.org/browse/JBIDE-21584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-01-26 at 17.51.24.png, Screen Shot 2016-01-26 at 17.52.02.png > > > Forge is missing default values in some wizards . Please see the screenshots. It used to be prefilled with default values (in previous versions of forge). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21371. ------------------------------- Resolution: Done Labels: new_and_noteworthy openshift_v3 server_adapter (was: openshift_v3 server_adapter) Reopening to add NN label > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21371 > URL: https://issues.jboss.org/browse/JBIDE-21371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter, new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21429) Add support for LiveReload

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21429?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21429: -------------------------------- Labels: new_and_noteworthy (was: ) > Add support for LiveReload > -------------------------- > > Key: JBIDE-21429 > URL: https://issues.jboss.org/browse/JBIDE-21429 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > The openshift 3 servers should have the Show In > ...Live Reload... menus > Live Reload enabled pages would reload automatically upon publishing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016