Closed dwinchell closed 11 years ago
This is mostly a standalone application so we have gone for ease of use without having to configure logging before you use it. I hesitate to deviate... maybe if you provide a pull request with a documented howto configure along with the code adjustment and a good argument for embedding this tool?
I can definitely do that, but if it's fundamentally intended as a standalone application, maybe I am off the mark. My use case is using it as a library in another migration tool (in this case primarily for EAP, but we want to expand it to more JBoss products). Now that you bring it up, there may not be other common enough use cases to justify added complexity for the vast number of users.
I see, I think it is better then to just leave it. I prefer working outta the box vs having them have to configure it. You can always explode and adjust as needed or just rebuild the project (mavanized) with your config.
I added jbpmmigration as a dependency