[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:Why do you have a "java" directory loose instead of under src/main?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:Maven expects you to use the standard directory structure. You are going to run into extra troubles by deviating from that.
Comal Rajagopalaratnam Muthukumar wrote:
Jeanne Boyarsky wrote:Maven expects you to use the standard directory structure. You are going to run into extra troubles by deviating from that.
Hi
archtypegenerate -D groupId=
-D artifactI=
-D achetypArtifactId=maven -archetype-quikstart
The project that is produced from the above is totally congruent to the
simple stucture shown in the text matter above adhering to the standard directory system
Hence my request for Deploy method need not be hurdle.
Thanks
As
CRMK
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Comal Rajagopalaratnam Muthukumar wrote:
Jeanne Boyarsky wrote:Maven expects you to use the standard directory structure. You are going to run into extra troubles by deviating from that.
Hi
archtypegenerate -D groupId=
-D artifactI=
-D achetypArtifactId=maven -archetype-quikstart
The project that is produced from the above is totally congruent to the
simple stucture shown in the text matter above adhering to the standard directory system
Hence my request for Deploy method need not be hurdle.
Thanks
As
CRMK
Stephan van Hulst wrote:You need to tell Maven how to run the application. For a J2EE application, your application server (such as Tomcat) typically provides a plugin that will copy your artifact to the appropriate directory. For a good example, find a Maven archetype that will setup a web application for a specific application server.
Here's an example for Tomcat: https://tomcat.apache.org/maven-plugin-2.2/
Stephan van Hulst wrote:The "mvn deploy" phase is not related to deploying a web application to a web application container. Deploying an artifact means uploading it to a remote repository.
To deploy your web application, execute the correct goal from the web application container plugin. For Tomcat 6, that's "mvn tomcat6:deploy". For Tomcat 7, the command is "mvn tomcat7:deploy".
Stephan van Hulst wrote:The "mvn deploy" phase is not related to deploying a web application to a web application container. Deploying an artifact means uploading it to a remote repository.
To deploy your web application, execute the correct goal from the web application container plugin. For Tomcat 6, that's "mvn tomcat6:deploy". For Tomcat 7, the command is "mvn tomcat7:deploy".
Stephan van Hulst wrote:Why do you have the same plugin declared twice?
Stephan van Hulst wrote:I can't help you without knowing the exact POM that you're using. The last one you showed is wrong because you declared the plugin twice with different configuration.
Regardless, have you used Google to find what could cause such an error to be thrown?
Stephan van Hulst wrote:The "mvn deploy" phase is not related to deploying a web application to a web application container. Deploying an artifact means uploading it to a remote repository.
To deploy your web application, execute the correct goal from the web application container plugin. For Tomcat 6, that's "mvn tomcat6:deploy". For Tomcat 7, the command is "mvn tomcat7:deploy".
Jeanne Boyarsky wrote:Maven expects you to use the standard directory structure. You are going to run into extra troubles by deviating from that.
Consider Paul's rocket mass heater. |