maven自动部署项目到tomcat总是403 Access Denied

试了很多权限都不行,如

目前的情况是可以登录tomcat的manger页面,但是maven部署的链接是
http://localhost:8080/manager/html/deploy?path=%2Fmyweb
对于http://localhost:8080/manager/html/deploy这个链接的访问就会报403 错误。

请问该怎么设置呢?先谢谢了。
弄了一天了,我想哭。。。

4个回答

wangdachui95345
wangdachui95345 还没解决,能帮忙看看吗
接近 3 年之前 回复

pom.xml:

     <plugin>
        <groupId>org.apache.tomcat.maven</groupId>  
        <artifactId>tomcat7-maven-plugin</artifactId>  
        <version>2.2</version> 
        <configuration>
            <url>http://localhost:8080/manager/html</url>
            <username>admin</username>  
            <password>123456</password>  
            <path>/${project.artifactId}</path>
        </configuration>
    </plugin>

tomcat-users.xml:

 <role rolename="manager"/>
<role rolename="admin"/>
<role rolename="manager-gui"/>
<role rolename="manager-script"/>
<user username = "admin" password = "123456" roles = "admin,manager,manager-gui,manager-script"/>

唉,没有解决,以后有时间再慢慢研究。

Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
其他相关推荐
Myeclipse中maven部署tomcat到指定tomcat中
请教一下:在MyEclipse2016环境中maven自动部署到自带的tomcat中。请问如何部署到自己下载的指定tomcat中?
maven部署项目到tomcat访问404
apache-tomcat-7.0.69, apache-maven-3.3.9-bin, myeclipse部署的项目可以访问。
从svn检出的maven项目怎么在tomcat下部署运行
eclipse环境中,从SVN检出的maven项目无法部署在tomcat下, tomcat检测不到可以部署的项目,求教大神,是不是还要进行处理才能运行? 怎样处理?
winxp下maven 部署项目到tomcat下出现的问题?
我的开发环境是windowsxp +eclipse3.4+tomcat+maven2.0, 我在pom.xml配置好了tomcat的插件,启动tomcat后,运行mvn tomcat:deploy可以进行正常的部署,当时我修改了java代码或者配置文件,想重新部署到tomcat下时,遇到如下问题, Cannot invoke Tomcat manager: FAIL - Application already exists at path / 我再查看tomcat下的webapp目录,发现mvn tomcat:undeploy后项目的目录还存在,项目目录下只留下了 WEB-INF文件夹,WEB-INF文件夹下只存在lib文件夹, 这个文件夹不能被undeploy掉,导致不能重新部署,不知道大家有遇到这个问题的吗? 如果没有遇到此问题,麻烦能告诉我如何在用maven进行热部署吗? 感激不尽
IDEA中maven工程无法部署到tomcat的问题
![图片说明](https://img-ask.csdn.net/upload/201703/09/1489026513_933777.png)网上类似这样的教程很多,什么maven部署Tomcat的,这样那样的,应有尽有 ,对照着试了试,可还是发现有这样的问题,问项目经理后,项目经理有十年的开发经验,说,这个项目存在的问题就是没法再本地启动,必须要有专门的服务器来搭建这个项目,我听的不是很懂。希望有大神来详细的教教我。![图片说明](https://img-ask.csdn.net/upload/201703/09/1489026525_171701.png)
请问谁知道 maven 的 tomcat插件 tomcat-maven-plugin 中 的tomcat是在那里?如何热部署?
小弟最近学习 maven 很好奇 maven 的 tomcat插件 tomcat-maven-plugin 中 的tomcat是在那里?如何热部署? 求大师讲解~
maven项目,tomcat的部署问题
在maven项目中,tomcat:run eclipse使用的是哪个tomcat,这个tomcat是怎么来的, 和pom.xml中的tomcat有联系吗。一般开发的过程中,是用maven的tomcat:run还是 用servers运行.
Maven项目部署到Tomcat的问题
项目不知道怎么回事,maven打包没有任何问题,Tomcat启动后web页面不能正常访问,控制台连续不断地输出以下信息: 七月 26, 2016 6:21:46 下午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["http-bio-8080"] 七月 26, 2016 6:21:46 下午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["http-bio-443"] 七月 26, 2016 6:21:46 下午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["ajp-bio-8009"] 七月 26, 2016 6:21:46 下午 org.apache.catalina.startup.Catalina start 信息: Server startup in 14546 ms 18:21:48.022 [Thread-7] DEBUG o.h.cache.redis.jedis.JedisClient - delete expired cache item in region[hibernate.org.hibernate.cache.internal.StandardQueryCache] expire time=[1469528508021] 18:22:00.015 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: schedFactoryBean_QuartzSchedulerThread 18:22:00.016 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: schedFactoryBean_QuartzSchedulerThread 18:22:00.018 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: schedFactoryBean_QuartzSchedulerThread Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=0 and order0_.PAYMETHOD_ID=? 18:22:00.144 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: schedFactoryBean_QuartzSchedulerThread 18:22:00.153 [schedFactoryBean_Worker-1] DEBUG org.quartz.core.JobRunShell - Calling execute on job DEFAULT.orderPayTimeOutJob Hibernate: select order0_.ID as ID1_29_, order0_.CREATEBY as CREATEBY2_29_, order0_.CREATETIME as CREATETI3_29_, order0_.UPDATEBY as UPDATEBY4_29_, order0_.UPDATETIME as UPDATETI5_29_, order0_.ADDR as ADDR6_29_, order0_.AREA_ID as AREA_ID32_29_, order0_.BUILDING as BUILDING7_29_, order0_.BUYCOUNT as BUYCOUNT8_29_, order0_.CITY_ID as CITY_ID33_29_, order0_.COMM_ID as COMM_ID34_29_, order0_.CONSIGEE as CONSIGEE9_29_, order0_.DELITIME as DELITIM10_29_, order0_.DELIVERY as DELIVER11_29_, order0_.DELIVERYFLAG as DELIVER12_29_, order0_.DELIVERYORDER_ID as DELIVER35_29_, order0_.DISTRCOMPLETETIME as DISTRCO13_29_, order0_.DISTRSTOREID as DISTRST14_29_, order0_.DISTRIBUTIONID as DISTRIB15_29_, order0_.FINSHTIME as FINSHTI16_29_, order0_.FLOOR as FLOOR17_29_, order0_.ORDER_ID as ORDER_I36_29_, order0_.MOBILE as MOBILE18_29_, order0_.NIGHTINCOME as NIGHTIN19_29_, order0_.NUMB as NUMB20_29_, order0_.ONLINEPAYNAME_ID as ONLINEP37_29_, order0_.OPERSTATUS as OPERSTA21_29_, order0_.ORDERBILLNO as ORDERBI22_29_, order0_.ORDERNO as ORDERNO23_29_, order0_.PAYABLE as PAYABLE24_29_, order0_.PAYMETHOD_ID as PAYMETH38_29_, order0_.PROVICE_ID as PROVICE39_29_, order0_.REMARK as REMARK25_29_, order0_.SHIPMENT as SHIPMEN26_29_, order0_.STATUS as STATUS27_29_, order0_.STORE_ID as STORE_I40_29_, order0_.STORETYPE_ID as STORETY41_29_, order0_.SUBMITORDERTIME as SUBMITO28_29_, order0_.TEL as TEL29_29_, order0_.TOTAL as TOTAL30_29_, order0_.UNIT as UNIT31_29_, order0_.USER_ID as USER_ID42_29_ from HS_ORDER order0_ where order0_.STATUS=? and order0_.SUBMITORDERTIME<? and order0_.PAYMETHOD_ID=? limit ? 18:22:00.208 [schedFactoryBean_Worker-1] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: schedFactoryBean_Worker-1 18:22:00.208 [schedFactoryBean_Worker-1] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: schedFactoryBean_Worker-1 18:22:00.209 [schedFactoryBean_Worker-1] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: schedFactoryBean_Worker-1 18:22:00.213 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: schedFactoryBean_QuartzSchedulerThread 18:22:00.213 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: schedFactoryBean_QuartzSchedulerThread 18:22:00.215 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: schedFactoryBean_QuartzSchedulerThread 18:22:00.286 [schedFactoryBean_QuartzSchedulerThread] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: schedFactoryBean_QuartzSchedulerThread 18:22:00.286 [schedFactoryBean_Worker-1] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: schedFactoryBean_Worker-1 18:22:00.290 [schedFactoryBean_Worker-2] DEBUG org.quartz.core.JobRunShell - Calling execute on job DEFAULT.tempOrderSettlementJob 18:22:00.347 [schedFactoryBean_Worker-2] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: schedFactoryBean_Worker-2 18:22:00.348 [schedFactoryBean_Worker-2] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: schedFactoryBean_Worker-2 18:22:00.348 [schedFactoryBean_Worker-2] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' given to: schedFactoryBean_Worker-2 18:22:00.395 [schedFactoryBean_Worker-2] DEBUG o.q.i.j.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' returned by: schedFactoryBean_Worker-2 Hibernate: select dictionary0_.ID as ID1_16_, dictionary0_.CREATEBY as CREATEBY2_16_, dictionary0_.CREATETIME as CREATETI3_16_, dictionary0_.UPDATEBY as UPDATEBY4_16_, dictionary0_.UPDATETIME as UPDATETI5_16_, dictionary0_.CODE as CODE6_16_, dictionary0_.KIND as KIND7_16_, dictionary0_.SORTNO as SORTNO8_16_, dictionary0_.STATUS as STATUS9_16_, dictionary0_.VALUE as VALUE10_16_, dictionary0_.VALUETYPE as VALUETY11_16_ from HS_DICTIONARY dictionary0_ where dictionary0_.CODE=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=0 and order0_.PAYMETHOD_ID=? Hibernate: select dictionary0_.ID as ID1_16_, dictionary0_.CREATEBY as CREATEBY2_16_, dictionary0_.CREATETIME as CREATETI3_16_, dictionary0_.UPDATEBY as UPDATEBY4_16_, dictionary0_.UPDATETIME as UPDATETI5_16_, dictionary0_.CODE as CODE6_16_, dictionary0_.KIND as KIND7_16_, dictionary0_.SORTNO as SORTNO8_16_, dictionary0_.STATUS as STATUS9_16_, dictionary0_.VALUE as VALUE10_16_, dictionary0_.VALUETYPE as VALUETY11_16_ from HS_DICTIONARY dictionary0_ where dictionary0_.CODE=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=10 and order0_.PAYMETHOD_ID=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.DELIVERY=1 and order0_.STATUS=10 Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.DELITIME<? and order0_.DELIVERY=2 and order0_.STATUS=15 18:22:42.981 [QuartzScheduler_schedFactoryBean-USER-20140708ZJ1469528502606_MisfireHandler] DEBUG o.q.impl.jdbcjobstore.JobStoreTX - MisfireHandler: scanning for misfires... 18:22:43.013 [QuartzScheduler_schedFactoryBean-USER-20140708ZJ1469528502606_MisfireHandler] DEBUG o.q.impl.jdbcjobstore.JobStoreTX - Found 0 triggers that missed their scheduled fire-time. Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=0 and order0_.PAYMETHOD_ID=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=10 and order0_.PAYMETHOD_ID=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.DELIVERY=1 and order0_.STATUS=10 Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.DELITIME<? and order0_.DELIVERY=2 and order0_.STATUS=15 Hibernate: select count(deliveryor0_.ID) as col_0_0_ from DELIVERY_ORDER deliveryor0_ where deliveryor0_.CREATETIME<? and deliveryor0_.STATUS=1 18:23:07.397 [Thread-7] DEBUG o.h.cache.redis.jedis.JedisClient - delete expired cache item in region[hibernate.com.hisun.shop.entity.MallVoucherAssignDetail] expire time=[1469528587396] 18:23:07.440 [Thread-7] DEBUG o.h.cache.redis.jedis.JedisClient - delete expired cache item in region[hibernate.org.hibernate.cache.internal.StandardQueryCache] expire time=[1469528587439] Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=0 and order0_.PAYMETHOD_ID=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.STATUS=10 and order0_.PAYMETHOD_ID=? Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.SUBMITORDERTIME<? and order0_.DELIVERY=1 and order0_.STATUS=10 Hibernate: select count(order0_.ID) as col_0_0_ from HS_ORDER order0_ where order0_.DELITIME<? and order0_.DELIVERY=2 and order0_.STATUS=15 Hibernate: select count(deliveryor0_.ID) as col_0_0_ from DELIVERY_ORDER deliveryor0_ where deliveryor0_.CREATETIME<? and deliveryor0_.STATUS=1 18:23:42.949 [QuartzScheduler_schedFactoryBean-USER-20140708ZJ1469528502606_MisfireHandler] DEBUG o.q.impl.jdbcjobstore.JobStoreTX - MisfireHandler: scanning for misfires... 18:23:42.982 [QuartzScheduler_schedFactoryBean-USER-20140708ZJ1469528502606_MisfireHandler] DEBUG o.q.impl.jdbcjobstore.JobStoreTX - Found 0 triggers that missed their scheduled fire-time. 18:23:42.983 [QuartzScheduler_schedFactoryBean-USER-20140708ZJ1469528502606_ClusterManager] DEBUG o.q.impl.jdbcjobstore.JobStoreTX - ClusterManager: Check-in complete.
发布项目到maven中央仓库时提示Access denied to
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project common-parent: Failed to deploy artifacts: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project common-parent: Failed to deploy artifacts: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy artifacts: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.apache.maven.plugin.deploy.DeployMojo.execute (DeployMojo.java:193) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:146) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy (AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute (DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.eclipse.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:301) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:211) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy (DefaultRepositorySystem.java:371) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:142) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy (AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute (DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact cn.dyaoming.common:common-parent:pom:1.0.0-20190411.094108-1 from/to maven-center-access (https://oss.sonatype.org/content/repositories/snapshots/): Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed (ArtifactTransportListener.java:52) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run (BasicRepositoryConnector.java:368) at org.eclipse.aether.connector.basic.BasicRepositoryConnector.put (BasicRepositoryConnector.java:287) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:295) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:211) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy (DefaultRepositorySystem.java:371) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:142) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy (AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute (DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: https://oss.sonatype.org/content/repositories/snapshots/cn/dyaoming/common/common-parent/1.0.0-SNAPSHOT/common-parent-1.0.0-20190411.094108-1.pom at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put (AbstractHttpClientWagon.java:724) at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put (AbstractHttpClientWagon.java:648) at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put (AbstractHttpClientWagon.java:630) at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put (AbstractHttpClientWagon.java:624) at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.put (AbstractHttpClientWagon.java:604) at org.eclipse.aether.transport.wagon.WagonTransporter$PutTaskRunner.run (WagonTransporter.java:686) at org.eclipse.aether.transport.wagon.WagonTransporter.execute (WagonTransporter.java:435) at org.eclipse.aether.transport.wagon.WagonTransporter.put (WagonTransporter.java:418) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$PutTaskRunner.runTask (BasicRepositoryConnector.java:554) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run (BasicRepositoryConnector.java:363) at org.eclipse.aether.connector.basic.BasicRepositoryConnector.put (BasicRepositoryConnector.java:287) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:295) at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:211) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.deploy (DefaultRepositorySystem.java:371) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:142) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy (AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute (DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) [ERROR] [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
maven tomcat 插件 部署原理,及tomcat的访问流程??
很久之前通过maven tomcat7 部署项目后,现在一启动tomcat 就默认访问此项目,想删除此项目。。可找不到。。。
maven 热部署远程tomcat 发布出错
本地的maven工程,想要热部署到远程tomcat服务器上,我按照网上的说法,首先在服务器端tomcat安装目录下修改conf / tomcat-user.xml文件,增加用户权限: ![图片说明](https://img-ask.csdn.net/upload/201611/29/1480403146_660407.png) 然后在本地maven库以及maven安装目录下的settings.xml文件中增加: ![图片说明](https://img-ask.csdn.net/upload/201611/29/1480403217_553579.png) 接着在pom.xml中配置插件 ![图片说明](https://img-ask.csdn.net/upload/201611/29/1480403092_39143.jpg) 网上说因为是第三方的插件,为了防止找不到库,还需要加上如下配置: ![图片说明](https://img-ask.csdn.net/upload/201611/29/1480403309_840518.jpg) 最后我使用package tomcat:deploy、package tomcat:redeploy命令,都提示如下错误 ![图片说明](https://img-ask.csdn.net/upload/201611/29/1480403188_250387.jpg) 不知是哪里出了问题
IDEA+Maven+JDK11与tomcat插件问题
我想请教下是不是jdk11版本不支持在maven里面添加tomcat插件了,导入tomcat7插件pom就一直报错,怎么都没法弄好
IDEA怎么配置tomcat以部署maven聚合web项目
1.聚合之前:idea配置tomcat后,会先将项目打包然后自动部署到本地的tomcat中,这个时候maven的workspace是这个web工程是没问题的 2.现在: war项目依赖前端项目的输出,maven-resources-plugin插件将后者输出的静态资源复制到 指定目录下,因此在前后端项目目录结构至上做了一个聚合项目(modules). 但是在配置tomcat的时候,我们只能选择部署子模块(package=war)的工程,idea也只会把这个子模块的 目录作为workSpace来mvn install,这样的话我之前的做的聚合相当于没有用.... 3.想问:如何让idea在打包时以聚合工程的目录作为workspace然后tomcat去读子模块输出的war包。能不能把这2步分开配置呀
maven 命令启动javaweb项目如何设置tomcat最大连接数,线程数等。【求解】
maven项目,pom使用tomcat7-maven-plugin插件。使用 mvn tomcat7:run 命令启动项目,如何设置tomcat的最大连接数,线程数等属性。
求教:maven工程部署到tomcat出现问题
八月 20, 2015 2:37:39 下午 org.apache.catalina.startup.Catalina start SEVERE: The required Server component failed to start so Tomcat is unable to start. org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) at org.apache.catalina.startup.Catalina.start(Catalina.java:689) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:739) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 7 more Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 9 more Caused by: org.apache.catalina.LifecycleException: A child container failed during start at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:300) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 11 more 八月 20, 2015 2:37:39 下午 org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["http-apr-8080"] 八月 20, 2015 2:37:39 下午 org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["ajp-apr-8009"] 八月 20, 2015 2:37:39 下午 org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina 八月 20, 2015 2:37:39 下午 org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["http-apr-8080"] 八月 20, 2015 2:37:39 下午 org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["ajp-apr-8009"] 八月 20, 2015 2:37:39 下午 org.apache.catalina.core.ApplicationContext log INFO: Closing Spring root WebApplicationContext 2015-08-20 14:37:39 [INFO] org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:862) : Closing Root WebApplicationContext: startup date [Thu Aug 20 14:37:19 CST 2015]; root of context hierarchy 八月 20, 2015 2:37:39 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/emp] registered the JDBC driver [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 八月 20, 2015 2:37:39 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/emp] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. ``` ```
maven项目发布到tomcat时报错
maven项目发布到tomcat时报错如下: ![图片说明](https://img-ask.csdn.net/upload/201707/18/1500339536_792446.png) 使用的tomcat7-maven-plugin插件: ![图片说明](https://img-ask.csdn.net/upload/201707/18/1500339654_419806.png) 百度很久也没解决,求大神指导
eclipse maven项目 怎么实现一点就会自动编译并发布到tomcat
eclipse maven项目 怎么实现一点就会自动编译并发布到tomcat
关于maven远程部署多模块web项目到tomcat失败问题
主模块: ``` <?xml version="1.0" encoding="UTF-8"?> <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>DeployTest</groupId> <artifactId>DeployTest</artifactId> <packaging>pom</packaging> <version>1.0-SNAPSHOT</version> <modules> <module>web2</module> <module>service</module> </modules> <build> <finalName>DeployTest</finalName> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.7</source> <target>1.7</target> <encoding>UTF-8</encoding> </configuration> </plugin> </plugins> </build> </project> ``` service模块: ``` <?xml version="1.0" encoding="UTF-8"?> <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"> <parent> <artifactId>DeployTest</artifactId> <groupId>DeployTest</groupId> <version>1.0-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>service</artifactId> <groupId>service</groupId> <version>1.0</version> </project> ``` web2模块: ``` <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"> <parent> <artifactId>DeployTest</artifactId> <groupId>DeployTest</groupId> <version>1.0-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>web2</artifactId> <packaging>war</packaging> <name>web2 Maven Webapp</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>service</groupId> <artifactId>service</artifactId> <version>1.0</version> </dependency> </dependencies> <build> <finalName>web2</finalName> <plugins> <plugin> <groupId>org.apache.tomcat.maven</groupId> <artifactId>tomcat7-maven-plugin</artifactId> <version>2.1</version> <configuration> <url>http://192.168.1.109:8080/manager/text</url> <username>admin</username> <password>admin</password> <server>tomcat</server> <path>/DeployTest</path> </configuration> </plugin> </plugins> </build> </project> ``` 运行tomcat7:redeploy时抛出异常,有关tomcat7-maven-plugin插件都会抛出异常,这里写的很明白是因为没找到service的jar,但是问题是他是子模块,我不需要这个子模块跑到本地仓库或者远程仓库啊,我只需要他在WEB-INF下的lib里就可以了,他现在是在的。求解决: ``` [ERROR] Failed to execute goal on project web2: Could not resolve dependencies for project DeployTest:web2:war:1.0-SNAPSHOT: Failure to find service:service:jar:1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project web2: Could not resolve dependencies for project DeployTest:web2:war:1.0-SNAPSHOT: Failure to find service:service:jar:1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) at org.codehaus.classworlds.Launcher.main(Launcher.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project DeployTest:web2:war:1.0-SNAPSHOT: Failure to find service:service:jar:1.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185) ... 32 more ``` 运行tomcat7:redeploy时抛出异常,有关tomcat7-maven-plugin插件都会抛出异常,这里写的很明白是因为没找到service的jar,但是问题是他是子模块,我不需要这个子模块跑到本地仓库或者远程仓库啊,我只需要他在WEB-INF下的lib里就可以了,他现在是在的。求解决
maven使用cargo插件自动部署到tomcat8报错
[INFO] Installing /Users/lixiuming/project/MarkFriends/pom.xml to /Users/lixiuming/Documents/repository/com/atguigu/maven/MarkFriends/0.0.1-SNAPSHOT/MarkFriends-0.0.1-SNAPSHOT.pom [INFO] [INFO] --- cargo-maven2-plugin:1.4.13:run (cargo-run) @ MarkFriends --- [INFO] No container defined, using a default [jetty7x, installed] container [INFO] [en2.ContainerRunMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-jetty:jar:1.4.13 for container jetty7x [INFO] [talledLocalContainer] Jetty 7.6.16.v20140903 starting... [INFO] [stalledLocalDeployer] The undeployment phase of the redeploy action has failed: org.codehaus.cargo.container.ContainerException: Not supported [WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Failed to create a Jetty 7.6.16.v20140903 existing configuration [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.772 s [INFO] Finished at: 2018-01-06T16:48:32+08:00 [INFO] Final Memory: 15M/174M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run (cargo-run) on project MarkFriends: Execution cargo-run of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.13:run failed: Failed to create a Jetty 7.6.16.v20140903 existing configuration: Failed to deploy [/Users/lixiuming/project/MarkFriends/target/AtgtuiguWeb.war] to [/Users/lixiuming/Downloads/apache-tomcat-8.0.38/webapps]: Failed to create file [/Users/lixiuming/Downloads/apache-tomcat-8.0.38/contexts/AtgtuiguWeb.xml]: No such file or directory -> [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/PluginExecutionException
相见恨晚的超实用网站
搞学习 知乎:www.zhihu.com 简答题:http://www.jiandati.com/ 网易公开课:https://open.163.com/ted/ 网易云课堂:https://study.163.com/ 中国大学MOOC:www.icourse163.org 网易云课堂:study.163.com 哔哩哔哩弹幕网:www.bilibili.com 我要自学网:www.51zxw
花了20分钟,给女朋友们写了一个web版群聊程序
参考博客 [1]https://www.byteslounge.com/tutorials/java-ee-html5-websocket-example
爬虫福利二 之 妹子图网MM批量下载
爬虫福利一:27报网MM批量下载    点击 看了本文,相信大家对爬虫一定会产生强烈的兴趣,激励自己去学习爬虫,在这里提前祝:大家学有所成! 目标网站:妹子图网 环境:Python3.x 相关第三方模块:requests、beautifulsoup4 Re:各位在测试时只需要将代码里的变量 path 指定为你当前系统要保存的路径,使用 python xxx.py 或IDE运行即可。
字节跳动视频编解码面经
引言 本文主要是记录一下面试字节跳动的经历。 三四月份投了字节跳动的实习(图形图像岗位),然后hr打电话过来问了一下会不会opengl,c++,shador,当时只会一点c++,其他两个都不会,也就直接被拒了。 七月初内推了字节跳动的提前批,因为内推没有具体的岗位,hr又打电话问要不要考虑一下图形图像岗,我说实习投过这个岗位不合适,不会opengl和shador,然后hr就说秋招更看重基础。我当时
Java学习的正确打开方式
在博主认为,对于入门级学习java的最佳学习方法莫过于视频+博客+书籍+总结,前三者博主将淋漓尽致地挥毫于这篇博客文章中,至于总结在于个人,实际上越到后面你会发现学习的最好方式就是阅读参考官方文档其次就是国内的书籍,博客次之,这又是一个层次了,这里暂时不提后面再谈。博主将为各位入门java保驾护航,各位只管冲鸭!!!上天是公平的,只要不辜负时间,时间自然不会辜负你。 何谓学习?博主所理解的学习,它
程序员必须掌握的核心算法有哪些?
由于我之前一直强调数据结构以及算法学习的重要性,所以就有一些读者经常问我,数据结构与算法应该要学习到哪个程度呢?,说实话,这个问题我不知道要怎么回答你,主要取决于你想学习到哪些程度,不过针对这个问题,我稍微总结一下我学过的算法知识点,以及我觉得值得学习的算法。这些算法与数据结构的学习大多数是零散的,并没有一本把他们全部覆盖的书籍。下面是我觉得值得学习的一些算法以及数据结构,当然,我也会整理一些看过
大学四年自学走来,这些私藏的实用工具/学习网站我贡献出来了
大学四年,看课本是不可能一直看课本的了,对于学习,特别是自学,善于搜索网上的一些资源来辅助,还是非常有必要的,下面我就把这几年私藏的各种资源,网站贡献出来给你们。主要有:电子书搜索、实用工具、在线视频学习网站、非视频学习网站、软件下载、面试/求职必备网站。 注意:文中提到的所有资源,文末我都给你整理好了,你们只管拿去,如果觉得不错,转发、分享就是最大的支持了。 一、电子书搜索 对于大部分程序员...
linux系列之常用运维命令整理笔录
本博客记录工作中需要的linux运维命令,大学时候开始接触linux,会一些基本操作,可是都没有整理起来,加上是做开发,不做运维,有些命令忘记了,所以现在整理成博客,当然vi,文件操作等就不介绍了,慢慢积累一些其它拓展的命令,博客不定时更新 顺便拉下票,我在参加csdn博客之星竞选,欢迎投票支持,每个QQ或者微信每天都可以投5票,扫二维码即可,http://m234140.nofollow.ax.
比特币原理详解
一、什么是比特币 比特币是一种电子货币,是一种基于密码学的货币,在2008年11月1日由中本聪发表比特币白皮书,文中提出了一种去中心化的电子记账系统,我们平时的电子现金是银行来记账,因为银行的背后是国家信用。去中心化电子记账系统是参与者共同记账。比特币可以防止主权危机、信用风险。其好处不多做赘述,这一层面介绍的文章很多,本文主要从更深层的技术原理角度进行介绍。 二、问题引入 假设现有4个人...
Python 基础(一):入门必备知识
目录1 标识符2 关键字3 引号4 编码5 输入输出6 缩进7 多行8 注释9 数据类型10 运算符10.1 常用运算符10.2 运算符优先级 1 标识符 标识符是编程时使用的名字,用于给变量、函数、语句块等命名,Python 中标识符由字母、数字、下划线组成,不能以数字开头,区分大小写。 以下划线开头的标识符有特殊含义,单下划线开头的标识符,如:_xxx ,表示不能直接访问的类属性,需通过类提供
这30个CSS选择器,你必须熟记(上)
关注前端达人,与你共同进步CSS的魅力就是让我们前端工程师像设计师一样进行网页的设计,我们能轻而易举的改变颜色、布局、制作出漂亮的影音效果等等,我们只需要改几行代码,不需...
国产开源API网关项目进入Apache孵化器:APISIX
点击蓝色“程序猿DD”关注我回复“资源”获取独家整理的学习资料!近日,又有一个开源项目加入了这个Java开源界大名鼎鼎的Apache基金会,开始进行孵化器。项目名称:AP...
程序员接私活怎样防止做完了不给钱?
首先跟大家说明一点,我们做 IT 类的外包开发,是非标品开发,所以很有可能在开发过程中会有这样那样的需求修改,而这种需求修改很容易造成扯皮,进而影响到费用支付,甚至出现做完了项目收不到钱的情况。 那么,怎么保证自己的薪酬安全呢? 我们在开工前,一定要做好一些证据方面的准备(也就是“讨薪”的理论依据),这其中最重要的就是需求文档和验收标准。一定要让需求方提供这两个文档资料作为开发的基础。之后开发
网页实现一个简单的音乐播放器(大佬别看。(⊙﹏⊙))
今天闲着无事,就想写点东西。然后听了下歌,就打算写个播放器。 于是乎用h5 audio的加上js简单的播放器完工了。 欢迎 改进 留言。 演示地点跳到演示地点 html代码如下`&lt;!DOCTYPE html&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;music&lt;/title&gt; &lt;meta charset="utf-8"&gt
Python十大装B语法
Python 是一种代表简单思想的语言,其语法相对简单,很容易上手。不过,如果就此小视 Python 语法的精妙和深邃,那就大错特错了。本文精心筛选了最能展现 Python 语法之精妙的十个知识点,并附上详细的实例代码。如能在实战中融会贯通、灵活使用,必将使代码更为精炼、高效,同时也会极大提升代码B格,使之看上去更老练,读起来更优雅。 1. for - else 什么?不是 if 和 else 才
数据库优化 - SQL优化
前面一篇文章从实例的角度进行数据库优化,通过配置一些参数让数据库性能达到最优。但是一些“不好”的SQL也会导致数据库查询变慢,影响业务流程。本文从SQL角度进行数据库优化,提升SQL运行效率。 判断问题SQL 判断SQL是否有问题时可以通过两个表象进行判断: 系统级别表象 CPU消耗严重 IO等待严重 页面响应时间过长
2019年11月中国大陆编程语言排行榜
2019年11月2日,我统计了某招聘网站,获得有效程序员招聘数据9万条。针对招聘信息,提取编程语言关键字,并统计如下: 编程语言比例 rank pl_ percentage 1 java 33.62% 2 c/c++ 16.42% 3 c_sharp 12.82% 4 javascript 12.31% 5 python 7.93% 6 go 7.25% 7
通俗易懂地给女朋友讲:线程池的内部原理
餐厅的约会 餐盘在灯光的照耀下格外晶莹洁白,女朋友拿起红酒杯轻轻地抿了一小口,对我说:“经常听你说线程池,到底线程池到底是个什么原理?”我楞了一下,心里想女朋友今天是怎么了,怎么突然问出这么专业的问题,但做为一个专业人士在女朋友面前也不能露怯啊,想了一下便说:“我先给你讲讲我前同事老王的故事吧!” 大龄程序员老王 老王是一个已经北漂十多年的程序员,岁数大了,加班加不动了,升迁也无望,于是拿着手里
经典算法(5)杨辉三角
杨辉三角 是经典算法,这篇博客对它的算法思想进行了讲解,并有完整的代码实现。
编写Spring MVC控制器的14个技巧
本期目录 1.使用@Controller构造型 2.实现控制器接口 3.扩展AbstractController类 4.为处理程序方法指定URL映射 5.为处理程序方法指定HTTP请求方法 6.将请求参数映射到处理程序方法 7.返回模型和视图 8.将对象放入模型 9.处理程序方法中的重定向 10.处理表格提交和表格验证 11.处理文件上传 12.在控制器中自动装配业务类 ...
腾讯算法面试题:64匹马8个跑道需要多少轮才能选出最快的四匹?
昨天,有网友私信我,说去阿里面试,彻底的被打击到了。问了为什么网上大量使用ThreadLocal的源码都会加上private static?他被难住了,因为他从来都没有考虑过这个问题。无独有偶,今天笔者又发现有网友吐槽了一道腾讯的面试题,我们一起来看看。 腾讯算法面试题:64匹马8个跑道需要多少轮才能选出最快的四匹? 在互联网职场论坛,一名程序员发帖求助到。二面腾讯,其中一个算法题:64匹
面试官:你连RESTful都不知道我怎么敢要你?
面试官:了解RESTful吗? 我:听说过。 面试官:那什么是RESTful? 我:就是用起来很规范,挺好的 面试官:是RESTful挺好的,还是自我感觉挺好的 我:都挺好的。 面试官:… 把门关上。 我:… 要干嘛?先关上再说。 面试官:我说出去把门关上。 我:what ?,夺门而去 文章目录01 前言02 RESTful的来源03 RESTful6大原则1. C-S架构2. 无状态3.统一的接
求小姐姐抠图竟遭白眼?痛定思痛,我决定用 Python 自力更生!
点击蓝色“Python空间”关注我丫加个“星标”,每天一起快乐的学习大家好,我是 Rocky0429,一个刚恰完午饭,正在用刷网页浪费生命的蒟蒻...一堆堆无聊八卦信息的网页内容慢慢使我的双眼模糊,一个哈欠打出了三斤老泪,就在此时我看到了一张图片:是谁!是谁把我女朋友的照片放出来的!awsl!太好看了叭...等等,那个背景上的一堆鬼画符是什么鬼?!真是看不下去!叔叔婶婶能忍,隔壁老王的三姨妈的四表...
为啥国人偏爱Mybatis,而老外喜欢Hibernate/JPA呢?
关于SQL和ORM的争论,永远都不会终止,我也一直在思考这个问题。昨天又跟群里的小伙伴进行了一番讨论,感触还是有一些,于是就有了今天这篇文。 声明:本文不会下关于Mybatis和JPA两个持久层框架哪个更好这样的结论。只是摆事实,讲道理,所以,请各位看官勿喷。 一、事件起因 关于Mybatis和JPA孰优孰劣的问题,争论已经很多年了。一直也没有结论,毕竟每个人的喜好和习惯是大不相同的。我也看
SQL-小白最佳入门sql查询一
不要偷偷的查询我的个人资料,即使你再喜欢我,也不要这样,真的不好;
项目中的if else太多了,该怎么重构?
介绍 最近跟着公司的大佬开发了一款IM系统,类似QQ和微信哈,就是聊天软件。我们有一部分业务逻辑是这样的 if (msgType = "文本") { // dosomething } else if(msgType = "图片") { // doshomething } else if(msgType = "视频") { // doshomething } else { // doshom...
致 Python 初学者
欢迎来到“Python进阶”专栏!来到这里的每一位同学,应该大致上学习了很多 Python 的基础知识,正在努力成长的过程中。在此期间,一定遇到了很多的困惑,对未来的学习方向感到迷茫。我非常理解你们所面临的处境。我从2007年开始接触 python 这门编程语言,从2009年开始单一使用 python 应对所有的开发工作,直至今天。回顾自己的学习过程,也曾经遇到过无数的困难,也曾经迷茫过、困惑过。开办这个专栏,正是为了帮助像我当年一样困惑的 Python 初学者走出困境、快速成长。希望我的经验能真正帮到你
“狗屁不通文章生成器”登顶GitHub热榜,分分钟写出万字形式主义大作
一、垃圾文字生成器介绍 最近在浏览GitHub的时候,发现了这样一个骨骼清奇的雷人项目,而且热度还特别高。 项目中文名:狗屁不通文章生成器 项目英文名:BullshitGenerator 根据作者的介绍,他是偶尔需要一些中文文字用于GUI开发时测试文本渲染,因此开发了这个废话生成器。但由于生成的废话实在是太过富于哲理,所以最近已经被小伙伴们给玩坏了。 他的文风可能是这样的: 你发现,...
程序员:我终于知道post和get的区别
是一个老生常谈的话题,然而随着不断的学习,对于以前的认识有很多误区,所以还是需要不断地总结的,学而时习之,不亦说乎
《程序人生》系列-这个程序员只用了20行代码就拿了冠军
你知道的越多,你不知道的越多 点赞再看,养成习惯GitHub上已经开源https://github.com/JavaFamily,有一线大厂面试点脑图,欢迎Star和完善 前言 这一期不算《吊打面试官》系列的,所有没前言我直接开始。 絮叨 本来应该是没有这期的,看过我上期的小伙伴应该是知道的嘛,双十一比较忙嘛,要值班又要去帮忙拍摄年会的视频素材,还得搞个程序员一天的Vlog,还要写BU...
相关热词 c#处理浮点数 c# 生成字母数字随机数 c# 动态曲线 控件 c# oracle 开发 c#选择字体大小的控件 c# usb 批量传输 c#10进制转8进制 c#转base64 c# 科学计算 c#下拉列表获取串口
立即提问