March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13603 at 3/4/13 9:25 PM: ------------------------------------------------------------ [~dgolovin] asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-signed-201209140800.jar {code} Since [~fbricon] is AFK for the next while, [~maxandersen], [~dgolovin], [~mickael_istria] WDYT? was (Author: nickboldt): [~dgolovin] asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-signed-201209140800.jar {code} > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13603 at 3/4/13 9:23 PM: ------------------------------------------------------------ [~dgolovin] asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar {code} was (Author: nickboldt): Denis asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar {code} > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13603 at 3/4/13 9:24 PM: ------------------------------------------------------------ [~dgolovin] asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar org.sonatype.m2e.mavenarchiver.feature_0.15.0.201207090125-signed-201209140800.jar {code} was (Author: nickboldt): [~dgolovin] asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar {code} > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13603: ------------------------------------ Denis asked: {quote} why in JBIDE-13603 instead of 1.3.0 included into Juno SR2 release we should add 1.3.1? IMO It should be version from 4.2.2 {quote} Versions in the 4.22.1 TP - http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... : {code} org.eclipse.m2e.feature_1.2.0.20120903-1050.jar org.eclipse.m2e.wtp.feature_0.16.0.20120914-0945.jar {code} > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13619: ----------------------------------- Release Notes Docs Status: Documented as Resolved Issue (was: Not Yet Documented) > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13619: ----------------------------------- Release Notes Text: Struts Tools is marked as deprecated and going to be removed in JBoss Tools 4.1.0. (was: Struts Tools is marked as deprecated and going to be removed in the next version of JBoss Tools.) > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13619: ----------------------------------- Release Notes Text: Struts Tools is marked as deprecated and going to be removed in the next version of JBoss Tools. > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13711) typo "JBos Enterprise Application Platform"

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13711: ----------------------------------- Summary: typo "JBos Enterprise Application Platform" Key: JBIDE-13711 URL: https://issues.jboss.org/browse/JBIDE-13711 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Reporter: Burr Sutter Assignee: Rob Stryker http://docs.jboss.org/tools/latest/en/jmx_ref_guide/html_single/index.html Search for "JBos Enterprise" In 2.4. Managing a JBoss application server Remotely -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13710) New Header Bar wizard

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-13710: --------------------------------------------- Summary: New Header Bar wizard Key: JBIDE-13710 URL: https://issues.jboss.org/browse/JBIDE-13710 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html source editing Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Alpha2 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13695) Rename Method Participant does not work correctly if project is out of synch

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13695?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13695: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/58, https://github.com/jbosstools/jbosstools-jst/pull/65, https://github.com/jbosstools/jbosstools-base/pull/58 (was: https://github.com/jbosstools/jbosstools-javaee/pull/57, https://github.com/jbosstools/jbosstools-jst/pull/65, https://github.com/jbosstools/jbosstools-base/pull/58) > Rename Method Participant does not work correctly if project is out of synch > ---------------------------------------------------------------------------- > > Key: JBIDE-13695 > URL: https://issues.jboss.org/browse/JBIDE-13695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, common/jst/core, JSF > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > See: https://community.jboss.org/message/800166#800166 > What to do: > 1. Do not block UI (put error in the log instead producing fatal error) > 2. Make error message more clear > 3. Try to refresh the 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

13 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 March 2013