[ https://jira.jboss.org/jira/browse/JBASM-15?page=com.atlassian.jira.plugi... ] Aleksandar Kostadinov updated JBASM-15: --------------------------------------- Summary: clean-up after 0.1.2.GA (was: clean-up after JBASM-3, JBASM-12 and JBASM-13) Description: Few things are good to be fixed: 1. There are some unnecessary excludes in the POM related to log4j. These were intended to avoid a harmless error message but a better approach seems the use of a jboss logging system property. 2. Switch server class to use jboss logging instead of log4j (currently a harmless error is printed out) - introduced in JBASM-13 3. Switch FailStartStopTest to use the common server configuration introduced in JBASM-13 4. switch to jboss-parent version 4 was: Few things are good to be fixed: 1. There are some unnecessary excludes in the POM related to log4j. These were intended to avoid a harmless error message but a better approach seems the use of a jboss logging system property. 2. Switch server class to use jboss logging instead of log4j (currently a harmless error is printed out) - introduced in JBASM-13 3. Switch FailStartStopTest to use the common server configuration introduced in JBASM-13 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBASM-15?page=com.atlassian.jira.plugi... ] Aleksandar Kostadinov resolved JBASM-15. ---------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira