March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-13599 at 3/7/13 4:02 PM: --------------------------------------------------------------- {quote} Wow - I did not realize you were using dmr code directly. {quote} I'm using the code from the org.jboss.ide.eclipse.as.dmr plugin. This plugin contains the dmr library, version 1.1.1.Final that doesn't resolve nested properties. If we want to use nested properties, we have to update this plugin to use dmr, version 1.1.6.Final. Nick's requests are satisfied in any case. {quote} And before Max says that's not true, the exception to this rule is JRebel and Android, which have their own sites. But everything else comes from A SINGLE URL. {quote} You can use more properties/URLs. However, the siteUrl attribute isn't localized using plugin.properties so that you must enter an expression to the plugin.xml directly. For instance: plugin.xml {code} <connectorDescriptor ... siteURL="$\{central.URL:central URL default value\}" ... </<connectorDescriptor> <connectorDescriptor ... siteURL="$\{jrebel.URL:jrebel default value\}" ... </<connectorDescriptor> <connectorDescriptor ... siteURL="$\{android.URL:android default value\}" ... </<connectorDescriptor> {code} Then, you can start Eclipse using: -Dcentral.URL=<url1> -Dandroid.URL=<url2> -Djrebel.URL=<url3> was (Author: snjeza): {quote} Wow - I did not realize you were using dmr code directly. {quote} I'm using the code from the org.jboss.ide.eclipse.as.dmr plugin. This plugin contains the dmr library, version 1.1.1.Final that doesn't resolve nested properties. If we want to use nested properties, we have to update this plugin to use dmr, version 1.1.6.Final. Nick's requests are satisfied in any case. {quote} And before Max says that's not true, the exception to this rule is JRebel and Android, which have their own sites. But everything else comes from A SINGLE URL. {quote} You can use more properties/URLs. However, the siteUrl attribute isn't localized using plugin.properties so that you must enter an expression to the plugin.xml directly. For instance: plugin.xml {code} <connectorDescriptor ... siteURL="$\{central.URL:central URL default value\}" ... </<connectorDescriptor> <connectorDescriptor ... siteURL="$\{jrebel.URL:jrebel default value\}" ... </<connectorDescriptor> <connectorDescriptor ... siteURL="$\{android.URL:android default value\}" ... </<connectorDescriptor> Then, you can start Eclipse using: -Dcentral.URL=<url1> -Dandroid.URL=<url2> -Djrebel.URL=<url3> > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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-2348) JBDS product page on redhat.com is out of date

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2348?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2348: ----------------------------- Attachment: JBDS-PE-datasheet.pdf Updated datasheet which no longer mentions outdated versions of Eclipse/WTP: [^JBDS-PE-datasheet.pdf] > JBDS product page on redhat.com is out of date > ---------------------------------------------- > > Key: JBDS-2348 > URL: https://issues.jboss.org/browse/JBDS-2348 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, documentation > Affects Versions: 5.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > Attachments: JBDS-PE-datasheet.pdf > > > This page [1] mentions Eclipse 3.6 and JBoss Tools 3, but JBDS 6 uses Eclipse 4.2 and JBoss Tools 4. > [1] https://www.redhat.com/apps/store/developers/jboss_developer_studio.html > Can we get that page updated? -- 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-13753) For users dealing with large numbers of runtimes - it would be helpful to enable sorting of discovered runtimes

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13753?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-13753: --------------------------------- Attachment: Screenshot.png > For users dealing with large numbers of runtimes - it would be helpful to enable sorting of discovered runtimes > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13753 > URL: https://issues.jboss.org/browse/JBIDE-13753 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1 > Environment: 4.1.0.alpha1c > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.1.0.Final > > Attachments: Screenshot.png > > > See the attached screenshot - can we enable sorting on the columns? -- 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-13753) For users dealing with large numbers of runtimes - it would be helpful to enable sorting of discovered runtimes

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-13753: ------------------------------------ Summary: For users dealing with large numbers of runtimes - it would be helpful to enable sorting of discovered runtimes Key: JBIDE-13753 URL: https://issues.jboss.org/browse/JBIDE-13753 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Affects Versions: 4.1.0.Alpha1 Environment: 4.1.0.alpha1c Reporter: Len DiMaggio Assignee: Snjezana Peco Priority: Minor Fix For: 4.1.0.Final See the attached screenshot - can we enable sorting on the columns? -- 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-13335) remove Juno SR1+ performance fix from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13335: ------------------------------- Release Notes Text: JBT and JBDS Central in 4.0.0/6.0.0 included a connector that would install a performance fix (patch feature) which was released after Eclipse Juno SR1 was released. That fix is INCLUDED in Juno SR2, so it's available now from Help > Search for Updates in Eclipse or in JBDS. As such the connector has been removed from Central for the 4.0.1/6.0.1 release as it's redundant to what's available from Eclipse.org directly or is bundled within JBDS. > remove Juno SR1+ performance fix from Central > ---------------------------------------------- > > Key: JBIDE-13335 > URL: https://issues.jboss.org/browse/JBIDE-13335 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.0.1.Final > > Attachments: JBIDE13335.patch.JBDS6.0.1.txt > > > For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars. > Need to therefore, for JBT 4.0.1 and JBDS 6.0.1: > a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places) > b) remove the connector from discovery plugins' plugin.xml (2 files) -- 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-11319) Use Eclipse-SourceReferences

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11319: ------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > Use Eclipse-SourceReferences > ---------------------------- > > Key: JBIDE-11319 > URL: https://issues.jboss.org/browse/JBIDE-11319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.1.x > > > In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- 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-11319) Use Eclipse-SourceReferences

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11319: ------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > Use Eclipse-SourceReferences > ---------------------------- > > Key: JBIDE-11319 > URL: https://issues.jboss.org/browse/JBIDE-11319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.1.x > > > In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- 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-11319) Use Eclipse-SourceReferences

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11319: ------------------------------------ Slip from 4.0.x to 4.1.x; assign to Mickael to clarify need/solution. > Use Eclipse-SourceReferences > ---------------------------- > > Key: JBIDE-11319 > URL: https://issues.jboss.org/browse/JBIDE-11319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.1.x > > > In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- 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-2432) Use newer version of Eclipse with performance fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2432?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2432. ---------------------------- Resolution: Duplicate Issue Dupe of JBIDE-13335 > Use newer version of Eclipse with performance fix > ------------------------------------------------- > > Key: JBDS-2432 > URL: https://issues.jboss.org/browse/JBDS-2432 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Eclipse project released a maintenance version (that might be the future 4.2.2) for Eclipse 4.2.1 which highly improves performances. http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation -- 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-2365) ESB projects cannot be deployed using Server Add/Remove

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2365: ----------------------------- Release Notes Text: Cause: as.core plugin did not know what ESB 4.11 or 4.12 was, so would not detect those runtimes Consequence: as.core plugin did not know what ESB 4.11 or 4.12 was, so would not detect those runtimes Fix: make as.core plugin know what ESB 4.11 & 4.12 are, so could detect those runtimes Result: ESB 4.11 and 4.12 projects can be deployed using JBDS. was: Cause: Consequence: Fix: Result: > ESB projects cannot be deployed using Server Add/Remove > ------------------------------------------------------- > > Key: JBDS-2365 > URL: https://issues.jboss.org/browse/JBDS-2365 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA-SOA > Environment: Fedora, jdk7 > Reporter: Jeremy Davis > Assignee: Nick Boldt > Priority: Critical > Fix For: 6.0.0.CR1, 6.0.1.GA > > > * Create a new server runtime for SOA-P 5.3 > -- Preferences -> Server -> Runtime Environments > * Create a new ESB project with the defaults > * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification. > The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove." -- 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