Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
- <groupId>kam.albert.study</groupId>
- <artifactId>BasicSetup</artifactId>
- <packaging>war</packaging>
- <version>0.0.1-SNAPSHOT</version>
- <name>BasicSetup Maven Webapp</name>
- <url>http://maven.apache.org</url>
- <dependencies>
- <dependency>
- <groupId>org.glassfish</groupId>
- <artifactId>javax.faces</artifactId>
- <version>2.1.3</version>
- <scope>compile</scope>
- </dependency>
- </dependencies>
- <build>
- <finalName>BasicSetup</finalName>
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-compiler-plugin</artifactId>
- <!-- http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html -->
- <configuration>
- <source>1.7</source>
- <target>1.7</target>
- <!-- if this is not set, then it'll use the java that runs eclipse
- Unable to locate the Javac Compiler in: C:\Program Files\Java\jre7\..\lib\tools.jar
- there are other solutions like : - changing the vm for running eclipse -
- change the default runtime jre to jdk path - use mvn jetty:run-forked (for
- new jetty plugin) - use fork (this is what we're doing) - see http://stackoverflow.com/questions/2222560/build-failed-question-maven-jre-or-jdk-problem -->
- <fork>true</fork>
- </configuration>
- </plugin>
- <!-- tomcat plugin dependencies http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html -->
- <plugin>
- <groupId>org.apache.tomcat.maven</groupId>
- <artifactId>tomcat7-maven-plugin</artifactId>
- <version>2.0-SNAPSHOT</version>
- <executions>
- <execution>
- <id>tomcat7-run</id>
- <goals>
- <goal>exec-war-only</goal>
- </goals>
- <phase>package</phase>
- <configuration>
- <path>/</path>
- <tomcatConfigurationFilesDirectory>src/main/webapp/WEB-INF</tomcatConfigurationFilesDirectory>
- </configuration>
- </execution>
- </executions>
- </plugin>
- <!-- jetty seems to very buggy, check : http://stackoverflow.com/questions/7886035/could-not-find-factory-javax-faces-context-facescontextfactory
- http://stackoverflow.com/questions/7885874/jsf-welcome-file-not-recognized -->
- <!--
- be careful when running this since it wont show any error while running as embedded mode
- this can be a source of confusion where u modify things, but doesnt show
- up the changes + no errors, and it turns out you have more than 1 embedded jetty running,
- and you're accessing the old one
- http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin
- more config options at http://radio.javaranch.com/balajidl/2007/11/27/1196176220918.html
- <plugin>
- <groupId>org.mortbay.jetty</groupId>
- <artifactId>jetty-maven-plugin</artifactId>
- <configuration>
- <scanIntervalSeconds>10</scanIntervalSeconds>
- <webApp>
- <contextPath>/basicSetup</contextPath>
- </webApp>
- </configuration>
- </plugin>
- -->
- </plugins>
- </pluginManagement>
- </build>
- <repositories>
- <repository>
- <id>jvnet-nexus-releases</id>
- <name>jvnet-nexus-releases</name>
- <url>https://maven.java.net/content/repositories/releases/</url>
- </repository>
- </repositories>
- <pluginRepositories>
- <!--
- using tomcat 7 snapshot
- use tomcat7:run
- http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
- -->
- <pluginRepository>
- <id>apache.snapshots</id>
- <name>Apache Snapshots</name>
- <url>http://people.apache.org/repo/m2-snapshot-repository</url>
- <releases>
- <enabled>false</enabled>
- </releases>
- <snapshots>
- <enabled>true</enabled>
- </snapshots>
- </pluginRepository>
- </pluginRepositories>
- </project>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement