https://bugzilla.redhat.com/show_bug.cgi?id=1023116
Stanislav Ochotnicky <sochotni(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |NeedsTestCase
Summary|xmvn_file seems to be |Add support for absolute
|installing the symlink in |paths for artifact symlinks
|the wrong location |
--- Comment #9 from Stanislav Ochotnicky <sochotni(a)redhat.com> ---
OK, so after talking to Mikolaj a bit we decided to switch this back to XMvn.
Reasoning:
1. XMvn currently doesn't support absolute paths for file symlinks. This is due
to the fact that XMvn handles these symlinks as complete artifacts (symlinking
even pom.xml and versioned alternatives automatically) and artifacts have to be
in *some* repository. We have repositories for _javadir and few other
directories but that won't help with absolute paths
2. javapackages-tools can't properly decide what relative paths to give to XMvn
because it doesn't know where the first file will end up (since XMvn decides
based on configuration). It could be _javadir or _jnidir or something
completely else. You *can* currently override with -p switch for mvn_file but
that means packager has to know where the file ends up before creating the
package and ... it gets confusing fast
All that said Mikolaj is now working on a proper fix in XMvn itself so that
absolute symlinks are possible.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=OTQrgUbURt&a=cc_unsubscribe