January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-16409: ----------------------------------------- No, don't use that repo. It's not declared and as such it's not released yet. This build is in Smoke Testing at the moment and is to be declared (if no problems appear) soon. The required fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=426939 (HTML5 attribute validator marks ng-app AngularJS attributes as undefined) should be released in this build. So, we need to use this build (M-3.5.2-20140130145234) but only when it passes the Smoke Tests and gets declared. The repo (if all OK) will be moved to http://download.eclipse.org/webtools/downloads/drops/ > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16409: ---------------------------------------- I believe we'll have to start the TP 4.32.x stream with this change. [~nickboldt] WDYT ? > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16343: ------------------------------------- Import is incorrect and it's too long for a menu anyway. Extraction location can be defined in wizard. See http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M5.html > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-16409: -------------------------------------- Assignee: Mickael Istria > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16403) Welcome page "Show on startup" option is grey

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16403?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16403: -------------------------------- Fix Version/s: 4.2.0.Beta1 > Welcome page "Show on startup" option is grey > --------------------------------------------- > > Key: JBIDE-16403 > URL: https://issues.jboss.org/browse/JBIDE-16403 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Final > Environment: Kubuntu 64 bits > Reporter: Emmanuel Hugonnet > Priority: Minor > Fix For: 4.2.0.Beta1 > > Attachments: jboss_central.png > > > The option "show on startup" is displayed with a grey background instead of the default one. Changing theme doesn't affect it. > See screenshot -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16409: ---------------------------------------- Should we use this repository? http://build.eclipse.org/webtools/committers/wtp4x-R3.5.2-M/2014013014523... Ideally, it would be cool if you could format your request as explained in https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... (that would prevent from some questions and save time). > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16343: ---------------------------------------- The issue with just "extract" is that it doesn't say where stuff is about to be extracted. What about "Import as Jars inside Project...". > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16343: ------------------------------------- How about "Extract jars from library"? [~burrsutter], [~maxandersen], [~mmurray] any suggestions? > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16402: -------------------------------- Fix Version/s: 4.1.2.CR1 4.2.0.Alpha2 > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16402: -------------------------------- Assignee: Koen Aers > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- 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, 1 month

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 January 2014