November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17550: ------------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3012) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3012: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3012 > URL: https://issues.jboss.org/browse/JBDS-3012 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 7.1.x > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3070) Mixed fonts in installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3070?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3070: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > Mixed fonts in installer > ------------------------ > > Key: JBDS-3070 > URL: https://issues.jboss.org/browse/JBDS-3070 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.0.x, 9.0.0.Alpha1 > > > since JBDS-3036 its become very obvious in the installer that the fonts are scrwed. > See http://screencast.com/t/ebR5zm1Cmmmw > On here is at least 3 or 4 different fonts. > Should use same clean fonts IMO -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3018: ----------------------------- Sprint: Sprint Beta2 CF, Sprint to CR1 Release (was: Sprint to CR1 Release) > Install screen moves to bottom left corner of the screen > -------------------------------------------------------- > > Key: JBDS-3018 > URL: https://issues.jboss.org/browse/JBDS-3018 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 7.1.1.GA > Environment: java version "1.8.0" > Java(TM) SE Runtime Environment (build 1.8.0-b132) > Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) > OSX 10.9.2 > One monitor > No additional software for windows management > Reporter: Arun Gupta > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.0.x, 9.0.x > > Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png > > > I started the install as > java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment. > This does not seem right. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3204) JBDS 8 workspace launcher is not shown in window list

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3204?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3204: ------------------------------------------- workaround: dont use gnome shell for java/swt apps. > JBDS 8 workspace launcher is not shown in window list > ----------------------------------------------------- > > Key: JBDS-3204 > URL: https://issues.jboss.org/browse/JBDS-3204 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Denis Golovin > > While launching JBDS 8.0.0 - if workspace launcher is in background of another focused window, I can't see it in windows list to switch to it. I need to manually minimize some windows to see it and use it. > This is experienced in Fedora 20 - Gnome Shell environment. I can say that the official Luna install of eclipse behave the same so it is a regression to JBDS 7 or Eclipse Kepler. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3199: ------------------------------ Component/s: upstream > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3199: ----------------------------- CDW pm_ack: + (was: ?) > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3198) HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3198?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3198: --------------------------------- Assignee: Michelle Murray (was: Fred Bricon) This is normal behaviour. The Sequence doesn't exist so therefore cannot be dropped at that point. It affects every example/quickstart/archetype that uses hibernate with the drop-create directive, which should only be used for demoing/prototyping stuff. Not sure where we should document this though. I would consider it as won't fix, but I'll let [~mmurray] decide whether it's worth documenting and where. > HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3198 > URL: https://issues.jboss.org/browse/JBDS-3198 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Michelle Murray > > Seeing this error when a newly created (default) HTML5 is created from Central and deployed to EAP. > 10:23:12,277 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export > 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: drop sequence hibernate_sequence > 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement: > drop sequence hibernate_sequence [90036-168] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18736) create python tooling to create new sprint/milestone targets in JBIDE/JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18736: --------------------------------------------- how about having the .tjp file reflect what is in jira - would that be an option ? > create python tooling to create new sprint/milestone targets in JBIDE/JBDS > -------------------------------------------------------------------------- > > Key: JBIDE-18736 > URL: https://issues.jboss.org/browse/JBIDE-18736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. > As part of that build, we can now > * generate updated Zimbra calendar > * generate new PP > In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. > This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18736) create python tooling to create new sprint/milestone targets in JBIDE/JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18736: --------------------------------------------- lets please first define how the sprints are done before we start automate this ;) > create python tooling to create new sprint/milestone targets in JBIDE/JBDS > -------------------------------------------------------------------------- > > Key: JBIDE-18736 > URL: https://issues.jboss.org/browse/JBIDE-18736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. > As part of that build, we can now > * generate updated Zimbra calendar > * generate new PP > In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA. > This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version ( https://issues.jboss.org/rest/api/2/version ) > Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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