July 2014 - jbosstools-issues - Jboss List Archives

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3012: -------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta3) Sprint: Sprint to CR1 Release (was: Sprint to Beta3 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 > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > 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.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17772) Include Forge 2.7.0

by Koen Aers (JIRA)

Koen Aers created JBIDE-17772: --------------------------------- Summary: Include Forge 2.7.0 Key: JBIDE-17772 URL: https://issues.jboss.org/browse/JBIDE-17772 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Priority: Blocker Fix For: 4.2.0.Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17759) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17759?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-17759. ----------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Hibernate] > ------------------------------------------------------- > > Key: JBIDE-17759 > URL: https://issues.jboss.org/browse/JBIDE-17759 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Hibernate]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17720) Can't install ADT from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17720?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17720. ------------------------------ Resolution: Done Not sure how you determined that my PR was to install bundles instead of features, since the change was simply to rename the existing list of features to include .feature in their name. Before and after the PR, Central is still installing features, because Central can ONLY install features. It doesn't know what a plugin is. However you ARE correct that the ADT connector only installs *some* of ADT: it includes only the parts that do NOT depend on CDT. Which coincidentally is stated in the plugin.xml and also visible in my PR. :D So... closing again. As to what users will see if they had the old ADT installed, no idea. I can't reproduce that because the ADT site only has the latest. I suspect they'll have to uninstall and then install the new version. Or they'll be presented w/ remediation. Central will likely report that they don't have ADT installed because the IU list compared to what's installed will show that it's not (fully) installed. Until someone can produce the scenario of "old version of ADT already installed, what happens w/ Beta3 version of Central Discovery" I can't know for sure. Maybe we can wait for a user to report a problem and address it then? > Can't install ADT from Central > ------------------------------ > > Key: JBIDE-17720 > URL: https://issues.jboss.org/browse/JBIDE-17720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > Attachments: ADT23.0-installed-prompts-for-new-SDK-install.png, adtinstallationerror0.png, adtinstallationerror1.png > > > Installation tests are failing to install Android Development Tools from Central. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-17700: -------------------------------------------- [~olpf] Had you run Forge before the time of this exception occurring? > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Priority: Critical > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17723) Display current selection in Forge Command Selector menu and Forge Wizards

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17723?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17723: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Display current selection in Forge Command Selector menu and Forge Wizards > -------------------------------------------------------------------------- > > Key: JBIDE-17723 > URL: https://issues.jboss.org/browse/JBIDE-17723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > Please consult with [~maxandersen] for how this should look, but the current UISelection needs to be displayed at the top of Forge wizards and the forge command picker menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17274) Support JPA 2.1 in Hibernate Tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17274?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17274: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Support JPA 2.1 in Hibernate Tools > ---------------------------------- > > Key: JBIDE-17274 > URL: https://issues.jboss.org/browse/JBIDE-17274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Until now Hibernate tools "survived" that Hibernate 3.5+ could load hibernate 3 and 4 projects metadata without problems. > With JPA 2.1 this changed and it requires Hibernate 4.3+ to load these metadata. > We could update hibernate tools to use hibernate 4.3 to load the metadata but in doing so we would gain support for JPA 2.1 but at least loose support for loading Hibernate 3.3-4.2+ projects that uses custom user types (there could be more combinations that fails - figuring out how much requires a lot of work, but for now at least we know the usertypes are not binary compatible anymore). > To fix this a rethink/reimplementation is needed of how hibernate tools works. > It basicallly needs to become completely independent of hibernate binaries/classes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17565) test failure due to timeout in hibernatetools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17565?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17565: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > test failure due to timeout in hibernatetools > --------------------------------------------- > > Key: JBIDE-17565 > URL: https://issues.jboss.org/browse/JBIDE-17565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: hibernate-test-fail.log > > > {code:https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-hibernate_4.2.luna/50/console} > [INFO] Expected eclipse log file: /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/tests/org.hibernate.eclipse.console.test/target/work/data/.metadata/.log > [INFO] Command line: > [/qa/tools/opt/x86_64/jdk1.6.0_45/jre/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, -javaagent:/mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/.repository/org/jacoco/org.jacoco.agent/0.7.1.201405082137/org.jacoco.agent-0.7.1.201405082137-runtime.jar=destfile=/mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/target/jacoco.exec,append=true,includes=org.hibernate.eclipse*, -Xms512m, -Xmx1024m, -XX:PermSize=256m, -XX:MaxPermSize=256m, -Dusage_reporting_enabled=false, -Dorg.jboss.tools.tests.skipPrivateRequirements=false, -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true, -Dosgi.clean=true, -jar, /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20140415-2008/org.eclipse.equinox.launcher-1.3.0.v20140415-2008.jar, -data, /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/tests/org.hibernate.eclipse.console.test/target/work/data, -install, /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/tests/org.hibernate.eclipse.console.test/target/work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/tests/org.hibernate.eclipse.console.test/target/work/configuration, -application, org.eclipse.tycho.surefire.osgibooter.uitest, -testproperties, /mnt/hudson_workspace/workspace/jbosstools-hibernate_4.2.luna/sources/tests/org.hibernate.eclipse.console.test/target/surefire.properties, -product, org.hibernate.eclipse.console.test.product] > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.hibernate.eclipse.console.test.ConsolePluginAllTests > ===================================================== > .. > Unable to set nested messages property. > [ERROR] Timeout 3600 s exceeded. Process was killed. > [INFO] org.hibernate.eclipse.console.test ................ FAILURE [1:00:15.102s] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17622) Remove "Experimental" label from Forge2 features when no longer incubating

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17622?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17622: ------------------------------------ Great, thanks. Now just triage your remaining issues and you can branch for Beta3. :) > Remove "Experimental" label from Forge2 features when no longer incubating > -------------------------------------------------------------------------- > > Key: JBIDE-17622 > URL: https://issues.jboss.org/browse/JBIDE-17622 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > Forge has 2 features which append " (Experimental)" onto their descriptions. > If these features are ready for prime-time, this qualifier should be removed. > Affected files: > https://github.com/jbosstools/jbosstools-forge/blob/master/features/org.j... > https://github.com/jbosstools/jbosstools-forge/blob/master/features/org.j... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15288) Invalid persistence.xml error when opening hibernate console for JPA 2.1 project

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15288?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-15288: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Invalid persistence.xml error when opening hibernate console for JPA 2.1 project > -------------------------------------------------------------------------------- > > Key: JBIDE-15288 > URL: https://issues.jboss.org/browse/JBIDE-15288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.CR1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Error while expanding JPA project with JPA 2.1 > This works ok when JPA 2.0 is used > {code} > org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration > Could not create JPA based Configuration > <No message> > java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException: <no message> > java.lang.reflect.InvocationTargetException > javax.persistence.PersistenceException: Invalid persistence.xml. > Error parsing XML (line-1 : column -1): cvc-elt.1: Cannot find the declaration of element 'persistence'. > Invalid persistence.xml. > Error parsing XML (line-1 : column -1): cvc-elt.1: Cannot find the declaration of element 'persistence'. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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