[jbosstools-issues] [JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files

Nick Boldt (JIRA) issues at jboss.org
Fri Nov 25 17:09:00 EST 2016


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

Nick Boldt commented on JBIDE-23475:
------------------------------------

I've got a pom.xml and a python script that can do per-segment (staging, snapshots, development, stable) file manipulation to swap in/out versions of JBT and devstudio from within the new .fragment files, then merge them into an ide-config.properties file that Cental will read.

It's still a work in progress -- want to be able to run it from commandline w/o having to edit the pom.xml but ran out of time today.

So, going forward, if you make changes to ide-config.properties itself, they may be overwritten if someone runs the maven build to do the python transform.

Instead, you should edit these fragment files [1] as required, and the pom.xml [2] (to enable/disable regex transformations), then run the build to re-merge them into a new ide-config.properties file.

[1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/jbosstools/configuration/src/main/
[1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/jbosstools/configuration/pom.xml


> split ide-config.properties into multiple files  
> -------------------------------------------------
>
>                 Key: JBIDE-23475
>                 URL: https://issues.jboss.org/browse/JBIDE-23475
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: build, central, central-update
>    Affects Versions: 4.4.2.AM3
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.4.2.Final
>
>
> I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation.
> So, rather than 1 big file [1] we could split this into 5 files:
> * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA)
> * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3)
> * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA)
> * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA)
> * ide-config.properties - contains all the other properties for 4.3.x and earlier releases
> [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties
> By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value.
> From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list