Maven Tomcat 7 - Build

Question

Tomcat 7을 사용하여 war 파일을 배포하고 있습니다. mojo tomcat-maven-plugin을 사용해야했습니다. tomcat에 설정된 My Http 포트가 8090이고 서버 이름이 localhost입니다.

메이븐은 다음과 같은 오류를주고있다으로 내 응용 프로그램을 배포 할 수 없습니다 :

[ERROR] Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project 01JsfExample: Cannot invoke Tomcat manager: Server returned HTTP response code: 403 for URL: http://localhost:8090/manager/deploy?path=%2Fbalaji&war= -> [Help 1] 

나는 프로그램의 실행하기 전에 다음과 같은 장소에있는 모든 변경이했다.

% TOMCAT_HOME %의/conf의/바람둥이 - users.xml에서

<?xml version='1.0' encoding='utf-8'?> 
<!-- 
    Licensed to the Apache Software Foundation (ASF) under one or more 
    contributor license agreements. See the NOTICE file distributed with 
    this work for additional information regarding copyright ownership. 
    The ASF licenses this file to You under the Apache License, Version 2.0 
    (the "License"); you may not use this file except in compliance with 
    the License. You may obtain a copy of the License at 

     http://www.apache.org/licenses/LICENSE-2.0 

    Unless required by applicable law or agreed to in writing, software 
    distributed under the License is distributed on an "AS IS" BASIS, 
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
    See the License for the specific language governing permissions and 
    limitations under the License. 
--> 
<tomcat-users> 
<!-- 
    NOTE: By default, no user is included in the "manager-gui" role required 
    to operate the "/manager/html" web application. If you wish to use this app, 
    you must define such a user - the username and password are arbitrary. 
--> 
<!-- 
    NOTE: The sample user and role entries below are wrapped in a comment 
    and thus are ignored when reading this file. Do not forget to remove 
    <!.. ..> that surrounds them. 
--> 
<!-- 
    <role rolename="tomcat"/> 
    <role rolename="role1"/> 
    <user username="tomcat" password="tomcat" roles="tomcat"/> 
    <user username="both" password="tomcat" roles="tomcat,role1"/> 
    <user username="role1" password="tomcat" roles="role1"/> 
--> 
    <role rolename="manager-gui"/> 
    <user username="admin" password="admin" roles="manager-gui"/> 

    <role rolename="admin-gui"/> 
    <user username="tomcat" password="s3cret" roles="admin-gui"/> 
</tomcat-users> 

%의 MAVEN_HOME %의/conf의/Settings.XML이 내 pom.xml 파일의 모조 플러그인에서

<?xml version="1.0" encoding="UTF-8"?> 

<!-- 
Licensed to the Apache Software Foundation (ASF) under one 
or more contributor license agreements. See the NOTICE file 
distributed with this work for additional information 
regarding copyright ownership. The ASF licenses this file 
to you under the Apache License, Version 2.0 (the 
"License"); you may not use this file except in compliance 
with the License. You may obtain a copy of the License at 

    http://www.apache.org/licenses/LICENSE-2.0 

Unless required by applicable law or agreed to in writing, 
software distributed under the License is distributed on an 
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 
KIND, either express or implied. See the License for the 
specific language governing permissions and limitations 
under the License. 
--> 

<!-- 
| This is the configuration file for Maven. It can be specified at two levels: 
| 
| 1. User Level. This settings.xml file provides configuration for a single user, 
|     and is normally provided in ${user.home}/.m2/settings.xml. 
| 
|     NOTE: This location can be overridden with the CLI option: 
| 
|     -s /path/to/user/settings.xml 
| 
| 2. Global Level. This settings.xml file provides configuration for all Maven 
|     users on a machine (assuming they're all using the same Maven 
|     installation). It's normally provided in 
|     ${maven.home}/conf/settings.xml. 
| 
|     NOTE: This location can be overridden with the CLI option: 
| 
|     -gs /path/to/global/settings.xml 
| 
| The sections in this sample file are intended to give you a running start at 
| getting the most out of your Maven installation. Where appropriate, the default 
| values (values used when the setting is not specified) are provided. 
| 
|--> 
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> 
    <!-- localRepository 
    | The path to the local repository maven will use to store artifacts. 
    | 
    | Default: ~/.m2/repository 
    <localRepository>/path/to/local/repo</localRepository> 
    --> 
<localRepository>F:/apache-maven-3.0.4/Repository</localRepository> 

    <!-- interactiveMode 
    | This will determine whether maven prompts you when it needs input. If set to false, 
    | maven will use a sensible default value, perhaps based on some other setting, for 
    | the parameter in question. 
    | 
    | Default: true 
    <interactiveMode>true</interactiveMode> 
    --> 

    <!-- offline 
    | Determines whether maven should attempt to connect to the network when executing a build. 
    | This will have an effect on artifact downloads, artifact deployment, and others. 
    | 
    | Default: false 
    <offline>false</offline> 
    --> 

    <!-- pluginGroups 
    | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e. 
    | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers 
    | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list. 
    |--> 
    <pluginGroups> 
    <!-- pluginGroup 
    | Specifies a further group identifier to use for plugin lookup. 
    <pluginGroup>com.your.plugins</pluginGroup> 
    --> 
    </pluginGroups> 

    <!-- proxies 
    | This is a list of proxies which can be used on this machine to connect to the network. 
    | Unless otherwise specified (by system property or command-line switch), the first proxy 
    | specification in this list marked as active will be used. 
    |--> 
    <proxies> 
    <!-- proxy 
    | Specification for one proxy, to be used in connecting to the network. 
    | 
    <proxy> 
     <id>optional</id> 
     <active>true</active> 
     <protocol>http</protocol> 
     <username>proxyuser</username> 
     <password>proxypass</password> 
     <host>proxy.host.net</host> 
     <port>80</port> 
     <nonProxyHosts>local.net|some.host.com</nonProxyHosts> 
    </proxy> 
    --> 
    </proxies> 

    <!-- servers 
    | This is a list of authentication profiles, keyed by the server-id used within the system. 
    | Authentication profiles can be used whenever maven must make a connection to a remote server. 
    |--> 
    <servers> 
    <!-- server 
    | Specifies the authentication information to use when connecting to a particular server, identified by 
    | a unique name within the system (referred to by the 'id' attribute below). 
    | 
    | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 
    |  used together. 
    | 
    <server> 
     <id>deploymentRepo</id> 
     <username>repouser</username> 
     <password>repopwd</password> 
    </server> 
    --> 

    <!-- Another sample, using keys to authenticate. 
    <server> 
     <id>siteServer</id> 
     <privateKey>/path/to/private/key</privateKey> 
     <passphrase>optional; leave empty if not used.</passphrase> 
    </server> 
    --> 
     <server> 
      <id>TomcatServer</id> 
      <username>tomcat</username> 
      <password>s3cret</password> 
     </server> 
    </servers> 

    <!-- mirrors 
    | This is a list of mirrors to be used in downloading artifacts from remote repositories. 
    | 
    | It works like this: a POM may declare a repository to use in resolving certain artifacts. 
    | However, this repository may have problems with heavy traffic at times, so people have mirrored 
    | it to several places. 
    | 
    | That repository definition will have a unique id, so we can create a mirror reference for that 
    | repository, to be used as an alternate download site. The mirror site will be the preferred 
    | server for that repository. 
    |--> 
    <mirrors> 
    <!-- mirror 
    | Specifies a repository mirror site to use instead of a given repository. The repository that 
    | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used 
    | for inheritance and direct lookup purposes, and must be unique across the set of mirrors. 
    | 
    <mirror> 
     <id>mirrorId</id> 
     <mirrorOf>repositoryId</mirrorOf> 
     <name>Human Readable Name for this Mirror.</name> 
     <url>http://my.repository.com/repo/path</url> 
    </mirror> 
    --> 
    </mirrors> 

    <!-- profiles 
    | This is a list of profiles which can be activated in a variety of ways, and which can modify 
    | the build process. Profiles provided in the settings.xml are intended to provide local machine- 
    | specific paths and repository locations which allow the build to work in the local environment. 
    | 
    | For example, if you have an integration testing plugin - like cactus - that needs to know where 
    | your Tomcat instance is installed, you can provide a variable here such that the variable is 
    | dereferenced during the build process to configure the cactus plugin. 
    | 
    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles 
    | section of this document (settings.xml) - will be discussed later. Another way essentially 
    | relies on the detection of a system property, either matching a particular value for the property, 
    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 
    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. 
    | Finally, the list of active profiles can be specified directly from the command line. 
    | 
    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact 
    |  repositories, plugin repositories, and free-form properties to be used as configuration 
    |  variables for plugins in the POM. 
    | 
    |--> 
    <profiles> 
    <!-- profile 
    | Specifies a set of introductions to the build process, to be activated using one or more of the 
    | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/> 
    | or the command line, profiles have to have an ID that is unique. 
    | 
    | An encouraged best practice for profile identification is to use a consistent naming convention 
    | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. 
    | This will make it more intuitive to understand what the set of introduced profiles is attempting 
    | to accomplish, particularly when you only have a list of profile id's for debug. 
    | 
    | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. 
    <profile> 
     <id>jdk-1.4</id> 

     <activation> 
     <jdk>1.4</jdk> 
     </activation> 

     <repositories> 
     <repository> 
      <id>jdk14</id> 
      <name>Repository for JDK 1.4 builds</name> 
      <url>http://www.myhost.com/maven/jdk14</url> 
      <layout>default</layout> 
      <snapshotPolicy>always</snapshotPolicy> 
     </repository> 
     </repositories> 
    </profile> 
    --> 

    <!-- 
    | Here is another profile, activated by the system property 'target-env' with a value of 'dev', 
    | which provides a specific path to the Tomcat instance. To use this, your plugin configuration 
    | might hypothetically look like: 
    | 
    | ... 
    | <plugin> 
    | <groupId>org.myco.myplugins</groupId> 
    | <artifactId>myplugin</artifactId> 
    | 
    | <configuration> 
    |  <tomcatLocation>${tomcatPath}</tomcatLocation> 
    | </configuration> 
    | </plugin> 
    | ... 
    | 
    | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to 
    |  anything, you could just leave off the <value/> inside the activation-property. 
    | 
    <profile> 
     <id>env-dev</id> 

     <activation> 
     <property> 
      <name>target-env</name> 
      <value>dev</value> 
     </property> 
     </activation> 

     <properties> 
     <tomcatPath>/path/to/tomcat/instance</tomcatPath> 
     </properties> 
    </profile> 
    --> 
    </profiles> 

    <!-- activeProfiles 
    | List of profiles that are active for all builds. 
    | 
    <activeProfiles> 
    <activeProfile>alwaysActiveProfile</activeProfile> 
    <activeProfile>anotherAlwaysActiveProfile</activeProfile> 
    </activeProfiles> 
    --> 
</settings> 

가 추가되었습니다 :

<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/xsd/maven-4.0.0.xsd"> 
    <modelVersion>4.0.0</modelVersion> 
    <groupId>com.achutha.labs</groupId> 
    <artifactId>01JsfExample</artifactId> 
    <version>0.0.1-SNAPSHOT</version> 
    <packaging>war</packaging> 
    <name>01JsfExample</name> 


    <dependencies> 

     <dependency> 
      <groupId>com.sun.faces</groupId> 
      <artifactId>jsf-api</artifactId> 
      <version>2.1.7</version> 
     </dependency> 
     <dependency> 
      <groupId>com.sun.faces</groupId> 
      <artifactId>jsf-impl</artifactId> 
      <version>2.1.7</version> 
     </dependency> 

     <dependency> 
      <groupId>javax.servlet</groupId> 
      <artifactId>jstl</artifactId> 
      <version>1.2</version> 
     </dependency> 

     <dependency> 
      <groupId>javax.servlet</groupId> 
      <artifactId>servlet-api</artifactId> 
      <version>2.5</version> 
     </dependency> 

     <dependency> 
      <groupId>javax.servlet.jsp</groupId> 
      <artifactId>jsp-api</artifactId> 
      <version>2.1</version> 
     </dependency> 

    </dependencies> 

    <build> 
     <finalName>JavaServerFaces</finalName> 

     <plugins> 

     <plugin> 
       <groupId>org.codehaus.mojo</groupId> 
       <artifactId>tomcat-maven-plugin</artifactId> 
       <configuration> 
        <url>http://localhost:8090/manager</url> 
        <server>TomcatServer</server> 
        <path>/balaji</path> 
       </configuration> 
      </plugin> 

      <plugin> 
       <groupId>org.apache.maven.plugins</groupId> 
       <artifactId>maven-compiler-plugin</artifactId> 
       <version>2.3.1</version> 
       <configuration> 
        <source>1.6</source> 
        <target>1.6</target> 
       </configuration> 
      </plugin> 
     </plugins> 
    </build> 

</project> 

"깨끗한 바람둥이 : 배포"라는 목표를 가지고 앱을 실행 한 후 결과가 표시됩니다. 여전히 날 같은 오류를 제공 관리자 ID와 암호입니다

<server> 
     <id>TomcatServer</id> 
     <username>admin</username> 
     <password>admin</password> 
    </server> 

:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". 
SLF4J: Defaulting to no-operation (NOP) logger implementation 
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 
[INFO] Scanning for projects... 
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.achutha.labs:01JsfExample:war:0.0.1-SNAPSHOT 
[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:tomcat-maven-plugin is missing. @ line 48, column 11 
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. 
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects. 
[WARNING] 
[INFO]                   
[INFO] ------------------------------------------------------------------------ 
[INFO] Building 01JsfExample 0.0.1-SNAPSHOT 
[INFO] ------------------------------------------------------------------------ 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 01JsfExample --- 
[INFO] Deleting F:\Workspace\01JsfExample\target 
[INFO] 
[INFO] >>> tomcat-maven-plugin:1.1:deploy (default-cli) @ 01JsfExample >>> 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 01JsfExample --- 
[debug] execute contextualize 
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent! 
[INFO] Copying 0 resource 
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ 01JsfExample --- 
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent! 
[INFO] Compiling 1 source file to F:\Workspace\01JsfExample\target\classes 
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 01JsfExample --- 
[debug] execute contextualize 
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent! 
[INFO] Copying 0 resource 
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @ 01JsfExample --- 
[INFO] Nothing to compile - all classes are up to date 
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ 01JsfExample --- 
[INFO] Surefire report directory: F:\Workspace\01JsfExample\target\surefire-reports 

------------------------------------------------------- 
T E S T S 
------------------------------------------------------- 

Results : 

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 

[INFO] 
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ 01JsfExample --- 
[INFO] Packaging webapp 
[INFO] Assembling webapp [01JsfExample] in [F:\Workspace\01JsfExample\target\JavaServerFaces] 
[INFO] Processing war project 
[INFO] Copying webapp resources [F:\Workspace\01JsfExample\src\main\webapp] 
[INFO] Webapp assembled in [47 msecs] 
[INFO] Building war: F:\Workspace\01JsfExample\target\JavaServerFaces.war 
[WARNING] Warning: selected war files include a WEB-INF/web.xml which will be ignored 
(webxml attribute is missing from war task, or ignoreWebxml attribute is specified as 'true') 
[INFO] 
[INFO] <<< tomcat-maven-plugin:1.1:deploy (default-cli) @ 01JsfExample <<< 
[INFO] 
[INFO] --- tomcat-maven-plugin:1.1:deploy (default-cli) @ 01JsfExample --- 
[INFO] Deploying war to http://localhost:8090/balaji 
[INFO] ------------------------------------------------------------------------ 
[INFO] BUILD FAILURE 
[INFO] ------------------------------------------------------------------------ 
[INFO] Total time: 2.015s 
[INFO] Finished at: Tue Dec 11 08:02:52 IST 2012 
[INFO] Final Memory: 8M/25M 
[INFO] ------------------------------------------------------------------------ 
[ERROR] Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project 01JsfExample: Cannot invoke Tomcat manager: Server returned HTTP response code: 403 for URL: http://localhost:8090/manager/deploy?path=%2Fbalaji&war= -> [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/MojoExecutionException 

나는이에 받는다는의 Settings.XML의 변화 같은 예를 시도했다. 오류 403은 액세스가 거부되었음을 의미합니다. 이 문제를 해결하는 방법?

Answer 1

배포에 사용하는 사용자는 manager-script 역할을 가져야합니다. 사용자 이름은 settings.xml에서 사용중인 것과 일치해야합니다.

<user username="admin" password="s3cret" roles="manager-gui,manager-script"/> 

그리고 플러그인의 URI가 있어야한다 /manager/text

<url>http://localhost:8090/manager/text</url> 

참고 : 관리자-GUI + 관리 스크립트 역할이 호스트 관리자 UI 및 REST 인터페이스, 매니저 GUI를 +위한 관리자 - 스크립트 역할은 배포 UI 및 REST 인터페이스 용입니다. 당신이 지시 한대로 난 내 Settings.XML이, 바람둥이-user.xml을하고 pom.xml 파일을 변경