August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20355) oc location preferences: location is not validated, no help is provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20355?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20355: ------------------------------------------ this was merged and pushed to upstream/master > oc location preferences: location is not validated, no help is provided > ----------------------------------------------------------------------- > > Key: JBIDE-20355 > URL: https://issues.jboss.org/browse/JBIDE-20355 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Labels: help_wanted, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: oc-binary-path-not-validated.png > > > # EXEC: go to OpenShift v3 preferences (Window->Preferences->OpenShift v3) > # EXEC: hit "Browse" and choose any file (ex. /tmp/test.txt) > Result: > The preferences wont validate your choice. Whatever you pick is used. > !oc-binary-path-not-validated.png! > There also is no explanation to what this "oc binary" is. A dummy user would have no idea what this is all about > Expected: > The preferences should do basic tests like > * is it executable? > * is it an "oc" binary > ...and add some explanations on what "oc binary" is and how to obtain it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20071: --------------------------------------------- [~nogotiated] please open bug describing your setup. We should most definitely not see performance go 3x slower for this. [~rob.stryker] sounds like we need to have this "agressive exploded jars" be something to optional turn on (or off) ? are we at least not exploding bundled jars and only exploding users modules ? > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20450) Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20450?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-20450: ----------------------------------- This issue has been popping up and disappearing for a some time now. Everything builds smoothly locally. I have discussed this with [~maxandersen] and he suggested it could have to do something with the build machine configuration (which as I understand is not always the same when Hudson launches a build). > Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test > ----------------------------------------------------------------------- > > Key: JBIDE-20450 > URL: https://issues.jboss.org/browse/JBIDE-20450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: testfailure > Fix For: 4.3.0.CR1 > > Attachments: org.hibernate.eclipse.console.test.log.txt > > > *Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... > Yet no test failures are logged, presumably because the test fails too early for logging to be done: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20454) Create tests for the ICriteria facade implementations

by Koen Aers (JIRA)

Koen Aers created JBIDE-20454: --------------------------------- Summary: Create tests for the ICriteria facade implementations Key: JBIDE-20454 URL: https://issues.jboss.org/browse/JBIDE-20454 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.3.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20445) Create tests for the IColumn facade implementations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20445?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20445. ------------------------------- Assignee: Koen Aers Resolution: Done > Create tests for the IColumn facade implementations > --------------------------------------------------- > > Key: JBIDE-20445 > URL: https://issues.jboss.org/browse/JBIDE-20445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20446) Hibernate 5.0 support

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20446?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-20446: ----------------------------------- I actually have been investigating this for some time already. The first hurdle to take is bringing the core Hibernate Tools up to date as there are breaking API changes in Hibernate 5. When that is done a new Hibernate runtime plugin with Hibernate 5. Because of the breaking API changes this will probably also require a substantial amount of implementation compared to the other Hibernate runtime plugins. Not sure if this is all feasible for 9.0 GA. I already had some discussions about it with [~maxandersen] and he has decided it may be a nice to have but not on the critical path for 9.0. > Hibernate 5.0 support > --------------------- > > Key: JBIDE-20446 > URL: https://issues.jboss.org/browse/JBIDE-20446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.0.CR1 > > > Hibernate 5.0 is close to be released (CR4 at the time of writing this JIRA). JBoss Tools Hibernate Tools should support this latest version. Would be good to have it in JBDS 9.0.GA at least in form of early access or experimental feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19410. ------------------------------- Then it's verified. Thanks a lot [~dgolovin]. Closing. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: need-info > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19410: --------------------------------------- To disable installation into JBDS open jbdevstudio/studio/configuration/config.ini and comment out *eclipse.p2.profile=jbds* using sharp char. For example: {code}#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser #Wed Aug 12 22:50:21 PDT 2015 org.eclipse.update.reconcile=false #eclipse.p2.profile=jbds osgi.framework=file\:plugins/org.eclipse.osgi_3.10.0.v20140606-1445.jar equinox.use.ds=true osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.1.0.v20131217-1203.jar@1\:start org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info eclipse.product=com.jboss.devstudio.core.product osgi.splashPath=platform\:/base/plugins/com.jboss.devstudio.core osgi.framework.extensions=reference\:file\:org.eclipse.osgi.compatibility.state_1.0.0.v20140403-1907.jar osgi.bundles.defaultStartLevel=4 eclipse.p2.data.area=@config.dir/../p2/ eclipse.application=org.eclipse.ui.ide.workbench{code} restart eclipse and try to install something from central. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: need-info > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-608) FeedHenry: Document exporting a Cordova app created using JBDS to FH

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-608?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-608: ------------------------------------ Looks good to me, [~supriya.bharadwaj] > FeedHenry: Document exporting a Cordova app created using JBDS to FH > -------------------------------------------------------------------- > > Key: TOOLSDOC-608 > URL: https://issues.jboss.org/browse/TOOLSDOC-608 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5-focused mobile application developer, I wish to use JBoss Tools and JBDS to craft my AngularJS+Ionic or jQuery Mobile-based application, testing it via CordovaSim, deploy the application to my iOS and/or Android phone and when I feel it is "about right", push it to FeedHenry's git URL. > It is currently unclear how an end-user takes his/her JBDS Hybrid Mobile (Cordova) project and sets it up to support a git push to FH. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13136) Deployment tab of server editor is always disabled

by Sumit Yerawar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13136?page=com.atlassian.jira.plugi... ] Sumit Yerawar commented on JBIDE-13136: --------------------------------------- Anyone Please Tell Me The Correct Solution For Problem. > Deployment tab of server editor is always disabled > -------------------------------------------------- > > Key: JBIDE-13136 > URL: https://issues.jboss.org/browse/JBIDE-13136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.0.CR1 > Environment: JBDS 6.0.0.CR1 B111 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.0.0.CR1 > > > The Deployment tab of server editor is disabled even if it shouldn't be. > Just add a AS 7.1.1 server and you'll see it (no projects needed). > This may be a regression from JBIDE-13033 > I saw this in two different instances of JBDS so hopefully you will be able to replicate this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015