March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13775) Add option 'Add references to JS/CSS' to Mobile Palette wizards

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13775?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13775: ------------------------------------------ Description: Checkbox 'Add references to JS/CSS' at the bottom of each wizard. Default state is true. Last choice is saved and applied to any Mobile Palette wizard. > Add option 'Add references to JS/CSS' to Mobile Palette wizards > --------------------------------------------------------------- > > Key: JBIDE-13775 > URL: https://issues.jboss.org/browse/JBIDE-13775 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > > Checkbox 'Add references to JS/CSS' at the bottom of each wizard. > Default state is true. Last choice is saved and applied to any Mobile Palette wizard. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13773) Clean-Up New Context Menu

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13773?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13773: ---------------------------------------- I'm afraid we cannot remove not our items from that menu (navigator content). These wizards are declared in upstream plugins for particular types of resources and shown up in all perspectives. We can remove Decorator and Interceptor since these wizards are declared in our cdi tools plugin. We also can control File->New menu in our perspective. > Clean-Up New Context Menu > ------------------------- > > Key: JBIDE-13773 > URL: https://issues.jboss.org/browse/JBIDE-13773 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Attachments: Screen Shot 2013-03-12 at 11.52.38 AM.png > > > The New context-menu in the JBoss Perspective has too many options, several of which are not valuable to the average end-user. > Possible Removals: > - Project > - SQL File > - Annotation > - Enum > - Dynamic Web Project > - Enterprise Application Project > - JSP File > - Filter > - Listener > - Servlet > - Decorator > - Interceptor > - Example... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13775) Add option 'Add references to JS/CSS' to Mobile Palette wizards

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-13775: --------------------------------------------- Summary: Add option 'Add references to JS/CSS' to Mobile Palette wizards Key: JBIDE-13775 URL: https://issues.jboss.org/browse/JBIDE-13775 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Alpha2 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2393) remove all references to JBDS Extras site from within JBDS 7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2393?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2393: ----------------------------- Fix Version/s: 7.0.x (was: 7.0.0.Alpha2) > remove all references to JBDS Extras site from within JBDS 7 > ------------------------------------------------------------ > > Key: JBDS-2393 > URL: https://issues.jboss.org/browse/JBDS-2393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 7.0.x > > > The following files in devstudio svn trunk need to be revised to no longer reference an extras/ site, if in fact we're going to obsolete it in favour of the Central composite site. > {quote} > ./documentation/Release_Guide/2012_Release_JBDS_Staging_For_QE.txt > ./devstudio.jboss.com/updates/6.0/central/core/compositeArtifacts.xml > ./devstudio.jboss.com/updates/6.0/central/core/compositeContent.xml > ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeArtifacts.xml > ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeContent.xml > ./devstudio.jboss.com/updates/6.0-staging/updatesites.xml > ./devstudio.jboss.com/updates/6.0-staging/index.html > ./devstudio.jboss.com/updates/6.0/index.html > ./devstudio.jboss.com/updates/6.0/updatesites.xml > ./product/features/com.jboss.jbds.product.feature.source/feature.xml > ./product/site/associate.properties > ./extras/site/associate.properties > ./techpreview/features/com.jboss.jbds.byoe.feature/feature.xml > ./techpreview/site/associate.properties > ./product-soa/site/associate.properties > ./qa/install-extras/jbds.properties > {quote} -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13672. -------------------------------- Resolution: Done Jobs in both 41x/70x and master/trunk should now be able to force a publish even if nothing has changed since the last published SHA. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13672 at 3/12/13 12:43 PM: -------------------------------------------------------------- Need to update jobs in 41x, and master to optionally pass through skipRevisionCheckWhenPublishing=true flag to the script. Does not affect 40x stream as those jobs use 4.0.x branch of the publish.sh script. Need to also verify this works when there's no pre-existing build folder. *FIXED* was (Author: nickboldt): Need to update jobs in 40x, 41x, and master to optionally pass through skipRevisionCheckWhenPublishing=true flag to the script. Need to also verify this works when there's no pre-existing build folder. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13672 at 3/12/13 12:44 PM: -------------------------------------------------------------- Updated jobs: {code:title=DevStudio_Trunk} # modified: RedDeer_master/config.xml # modified: devstudio.product_trunk/config.xml # modified: jbosstools-4.1_trunk.integrationtests.aggregate/config.xml # modified: jbosstools-TEMPLATE.NESTED_master/config.xml # modified: jbosstools-TEMPLATE_master/config.xml # modified: jbosstools-aerogear_master/config.xml # modified: jbosstools-build-sites.aggregate.coretests_master/config.xml # modified: jbosstools-build-sites.aggregate.site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools_master/config.xml # modified: jbosstools-central_master/config.xml # modified: jbosstools-forge_master/config.xml # modified: jbosstools-freemarker_master/config.xml # modified: jbosstools-gwt_master/config.xml # modified: jbosstools-hibernate_master/config.xml # modified: jbosstools-integration-tests.aggregate_master/config.xml # modified: jbosstools-javaee_master/config.xml # modified: jbosstools-jst_master/config.xml # modified: jbosstools-openshift_master/config.xml # modified: jbosstools-portlet_master/config.xml # modified: jbosstools-server_master/config.xml # modified: jbosstools-vpe_master/config.xml # modified: jbosstools-webservices_master/config.xml # modified: xulrunner-1.9.2/config.xml {code} {code:title=DevStudio_7.0.kepler} # modified: devstudio.product_70/config.xml # modified: jbosstools-base_41/config.xml # modified: jbosstools-birt_41/config.xml # modified: jbosstools-build-sites.aggregate.site_41/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_41/config.xml # modified: jbosstools-central_41/config.xml # modified: jbosstools-forge_41/config.xml # modified: jbosstools-freemarker_41/config.xml # modified: jbosstools-gwt_41/config.xml # modified: jbosstools-hibernate_41/config.xml # modified: jbosstools-integration-tests.aggregate_41/config.xml # modified: jbosstools-javaee_41/config.xml # modified: jbosstools-jst_41/config.xml # modified: jbosstools-openshift_41/config.xml # modified: jbosstools-portlet_41/config.xml # modified: jbosstools-server_41/config.xml # modified: jbosstools-vpe_41/config.xml # modified: jbosstools-webservices_41/config.xml {code} {code:title=DevStudio_6.0.juno} (none) {code} was (Author: nickboldt): Updated jobs: {code:title=DevStudio_Trunk} # modified: RedDeer_master/config.xml # modified: devstudio.product_trunk/config.xml # modified: jbosstools-4.1_trunk.integrationtests.aggregate/config.xml # modified: jbosstools-TEMPLATE.NESTED_master/config.xml # modified: jbosstools-TEMPLATE_master/config.xml # modified: jbosstools-aerogear_master/config.xml # modified: jbosstools-build-sites.aggregate.coretests_master/config.xml # modified: jbosstools-build-sites.aggregate.site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools_master/config.xml # modified: jbosstools-central_master/config.xml # modified: jbosstools-forge_master/config.xml # modified: jbosstools-freemarker_master/config.xml # modified: jbosstools-gwt_master/config.xml # modified: jbosstools-hibernate_master/config.xml # modified: jbosstools-integration-tests.aggregate_master/config.xml # modified: jbosstools-javaee_master/config.xml # modified: jbosstools-jst_master/config.xml # modified: jbosstools-openshift_master/config.xml # modified: jbosstools-portlet_master/config.xml # modified: jbosstools-server_master/config.xml # modified: jbosstools-vpe_master/config.xml # modified: jbosstools-webservices_master/config.xml # modified: xulrunner-1.9.2/config.xml {code} {code:title=DevStudio_7.0.kepler} # modified: devstudio.product_70/config.xml # modified: jbosstools-base_41/config.xml # modified: jbosstools-birt_41/config.xml # modified: jbosstools-build-sites.aggregate.site_41/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_41/config.xml # modified: jbosstools-central_41/config.xml # modified: jbosstools-forge_41/config.xml # modified: jbosstools-freemarker_41/config.xml # modified: jbosstools-gwt_41/config.xml # modified: jbosstools-hibernate_41/config.xml # modified: jbosstools-integration-tests.aggregate_41/config.xml # modified: jbosstools-javaee_41/config.xml # modified: jbosstools-jst_41/config.xml # modified: jbosstools-openshift_41/config.xml # modified: jbosstools-portlet_41/config.xml # modified: jbosstools-server_41/config.xml # modified: jbosstools-vpe_41/config.xml # modified: jbosstools-webservices_41/config.xml {code} {code:title=DevStudio_6.0.juno} {code} > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13774) BrowserSim: remember last device orientation

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-13774: ---------------------------------------------- Summary: BrowserSim: remember last device orientation Key: JBIDE-13774 URL: https://issues.jboss.org/browse/JBIDE-13774 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 4.1.0.Alpha2 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.1.0.Alpha2 remembering device orientation will be rather useful -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13672 at 3/12/13 12:38 PM: -------------------------------------------------------------- Updated jobs: {code:title=DevStudio_Trunk} # modified: RedDeer_master/config.xml # modified: devstudio.product_trunk/config.xml # modified: jbosstools-4.1_trunk.integrationtests.aggregate/config.xml # modified: jbosstools-TEMPLATE.NESTED_master/config.xml # modified: jbosstools-TEMPLATE_master/config.xml # modified: jbosstools-aerogear_master/config.xml # modified: jbosstools-build-sites.aggregate.coretests_master/config.xml # modified: jbosstools-build-sites.aggregate.site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools_master/config.xml # modified: jbosstools-central_master/config.xml # modified: jbosstools-forge_master/config.xml # modified: jbosstools-freemarker_master/config.xml # modified: jbosstools-gwt_master/config.xml # modified: jbosstools-hibernate_master/config.xml # modified: jbosstools-integration-tests.aggregate_master/config.xml # modified: jbosstools-javaee_master/config.xml # modified: jbosstools-jst_master/config.xml # modified: jbosstools-openshift_master/config.xml # modified: jbosstools-portlet_master/config.xml # modified: jbosstools-server_master/config.xml # modified: jbosstools-vpe_master/config.xml # modified: jbosstools-webservices_master/config.xml # modified: xulrunner-1.9.2/config.xml {code} {code:title=DevStudio_7.0.kepler} # modified: devstudio.product_70/config.xml # modified: jbosstools-base_41/config.xml # modified: jbosstools-birt_41/config.xml # modified: jbosstools-build-sites.aggregate.site_41/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_41/config.xml # modified: jbosstools-central_41/config.xml # modified: jbosstools-forge_41/config.xml # modified: jbosstools-freemarker_41/config.xml # modified: jbosstools-gwt_41/config.xml # modified: jbosstools-hibernate_41/config.xml # modified: jbosstools-integration-tests.aggregate_41/config.xml # modified: jbosstools-javaee_41/config.xml # modified: jbosstools-jst_41/config.xml # modified: jbosstools-openshift_41/config.xml # modified: jbosstools-portlet_41/config.xml # modified: jbosstools-server_41/config.xml # modified: jbosstools-vpe_41/config.xml # modified: jbosstools-webservices_41/config.xml {code} {code:title=DevStudio_6.0.juno} {code} was (Author: nickboldt): Updated jobs: {code} # modified: RedDeer_master/config.xml # modified: devstudio.product_trunk/config.xml # modified: jbosstools-4.1_trunk.integrationtests.aggregate/config.xml # modified: jbosstools-TEMPLATE.NESTED_master/config.xml # modified: jbosstools-TEMPLATE_master/config.xml # modified: jbosstools-aerogear_master/config.xml # modified: jbosstools-build-sites.aggregate.coretests_master/config.xml # modified: jbosstools-build-sites.aggregate.site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools_master/config.xml # modified: jbosstools-central_master/config.xml # modified: jbosstools-forge_master/config.xml # modified: jbosstools-freemarker_master/config.xml # modified: jbosstools-gwt_master/config.xml # modified: jbosstools-hibernate_master/config.xml # modified: jbosstools-integration-tests.aggregate_master/config.xml # modified: jbosstools-javaee_master/config.xml # modified: jbosstools-jst_master/config.xml # modified: jbosstools-openshift_master/config.xml # modified: jbosstools-portlet_master/config.xml # modified: jbosstools-server_master/config.xml # modified: jbosstools-vpe_master/config.xml # modified: jbosstools-webservices_master/config.xml # modified: xulrunner-1.9.2/config.xml {code} > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13672: ------------------------------------ Updated jobs: {code} # modified: RedDeer_master/config.xml # modified: devstudio.product_trunk/config.xml # modified: jbosstools-4.1_trunk.integrationtests.aggregate/config.xml # modified: jbosstools-TEMPLATE.NESTED_master/config.xml # modified: jbosstools-TEMPLATE_master/config.xml # modified: jbosstools-aerogear_master/config.xml # modified: jbosstools-build-sites.aggregate.coretests_master/config.xml # modified: jbosstools-build-sites.aggregate.site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools-site_master/config.xml # modified: jbosstools-build-sites.aggregate.webtools_master/config.xml # modified: jbosstools-central_master/config.xml # modified: jbosstools-forge_master/config.xml # modified: jbosstools-freemarker_master/config.xml # modified: jbosstools-gwt_master/config.xml # modified: jbosstools-hibernate_master/config.xml # modified: jbosstools-integration-tests.aggregate_master/config.xml # modified: jbosstools-javaee_master/config.xml # modified: jbosstools-jst_master/config.xml # modified: jbosstools-openshift_master/config.xml # modified: jbosstools-portlet_master/config.xml # modified: jbosstools-server_master/config.xml # modified: jbosstools-vpe_master/config.xml # modified: jbosstools-webservices_master/config.xml # modified: xulrunner-1.9.2/config.xml {code} > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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

13 years, 1 month

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 March 2013