May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14657) Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version'

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14657?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-14657: ------------------------------------ Attachment: JSF_Servletversion.png > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > --------------------------------------------------------------------- > > Key: JBIDE-14657 > URL: https://issues.jboss.org/browse/JBIDE-14657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Attachments: JSF_Servletversion.png > > > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > (screen caption attached) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14657) Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version'

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-14657: --------------------------------------- Summary: Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' Key: JBIDE-14657 URL: https://issues.jboss.org/browse/JBIDE-14657 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.1.0.Beta1 Reporter: Michelle Murray Attachments: JSF_Servletversion.png Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' (screen caption attached) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2456: --------------------------------------- Thanks [~nickboldt]. In part it is a case of RTFI on my part but in my defence I couldn't find the instructions so I think they should be moved/duplicated. I assumed the info would be in product/README.md and didn't think to look in the pom.xml. I'm just not used to working with pom.xml's and didn't think they would be a source of comments on building. I am not suggesting removing the info from pom.xml (unless you think it shouldn't be duplicated). But install info could be added to the README.md? I would suggest: * Change the '## Install' section title in the README.md to '## Download' or '## Get the code' or something, so can use '## Install' later. * README.md mentions getting code from web and svn. Is it necessary to mention svn method as buildable source is now available from weblinks? * Add a section titled '## Install' after '##Building' section, about installing JBDS (looking in installer/target for jbdevstudio*.jar and running java -jar ...), with text something link: {{## Install After building from source, the installer(s) will be produced in installer/target/. Navigate to the installer and run it with this command: $ java -jar jbdevstudio-*.jar}} * What's the difference between 'mvn clean verify' and 'mvn install' or 'mvn clean install'? Will 'mvn clean verify' also install? Should the command in '## Build' have 'install' in it? > JBDS should be buildable from source zip > ---------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > Attachments: log.eap-hudson.txt, log.eap.txt, log.hudson.txt, log.txt > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2456: ---------------------------------- {quote} I found jbdevstudio-product-universal-7.0.0*.jar. So do I just run that as usual, with java -jar ...?{quote} Yes. There should be a README.md in the root of the zip, too. If you feel something is missing, feel free to attach a patch or suggest contributions, and I'll add missing instructions. Note too that there is more information in the product/pom.xml file. Should that be moved/copied into the product/README.md file? {quote}{code} Build product features, site, and installers like this: mvn clean install To replicate a Jenkins CI build, run like this (unified.target and hudson profile require VPN access): mvn clean install -P hudson,eap,pack200 -Dtpc.targetKind=unified -DTARGET_PLATFORM_VERSION=4.30.5.Alpha4-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.30.5.Alpha4-SNAPSHOT -DBUILD_NUMBER=1234 -DJOB_NAME=devstudio.product_trunk -Dupdate.site.description="Development Milestone" Installer(s) will be produced in installer/target/ and can be installed using 'java -jar jbdevstudio-*.jar' Sources zip can be found in results/target/; you can build from the source zip by unpacking it, then using the instructions above. Unpacked update site can be found in site/target/repository/. You can now use the installer jar as an update site archive. Launch Eclipse or JBDS, then select: Help > Install New Software... > Add... > Archive... > Browse for the JBDS installer jar > OK > Work with: jar:file:/path/to/jbdevstudio-product-*.jar!/ > Install the JBDS feature(s) > Restart when prompted. To update from one version of JBDS to another: * Help > Install from the generated site in site/target/repository/ * Uncheck the box for 'Group items by category' * Select the "JBoss Developer Studio (Branded Product)" feature Or, to install the "Bring Your Own Eclipse" category or "Core Features" feature into Eclipse (not as an update to an existing JBDS install): * Help > Install from the generated site in site/target/repository/ * Select the "JBoss Developer Studio (Core Features)" feature {code}{quote} > JBDS should be buildable from source zip > ---------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta1 > > Attachments: log.eap-hudson.txt, log.eap.txt, log.hudson.txt, log.txt > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-341?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-341: ------------------------------------- Attachment: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf > Review: QE to review Beta1 Release Notes > ---------------------------------------- > > Key: TOOLSDOC-341 > URL: https://issues.jboss.org/browse/TOOLSDOC-341 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Jiri Peterka > Fix For: 4.1.0 > > Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf > > > *Please review* the Beta1 Release Notes document: > 1) Are new features correctly documented? > 2) Are there any new features that are missing? > 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 > *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-341?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-341: ------------------------------------------ I just noticed that the pdf version doesn't state Beta1 but html versions do - I will fix this before release. > Review: QE to review Beta1 Release Notes > ---------------------------------------- > > Key: TOOLSDOC-341 > URL: https://issues.jboss.org/browse/TOOLSDOC-341 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Jiri Peterka > Fix For: 4.1.0 > > Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf > > > *Please review* the Beta1 Release Notes document: > 1) Are new features correctly documented? > 2) Are there any new features that are missing? > 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 > *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-341?page=com.atlassian.jira.plug... ] Michelle Murray edited comment on TOOLSDOC-341 at 5/27/13 10:23 PM: -------------------------------------------------------------------- I just noticed that the pdf version doesn't state Beta1 but html versions do - I will fix this before release. Please review anyway. was (Author: mmurray): I just noticed that the pdf version doesn't state Beta1 but html versions do - I will fix this before release. > Review: QE to review Beta1 Release Notes > ---------------------------------------- > > Key: TOOLSDOC-341 > URL: https://issues.jboss.org/browse/TOOLSDOC-341 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Jiri Peterka > Fix For: 4.1.0 > > Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf > > > *Please review* the Beta1 Release Notes document: > 1) Are new features correctly documented? > 2) Are there any new features that are missing? > 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 > *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-341: ---------------------------------------- Summary: Review: QE to review Beta1 Release Notes Key: TOOLSDOC-341 URL: https://issues.jboss.org/browse/TOOLSDOC-341 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Jiri Peterka Fix For: 4.1.0 *Please review* the Beta1 Release Notes document: 1) Are new features correctly documented? 2) Are there any new features that are missing? 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-340) Review: All to review Beta1 Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-340?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-340: ------------------------------------------ Just noticed the pdf version doesn't specify Beta1 but the html versions do - will fix this. > Review: All to review Beta1 Release Notes > ----------------------------------------- > > Key: TOOLSDOC-340 > URL: https://issues.jboss.org/browse/TOOLSDOC-340 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf > > > *Please review* the Beta1 Release Notes document: > 1) Are new features correctly documented? > 2) Are there any new features that are missing? > 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 > *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. > Just for info: > *Note sure if the JIRA needs a release note?* > A JIRA needs a release note if: > a) the JIRA was reported by GSS > b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat) > d) the JIRA fixes a bug that users would have encountered or been aware of > c) the JIRA fix may surprise users (in a good or bad way) > e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release) > A JIRA does not need a release note if: > a) the JIRA fixes a bug that occurred from an internal build > b) the JIRA fixes a bug that users would not have been aware of > c) the JIRA was just part of a developer's to-do-list -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14656) Arquillian is not included in JBoss Central for 4.1.0.beta1

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14656?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-14656: --------------------------------- Labels: respin-b (was: ) > Arquillian is not included in JBoss Central for 4.1.0.beta1 > ----------------------------------------------------------- > > Key: JBIDE-14656 > URL: https://issues.jboss.org/browse/JBIDE-14656 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Len DiMaggio > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Can we add Arquillian to Central for beta1? -- 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, 11 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