August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-387) Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-387?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-387: ------------------------------------------ PRs made: Apply PRs to 3.2.x branches: jbosstools-javaee: https://github.com/jbosstools/jbosstools-javaee/pull/136 jbosstools-portlet: https://github.com/jbosstools/jbosstools-portlet/pull/15 jbosstools-server: https://github.com/jbosstools/jbosstools-server/pull/140 jbosstools-hibernate: https://github.com/jbosstools/jbosstools-hibernate/pull/26 jbosstools-esb: https://github.com/jbosstools/jbosstools-esb/pull/42 jbosstools-jbpm: https://github.com/jbosstools/jbosstools-jbpm/pull/19 jbosstools-bpel: https://github.com/jbosstools/jbosstools-bpel/pull/19 modeshape-tools: https://github.com/ModeShape/modeshape-tools/pull/47 > Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page > ----------------------------------------------------------------- > > Key: TOOLSDOC-387 > URL: https://issues.jboss.org/browse/TOOLSDOC-387 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 3.2.2.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Attachments: 40docs.png > > > See attached screen capture for list of docs to be moved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-385) Get all JBDS 5.0 docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-385?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-385: ------------------------------------------ All 5.0 docs now moved to access.redhat: https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ PRs made: Apply PRs to 3.3.x branches: jbosstools-javaee: https://github.com/jbosstools/jbosstools-javaee/pull/134 jbosstools-portlet: https://github.com/jbosstools/jbosstools-portlet/pull/14 jbosstools-webservices: https://github.com/jbosstools/jbosstools-webservices/pull/79 jbosstools-server: https://github.com/jbosstools/jbosstools-server/pull/139 jbosstools-central: https://github.com/jbosstools/jbosstools-central/pull/150 jbosstools-openshift: https://github.com/jbosstools/jbosstools-openshift/pull/211 jbosstools-hibernate: https://github.com/jbosstools/jbosstools-hibernate/pull/25 Apply PRs to 4.0.0.Beta2x branches: jbosstools-forge: https://github.com/jbosstools/jbosstools-forge/pull/52 jbosstools-javaee: https://github.com/jbosstools/jbosstools-javaee/pull/135 > Get all JBDS 5.0 docs on the customer portal moved to RHJBDS page > ----------------------------------------------------------------- > > Key: TOOLSDOC-385 > URL: https://issues.jboss.org/browse/TOOLSDOC-385 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Reporter: Michelle Murray > Assignee: Michelle Murray > Attachments: 50docs.png > > > See attached screen capture for list of docs to be moved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-385) Get all JBDS 5.0 docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-385?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-385. -------------------------------------- Resolution: Done Waiting on PRs to be accepted but otherwise done. > Get all JBDS 5.0 docs on the customer portal moved to RHJBDS page > ----------------------------------------------------------------- > > Key: TOOLSDOC-385 > URL: https://issues.jboss.org/browse/TOOLSDOC-385 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues > Reporter: Michelle Murray > Assignee: Michelle Murray > Attachments: 50docs.png > > > See attached screen capture for list of docs to be moved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15379) Hyperlink on CSS file links works only for Dynamic Web Projects

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15379?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-15379: ---------------------------------- Description: Now we have WTP hyperlink "Open 'filename ' with CSS Editor" which works on every kind of projects. We need just delete our hyperlink org.jboss.tools.jst.text.ext.hyperlink.JSPStylesheetRelLinkHyperlink Test case: EXECUTE: 1. Create project (Non Dynamic Web Project) 2. Create file a.html: {code} <html> <head> <link rel="stylesheet" href="aaaa.css" /> </head> <body> </body> {code} 3. Create empty file aaaa.css 4. Open a.html file in Visual Page Editor and try to Ctrl click mouse on "aaaa.css" There are two hyperlinks: 1. Open file 'aaaa.css' 2. Open 'aaaa.css' with CSS File Editor 5. Try to select first hyperlink FAIL: nothing happened Note: after removing our hyperlink (1.) should remain only second one which works. was: Now we have WTP hyperlink "Open 'filename ' with CSS Editor" which works on every kind of projects. We need just delete our hyperlink org.jboss.tools.jst.text.ext.hyperlink.JSPStylesheetRelLinkHyperlink > Hyperlink on CSS file links works only for Dynamic Web Projects > --------------------------------------------------------------- > > Key: JBIDE-15379 > URL: https://issues.jboss.org/browse/JBIDE-15379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Final > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > Now we have WTP hyperlink "Open 'filename ' with CSS Editor" which works on every kind of projects. > We need just delete our hyperlink org.jboss.tools.jst.text.ext.hyperlink.JSPStylesheetRelLinkHyperlink > Test case: > EXECUTE: > 1. Create project (Non Dynamic Web Project) > 2. Create file a.html: > {code} > <html> > <head> > <link rel="stylesheet" href="aaaa.css" /> > </head> > <body> > </body> > {code} > 3. Create empty file aaaa.css > 4. Open a.html file in Visual Page Editor and try to Ctrl click mouse on "aaaa.css" > There are two hyperlinks: > 1. Open file 'aaaa.css' > 2. Open 'aaaa.css' with CSS File Editor > 5. Try to select first hyperlink > FAIL: nothing happened > Note: after removing our hyperlink (1.) should remain only second one which works. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15381: ----------------------------------- Labels: new_and_noteworthy (was: ) > Support annotation @Vetoed > -------------------------- > > Key: JBIDE-15381 > URL: https://issues.jboss.org/browse/JBIDE-15381 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: CDI > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15381: --------------------------------------------- Summary: Support annotation @Vetoed Key: JBIDE-15381 URL: https://issues.jboss.org/browse/JBIDE-15381 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-387) Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-387: ---------------------------------------- Summary: Get all JBDS 4.1 docs on the customer portal moved to RHJBDS page Key: TOOLSDOC-387 URL: https://issues.jboss.org/browse/TOOLSDOC-387 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Security Level: Public (Everyone can see) Components: General documentation issues Affects Versions: 3.2.2.Final Reporter: Michelle Murray Assignee: Michelle Murray -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15379) Hyperlink on CSS file links works only for Dynamic Web Projects

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15379?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-15379: ---------------------------------- Fix Version/s: 4.2.0.Alpha1 > Hyperlink on CSS file links works only for Dynamic Web Projects > --------------------------------------------------------------- > > Key: JBIDE-15379 > URL: https://issues.jboss.org/browse/JBIDE-15379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Final > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > Now we have WTP hyperlink "Open 'filename ' with CSS Editor" which works on every kind of projects. > We need just delete our hyperlink org.jboss.tools.jst.text.ext.hyperlink.JSPStylesheetRelLinkHyperlink -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-162?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-162: ----------------------------- Description: JBT has two types of .target files: * multiple [1], which references multiple upstream URLs from which its IUs are sourced, and * unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. [1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... [2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... Should JBTIS have a similar notion? was: JBT has two types of .target files: * multiple, which references multiple upstream URLs from which its IUs are sourced, and * unified, which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. Should JBTIS have a similar notion? > Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them? > -------------------------------------------------------------------------------------------------------- > > Key: JBTIS-162 > URL: https://issues.jboss.org/browse/JBTIS-162 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.3 > Reporter: Nick Boldt > > JBT has two types of .target files: > * multiple [1], which references multiple upstream URLs from which its IUs are sourced, and > * unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. > [1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > [2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > Should JBTIS have a similar notion? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-162: -------------------------------- Summary: Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them? Key: JBTIS-162 URL: https://issues.jboss.org/browse/JBTIS-162 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: target-platform Affects Versions: 4.1.3 Reporter: Nick Boldt JBT has two types of .target files: * multiple, which references multiple upstream URLs from which its IUs are sourced, and * unified, which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL. Should JBTIS have a similar notion? -- 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, 7 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