Maven2

From Resin 3.0

(Difference between revisions)
Jump to: navigation, search
Line 7: Line 7:
 
Which starts a Resin instance pointing to your build directory
 
Which starts a Resin instance pointing to your build directory
  
 +
== Pointing Resin to the build directory ==
 +
 +
Resin can point a web-app directly to the Maven build directory, letting you deploy automatically without involving any extra maven plugins.  The resin.conf configuration looks like:
 +
 +
<resin xmlns="http://caucho.com/ns/resin">
 +
    ...
 +
    <cluster id="">
 +
      ...
 +
      <host id="">
 +
        ...
 +
        <web-app id="my-webapp"
 +
                            root-directory="/home/ferg/maven/my-webapp/target/my-webapp"/>
 +
        ...
 +
 +
You can also grab a generated .war file directly and have it expand into your own Resin workspace, by setting the 'archive-path' attribute of a <web-app> defined in the resin.conf:
 +
 +
  <resin ...
 +
      ...
 +
      <host id="">
 +
      ...
 +
        <web-app id="/my-webapp" root-directory="my-webapp-dir"
 +
                            archive-path="/home/ferg/maven/my-webapp/target/my-webapp.war"/>
 +
      ...
 
== Adding Resin plugin to pom.xml ==
 
== Adding Resin plugin to pom.xml ==
  

Revision as of 03:45, 10 January 2008

Resin 3.1 has a Maven2 snapshot repository at http://caucho.com/m2-snapshot

The Resin Maven plugin supports the following command:

 mvn resin:run

Which starts a Resin instance pointing to your build directory

Pointing Resin to the build directory

Resin can point a web-app directly to the Maven build directory, letting you deploy automatically without involving any extra maven plugins. The resin.conf configuration looks like:

<resin xmlns="http://caucho.com/ns/resin">
   ...
   <cluster id="">
     ...
     <host id="">
       ...
       <web-app id="my-webapp" 
                           root-directory="/home/ferg/maven/my-webapp/target/my-webapp"/>
       ...

You can also grab a generated .war file directly and have it expand into your own Resin workspace, by setting the 'archive-path' attribute of a <web-app> defined in the resin.conf:

 <resin ...
     ...
     <host id="">
     ...
        <web-app id="/my-webapp" root-directory="my-webapp-dir"
                            archive-path="/home/ferg/maven/my-webapp/target/my-webapp.war"/>
     ...

Adding Resin plugin to pom.xml

To add Resin plugins to your maven build, modify the pom.xml as follows:

<project ...>
  ...

   <pluginRepositories>
     <pluginRepository>
       <id>caucho-snap</id>
       <name>Caucho Snapshots</name>
       <url>http://caucho.com/m2-snapshot</url>
     </pluginRepository>
   </pluginRepositories>

  ...

   <build>
     ...
     <plugins>
       <plugin>
         <groupId>caucho.com</groupId>
         <artifactId>resin-maven-plugin</artifactId>
         <version>3.1-SNAPSHOT</version>
       </plugin>
     </plugins>

   </build
</project>

resin:run

On the command line, you can then use

 mvn resin:run

resin:run will start a new Resin instance based on your maven build area. You can then browse the instance directly to verify your code.

Personal tools