sinyagin commented on issue #836:
URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1661295678
Faced the same issue on 1.0-m7 windows version.
`Apache Maven Daemon (mvnd) 1.0-m7 windows-amd64 native client
(b2ef5d81997adbcdb72dc8c5603722538fa641fe)
Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal
Apache Maven 4.0.0-alpha-7 (bf699a388cc04b8e4088226ba09a403b68de6b7b)
Maven home: C:\work\tools\mvnd-0.7.1-windows-amd64\mvn
Java version: 11.0.15, vendor: Eclipse Adoptium, runtime:
C:\work\tools\java\jdk-11.0.15.10-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"`
I was able to get a full stack trace
` Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire
write lock for 'C:\work\repository\.locks\artifact~antlr~antlr~2.7.6.lock' in
30 SECONDS
at
org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
(NamedLockFactoryAdapter.java:202)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:271)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:259)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies
(DefaultRepositorySystem.java:352)
at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
(DefaultProjectDependenciesResolver.java:187)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:242)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectArtifacts
(LifecycleDependencyResolver.java:193)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:131)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:361)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:318)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:178)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:77)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:166)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:163)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:114)
at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject
(SmartBuilderImpl.java:209)
at
io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run
(SmartBuilderImpl.java:81)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1128)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:628)
at java.lang.Thread.run (Thread.java:829)`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
