I'm trying to deploy ear using maven on weblogic 10.3.2 but i faced problem at run time as
"Failed to execute goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy (default) on project spring-ear: Execution default of goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy failed: Plugin org.codehaus.mojo:weblogic-maven-plugin:2.9.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.codehaus.mojo:weblogic-maven-plugin:jar:2.9.1 (): No versions available for weblogic:weblogic:jar:[9.0,11.0) within specified range -> [Help 1]".
so, please can anyone support me for solving this problem in steps.
i've applied the above installation and i've faced another error :
"Failed to execute goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy (default) on project spring-ear: Execution default of goal org.codehaus.mojo:weblogic-maven-plugin:2.9.1:deploy failed: Unable to load the mojo 'deploy' in the plugin 'org.codehaus.mojo:weblogic-maven-plugin:2.9.1'. A required class is missing: org/apache/tools/ant/BuildListener".
Usually this indicates that the POM for the plugin is incorrect - it should be referencing the necessary JARs as dependencies so that they appear in the classpath. I looked in the plugin's POM and it does reference the Ant artifact, which is good because the plugin would not compile without it. Was there any indication that the ant artifact failed to download? Is there an ant/ant/1.6.5/ant-1.6.5.jar file in your local repository?
If none of that helps, run mvn again with the -X option, redirect both stderr and stdout to a file, and attach the file.
By the way, for those of you following along at home, this post points to one of the strengths of Maven. I have no clue as to how the weblogic maven plugin works, and I have never used it. But because it follows the standard Maven build patterns, has a POM that defines its dependencies, and those dependencies are easily located in the central Maven repository. So even though i have no clue as to what the plugin is doing or how it works, I can still do enough digging to provide suggestions as to how to deal with the problem. (For a non-maven project, I would have said "you need to contact the people who created the plugin.")