4 Replies Latest reply on Jul 2, 2011 1:08 AM by ceefour

    Proposed change to how we use Maven


      Some of the JBoss artifacts are being pushed into Maven central, but IIUC ModeShape is not yet able to be pushed because our parent POM has the JBoss Maven repository hard-coded into it.


      So I'd like to eliminate that for ModeShape 2.6.x releases and beyond. I've logged MODE-1197 to cover this work.


      What does this mean for users?


      Probably not much. We've recommended for a while that define the JBoss Maven repository in their own '~/.m2/settings.xml' file. That's about the only way to see our POMs to begin with.


      And in fact, if we can get ModeShape artifacts pushed into Maven Central, it'll make users' lives tremendously easier, because they won't have to do anything with their Maven settings to find the ModeShape artifacts.


      What does this mean for contributors?


      Contributors in all likelihood also have had to define the JBoss Maven repository in their '~/.m2/settings.xml' file. However, you might not have needed to change your '~/.m2/settings.xml' if you have our code locally, since our parent POM defined the JBoss Maven repository. So when we remove the JBoss Maven repository from our parent POM, you will have to do one of the following:


      1. Make sure your '~/.m2/settings.xml' file correctly defines the JBoss Maven repository (see ModeShape and Maven), or
      2. Use "mvn -s settings.xml ..." on your build commands, and do something similar in your IDE.


      The first option would definitely be preferred.