Closed maybeec closed 7 years ago
I ran into a similiar problem. I found that the 'default' JVM the installer chooses is a link to somewhere. The copy task seems not to follow the link (although I told him otherwise).
If it is the same Problem you need to change the JVM to that one that is actually present in +usr/lib/jvm/+
You are right, it does not follow symlinks. However, this may be a special case as the folder/link you are intent to be copied is a already a link. Thus it may just copy the link. However, it does not copy the link, but interprets the link as an empty folder instead.
You are copying files with nio Path, are you? Maybe you have to treat the root folder to be copied by hand to follow the symlink.
The current oomph-task-fscopy implementation does the following:
java/doc
Currently the fscopy task is failing if the folder already exists. I am not sure, whether the folder is added manually beforehand and thus conflicting with this task, or if it is a bug in the fscopy task. I installed into a clean folder. Nothing was existing to be "upgraded". Please evaluate.