[jbosstools-issues] [JBoss JIRA] (JBIDE-24893) Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home

[ https://issues.jboss.org/browse/JBIDE-24893?page=com.atlassian.jira.plugi... ] Nuno Godinho de Matos commented on JBIDE-24893: ----------------------------------------------- Hi Rob, Sure. 1. Step one - for each specific user project, a software developer will have config folder with - Datasource configuration.properties - Jms configuration.properties - jvm settings - main settings - and so on and so on... 2. We then have a so called create domain python script that swallows all of that configuration and ends up producing a wildfly *standalone* domain. - so this not a domain in the sense of a wildfly instance to coordinate the deployment to multiple managed instances. But a domain in the sense of a singular wilfly instance that will run a specific project applications(s) with its own configuration 3. This create domain script will produce this stand alone domain by combining a mix of a very simple stand alone template + all the configuration the user wants which gets injected in there during domain creation via CLI script. 4. At the end of this domain/instance creation process you end up with a WILDFLY_HOM/user_projects/domains/myIndividualDevelopperDomainWithAllConfigurationILike And in this instance folder you have all the normal things: (a) log folder (b) temp (c) deployments ... (zz) bin/ The bin folder is created by the create domain tool. and poduces easy to use scripts for starting, stopping etc... the instance. 5. When you are developping you do not care about this bin/ folder. You care about the eclipse plugin working properly. And the first problem you ecounter is that when you tell eclipse to work with a specific standalone instance, the plugin is addicted to some very constant startup settings. 6. This is where I wulld like an enhancement. I would like to be able to stop having to visit the open launch configuraiton window every time i tell wildfly where my instance folder is located and the standalone.xml it should use. I would much rather like that the plugin looks at the configuration folder, e.g. where you have that dynamic logging.properties, the user realm passwords and all of that, and that it looks in there and sees something like: .eclipse_launch_configuration.properties Or some other file format you think appropriate. And that instead of deciding on his own what launch configurations to use by default, to use this "overriding" set of configurations. In this way, when I developper creates a new domain/instance he would automatically see this eclipse plugin properties file tunning, and not have to waste time going to the bin/startWildfly.bat to copy the java_opts he wants to use. I hope the explanation is not too big and confusing. Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)