May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14706) openshift-java-client: add support for initial git url when creating a new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14706?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14706: ------------------------------------- Labels: (was: new_and_noteworthy) > openshift-java-client: add support for initial git url when creating a new application > -------------------------------------------------------------------------------------- > > Key: JBIDE-14706 > URL: https://issues.jboss.org/browse/JBIDE-14706 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > > It'd be nice to create an OpenShift app directly from a remote git repo, to be consistent with the Web UI : > !http://content.screencast.com/users/fbricon/folders/Jing/media/3fcb6305-5340-4529-91c9-2466266d32c4/2013-05-22_1857.png! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14705) In Preferences, JBoss Tools should have neutral name

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-14705: --------------------------------------- Summary: In Preferences, JBoss Tools should have neutral name Key: JBIDE-14705 URL: https://issues.jboss.org/browse/JBIDE-14705 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.1.0.Beta1 Reporter: Michelle Murray Attachments: Server_JBTruntimedetection2.png In Preferences there is 'JBoss Tools', under which all of the JBoss specific preferences are listed. Screen capture attached. The name 'JBoss Tools' is JBT-centric. Could we change this to something more neutral and therefore suitable for JBDS? How about dropping 'Tools' and simply having 'JBoss'? Any other suggestions? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14705) In Preferences, JBoss Tools should have neutral name

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14705?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-14705: ------------------------------------ Attachment: Server_JBTruntimedetection2.png > In Preferences, JBoss Tools should have neutral name > ---------------------------------------------------- > > Key: JBIDE-14705 > URL: https://issues.jboss.org/browse/JBIDE-14705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Attachments: Server_JBTruntimedetection2.png > > > In Preferences there is 'JBoss Tools', under which all of the JBoss specific preferences are listed. Screen capture attached. > The name 'JBoss Tools' is JBT-centric. Could we change this to something more neutral and therefore suitable for JBDS? How about dropping 'Tools' and simply having 'JBoss'? Any other suggestions? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14704) In Preferences, 'JBoss Tools Runtime Detection' should have neutral name

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-14704: --------------------------------------- Summary: In Preferences, 'JBoss Tools Runtime Detection' should have neutral name Key: JBIDE-14704 URL: https://issues.jboss.org/browse/JBIDE-14704 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.0.Beta1 Reporter: Michelle Murray Attachments: Server_JBTruntimedetection.png Under Preferences > JBoss Tools there is 'JBoss Tools Runtime Detection'. Screen capture attached. This name is fine for JBT but not JBDS. I suggest changing the name to something neutral. How about dropping 'Tools', so simply 'JBoss Runtime Detection'? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14704) In Preferences, 'JBoss Tools Runtime Detection' should have neutral name

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14704?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-14704: ------------------------------------ Attachment: Server_JBTruntimedetection.png > In Preferences, 'JBoss Tools Runtime Detection' should have neutral name > ------------------------------------------------------------------------ > > Key: JBIDE-14704 > URL: https://issues.jboss.org/browse/JBIDE-14704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Attachments: Server_JBTruntimedetection.png > > > Under Preferences > JBoss Tools there is 'JBoss Tools Runtime Detection'. Screen capture attached. > This name is fine for JBT but not JBDS. I suggest changing the name to something neutral. How about dropping 'Tools', so simply 'JBoss Runtime Detection'? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-345: ------------------------------------------ Email from Rob (9th April, 2013): Support for Port detection by reading the standalone.xml (or whatever config file is chosen) Port offset detection for AS7 (ie, users can start their server with a port offset of 100 or 200 or whatever, which means if standalone.xml says '8080' the real port is '8180') Deployment to a remote server (integration with eclipse RSE) Integration with JMX tools (MBean Explorer view and its editors) Support for a 'single file' or 'single folder' deployment (right-click on any file in the workspace and make it deployable) SAR projects EJB3 classpath container (right-click any project, go to classpath, add an ejb 3.0 classpath container) Basically almost all of the features that you see are provided via hooks into wtp. WTP provides the framework, but when compared to generic server, we have better implementations. So "publishing" is not unique, but we use project archives (jbt project in server repo) to make sure deployment is much faster (we use incremental updates) than generic server (which uses ant). When using 'run as -> run on server" on a web project, for example, we also make sure to not open the browser until the server assures us the module is properly deployed. If you open too fast (or use generic server) you'd get a 404 since the webapp is not fully deployed yet. Generic server for jboss also is able to tell if the server is up, and it works, but it's not optimal and doesn't give enough choices. We allow choices on how to do this (jmx / as7 management request, or web port polling, etc). So ... thats what I got so far ;) > NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools > --------------------------------------------------------------- > > Key: TOOLSDOC-345 > URL: https://issues.jboss.org/browse/TOOLSDOC-345 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JBoss Server Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools. > The unique JBoss Server Tools features I have are: > * automatic runtime detection > * ability to download and install a JBoss runtime > * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique > * set a default server icon > * set default filesets > * set default classpath entries > * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone > What have I missed? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-345: ---------------------------------------- Summary: NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools Key: TOOLSDOC-345 URL: https://issues.jboss.org/browse/TOOLSDOC-345 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: User Guide - JBoss Server Tools Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools. The unique JBoss Server Tools features I have are: * automatic runtime detection * ability to download and install a JBoss runtime * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique * set a default server icon * set default filesets * set default classpath entries * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone What have I missed? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-344) NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0?

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-344?page=com.atlassian.jira.plug... ] Burr Sutter commented on TOOLSDOC-344: -------------------------------------- >From my local copy of JBDS 7 Beta x (forgotten which build) http://screencast.com/t/QiQpaKCqY the maven is embedded > NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > --------------------------------------------------------------------------------------- > > Key: TOOLSDOC-344 > URL: https://issues.jboss.org/browse/TOOLSDOC-344 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0 > > > Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > I am thinking of this particularly in relation to the Getting Started Guide [http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...] and the Ticket Monster introduction [http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/]. > As part of the assumptions, the Getting Started Guide states: '... a number of assumptions are made about your system ... Maven is installed' -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-344) NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-344?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-344: ------------------------------------------ I didn't realise Maven came with JBDS. I thought a user had to install it independently. > NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > --------------------------------------------------------------------------------------- > > Key: TOOLSDOC-344 > URL: https://issues.jboss.org/browse/TOOLSDOC-344 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0 > > > Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > I am thinking of this particularly in relation to the Getting Started Guide [http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...] and the Ticket Monster introduction [http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/]. > As part of the assumptions, the Getting Started Guide states: '... a number of assumptions are made about your system ... Maven is installed' -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-344) NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0?

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-344?page=com.atlassian.jira.plug... ] Burr Sutter commented on TOOLSDOC-344: -------------------------------------- It is "bundled". Fred can provide the exact version of Maven embedded in the tools. > NeedInfo: Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > --------------------------------------------------------------------------------------- > > Key: TOOLSDOC-344 > URL: https://issues.jboss.org/browse/TOOLSDOC-344 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0 > > > Is there a specific version of Maven we expect users to use with JBDS 7.0.0? > I am thinking of this particularly in relation to the Getting Started Guide [http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...] and the Ticket Monster introduction [http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/]. > As part of the assumptions, the Getting Started Guide states: '... a number of assumptions are made about your system ... Maven is installed' -- 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, 10 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 May 2013