[jbosstools-issues] [JBoss JIRA] (JBIDE-13767) JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13767:
------------------------------------

[~dgolovin] please merge the above PRs.
                
> JBoss Tools 4.1 Central points to JBoss Tools 4.0's central site
> ----------------------------------------------------------------
>
>                 Key: JBIDE-13767
>                 URL: https://issues.jboss.org/browse/JBIDE-13767
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: project-examples
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>             Fix For: 4.1.0.Alpha1
>
>
> Due to some ugly hardcoding in the project examples plugin, we forgot to update JBT Central to pull from the new Kepler site.
> Thus:
> {code:title=examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java} 
> 44-	// TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/
> 45:	private static final String JBOSS_DIRECTORY_URL_DEFAULT = "http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-directory.xml"; //$NON-NLS-1$
> 46-
> 47-	// see pom.xml for actual value -- this is passed it at build-time via Maven
> {code}
> {code:title=examples/plugins/org.jboss.tools.project.examples/pom.xml}
> 13-	<properties>
> 14-		<!-- TODO: when moving to Kepler, use /development/kepler/ then later /stable/kepler/ -->
> 15:		<jboss.discovery.directory.url>http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-directory.xml</jboss.discovery.directory.url>
> 16-	</properties>
> 17-
> {code}
> So... oops. 
> We should really figure out a better way to externalize this.

--
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