February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-9212) Consider introducing Profiles of AS Server adapteres

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9212?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9212: --------------------------------------- Priority: Major (was: Minor) > Consider introducing Profiles of AS Server adapteres > ---------------------------------------------------- > > Key: JBIDE-9212 > URL: https://issues.jboss.org/browse/JBIDE-9212 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > > With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak. > Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones. > These profiles would cover: > ports, start/stop behavior, pollers, deployments and launch setup. (more?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16467) Streamline server groups in New Server dialog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16467?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16467: --------------------------------------------- btw. we dont bundle the eclipse JBoss in JBDS installer for this reason :) > Streamline server groups in New Server dialog > --------------------------------------------- > > Key: JBIDE-16467 > URL: https://issues.jboss.org/browse/JBIDE-16467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Today I noticed that the group for JBoss EAP servers is now called Red Hat JBoss Middleware (JBIDE-15269). Seeing it got me thinking that the way it is now is actually pretty confusing and looks like a mess. Let me explain. > When you have JBoss Tools installed today, you get 3 JBoss-related groups in the New Server dialog. > 1. JBoss - this is in Eclipse by default. It contains very old servers only - up to JBoss AS 5. Could we possibly lobby for getting this removed/replaced with our own adapters? > 2. JBoss Community - this is where all our JBoss AS and Wildfly adapters are. > 3. Red Hat JBoss Middleware - this contains all EAP servers. > When you try to look at it from a new user's perspective, somebody who doesn't work at RH, it can give the impression that probably nobody took the time to put some order to this - there are 3 different groups, not even next to one another (because it's sorted alphabetically of course). > Granted, the Eclipse's JBoss group is not in our control, but maybe we can try to do something there, too? > I'm not sure what's the solution here. But if we must use Red Hat JBoss Middleware, couldn't we put everything in this group? Or are there any other alternatives to the current state? Or is it just me who finds this confusing? Opinions welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16368) Clean useless features from TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16368?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16368: ---------------------------------------- I'd like this to be merged before Luna M6 is released (March 13th). Any objection to merge it as suggested in PR? > Clean useless features from TP > ------------------------------ > > Key: JBIDE-16368 > URL: https://issues.jboss.org/browse/JBIDE-16368 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.x > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.0.Beta1 > > > In order to trim some stuff out of our target-platform, we should: > * Install JBDS from installer > * Look at its content in plugins/ and features/ and compare it with content of the TP site. > Everything that is in TP site but not in JBDS is probably worth being removed from TP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-12355: --------------------------------------- [~rrabara], [~mlabuda], Thanks for your feedbacks ! I just fixed the problems your reported. The http://tools-stg.jboss.org/ site has been updated. Please, don't hesitate to report other problems ! Thanks again > JBoss tools website redesign > ---------------------------- > > Key: JBIDE-12355 > URL: https://issues.jboss.org/browse/JBIDE-12355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png > > > jboss.org/tools have started to have issues scaling on several fronts. > 1) no clear path to what we want users to download (too many upfront choices) > 2) we are missing info about what jbosstools actually does > 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live) > 4) the content is generally getting very stale > 5) it is not easy to blog via community.jboss.org - resulting in less content (#4) > etc. etc. > 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor. > We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content. > https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress. > http://tools-stg.jboss.org/ <-- current staged version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15290) Database Connection Usability Improvements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15290?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15290: ---------------------------------------- Fix Version/s: (was: LATER) This issue is related to overall datasource usability concern. > Database Connection Usability Improvements > ------------------------------------------ > > Key: JBIDE-15290 > URL: https://issues.jboss.org/browse/JBIDE-15290 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Burr Sutter > > The current end-user workflow is fairly challenging and has amble opportunities for end-user error. You can see it starting around minute 4 in this video: > https://vimeo.com/39608294 > This workflow is also used with the Forge: Entities from Tables Wizard. > Here are the current steps, starting from the Forge Wizard: > http://www.screencast.com/t/mSyhEtlwfp > http://www.screencast.com/t/pNk17S4Xk9 > http://www.screencast.com/t/MssISpUZW6 > http://www.screencast.com/t/XxkzckHdi > http://www.screencast.com/t/j5pBIE0ESBM0 > http://www.screencast.com/t/GzLvpgNv8m > http://www.screencast.com/t/6KsGhlPx > http://www.screencast.com/t/yHHPnHva > http://www.screencast.com/t/v26qYQ3Cjr > http://www.screencast.com/t/NHvDtza1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-7515: --------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9479: --------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Enhance custom classpath containers for additional support such as as7's modules tag > ------------------------------------------------------------------------------------ > > Key: JBIDE-9479 > URL: https://issues.jboss.org/browse/JBIDE-9479 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 3.3.0.M3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > Enhance /JBIDE-1354 to allow for additional types of filesets. > 1) Add API > 2) Add extension point > 3) Add UI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14073) add remote deployment feature as EAP6 CLI does to JBDS.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14073?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14073: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > add remote deployment feature as EAP6 CLI does to JBDS. > ------------------------------------------------------- > > Key: JBIDE-14073 > URL: https://issues.jboss.org/browse/JBIDE-14073 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Labels: UHG > Fix For: 4.2.0.Beta1 > > > EAP6 CLI provides feature to do remote deployment: > bin/jboss-cli.sh --connect --controller="127.0.0.1:9999" --command="deploy ../tmp/sample.war" --user="User" > Is it possible to have such feature available in JBDS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14001: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > First restart of JBDS/App Server results in deployed archive being deleted from deploy directory. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14001 > URL: https://issues.jboss.org/browse/JBIDE-14001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.1.Final > Environment: Windows 7 > Reporter: David Stephan > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly. > Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted. > After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar. > Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12355: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > JBoss tools website redesign > ---------------------------- > > Key: JBIDE-12355 > URL: https://issues.jboss.org/browse/JBIDE-12355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png > > > jboss.org/tools have started to have issues scaling on several fronts. > 1) no clear path to what we want users to download (too many upfront choices) > 2) we are missing info about what jbosstools actually does > 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live) > 4) the content is generally getting very stale > 5) it is not easy to blog via community.jboss.org - resulting in less content (#4) > etc. etc. > 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor. > We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content. > https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress. > http://tools-stg.jboss.org/ <-- current staged version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 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 February 2014