AfflictionNetworks/vilya
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Deploy actionscript library too

Browse Source 
This looks like a bug. Since our bamboo server uses the deploy target for populating the maven
repository, we need to do both libraries there. Alternatively, maybe the build server should use
the install target. (This will overwrite the 1.4.2 jar, but it should be identical).
This commit is contained in:
Jamie Doornbos
2012-12-02 09:48:27 -08:00
parent f578184826
commit 86c395414e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
build.xml
+1 -1
View File
@@ -257,7 +257,7 @@
<target name="-as-deploy" depends="aslib" if="flexsdk.dir"> <target name="-as-deploy" depends="aslib" if="flexsdk.dir">
<mavendeploy file="${deploy.dir}/${ant.project.name}lib.swc" pom="etc/as-pom.xml"/> <mavendeploy file="${deploy.dir}/${ant.project.name}lib.swc" pom="etc/as-pom.xml"/>
</target> </target>
<target name="deploy" depends="dist,aslib,tests,javadoc" <target name="deploy" depends="dist,-as-deploy,tests,javadoc"
description="Deploys our build artifacts to a Maven repository."> description="Deploys our build artifacts to a Maven repository.">
<mavendeploy file="${deploy.dir}/${ant.project.name}.jar" pom="pom.xml" <mavendeploy file="${deploy.dir}/${ant.project.name}.jar" pom="pom.xml"
srcdir="${src.dir}" docdir="${deploy.dir}/docs"/> srcdir="${src.dir}" docdir="${deploy.dir}/docs"/>