December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles commented on JBIDE-18862: -------------------------------------- Informing the user of a problem during publish, with details of the problem (not a "the publish failed" error message) actually helps get problems solved. The alternative maybe that the user start/stop container, add/remove module, start/stop module multiple times over several minutes to try to reset the system to continue development. It may also be useful to have an action to delete the *.isdeploying file from the IDE, this saves the user a trip to an outside application (file manager) to do this manually, helping to heelp workflow inside IDE. The user can not take any action to fix a matter the IDE knows about but fails to inform the user. The end result is that XYZ just isn't working. Further to the above if the IDE knows the container is not running and *.isdeploying file exists, it can also consider it stale. > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles commented on JBIDE-18862: -------------------------------------- True but you do know the timestamp of the file from the Last Modification time. If it is older than the configured AS startup time, then you can consider is stable, and maybe the user is warned of the stale file with option to "continue publish anyway" or "abort publish". > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18925) Choose a default target server runtime as the latest available

by Marek Novotny (JIRA)

Marek Novotny created JBIDE-18925: ------------------------------------- Summary: Choose a default target server runtime as the latest available Key: JBIDE-18925 URL: https://issues.jboss.org/browse/JBIDE-18925 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Marek Novotny This suggestion for enhancement distilled from JBDS-3240 comments. The creating of new project from Maven archetype (Start from Scratch in JBoss Central) is the starting point. Could a runtime in the Target runtime field be set by default (the latest is the best) from available runtimes ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18924) Cordovasim: Url parameter for the start page disappears after refresh / device changing for JavaFx web-engine Oracle JDK 8

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-18924: ----------------------------------- Summary: Cordovasim: Url parameter for the start page disappears after refresh / device changing for JavaFx web-engine Oracle JDK 8 Key: JBIDE-18924 URL: https://issues.jboss.org/browse/JBIDE-18924 Project: Tools (JBoss Tools) Issue Type: Bug Components: cordovasim Affects Versions: 4.2.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18921: --------------------------------------------- why do we need to put this into Mars before we have a relase of our own ? > release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it > --------------------------------------------------------------------------------------- > > Key: JBIDE-18921 > URL: https://issues.jboss.org/browse/JBIDE-18921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?) > Destination folder (new folder hierarchy as of JBDS-3208 reorg): > http://download.jboss.org/jbosstools/mars/stable/updates/webtools/ > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18862: --------------------------------------------- we can't know if the .isdeploying is a something the server is actually doing or a left over from a dead server. Use putting content into the deployment via incremental updates should not be blocked by ongoing deployment IMO and actually it is never going to add a .deployed or .failed for incremental deployments since incremental deployments are *not* triggering anything on the server since we are not putting any .dodeploy file there. it is purely for updating html/css/etc. files. I'm failing to see what the advanced and user interrupting logic above will solve/help ? > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3286: ------------------------------------------- I'm +1 for this not having to be default installed by Devstudio 9 installer and BYOE from marketplace. > Remove Seam tooling from default JBDS installation > -------------------------------------------------- > > Key: JBDS-3286 > URL: https://issues.jboss.org/browse/JBDS-3286 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > > With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already). > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3285: ------------------------------------------- " I find it very difficult to clone and import a project correctly into JBDS" Do you mean *any* kind of project, or a *maven* project ? if it is already an eclipse project it just works. The issue is if the project is not something egit knows about it wont know how to import it. This is why we created easymport that are being contributed to eclipse platform to allow wizards like egit import to detect and automaically configure/open projects based on their content even for things they might not know about yet. "having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance" can you be a bit more specific what you mean here ? today if your project is a pom.xml and you get it imported all this should all be there and I believe we cannot really get any better/closer at this. With JBDS the server is there by default and you can drag it to the server and it will "just work". What parts are missing here in your opinon ? what kind of projects are you maybe thinking on that is *not* maven projects ? > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Labels: requirements, usability > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3245) Improve Eclipse Platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3245: -------------------------------------- Target Release: 9.0.0.GA (was: 8.1.0.GA) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration > Reporter: Max Rydahl Andersen > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3285: -------------------------------------- Labels: requirements usability (was: usability) > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Labels: requirements, usability > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014