[ https://jira.jboss.org/browse/SHRINKWRAP-206?page=com.atlassian.jira.plug... ] Dan Allen commented on SHRINKWRAP-206: -------------------------------------- How do we maintain backwards compatibility? Do we just say that you have to make sure you link against 1.0.0-alpha-10 if you are using the previous artifact? Seems reasonable to me. We just aren't releasing any more versions of the module under the old name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/SHRINKWRAP-206?page=com.atlassian.jira.plug... ] Andrew Lee Rubinger commented on SHRINKWRAP-206: ------------------------------------------------ I don't say it often, but screw back-compat here. I only know of one consumer, Arquillian, who is using this now. So since we're changing artifactIds, it makes sense that a package namespace would move too. First thing that'll happen is users will upgrade SW versions and see a missing artifact, so that'll be a new sign. IDE > Organize Imports... fixes the rest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/SHRINKWRAP-206?page=com.atlassian.jira.plug... ] Dan Allen commented on SHRINKWRAP-206: -------------------------------------- Sounds good to me. I just wanted to make sure you knew I was thinking about it ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira