Robert Burrell Donkin ha scritto: > IIRC there has been some uncertainty about whether the pom.xml in the > jsieve project is good enough to be published as meta-data into the > repository. it looks ok-ish to me but i'm not a maven expert. > hopefully those who know more will jump in.
Now that we removed the stage repository references and that all of our dependencies are officially published in a public maven repository I think it's safe to use that pom.xml as descriptor. > if we wanted to publish a future jsieve release through the repository: > > 1. what improvements would be needed to > http://svn.apache.org/repos/asf/james/jsieve/trunk/pom.xml ...? Maybe the disclaimer we added to pom.xml should be changed so to reflect the fact that the pom is also used to publish the artifact to the maven repository. > 2. would we need to publish the parent poms ...? They should be already public because we used them for previous jspf and mime4j releases: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/james/james-project/1.2/ Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
