ivy

Saving a Linq to Xml file as ANSI instead of UTF-8 in C# (Ivy)

点点圈 提交于 2019-12-01 07:33:43
In C#, I need to create XML files for use with Ivy and NAnt, but am having difficulty in getting the right encoding in the output file. If I use XElement's .Save("C:\foo.xml"), I get the correct looking file, but Ivy and/or NAnt gets upset, as the file is actually saved using UTF-8 but I actually need to save it as ANSI in order to be able to use it. I have a bodge in place at present, which is to use .ToString() to get the text and then use a StreamWriter to write it to a file. Ideally, I'd like to set the format during the .Save() but can't find any information on this. Thanks. XDocument

Apache Ivy: Dependency Ivy FIles

五迷三道 提交于 2019-12-01 06:14:43
问题 Threequick questions regarding Apache Ivy: (1) Throughout our projects, we use over 100 "common" JARs (log4j, junit, commons-cli, etc.). Do we have to write the ivy.xml ("module descriptor") files for all of them, or are there generic ones I can find in the ibiblio (or other) repo? To force your users to write their own ivy files for each dependency sounds pretty cruel and unusual to me. (2) Are ivy files even required for a particular JAR, or does Ivy have defaults for when it looks in a

How to copy runtime libraries without the provided ones in IVY

自作多情 提交于 2019-12-01 06:05:30
I thought I wouldn't need to ask this but I am not having any progress. The solution to this question: How are maven scopes mapped to ivy configurations by ivy actually addresses question but in its theoretical part. I have this configuration: <conf name="compile" description="???" /> <conf name="runtime" description="???" extends="compile" /> <conf name="test" description="???" extends="runtime" /> <conf name="provided" description="???" /> Assume I have this dependency: <dependency org="org.apache.tomcat" name="servlet-api" rev="6.0.16" transitive="false" /> What I want is: when I invoke the

Saving a Linq to Xml file as ANSI instead of UTF-8 in C# (Ivy)

半城伤御伤魂 提交于 2019-12-01 04:20:21
问题 In C#, I need to create XML files for use with Ivy and NAnt, but am having difficulty in getting the right encoding in the output file. If I use XElement's .Save("C:\foo.xml"), I get the correct looking file, but Ivy and/or NAnt gets upset, as the file is actually saved using UTF-8 but I actually need to save it as ANSI in order to be able to use it. I have a bodge in place at present, which is to use .ToString() to get the text and then use a StreamWriter to write it to a file. Ideally, I'd

How to copy runtime libraries without the provided ones in IVY

元气小坏坏 提交于 2019-12-01 03:45:14
问题 I thought I wouldn't need to ask this but I am not having any progress. The solution to this question: How are maven scopes mapped to ivy configurations by ivy actually addresses question but in its theoretical part. I have this configuration: <conf name="compile" description="???" /> <conf name="runtime" description="???" extends="compile" /> <conf name="test" description="???" extends="runtime" /> <conf name="provided" description="???" /> Assume I have this dependency: <dependency org="org

How to publish native libraries with Ivy?

佐手、 提交于 2019-12-01 01:05:49
For Java library projects, the artifact to publish is straightforward since the output is a single jar file. However, I also have a project with the following stuff to publish: MyLib.jar armeabi/libStuff.so armeabi-v7a/libStuff.so mips/libStuff.so x86/libStuff.so I cannot setup all those .so files as artifacts, since they all have the same name. What is the recommended way to go? Put everything in a zip and let users use gradle (or ant or whatever) to unzip it prior to the build? Should I put the Jar file aside from the zip? Is there a convention for such artifacts? Nicolas Lalevée The best

How to publish native libraries with Ivy?

无人久伴 提交于 2019-11-30 20:15:49
问题 For Java library projects, the artifact to publish is straightforward since the output is a single jar file. However, I also have a project with the following stuff to publish: MyLib.jar armeabi/libStuff.so armeabi-v7a/libStuff.so mips/libStuff.so x86/libStuff.so I cannot setup all those .so files as artifacts, since they all have the same name. What is the recommended way to go? Put everything in a zip and let users use gradle (or ant or whatever) to unzip it prior to the build? Should I put

How do you integrate ivy with MSbuild

大城市里の小女人 提交于 2019-11-30 20:04:10
What approach has worked well for you combining IVY + msbuild? Our goal is to integrate IVY into the C#/C++ build process for dependency resolution and publishing. We have tried adding it to custom tasks at the beginning and end of the build and we have tried wrapping the msbuild calls with ant+ apache-ant-dotnet. Other options might be gradle, buildr, rake. What do you use? Thanks Peter Most build technologies can use libraries found in a local directory. I'd suggest using the command-line ivy program to populate this, at the start of your build: java -jar ivy.jar -ivy ivy.xml -settings

Ivy: Fetching Javadocs and Sources

孤街醉人 提交于 2019-11-30 19:59:24
I'm fairly new to Ivy, but have gotten it to work with jar dependencies. The problem is trying to set it up, so I can fetch javadocs and sources independently of jars. I have a simple test project, but no matter what I'm doing, I'm fetching the jar with the class files in it. I have the following ivy.xml file: <ivy-module version="1.0"> <info organisation="com.vegicorp" module="test" revision="1.0" status="release"/> <configurations> <conf name="default" visibility="public" extends="runtime,master"/> <conf name="master" visibility="public"/> <conf name="compile" visibility="public"/> <conf

Ivy: Forcing local snapshot for dependency

心不动则不痛 提交于 2019-11-30 15:47:35
I have a Project A which depends on Project B; both are internal projects in active development. Say the latest Project A release is 1.1.2 which depends on Project B 1.1.1. Now we are developing Project A 1.2.0 which depends on the Project B 1.2.0 also in development. <dependency org="my.org" name="projectB" rev="1.2.0" transitive="true" conf="..." changing="true"/> New intergration builds for Project B 1.2.0 are pushed by the CI server in the common local repository, so thanks to "changing" everyone gets the latest integration builds as soon as they are published. Say Bob is developing a new