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

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759580#comment-12759580 ] 

Snjezana Peco edited comment on JBIDE-13599 at 3/7/13 4:05 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.
See https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/org.jboss.ide.eclipse.as.dmr/jboss-dmr-1.1.1.Final.jar
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>
{code}

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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12755106 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