August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2573) JBDS70_1411: [Uncommit] (Dev) (P1) Track more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2573?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2573: ---------------------------------------- [~maxandersen][~burrsutter] yes as Max pointed out, GA limits request to 2048 characters. Thus having shorthand names are IMHO the way to go for now. The shorthand names I map to are derived from the directory structure we had in SVN (before moving to git). Reporting lists is IMHO (as lined out above) only possible via several requests (vs. a single request right now). > JBDS70_1411: [Uncommit] (Dev) (P1) Track more > --------------------------------------------- > > Key: JBDS-2573 > URL: https://issues.jboss.org/browse/JBDS-2573 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 7.0.1.GA > > Attachments: advanced-segments.png, as-users-segment.png > > > What JBoss and 3rd party plug-ins are end-users really using? Allowing us to invest more in the most popular. (Note: This was deferred JBDS60_0920.) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15338) use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-15338: ------------------------------------ I vote for [2] as the best place to locate jbpm 4.5.200.Final. We're actually at JBTIS 4.1.2 now so if you [~nickboldt] could copy it to [2] - I'll bump the versions and add it to the composites. > use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final > --------------------------------------------------------------------------------------- > > Key: JBIDE-15338 > URL: https://issues.jboss.org/browse/JBIDE-15338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-2425: -------------------------------------- >From a content point of view it's not missing anything I believe. I'll leave it up to the docs team and [~mmurray] to reword it so there is no ambiguity. > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.x, 8.0.x, 7.1.x > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2425: --------------------------------------- My feedback Query: * Who is 'We'? Is this Red Hat? Can 'We' be changed to something more specific/representative? Grammar, typos: * '... which allow a user to resolve all *upstream dependencies of a Red Hat JBoss Developer Studio Central connector* via ...' * 'Simply launch *JBoss Developer Studio*, open *the JBoss Central tab*, then select ...' * 'Content available from JBoss Central has been tested by Red Hat *but* support ...' * Typo: plugins > *plug-ins* * '... provided by another vendor *and* simply redistributed.' * '*We attempt* to report ...' * '*We attempt* to monitor ...' * '... as soon as reasonable' > '... within a reasonable time frame ...' or leave phrase out entirely. > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.x, 8.0.x, 7.1.x > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-351) User Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-351?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-351: ------------------------------------------ Added screen captures to BrowserSim chapter: https://github.com/jbosstools/jbosstools-documentation/pull/162 > User Guide 7.0.0 - add screen captures > -------------------------------------- > > Key: TOOLSDOC-351 > URL: https://issues.jboss.org/browse/TOOLSDOC-351 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15338) use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15338: ------------------------------------ http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc/... now contains the updated jbpm3 4.5.100.Final bits. [~pleacu], should I push them into http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... too? Does that happen automatically? > use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final > --------------------------------------------------------------------------------------- > > Key: JBIDE-15338 > URL: https://issues.jboss.org/browse/JBIDE-15338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15338) use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15338?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15338 at 8/14/13 10:59 PM: -------------------------------------------------------------- http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc/... now contains the updated jbpm3 4.5.200.Final bits. [~pleacu], should I push them into http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... too? Does that happen automatically? was (Author: nickboldt): http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc/... now contains the updated jbpm3 4.5.100.Final bits. [~pleacu], should I push them into http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... too? Does that happen automatically? > use latest parent pom & target platform so we can release jBPM3 tooling v 4.5.200.Final > --------------------------------------------------------------------------------------- > > Key: JBIDE-15338 > URL: https://issues.jboss.org/browse/JBIDE-15338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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, 8 months

1
0
0 / 0

[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 Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-313?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-313: ------------------------------------------ Relooking at this JIRA to see what progress needs to be made to close it. Looked at Max's PR but I don't understand how it solves the version numbering issue. The version number was hardcoded in one place and now it is hardcoded in a different place. The version still has to be changed by hand in pom.xml. [~maxandersen], please can you clarify. > 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: Nick Boldt > Fix For: 4.1.1 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plug... ] Nick Boldt updated TOOLSDOC-310: -------------------------------- Fix Version/s: 4.1.0 > redirect /latest to /reference where the latest released docs can be found > -------------------------------------------------------------------------- > > Key: TOOLSDOC-310 > URL: https://issues.jboss.org/browse/TOOLSDOC-310 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0 > > > for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build. > That is not what it is for. > It is to point to the latest docs made available. > This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation. > I believe this should be put back since this is how other docs refer to the latest version. > We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them. > Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember. -- 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, 8 months

1
0
0 / 0

[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 updated TOOLSDOC-313: -------------------------------- Fix Version/s: 4.1.1 > 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: Nick Boldt > Fix For: 4.1.1 > > > 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, 8 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 August 2013