August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16330) [Android] Deployment to Android emulator ignores saved run configuration

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16330?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-16330: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > [Android] Deployment to Android emulator ignores saved run configuration > ------------------------------------------------------------------------ > > Key: JBIDE-16330 > URL: https://issues.jboss.org/browse/JBIDE-16330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 4.5.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The deployment to an emulator is always performed on a currently running AVD even if the runtime config for the project specifies a different AVD. > Ignore/reject if this is by design. But from the point of view of the user, it would be better to ensure consistency - when a user wants to run his project on a specific AVD, he needs to create a runtime config, but the moment a different AVD is running, this config is ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15866) Skip specific validation if problem level was set to "ignore"

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15866?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-15866: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Skip specific validation if problem level was set to "ignore" > -------------------------------------------------------------- > > Key: JBIDE-15866 > URL: https://issues.jboss.org/browse/JBIDE-15866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.5.x > > > There's no need to perform the validation and attempt to create a marker if the problem level was set to "Ignore" by the user. This is wasted CPU time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20492) Allow configuring FreeMarker (per project)

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20492?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-20492: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Allow configuring FreeMarker (per project) > ------------------------------------------ > > Key: JBIDE-20492 > URL: https://issues.jboss.org/browse/JBIDE-20492 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.5.x > > > Some configuration settings affect parsing, and more such settings may appear in the future. A simple yet quite flexible and future-proof way of allowing configuring per project is adding a multi-line text input with label "Configuration settings (Java properites format)" under Project properties / FreeMarker, where the user can enter arbitrary text, then parse that with {{java.util.Properties}} and pass it to {{Configuration.setSettings(Properties)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23306) Application wizard: Provide increased "Details" panel size

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23306?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23306: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Application wizard: Provide increased "Details" panel size > ---------------------------------------------------------- > > Key: JBIDE-23306 > URL: https://issues.jboss.org/browse/JBIDE-23306 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: application_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > Currently, it provides a 2 lines and half visibility. > 2 things: > - perhaps we can add enough space for mor elines, 4? > - if we can avoid to cut the 3rd line (not sure that it is easy as it might be dependent on font?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20102) Empty window occurs when expanding hibernate console and JDBC driver is missing

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20102?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-20102: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Empty window occurs when expanding hibernate console and JDBC driver is missing > ------------------------------------------------------------------------------- > > Key: JBIDE-20102 > URL: https://issues.jboss.org/browse/JBIDE-20102 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-B50,L64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.5.x > > Attachments: hibernate-console-empty-window.png > > > See the screenshot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23654) Remember last Project type, build system and stack used to create a new project using the forge tooling

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23654?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23654: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Remember last Project type, build system and stack used to create a new project using the forge tooling > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23654 > URL: https://issues.jboss.org/browse/JBIDE-23654 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > Attachments: image-2016-12-19-13-21-02-213.png > > > When using the Forge tooling to create a new project, it would be nice to remember the last project type, build system and stack used on the first wizard page. > !image-2016-12-19-13-21-02-213.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23736) Implement smoke test for running batch application

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23736?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23736: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Implement smoke test for running batch application > -------------------------------------------------- > > Key: JBIDE-23736 > URL: https://issues.jboss.org/browse/JBIDE-23736 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.5.x > > > Implement smoke test for running batch demo application on server. > 1. Add requirement for running app. server (ie. JBoss EAP 7.x) > 2. Deploy batch demo app > 3. Start batch app. on server > 4. Check main functionality -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-18876: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.5.x > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-17838: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Make discovery-site a Maven module > ---------------------------------- > > Key: JBIDE-17838 > URL: https://issues.jboss.org/browse/JBIDE-17838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central-update > Affects Versions: 4.2.0.Beta3 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.x > > > Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15769) [Config Editor] Only Android parameters added to parameters table

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15769?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-15769: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > [Config Editor] Only Android parameters added to parameters table > ----------------------------------------------------------------- > > Key: JBIDE-15769 > URL: https://issues.jboss.org/browse/JBIDE-15769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Fix For: 4.5.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In Cordova Configuration Editor, Platform Properties mode: > 1. Click Add for first features table (opens Cordova Plugin Discovery window) > 2. Select check box for cordova item (e.g., org.apache.cordova.camera) > 3. Click Next > 4. Click Finish > Outcomes: > * "Camera" is added to feature table > * "android-package" is added to parameter table > * Following is added to file in config.xml mode > {noformat} > <feature name="Camera"> > <param name="android-package" value="org.apache.cordova.camera.CameraLauncher" /> > <param name="ios-package" value="CDVCamera" /> > </feature> > {noformat} > So looks like only the Android parameter is being added to the parameter table. Should the iOS parameter be automatically added to the parameter table too? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 2017