1 Reply Latest reply on Mar 13, 2013 3:03 PM by Marc Gagnon

    Configure Maven for JBoss AS 7, associating Maven with project, unable to create Ticket-Monster project. Unable to obtain central repository.

    Charles Harris Newbie

      Hello,

       

      This is my first time ever utilizing JBoss, so please be kind :-)  The problem that I'm having is trying to associate the Maven archetype with the Ticket-Monster turorial.  I have set up Maven, and the jboss-as-7.1.1.Final Server starts up successfully.  Unfortunately, no matter what I do.  I am unable to advance past this point.  These are the sequences of steps that I have taken thus far:

       

      1) Successfully Installed Maven.  I know this because when I issue the mvn --version command I get correct versioning information.

       

      2) But upon trying to proceed with the various processes to create the project I get  (As indicated earlier, the jboss-as-7.1.1.Final Server starts up successfully) :

       

      3) And ultimately, the treaded Error.

      Screenshot1.png

       

      Screenshot2.png

       

       

      What have I have tried?

      Pointing the Maven User settings to the user.home/.m2/settings.xml (which never existed to begin with), but was still unsuccessful.  Which ultimately led me to try pointing to the settings.xml file in the apache-maven directory, as shown here.

      Screenshot4.png

       

      I have also tried modifying the contents within the settings.xml file itself, to what Apache advises me to use.  However, again no success.  Can someone please help me.  I have been stuck on this for the last 2 weeks.

       

      Very Respectfully,

      Charles

        • 1. Re: Configure Maven for JBoss AS 7, associating Maven with project, unable to create Ticket-Monster project. Unable to obtain central repository.
          Marc Gagnon Newbie

          Some people will hate me but the simple truth is that you should build the project using maven from the command line: eclipse is just an interface, not a build management tool.

          When you have a command line builtd success, proceed with projects importation in eclipse.

          This is not as fancy as tools developpers suggest it should be and this is more work than what it should be...

          But once you master this basic recipe, you will always be in control (and when the "magic" IDE will fail, you will still be in control).

          Once you master theses steps, if the IDE gets fixed, then retry with the proposed way of managing the projects: if it works then great! otherwise... back to the two steps process which will always work.

          I know this is not the answer you were expecting, but at least you will never again be stuck with tools which fail to help you.