March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13715?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13715: ---------------------------------- Release Notes Docs Status: Not Required > soa-p 5.3 is incorrectly detected as 5.2 > ---------------------------------------- > > Key: JBIDE-13715 > URL: https://issues.jboss.org/browse/JBIDE-13715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > Attachments: Screenshot.png > > > When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. > When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- 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-13714) Typo runtimea instead of rutime

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13714?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13714: ---------------------------------- Release Notes Docs Status: Not Required > Typo runtimea instead of rutime > ------------------------------- > > Key: JBIDE-13714 > URL: https://issues.jboss.org/browse/JBIDE-13714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > There's a typo when adding EAP6.1. It says JBoss Enterprise Application Platform 6.1 Runtimea. -- 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-13690) Detect future EAP 6 based server like SOA-P

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13690?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13690: ---------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > Detect future EAP 6 based server like SOA-P > ------------------------------------------- > > Key: JBIDE-13690 > URL: https://issues.jboss.org/browse/JBIDE-13690 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots. -- 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-13690) Detect future EAP 6 based server like SOA-P

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13690?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13690: ---------------------------------- Labels: new_and_noteworthy (was: ) > Detect future EAP 6 based server like SOA-P > ------------------------------------------- > > Key: JBIDE-13690 > URL: https://issues.jboss.org/browse/JBIDE-13690 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots. -- 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-13628) Only one JBoss Central Configurator is selected for display

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-13628. ------------------------------- > Only one JBoss Central Configurator is selected for display > ----------------------------------------------------------- > > Key: JBIDE-13628 > URL: https://issues.jboss.org/browse/JBIDE-13628 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Paul Richardson > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png] > However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator. > This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]: > {code:title=ProjectExamplesActivator.java|borderStyle=solid} > // ... ~ Line 1163 > IExtension extension = extensions[0]; > IConfigurationElement[] configurationElements = extension.getConfigurationElements(); > for (int j = 0; j < configurationElements.length; j++) { > IConfigurationElement configurationElement = configurationElements[j]; > if (CONFIGURATOR.equals(configurationElement.getName())) { > try { > configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class"); > } catch (CoreException e) { > ProjectExamplesActivator.log(e); > continue; > } > break; > } > } > // ... > {code} > > Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly. > Happy to provide a patch if required. > [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator > [2] org.jboss.tools.project.examples.configurators > [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java -- 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-13714) Typo runtimea instead of rutime

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13714?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13714: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 > Typo runtimea instead of rutime > ------------------------------- > > Key: JBIDE-13714 > URL: https://issues.jboss.org/browse/JBIDE-13714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > There's a typo when adding EAP6.1. It says JBoss Enterprise Application Platform 6.1 Runtimea. -- 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] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2395: ----------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) Description: As reported in JBDS-2280, there are two problems with Spring IDE 3.0: * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: https://dist.springframework.org/milestone/IDE/ - 3.1.0.201209120646-M1 (maybe misnamed?) http://dist.springframework.org/snapshot/IDE/nightly/ - 3.2.0.201211201813-CI-B170 Also, 3.1.0 release version is currently on Eclipse Marketplace. Suggest we wait until they release 3.2.0 in March and include it then in our next release. was: As reported in JBDS-2280, there are two problems with Spring IDE 3.0: * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: https://dist.springframework.org/milestone/IDE/ – 3.1.0.201209120646-M1 (maybe misnamed?) http://dist.springframework.org/snapshot/IDE/nightly/ – 3.2.0.201211201813-CI-B170 Also, 3.1.0 release version is currently on Eclipse Marketplace. Suggest we wait until they release 3.2.0 in March and include it then in our next release. > Investigate use of SpringIDE 3.x in JBoss 6.x & 7.x Central > ----------------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ - 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ - 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13603: --------------------------------------- [~nickboldt]: [~mickael_istria]: + 1 to include versions Fred suggested > 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-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13672: ------------------------------------ In corner cases, devs can force a rebuild (once I get the jobs configured correctly to allow skipRevisionCheckWhenPublishing=true to be passed through. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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-13004) Return back to WTP's original DirtyRegionProcessor clode after it is fixed in WTP 3.5

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13004?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13004: ----------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.x) > Return back to WTP's original DirtyRegionProcessor clode after it is fixed in WTP 3.5 > ------------------------------------------------------------------------------------- > > Key: JBIDE-13004 > URL: https://issues.jboss.org/browse/JBIDE-13004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.0.0.Alpha1 > Environment: Juno > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha2 > > > Because of [DirtyRegionProcessor's issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=384776] we have a fixed copy of this class due to fix [JBIDE-12418|https://issues.jboss.org/browse/JBIDE-12418]. > The referenced BugZilla issue is marked as fixed and is targeted for WTP 3.5.M3, so, probably we should return to original class and not to have its copy in our 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

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