I'm researching the possibility of using a single enterprise repo for
Maven and Ivy dependencies.
I've generated a pom for my module using the makepom task, but the
publish task doesn't want to send it to my Ivy repo. Here is my publish
task:
<target name="publish-shared" depends="dist" description="publish to
the shared repo">
<!--generate the ivy file with resolved dependencies for this
build-->
<ivy:deliver organisation="shps" module="${module}"
revision="${revision}" deliverpattern="ivy-resolved.xml"/>
<!--publish the artifact to the shared repo-->
<ivy:publish resolver="shared" organisation="shps"
module="${module}" revision="${revision}"
artifactspattern="${dist}/[module].[ext]"
overwrite="true"/>
<ivy:makepom ivyfile="ivy.xml" pomfile="${module}-${revision}.pom"/>
<ivy:publish resolver="shared" organisation="shps"
module="${module}" revision="${revision}"
artifactspattern="${module}-${revision}.pom"
overwrite="true"/>
</target>
and here is the output for that task:
publish-shared:
[ivy:deliver] :: delivering :: shps#mymodule;20081008 :: 20081008 ::
integration :: Wed Oct 15 10:43:16 CDT 2008
[Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from
their substitution group) violate "Unique Particle Attribution". During
validation against this schema, ambiguity would be created for those two
particles.
[ivy:deliver] delivering ivy file to ivy-resolved.xml
[ivy:publish] :: delivering :: shps#mymodule;20081008 :: 20081008 ::
integration :: Wed Oct 15 10:43:16 CDT 2008
[Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from
their substitution group) violate "Unique Particle Attribution". During
validation against this schema, ambiguity would be created for those two
particles.
[ivy:publish] delivering ivy file to
D:\eclipse-workspace\mymodule\dist/mymodule.xml
[ivy:publish] :: publishing :: shps#mymodule
[ivy:publish] published mymodule to
D:\ivyrepo/shps/mymodule/jars/mymodule-20081008.jar
[ivy:publish] published ivy to
D:\ivyrepo/shps/mymodule/ivys/ivy-20081008.xml
[ivy:publish] :: publishing :: shps#mymodule
BUILD FAILED
D:\eclipse-workspace\mymodule\build-byhand.xml:150: impossible to
publish artifacts for shps#mymodule;20081008:
java.lang.IllegalStateException: bad ivy file for
shps#mymodule;20081008: mymodule-20081008.pom: java.text.ParseException:
problem occured while parsing ivy file. message: null in
file:/D:/eclipse-workspace/mymodule/mymodule-20081008.pom
I've got it setup to deliver on my local machine using the ant copy
task, but I don't think that will work if my repo is on another machine.
Mike Partridge<HTML><BODY><P><hr size=1></P>
<P><STRONG>
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only
for the person or the entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. If you have received this transmission, but are not the intended
recipient, you are hereby notified that any disclosure, copying, distribution
or use of the contents of this information is strictly prohibited. If you have
received this e-mail in error, please contact the sender of the e-mail and
destroy the original message and all copies.
</STRONG></P></BODY></HTML>
