[jbosstools-issues] [JBoss JIRA] (JBIDE-17153) Provide a way to configure IDE properties remotely, supporting multiple product/project versions
Fred Bricon (JIRA)
issues at jboss.org
Thu May 15 11:23:56 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968176#comment-12968176 ]
Fred Bricon commented on JBIDE-17153:
-------------------------------------
PRs updated :
* simpler API (no CoreException, monitors)
* highest priority means highest priority :-)
* falls back on a default embedded properties in case the remote URL can't be accessed
* project examples urls now use remote properties
> Provide a way to configure IDE properties remotely, supporting multiple product/project versions
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17153
> URL: https://issues.jboss.org/browse/JBIDE-17153
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, discovery
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta2
>
>
> Currently, discovery urls are defined at build time and require modifying eclipse.ini or jbdevstudio.ini for each release. This is often error prone / annoying.
> [~maxandersen] came up with the following idea :
> make all these URLs (and others if applicable) defined in one place, that we can update remotely.
> So a remote properties file would contain the urls per project/product and per version.
> If we have foo|devstudio|8.0.0.Beta2=bar then :
> * devstudio 8.0.0.Beta2-123456-65432 will get bar.
> * If no matching key/version is defined, then we'd look for foo|devstudio|8.0.0
> * then foo|devstudio|8.0
> * then foo|devstudio|8
> * then foo|devstudio
> * then foo
> That solution allows us to fine tune discovery urls per version if needed and doesn't require users/QE to mess with *.ini to test each milestone.
> http://download.jboss.org/jbosstools/configuration/ide-config.properties would be the bundle resource master of all properties.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the jbosstools-issues
mailing list