January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13330) JBoss Developer Framework Quickstarts section on JBoss Central should be JBoss Quickstarts

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13330?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13330. ------------------------------ Verified in JBT 4.0.0 and JBDS 6.0.0 > JBoss Developer Framework Quickstarts section on JBoss Central should be JBoss Quickstarts > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13330 > URL: https://issues.jboss.org/browse/JBIDE-13330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0 > Reporter: Pete Muir > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.0.0.Final > > > JBoss Developer Framework Quickstarts section on JBoss Central should be called JBoss Quickstarts, the principle brand for the quickstarts is JBoss. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13266 at 1/4/13 5:04 AM: ---------------------------------------------------------------- Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2. The big gain is: * 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT) We can also expect: * Saved some time at build time to get other JBT artifacts The cost is: * +30 to 40% size of our repository (consumed on download.jboss.org) pack200 seems worth giving it a try. was (Author: mickael_istria): Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2. The big gain is: * more 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT) We can also expect: * Saved some time at build time to get other JBT artifacts The cost is: * +30 to 40% size of our repository (consumed on download.jboss.org) pack200 seems worth giving it a try. > Use pack200 to speed up download and install > -------------------------------------------- > > Key: JBIDE-13266 > URL: https://issues.jboss.org/browse/JBIDE-13266 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Affects Versions: 4.0.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing. > We should set up our repo to create the pack200'd artifacts. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13266: ---------------------------------------- Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2. The big gain is: * more 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT) We can also expect: * Saved some time at build time to get other JBT artifacts The cost is: * +30 to 40% size of our repository (consumed on download.jboss.org) pack200 seems worth giving it a try. > Use pack200 to speed up download and install > -------------------------------------------- > > Key: JBIDE-13266 > URL: https://issues.jboss.org/browse/JBIDE-13266 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Affects Versions: 4.0.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing. > We should set up our repo to create the pack200'd artifacts. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13341) Test the RichFaces Kitchensink archetype upgrade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13341?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13341: ------------------------------------- I can't find the 4.2.3.Final-2 archetype anywhere. Neither in the [staging repo|https://repository.jboss.org/nexus/content/groups/staging/org/richfa...] nor in [nexus|https://repository.jboss.org/nexus/index.html#nexus-search;quick~ri...] > Test the RichFaces Kitchensink archetype upgrade > ------------------------------------------------ > > Key: JBIDE-13341 > URL: https://issues.jboss.org/browse/JBIDE-13341 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: central > Reporter: Brian Leathem > Assignee: Fred Bricon > Priority: Critical > Labels: exampleswarnings > Fix For: 4.0.0.Final > > > RichFaces kitchensink archetype 4.2.3.Final-2 is currently in a JBoss staging repository. > The archetype will be promoted out of staging when JBoss tools QA is complete. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13341) Test the RichFaces Kitchensink archetype upgrade

by Brian Leathem (JIRA)

Brian Leathem created JBIDE-13341: ------------------------------------- Summary: Test the RichFaces Kitchensink archetype upgrade Key: JBIDE-13341 URL: https://issues.jboss.org/browse/JBIDE-13341 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: central Reporter: Brian Leathem Assignee: Fred Bricon Priority: Critical Fix For: 4.0.0.Final RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository. The archetype will be promoted out of staging when JBoss tools QA is complete. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13341) Test the RichFaces Kitchensink archetype upgrade

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13341?page=com.atlassian.jira.plugi... ] Brian Leathem updated JBIDE-13341: ---------------------------------- Description: RichFaces kitchensink archetype 4.2.3.Final-2 is currently in a JBoss staging repository. The archetype will be promoted out of staging when JBoss tools QA is complete. was: RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository. The archetype will be promoted out of staging when JBoss tools QA is complete. > Test the RichFaces Kitchensink archetype upgrade > ------------------------------------------------ > > Key: JBIDE-13341 > URL: https://issues.jboss.org/browse/JBIDE-13341 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: central > Reporter: Brian Leathem > Assignee: Fred Bricon > Priority: Critical > Labels: exampleswarnings > Fix For: 4.0.0.Final > > > RichFaces kitchensink archetype 4.2.3.Final-2 is currently in a JBoss staging repository. > The archetype will be promoted out of staging when JBoss tools QA is complete. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-12592: -------------------------------------- Assignee: Victor Rubezhny (was: Alexey Kazakov) > El is not revalidated in java comments > -------------------------------------- > > Key: JBIDE-12592 > URL: https://issues.jboss.org/browse/JBIDE-12592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.0.0.Alpha1 > Environment: Juno > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha1 > > > 1. Create the following class: > {code} > package test; > import javax.enterprise.inject.Produces; > import javax.inject.Named; > public class Bean_Broken { > public void foo() { > String s = "#{string.ss}"; > } > @Named > @Produces > public String string() { > return ""; > } > } > {code} > 2. The EL is marked as a problem > 3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file. > 4. FAILURE: There is still a validation problem on the EL. > 5. Save the file. The problem in the comment is gone. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12592: ----------------------------------- Description: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. The EL is marked as a problem 3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file. 4. FAILURE: There is still a validation problem on the EL. 5. Save the file. The problem in the comment is gone. was: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. The EL is marked as a problem 3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file. 4. FAILURE: There is still a validation problem on the EL. 5. Save the file. The problem in the comment is gone. > El is not revalidated in java comments > -------------------------------------- > > Key: JBIDE-12592 > URL: https://issues.jboss.org/browse/JBIDE-12592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.0.0.Alpha1 > Environment: Juno > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > 1. Create the following class: > {code} > package test; > import javax.enterprise.inject.Produces; > import javax.inject.Named; > public class Bean_Broken { > public void foo() { > String s = "#{string.ss}"; > } > @Named > @Produces > public String string() { > return ""; > } > } > {code} > 2. The EL is marked as a problem > 3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file. > 4. FAILURE: There is still a validation problem on the EL. > 5. Save the file. The problem in the comment is gone. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12592: ----------------------------------- Description: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. The EL is marked as a problem 3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file. 4. FAILURE: There is still a validation problem on the EL. 5. Save the file. The problem in the comment is gone. was: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. The EL is marked as a problem 3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file. 4. FAILURE: There is still a validation problem on the EL. 5. Save the file. The problem in the comment is gone. > El is not revalidated in java comments > -------------------------------------- > > Key: JBIDE-12592 > URL: https://issues.jboss.org/browse/JBIDE-12592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.0.0.Alpha1 > Environment: Juno > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > 1. Create the following class: > {code} > package test; > import javax.enterprise.inject.Produces; > import javax.inject.Named; > public class Bean_Broken { > public void foo() { > String s = "#{string.ss}"; > } > @Named > @Produces > public String string() { > return ""; > } > } > {code} > 2. The EL is marked as a problem > 3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file. > 4. FAILURE: There is still a validation problem on the EL. > 5. Save the file. The problem in the comment is gone. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12592: ----------------------------------- Description: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. The EL is marked as a problem 3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file. 4. FAILURE: There is still a validation problem on the EL. 5. Save the file. The problem in the comment is gone. was: 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; String s2 = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. Both ELs are marked as a problem 3. Ctrl + / on s2 = "#{string.ss}"; Don't save the file. 4. FAILURE: There is still the validation problem on the second EL. 5. Save the file. The problem in the comment is gone. > El is not revalidated in java comments > -------------------------------------- > > Key: JBIDE-12592 > URL: https://issues.jboss.org/browse/JBIDE-12592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.0.0.Alpha1 > Environment: Juno > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > 1. Create the following class: > {code} > package test; > import javax.enterprise.inject.Produces; > import javax.inject.Named; > public class Bean_Broken { > public void foo() { > String s = "#{string.ss}"; > } > @Named > @Produces > public String string() { > return ""; > } > } > {code} > 2. The EL is marked as a problem > 3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file. > 4. FAILURE: There is still a validation problem on the EL. > 5. Save the file. The problem in the comment is gone. -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013