ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Kahn <>
Subject Publish ibiblio + filesystem converts organisation to directories but ibiblio + ssh does not - Where did I go wrong?
Date Thu, 12 May 2011 21:45:57 GMT
Hi all,

Can someone point me to the right place to look to understand why publish
with filesystem artifact pattern expands [organisation] into directories
(repository/com/foo/bar/) but ssh doesn't (repository/

I'm publishing to a maven style repository (local and nexus).  The local
uses filesystem which converts '.'  from [organisation] into sub directories
and ssh does not.  I can hard code the path since my org/groupID isn't
likely to change but I'm perplexed.

<filesystem name="local-m2-publish" m2compatible="true">

<ssh name="nexus-m2-publish-snapshot" user="nexus-user" host="mynexus"

<ivy-module version="2.0" xmlns:m=""> <info
organisation="" module="mylibrary" revision="${revision}" />
<configurations> <conf name="default"/> <conf name="sources"/>
</configurations> <publications> <artifact name="mylibrary" ext="pom"
type="pom" conf="default"/> <artifact name="mylibrary" ext="jar" type="jar"
conf="default"/> </publications> </ivy-module>

The two publish calls are identical except for the resolver

<ivy:publish resolver="local-m2-publish" forcedeliver="true"
module="mylibrary" srcivypattern="ivy.xml" publishivy="false">
<artifacts pattern="${target}/[artifact].[ext]"/>

Please let me know if you see what I'm missing or where's the right place to
find out how pattern's used by ssh.  I have the source and was going to look
there since I can find an answer in the docs.

Thanks for the help


Peter Kahn
Awareness - Intention - Action

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message