10 Replies Latest reply on Feb 25, 2013 6:47 AM by aquadrehz

    Maven try to find invalid plugin

    aquadrehz

      I try todeploy this project with goal: clean package jboss-as:deploy -X

      First time it's deployed and can check th result from: http://localhost:8080/RESTfulExample/customer/print

      The example project which found error is from this link: http://www.mkyong.com/webservices/jax-rs/resteasy-spring-integration-example/

       

       

      Then I deploy it again but t failed and the error displayed below.

       

      [Some part of console]

      .....

      [INFO] Scanning for projects...

      [DEBUG] Extension realms for project com.mkyong.common:RESTfulExample:war:1.0-SNAPSHOT: (none)

      [DEBUG] Looking up lifecyle mappings for packaging war from ClassRealm[plexus.core, parent: null]

      [DEBUG] Resolving plugin version for URL=http://localhost

      [DEBUG] Could not find metadata URL=http://localhost/maven-metadata.xml in local (C:\Users\AquaDrehz\.m2\repository)

      [DEBUG] Failure to find URL=http://localhost/maven-metadata.xml in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

      [INFO] ------------------------------------------------------------------------

      [INFO] BUILD FAILURE

      [INFO] ------------------------------------------------------------------------

      [INFO] Total time: 0.230s

      [INFO] Finished at: Wed Feb 13 13:57:17 ICT 2013

      [INFO] Final Memory: 4M/15M

      [INFO] ------------------------------------------------------------------------

      [ERROR] Error resolving version for plugin 'URL=http://localhost' from the repositories [local (C:\Users\AquaDrehz\.m2\repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository -> [Help 1]

      org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for plugin 'URL=http://localhost' from the repositories [local (C:\Users\AquaDrehz\.m2\repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository

       

      ....

       

      ------------------See the detail in attachment: "RestfulExampleError001.txt.zip"------------------------

      or Check Result of Deploying via Maven stand alone version on attachment "MavenStandalone20130213.txt"

       

       

      We found this plugin is created without pom.xml refered also it isn't plug-in name too. (See pom.xml attachment)

      Does it created correcly?
      And what's next step to solve or identify this problem. Please advise.

      More detail can request via this topic, I'll answer as quick as I can.

      RestfulExampleError001.png

       

      ------- Update-----

      - Result of Deploying via Maven 3.0.4  stand alone version on attachment "MavenStandalone20130213.txt"

      - Current project reference which found this issue: http://www.mkyong.com/webservices/jax-rs/resteasy-hello-world-example/

      - [Not resolved; same Result] Reinstall JBoss Developer Studio Version: 6.0.0.GA

      - [Not resolved; same Result] Reinstall JBoss AS 7.1.1 Final.

      - [Not resolved; same Result] Import example project from clean download link.

      - [Not resolved; same Result] Start JBoss Dev. Stu. via ...\jbdevstudio\studio\jbdevstudio.exe -clean.

      - Correct the project download link (previous is incorrect)
      - The error message was changed in this example Reference: http://www.mkyong.com/webservices/jax-rs/jersey-spring-integration-example/

      - [Resolved] Remove .metadata in workspace DIR then all conflict gone.

       

       

      Message was edited by: Aqua Drehz

        • 1. Re: Maven try to find invalid plugin
          nickarls

          Strange. Can you see the artifact in your local repository? How does the build react to an -U parameter?

          • 2. Re: Maven try to find invalid plugin
            aquadrehz

            @Nicolas
            Even -U is result in Build failure. Maybe I 'll try to re-install the JBoss Dev studio.

            • 3. Re: Maven try to find invalid plugin
              nickarls

              Are you running the build from within the Dev studio? Have you tried a stand-alone maven installation?

              1 of 1 people found this helpful
              • 4. Re: Maven try to find invalid plugin
                aquadrehz

                Yes, I always run from IDE. The re-installation doesn't work.
                I suggesr there's some configuration in my project was broken.


                I've execute the deploying procedure via maven standalone version and got different issue.

                Please see the attachment of first message for more detail.

                 

                I also add the reference project detail for further investigateion.

                • 5. Re: Maven try to find invalid plugin
                  aquadrehz

                  I'm stil findout what's wrong while I suggest it's bug!

                  (I've deployed 1 time successfully before it's always broke forever)


                  Anyway,  I need other to check and identify this problem with me.

                  Especially, why it's happened ?

                   

                  After tried from clean download project. The problem doesn't disappear.

                  • 6. Re: Maven try to find invalid plugin
                    nickarls

                    The URL localhost references look strange. Have you tried creating a test project from one of the quickstart maven archetypes?

                    • 7. Re: Maven try to find invalid plugin
                      sfcoy

                      Do you have a ~/.m2/settings.xml file?

                       

                      What does it contain?

                      • 8. Re: Maven try to find invalid plugin
                        aquadrehz

                        @Stephen I have no setting.xml This's clean install. I'm beginner in JBoss.
                        @Nicolas Yes it is strange. I've never use archetypr before. I'll try one.

                         

                        The most I focus is where does the strange URL plugin come from. I suggest that configuration went wrong somewhere.

                        But with my lack of experience I still can't find out.

                        • 9. Re: Maven try to find invalid plugin
                          aquadrehz

                          The error was slighly change after I try another example but it seem related to the same cause.

                           

                           

                          [INFO] Scanning for projects…
                          [INFO] ————————————————————————
                          [INFO] BUILD FAILURE
                          [INFO] ————————————————————————
                          [INFO] Total time: 0.209s
                          [INFO] Finished at: Sun Feb 24 17:31:42 ICT 2013
                          [INFO] Final Memory: 4M/15M
                          [INFO] ————————————————————————
                          [ERROR] Error resolving version for plugin ‘URL=http://localhost’ from the repositories [local (C:\Users\AquaDrehz\.m2\repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository -> [Help 1]
                          [ERROR]
                          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
                          [ERROR] Re-run Maven using the -X switch to enable full debug logging.
                          [ERROR]
                          [ERROR] For more information about the errors and possible solutions, please read the following articles:
                          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException

                          My topic on Jboss Community.

                          • 10. Re: Maven try to find invalid plugin
                            aquadrehz

                            Solution:

                            This cause from th IDE configure.

                            Remove the configuration directory; metadata, as seen in workspace.

                            (All setting in preference will revrted to default value).

                             

                            InvalidClassSolution.png

                             

                            If the IDE start to show strange error and have no solution.

                            I recommend to remove this directory first.