November 2013 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-313) Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-313?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-313: ------------------------------------- I see that the changes described in the latest PR (#71) have been done in master branch, but not in 4.1.x branch. Therefore: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... ** https://github.com/jbosstools/jbosstools-hibernate/blob/master/docs/refer... *** http://docs.jboss.org/tools/nightly/trunk/en/hibernatetools/html/index.html {code} Version: 4.2.0.Final-SNAPSHOT Copyright © 2007, 2008, 2009, 2010, 2011{code} But: * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... ** https://github.com/jbosstools/jbosstools-hibernate/blob/jbosstools-4.1.x/... *** http://docs.jboss.org/tools/4.1.1.x/en/hibernatetools/html/index.html {code} Version: 3.3.0.M5 Copyright © 2007, 2008, 2009, 2010, 2011{code} > Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version > ---------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-313 > URL: https://issues.jboss.org/browse/TOOLSDOC-313 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.0.1, 4.1.0 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Some places where docs' copyright dates and stated versions do not align with the version of the doc: > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/GettingStartedGuide/html/index.html} > Version: 4.0.0 > Copyright © 2012 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/beginners_guide/html/index.html} > Version: 3.3.0.M5 > Copyright © 2011 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/as/html/index.html} > Version: 3.3.0.M5 > Copyright © 2007, 2008, 2009, 2010 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/jmx_ref_guide/html/index.html} > Copyright © 2007, 2008, 2009, 2010, 2011 JBoss by Red Hat > {code} > And yes, this is still a problem in trunk: > {code:title=http://docs.jboss.org/tools/nightly/trunk/en/beginners_guide/html/index.html} > Version: 3.3.0.M5 > Copyright © 2011 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/nightly/trunk/en/forge_reference/html/index.html} > Version: 3.3.1 > Copyright © 2012 JBoss by Red Hat > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2807) Update jrebel updatesite to use separate url for install feedback

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2807?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2807. ---------------------------- Closing. > Update jrebel updatesite to use separate url for install feedback > ----------------------------------------------------------------- > > Key: JBDS-2807 > URL: https://issues.jboss.org/browse/JBDS-2807 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: central, discovery > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: respin-a > Fix For: 5.0.2.GA, 6.0.1.GA, 7.0.1.GA, 7.1.0.Beta1 > > Attachments: JBDS2807_after_install_JRebel.png, JBDS2807_after_install_JRebel_JBDS7beta1_b441.png, JBDS2807_JBDS502_JRebel540_installed.png, JBDS2807_JBDS50x_patch.txt, JBDS2807_JBDS50x_patch2.txt, JBDS2807_JBDS601_JRebel540_installed.png, JBDS2807_JBDS60x_patch.txt, JBDS2807_JBDS60x_patch2.txt, JBDS2807_JBDS700_JRebel540_installed.png, JBDS2807_JBT33x_patch.txt, JBDS2807_JBT33x_patch2.txt > > > jrebel would like to see how many installs central gives and have given us this special url to use in discovery.xml. > http://update.zeroturnaround.com/update-site-jboss/ > (the / at the end is important) > We should change this for all active discovery plugins that have jrebel mentioned. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) OpenShift wizard displays wrong cloning location

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14322?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14322: ------------------------------------------ The following screencast shows the effect: !http://screencast.com/t/Tf8gPKZl0Hc! > OpenShift wizard displays wrong cloning location > ------------------------------------------------ > > Key: JBIDE-14322 > URL: https://issues.jboss.org/browse/JBIDE-14322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: clonning.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-15630: --------------------------------------- I just reproduced JIRA behavior and hided some fields that may be filled automatically. Which fields should be visible for user - this is subject for discussion. Preference page is always a good idea. I think, first of all we need a detailed description of everything. That's what I'm trying to do right now. Let me finish my description mock-up. In order to have something to start with. And we will discuss it. > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: ReportBugImpl.png > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) OpenShift wizard displays wrong cloning location

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14322?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14322 at 11/20/13 1:58 PM: -------------------------------------------------------------------- The following screencast shows the effect: http://screencast.com/t/Tf8gPKZl0Hc was (Author: adietish): The following screencast shows the effect: !http://screencast.com/t/Tf8gPKZl0Hc! > OpenShift wizard displays wrong cloning location > ------------------------------------------------ > > Key: JBIDE-14322 > URL: https://issues.jboss.org/browse/JBIDE-14322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: clonning.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15630: ---------------------------------------- Ok. My tentative doesn't provide look for duplicate but splits the Description in 2 parts to guide to better reports. I also wrote a preference page to store the JBoss.org credentials of user. As this dialog is targetting JBT/JBDS users, I think the Priority and Components fields are too much to require from a end-user. WDYT? > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: ReportBugImpl.png > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-15630: ---------------------------------- Attachment: ReportBugImpl.png [~mickael_istria], I did some dialog implementation with some searching for duplicate issues > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: ReportBugImpl.png > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-15630 at 11/20/13 1:27 PM: ----------------------------------------------------------------- [~mickael_istria], I did some dialog implementation with some searching for duplicate issues !ReportBugImpl.png! was (Author: dazarov): [~mickael_istria], I did some dialog implementation with some searching for duplicate issues > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: ReportBugImpl.png > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15772) Remove referenced juno sites in integration-tests site pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15772?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15772 at 11/20/13 1:25 PM: -------------------------------------------------------------- [~mmalina] Now the only remaining concern is that when you publish your site, it will reference nightly and staging sites that may cease to exist later. This is great because anyone can immediately install the plugins w/o having to search for upstream deps, but... You will need to update your root pom [1] to point at released, stable URLs when you're ready to build and release a *.Final* version of this site, as /staging/ and /nightly/ are subject to disappear or change w/o notice. [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... Also, I screwed up the indents here: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... :( was (Author: nickboldt): Now the only remaining concern is that when you publish your site, it will reference nightly and staging sites that may cease to exist later. Therefore, you should update your root pom [1] to point at released, stable URLs when you're ready to build and release a *.Final* version of this site. /staging/ and /nightly/ are subject to disappear or change w/o notice. [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... Also, I screwed up the indents here: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... :( > Remove referenced juno sites in integration-tests site pom > ---------------------------------------------------------- > > Key: JBIDE-15772 > URL: https://issues.jboss.org/browse/JBIDE-15772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.1.CR1 > > > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... > {code} > <associateSite>http://download.jboss.org/jbosstools/updates/juno/soa-tooling/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/stable/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/</associateSite> > {code} > These are added when you add the integration-tests update site to Eclipse to resolve dependencies. > We most probably don't need them. Or if we do, we should update to kepler links. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15639) Support running on Eclipse Luna M3 (4.4.M3) platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15639?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15639: ------------------------------- Summary: Support running on Eclipse Luna M3 (4.4.M3) platform (was: Support running on Eclipse Luna M2 (4.4.M2) platform) > Support running on Eclipse Luna M3 (4.4.M3) platform > ---------------------------------------------------- > > Key: JBIDE-15639 > URL: https://issues.jboss.org/browse/JBIDE-15639 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > Luna M2 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna. > As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with > {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code} > If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira. > WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX > Eclipse core: Not published yet. -- 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, 5 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 November 2013