October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15509 at 10/7/13 5:28 PM: ------------------------------------------------------------- Documented JDK 7u40 bug as follows: !note-jdk7u40.png! {quote} NOTE: If you are using Oracle JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [7u25 (1.7.0_25)|http://www.oracle.com/technetwork/java/javase/downloads/java-ar...] to work around this issue until a new version is available.{quote} was (Author: nickboldt): Documented JDK 7u40 bug as follows: !note-jdk7u40.png! {quote} NOTE: If you are using Oracle JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [http://www.oracle.com/technetwork/java/javase/downloads/java-archive-down... (1.7.0_25)] to work around this issue until a new version is available.{quote} > prepare for JBDS 7.0.1 patch release > ------------------------------------ > > Key: JBIDE-15509 > URL: https://issues.jboss.org/browse/JBIDE-15509 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.1.Final > > Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, note-jdk7u40.png > > > Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA: > 1. branch jbosstools-central from 4.1.x to 4.1.0.x > 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources) > 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch > 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg., > http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... > 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x > 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0) > 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration: > {code} > jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c... > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15509 at 10/7/13 5:28 PM: ------------------------------------------------------------- Documented JDK 7u40 bug as follows: !note-jdk7u40.png! {quote} *NOTE:* If you are using Oracle JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [7u25 (1.7.0_25)|http://www.oracle.com/technetwork/java/javase/downloads/java-ar...] to work around this issue until a new version is available.{quote} was (Author: nickboldt): Documented JDK 7u40 bug as follows: !note-jdk7u40.png! {quote} NOTE: If you are using Oracle JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [7u25 (1.7.0_25)|http://www.oracle.com/technetwork/java/javase/downloads/java-ar...] to work around this issue until a new version is available.{quote} > prepare for JBDS 7.0.1 patch release > ------------------------------------ > > Key: JBIDE-15509 > URL: https://issues.jboss.org/browse/JBIDE-15509 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.1.Final > > Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, note-jdk7u40.png > > > Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA: > 1. branch jbosstools-central from 4.1.x to 4.1.0.x > 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources) > 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch > 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg., > http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... > 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x > 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0) > 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration: > {code} > jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c... > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15627) ORM Bug Loading Entity with Two ID Properties

by Greg Moser (JIRA)

Greg Moser created JBIDE-15627: ---------------------------------- Summary: ORM Bug Loading Entity with Two ID Properties Key: JBIDE-15627 URL: https://issues.jboss.org/browse/JBIDE-15627 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Mac OSX, MySQL Reporter: Greg Moser When an entity is defined with two columns as the ID it is able to be saved fine, however whenever an entity is loaded with either entityLoad() or ormExecuteQuery() neither of the properties are populated. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15627) ORM Bug Loading Entity with Two ID Properties

by Greg Moser (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15627?page=com.atlassian.jira.plugi... ] Greg Moser commented on JBIDE-15627: ------------------------------------ Sorry, posted on the wrong issue tracker. > ORM Bug Loading Entity with Two ID Properties > --------------------------------------------- > > Key: JBIDE-15627 > URL: https://issues.jboss.org/browse/JBIDE-15627 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: Mac OSX, MySQL > Reporter: Greg Moser > > When an entity is defined with two columns as the ID it is able to be saved fine, however whenever an entity is loaded with either entityLoad() or ormExecuteQuery() neither of the properties are populated. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15360) Support CDI 1.1 in New CDI Project wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15360?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15360: ----------------------------------- Summary: Support CDI 1.1 in New CDI Project wizard (was: CDI 1.1 project facet) > Support CDI 1.1 in New CDI Project wizard > ----------------------------------------- > > Key: JBIDE-15360 > URL: https://issues.jboss.org/browse/JBIDE-15360 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.x > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15621) Runtime isn't detected when adding it right after it was deleted

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15621?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15621: ---------------------------------- Fix Version/s: 4.2.0.Alpha1 > Runtime isn't detected when adding it right after it was deleted > ---------------------------------------------------------------- > > Key: JBIDE-15621 > URL: https://issues.jboss.org/browse/JBIDE-15621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.1.Final > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha1 > > Attachments: runtime 01 - select a folder.jpg, runtime 02 - found runtime.jpg, runtime 03 - remove runtime.jpg, runtime 04 - select the folder again.jpg, runtime 05 - no runtime found.jpg, runtime 06 - workaround - uncheck.jpg, runtime 07 - workaround - check.jpg > > > JBoss Runtime Detection doesn't detect a runtime, when the runtime is removed and then added. > Workaround exists. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2770) Cheatsheet for JBoss Central archetypes: kitchensink-html5-mobile

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2770?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on JBDS-2770: ----------------------------------- I created template cheatsheets for the kitchensink-html5-mobile and kitchensink-rf quickstarts and attached them to these JIRAs: https://issues.jboss.org/browse/JDF-497 (kitchensink-html5-mobile) https://issues.jboss.org/browse/JDF-498 (kitchensink-rf) > Cheatsheet for JBoss Central archetypes: kitchensink-html5-mobile > ----------------------------------------------------------------- > > Key: JBDS-2770 > URL: https://issues.jboss.org/browse/JBDS-2770 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Sande Gilda > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15621) Runtime isn't detected when adding it right after it was deleted

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15621?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15621: --------------------------------------- I think that is correct behaviour. When you say: {quote} 2. Remove added runtime: STEP: Click on the button "Remove" 3. Add the same runtime again {quote} do you mean removing a runtime/server or removing a runtime path? I suppose you mean "removing a runtime path". If you remove it, the Runtime Detection plugin doesn't find a new runtime because, in the step 1, you have already created all the runtimes/servers for that path. If you remove a runtime (using the JBoss AS link) and a runtime path (with the Remove button), you will be able to create the same runtime again. Your workaround contains a bug. If you check an already created runtime, the OK button shouldn't be enabled. The PR fixes this bug. We could replace the "No runtime found" message with the "No new runtime found" message. Please reopen the jira if you want me to do it. > Runtime isn't detected when adding it right after it was deleted > ---------------------------------------------------------------- > > Key: JBIDE-15621 > URL: https://issues.jboss.org/browse/JBIDE-15621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.1.Final > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Attachments: runtime 01 - select a folder.jpg, runtime 02 - found runtime.jpg, runtime 03 - remove runtime.jpg, runtime 04 - select the folder again.jpg, runtime 05 - no runtime found.jpg, runtime 06 - workaround - uncheck.jpg, runtime 07 - workaround - check.jpg > > > JBoss Runtime Detection doesn't detect a runtime, when the runtime is removed and then added. > Workaround exists. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15626) Bump Seam version to 3.5.1 in 4.1.x branch

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-15626: -------------------------------------- Summary: Bump Seam version to 3.5.1 in 4.1.x branch Key: JBIDE-15626 URL: https://issues.jboss.org/browse/JBIDE-15626 Project: Tools (JBoss Tools) Issue Type: Task Components: seam2 Affects Versions: 4.1.1.Alpha2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.1.1.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15625) Faces-config validation wrongly reports a warning for two renderers with the same renderer-type

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15625: --------------------------------------------- Summary: Faces-config validation wrongly reports a warning for two renderers with the same renderer-type Key: JBIDE-15625 URL: https://issues.jboss.org/browse/JBIDE-15625 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 https://community.jboss.org/message/840399?et=watches.email.thread#840399 Validation should take into account both renderer-type and component-family. -- 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, 6 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 October 2013