Shawn, thanks for that valuable input.
I assume we're going for a pretty similar procedure.
We're using Hudson to verify that the build still works on all platforms
and compilers.
So I guess it's also possible to have Hudson publish the artifacts right away
(didn't try that yet).
However there's
Hi,
I'm creating a local repo from a public m2 repo.
I'd like to re-map the type from sources to srcs in my local repo.
What would be the best way to do this.
Thanks,
Eelamae
--
View this message in context:
http://old.nabble.com/How-to-remap-types-when-creating-local-repository-from-m2-
I can't answer your question, but I can tell you how I handle this.
I felt it was a bad idea to publish a partial module such that one platform's
artifacts are present and other are not. If this happens because of a compiler
error on one platform but not others, then you can get into a bad situ
I already found the cause of my problem.
Apparently it is not a problem to publish just the artifacts for specific
configurations. I just mixed up things when trying to call ivy standalone
(from Makefiles)
Felix Drueke wrote, on 01/12/2011 11:58 AM:
Hi,
I'd like to manage the dependencies of a
I don't know of any way to "partially publish". You might need a two-step
process, where the second step gathers the artifacts built on the various
platforms together (and temporarily stored somewhere) and then does the
actual ivy publishing.
-Archie
2011/1/12 Felix Drueke
> Hi,
>
> I'd like to
Hi,
I'd like to manage the dependencies of a set of C-modules with ivy.
Each of these modules needs to be compiled on different platforms (i.e.
Solaris, Linux, HP-UX and others).
This requires that the same sources are compiled in separate workspaces
(on the different hosts).
In a first attempt
