October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12755) Forge is installed -> Forge feature isn't in installed fetures

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12755: --------------------------------------------- this indicate something is broken in the packaging -> Blocker. > Forge is installed -> Forge feature isn't in installed fetures > -------------------------------------------------------------- > > Key: JBIDE-12755 > URL: https://issues.jboss.org/browse/JBIDE-12755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, updatesite > Affects Versions: 4.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.0.0.CR1 > > Attachments: Forge.png > > > I have installed Forge in JBT 4.0.0.Alpha2a, but it isn't showing in Help->About Eclipse->Installation Details->Features (see attached image). > Because of this, Usage reporting cannot report Forge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12755) Forge is installed -> Forge feature isn't in installed fetures

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12755: ---------------------------------------- Priority: Blocker (was: Major) > Forge is installed -> Forge feature isn't in installed fetures > -------------------------------------------------------------- > > Key: JBIDE-12755 > URL: https://issues.jboss.org/browse/JBIDE-12755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, updatesite > Affects Versions: 4.0.0.Alpha2 > Reporter: Radim Hopp > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.0.0.CR1 > > Attachments: Forge.png > > > I have installed Forge in JBT 4.0.0.Alpha2a, but it isn't showing in Help->About Eclipse->Installation Details->Features (see attached image). > Because of this, Usage reporting cannot report Forge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12851) OpenShift Server Adapter wizard: link should point to creation wizard in case user don't have app/domain

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12851: -------------------------------------- Summary: OpenShift Server Adapter wizard: link should point to creation wizard in case user don't have app/domain Key: JBIDE-12851 URL: https://issues.jboss.org/browse/JBIDE-12851 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers, openshift Affects Versions: 4.0.0.Beta1 Reporter: Stefan Bunciak Assignee: Rob Stryker Fix For: 4.0.0.Beta1, 4.0.x In case the user doesn't have an application on openshift (or domain) link should point to Create OpenShift Application wizard not to the Import OpenShift Application wizard. Also the link could be named more appropriately in this case - user will be creating application, not importing. !newappserver.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1666) If a new namespace prefic is created in a .bpel file, the new namespace does not appear until the file is closed and re-opened - saving the file is not enough

by Len DiMaggio (JIRA)

If a new namespace prefic is created in a .bpel file, the new namespace does not appear until the file is closed and re-opened - saving the file is not enough -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1666 URL: https://issues.jboss.org/browse/JBDS-1666 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 Reporter: Len DiMaggio Attachments: Screenshot.png To recreate: Define a new namespace prefix in the source to a .bpel definition file - save the file. Note that if the prefix is deleted, it is removed from the prefix list when the .bpel file is saved. See attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
12
0 / 0

[JBoss JIRA] (JBDS-2214) SOA tooling BRMS needs update from jBPM 5.4.x to work with human task view

by Eric D. Schabell (JIRA)

13 years, 4 months

4
14
0 / 0

[JBoss JIRA] (JBDS-2341) CI job to build and publish jbds.target

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2341: ------------------------------------ Summary: CI job to build and publish jbds.target Key: JBDS-2341 URL: https://issues.jboss.org/browse/JBDS-2341 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Build Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 6.0.0.Beta1 JBDS uses different target-platforms than JBoss Tools, but consume it in the same way. So jbds.target should also have a build/verify/publish job on Jenkins, similar to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12003) Provide a way to ensure we provide usable Target Platforms

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12003: -------------------------------------- Summary: Provide a way to ensure we provide usable Target Platforms Key: JBIDE-12003 URL: https://issues.jboss.org/browse/JBIDE-12003 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng, target-platform Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.x, 3.4.x Since we often encounter issue with TP being not usable for both developers and builds, it highlight the fact that we have an issue in maintaining them correctly, which is a first necessary step towards getting them used. We should provide a way to ensure the TP we ship are usable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8192) Could not instantiate dialect class HibernateException when Database in CC is expanded

by Jiri Peterka (JIRA)

Could not instantiate dialect class HibernateException when Database in CC is expanded -------------------------------------------------------------------------------------- Key: JBIDE-8192 URL: https://issues.jboss.org/browse/JBIDE-8192 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Environment: JBDS 4.0.0.CR1 H88, Linux 64 Reporter: Jiri Peterka For example when creating dynamic web project and hibernate console (for precise steps see JBIDE-8189) when trying to expand HB CC -> Database for the FIRST TIME there is an HibernateException (see below). After "Rebuild Configuration" everything goes to normal. Exception is not always here but I saw it several times during few days. org.hibernate.HibernateException: Could not instantiate dialect class at org.hibernate.dialect.resolver.DialectFactory.constructDialect(DialectFactory.java:163) at org.hibernate.dialect.resolver.DialectFactory.buildDialect(DialectFactory.java:109) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:146) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2155) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:110) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.ClassCastException: org.hibernate.dialect.HSQLDialect cannot be cast to org.hibernate.dialect.Dialect at org.hibernate.dialect.resolver.DialectFactory.constructDialect(DialectFactory.java:157) ... 12 more rebuild -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
6
0 / 0

[JBoss JIRA] (JBDS-2271) JBDS 6 crashes

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-2271: --------------------------------------- Summary: JBDS 6 crashes Key: JBDS-2271 URL: https://issues.jboss.org/browse/JBDS-2271 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 6.0.0.Alpha1 Reporter: Andrej Podhradsky Assignee: Nick Boldt Priority: Blocker JBDS 6 crahes due to a bug in Eclipse Juno, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=383890 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
19
0 / 0

[JBoss JIRA] (JBIDE-12390) "Add missing required attribute(s)" quick fix for "Missing required attribute" WTP problem marker

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-12390: ------------------------------------- Summary: "Add missing required attribute(s)" quick fix for "Missing required attribute" WTP problem marker Key: JBIDE-12390 URL: https://issues.jboss.org/browse/JBIDE-12390 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.4.0.M1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
11
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 October 2012