Opened 11 years ago
Closed 11 years ago
#41513 closed defect (fixed)
maven-ant-tasks failed install on "mvn: command not found" on OSX 10.9
Reported by: | ketur@… | Owned by: | ieure@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | lynxluna (Didiet) | |
Port: | maven-ant-tasks |
Description
When attempting to install Leiningen via MacPorts, the maven-ant-tasks dependency failed to install. After cleaning I attempted to install maven-ant-tasks alone and received the following error: "mvn: command not found"
info:build sh: mvn: command not found :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant-tasks/work/maven-ant-tasks-2.1.3" && mvn package :info:build Exit code: 127 :error:build org.macports.build for port maven-ant-tasks returned: command execution failed :debug:build Error code: CHILDSTATUS 11998 127 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for maven-ant-tasks: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port maven-ant-tasks for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant-tasks/main.log
Attachments (3)
Change History (12)
comment:1 follow-up: 4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | mavericks added; Mavericks removed |
---|---|
Owner: | changed from macports-tickets@… to ieure@… |
Changed 11 years ago by hal.dace@…
Attachment: | main.2.log added |
---|
comment:2 Changed 11 years ago by hal.dace@…
I'm not the OP but have the same issue. I have attached my main.log here too.
Suggestion: Maven port now installs executable as mvn2, not mvn.
comment:3 follow-ups: 5 6 Changed 11 years ago by hal.dace@…
Update: Workaround - symlinked /opt/local/bin/mvn2 to /opt/local/bin/mvn. Portfile should probably be updated though
comment:4 Changed 11 years ago by ketur@…
Replying to ryandesign@…:
The lines in the log that say "Skipping completed" show this was not a clean attempt. Please "sudo port clean maven-ant-tasks", then try again, then attach the new main.log file.
Sorry, think I attached the log file from my second attempt. I've uploaded the log for the first "sudo port install maven-ant-tasks" after "sudo port clean maven-ant-tasks".
comment:5 Changed 11 years ago by FoolishEwe@…
Replying to hal.dace@…:
Update: Workaround - symlinked /opt/local/bin/mvn2 to /opt/local/bin/mvn. Portfile should probably be updated though
I too had this problem the workaround fixed my issue as well.
comment:6 Changed 11 years ago by pebrc (Peter Brachwitz)
Replying to hal.dace@…:
Update: Workaround - symlinked /opt/local/bin/mvn2 to /opt/local/bin/mvn. Portfile should probably be updated though
sudo port select --set maven maven2
does the trick as well and seems cleaner to me.
comment:7 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | lynxluna@… added |
---|
Has duplicate #41944.
The maven-ant-tasks
port should patch the install process to explicitly use mvn2
.
Changed 11 years ago by lynxluna (Didiet)
Attachment: | Portfile.diff added |
---|
Patch for Portfile on maven
comment:8 follow-up: 9 Changed 11 years ago by lynxluna (Didiet)
I attached the Portfile patch to explicitly use mvn2
command. attachment:Portfile.diff
comment:9 Changed 11 years ago by larryv (Lawrence Velázquez)
Keywords: | mavericks removed |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Thanks. r115203, maintainer timeout.
The lines in the log that say "Skipping completed" show this was not a clean attempt. Please "sudo port clean maven-ant-tasks", then try again, then attach the new main.log file.