ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Castrianni <Shawn.Castria...@halliburton.com>
Subject files without extensions as artifacts
Date Sun, 13 Apr 2008 05:37:00 GMT
1. Shouldn't (.[ext]) be the default?  I can't think of why I would ever need a dot with an
extension so it seems better to require the user to do something special to turn that on instead
of the other way around.



2. Which pattern do I change to (.[ext])?  I have cache patterns, resolver patterns, retrieve
patterns, and publish patterns.  Should I go ahead and change all of them?



---

Shawn Castrianni





-----Original Message-----

> Does IVY support files without extensions as artifacts?



Yes





>

>

> I am getting this error looking for my policy file which has no extension:

>

>

> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

>

> [ivy:resolve]           ::              FAILED DOWNLOADS            ::

>

> [ivy:resolve]           :: ^ see resolution messages for details  ^ ::

>

> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

>

> [ivy:resolve]           ::

> Landmark#dsinfra#HEAD;R5000_1.HEAD.1!policy.(homes)

>

> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

>

>

> The (homes) is the type of the artifact and I specified the empty

> string for the ext attribute since there is no extension.



What pattern do you use? You can use conditional parts in your pattern to tell Ivy you don't
want the dot when there's no extension. Eg

[artifact](.[ext])



Xavier



>

>

> This is a show stopper for us.

>

>

> ---

> Shawn Castrianni


---
Shawn Castrianni
CM Chief Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX  77042
Work:  713-839-3086
Cell:  832-654-0888
Fax:  713-839-2758

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information
for the sole use of the intended recipient.  Any review, use, distribution, or disclosure
by others is strictly prohibited.  If you are not the intended recipient (or authorized to
receive information for the intended recipient), please contact the sender by reply e-mail
and delete all copies of this message.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message