groovy: 1 required artifact is missing

[skyisred@…]

Been trying to use macports to install groovy on mac ox 10.6.8 using sudo port install groovy, but get the following error from main.log

:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_groovy/work/groovy-1.8.0" && ant install -DskipTests=true " returned error 1
:error:build Target org.macports.build returned: shell command failed (see log for details)
:debug:build Backtrace: shell command failed (see log for details)
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for groovy): org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Log for groovy is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_groovy/main.log
 

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log.

[skyisred@…]

main.log

[nerdling (Jeremy Lavergne)]

org.fusesource.jansi:jansi:jar:1.6 is missing. It suggests manually downloading as a workaround: should we create a second distfile to handle this or is the host only temporarily down?

[ryandesign (Ryan Carsten Schmidt)]

It built fine for me. :/

[skyisred@…]

jansi-1.6.jar is in groovy-1.8.1/lib folder. Do I need to move it somewhere else or do anything so it sees that file?

[breskeby@…]

the groovy installation downloads some artifacts from maven repositories. I just tested the build again with an empty local maven repo and it works fine for me too. not yet sure what happened during your build.

[breskeby@…]

after having a closer look on your log file, I assume that you may have write access problems within your .m repository. can you retry the port installation with a deleted/removed ~/.m2 directory. Do you have write access to this directory? regards, René

[skyisred@…]

When I tried to delete it as a normal user, I wasn't able to. I had to use sudo bash and then deleted the .m2 directory. Tried a new install of macport and still the same main.log.

[reid.wilbur@…]

I'm seeing a similar issue. I tried removing the ~/.m2 dir, which I had to sudo to get it to work, but still see similar errors. Seems weird to me that the artifact dirs in the .m2 dir are owned by root, presumably because I'm executing "sudo port install groovy" but at the top of the build log

:debug:main Privilege de-escalation not attempted as not running as root.

[reid.wilbur@…]

failed build log

[reid.wilbur@…]

Cc Me!

[packet@…]

I also encountered this bug. I was able to fix it by deleting my old .m2 directory and creating a new .m2 directory, which I then made world-writable (777). This worked. After the groovy port was successfully built, there were some new subdirectories owned by the user "macports". It would probably be best if the groovy port used its own maven .m2 directory and not the one belonging to the user executing the "port" command.

[packet@…]

Cc Me!

[breskeby@…]

thanks for the answers here. i have an idea how to fix this and hope to get it done this evening. thx for your patience

[breskeby@…]

relocate the local m2 repo used by the groovy ant install to the working directory of this port to avoid permission problems during installation.