apache / apache/maven-dependency-plugin
[MDEP-812] Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Kamalpreet](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER288713)** opened **[MDEP-812](https://issues.apache.org/jira/browse/MDEP-812?redirect=false)** and commented
My profile :-
```java
test
maven-dependency-plugin
3.3.0
getClasspathFilenames
properties
org.codehaus.mojo
exec-maven-plugin
3.1.0
java
test
java
-javaagent:${groupId:artifactId:jar}
-classpath
sampleTest
```
When running command
```java
mvn exec:exec -P test
```
, I'm getting error
```java
Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
Error occurred during initialization of VM
agent library failed to init: instrument
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:1000)
```
Why maven-dependency-plugin is not able to resolve jar path? Is there anyway to fix this issue? Any help is much appreciated.
---
**Attachments:**
- [dependency-tree.txt](https://issues.apache.org/jira/secure/attachment/13047414/dependency-tree.txt) (_22.81 kB_)
- [log.txt](https://issues.apache.org/jira/secure/attachment/13047404/log.txt) (_10.34 kB_)
- [log-1.txt](https://issues.apache.org/jira/secure/attachment/13047413/log-1.txt) (_22.22 kB_)
**Issue Links:**
- [MNG-6058](https://issues.apache.org/jira/browse/MNG-6058) Test dependencies should override application dependencies only during testing
(_**"is caused by"**_)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported `mvn exec:exec -P test` command and reviewing the profile configuration, dependency-tree.txt, and log attachments. Compare the behavior with the linked MNG-6058 issue; done means the cause of the unresolved `${groupId:artifactId:jar}` path and an accepted resolution are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100