Is it possible to use [conf] in the artifactspattern for ivy:publish?
A little bit of background, our product needs to be compiled a little
differently for creating different installers, and so what happens is we just
rebuild those binaries with a different Configuration which defines a
conditi
OK so here's a followup. It looks like the resolver can't figure out the [conf]
either. I've got the following resolver with the following ivy:publish:
Instead of publishing to ${local.bin.dir}\binaries\[artifact].[ext] as I would
expect when publishing the bin
zharvey wrote on 09/15/2011 10:56 AM:
(c) It, theoretically, would be possible to script my Apache server to
accept the PUT from Ivy and write these files to my ivyrepo. (Yes, I am
aware of the security concerns that will arise from this, and would have to
take measure into my own hands on that a
Kirby,
I have a number of sub-questions spawning from your last (and very helpful!)
response; but only one of them concerns me immediately. I'll address the
others later.
I guess it makes sense that you can't write to a HTTP url. However, HTTP
does have the PUT method. And now that I've cleaned
zharvey wrote on 09/15/2011 09:29 AM:
Hi Kirby,
Thanks for getting back to me so quickly.
Here's my settings file (ivy-settings.xml):
===
http://my-server.net/modul
On 9/15/2011 6:20 AM, zharvey wrote:
Alan,
Wow - thanks for such a thorough answer! I'm still not seeing the blatent
connection between the publications tag and my ivy:publish task though. Say
I change my ivy.xml:
This just tells Ivy that I've got something to publish called MyModule.
zharvey wrote on 09/15/2011 09:20 AM:
Alan,
Wow - thanks for such a thorough answer! I'm still not seeing the blatent
connection between the publications tag and my ivy:publish task though. Say
I change my ivy.xml:
If you're just going to stick with the default of having the artifac
Hi Kirby,
Thanks for getting back to me so quickly.
Here's my settings file (ivy-settings.xml):
===
http://my-server.net/module_descriptors/[organisation]/[module]-[re
Alan,
Wow - thanks for such a thorough answer! I'm still not seeing the blatent
connection between the publications tag and my ivy:publish task though. Say
I change my ivy.xml:
This just tells Ivy that I've got something to publish called MyModule. But
where do I tell Ivy that MyModule
On 9/15/2011 5:58 AM, zharvey wrote:
(1) What is is the difference between the ivy:publish task called from the
ant buildscript, and the "publications" element defined in the ivy.xml file
("module descriptor")? According to the docs, the publications element is
used to "declare artifacts to be pu
zharvey wrote on 09/15/2011 09:07 AM:
I'm trying to get a project up and running using Ivy for the first time ever.
I'm working on ivy:publish and getting an IllegalStateException stating:
ivy file not found in cache for myOrg#myModule;1.0: please resolve
dependencies before delivering
(C:\User
I'm trying to get a project up and running using Ivy for the first time ever.
I'm working on ivy:publish and getting an IllegalStateException stating:
ivy file not found in cache for myOrg#myModule;1.0: please resolve
dependencies before delivering
(C:\Users\MyUser\.ivy2\cache\resolved-myOrg-myMo
(1) What is is the difference between the ivy:publish task called from the
ant buildscript, and the "publications" element defined in the ivy.xml file
("module descriptor")? According to the docs, the publications element is
used to "declare artifacts to be published", whereas the ivy:publish task
Hi
Anyone with any leads at all?
Cheers / Erik
On Sun, Mar 27, 2011 at 9:09 PM, Erik Andersson wrote:
> Hi
>
> I'm fresh on Ivy and am just starting up my build of dependencies.
> Things were working fine until I ran into beeing dependent of modules
> who also had some same dependencies.
>
> I
14 matches
Mail list logo
