Emmanuel didn't contribute the existing POM generation stuff, but did create some patches for it that still need applying. The slf4j issue below will be my fault by the looks of it.
I would just go for having both qpid-client and qpid-common at this point and make use of the existing build output. Robbie > -----Original Message----- > From: Andrew Kennedy [mailto:[email protected]] > Sent: 06 February 2011 23:49 > To: [email protected] > Subject: Re: 0.10 release update > > > On 6 Feb 2011, at 23:04, Marnie McCormack wrote: > >> Speaking with others, I think we should definitely target maven > >> artefacts as > >> part of our release distirbution for 0.10. > >> > >> All - are we in shape for this i.e. do the maven artefacts create- > >> able from > >> the build work ok/include the correct dependencies ? I haven't > >> tried them, > >> but iirc others have ? > > Agreed. > > There is a 'genpom' script, called from 'ant pom', but I have no idea > how it is meant to work...? > > > [adk@magenta java]$ ant pom > > Buildfile: /home/adk/projects/qpid-dcommit/qpid/java/build.xml > > > > pom: > > [echo] Running ant for module : junit-toolkit > > > > prepare: > > > > pom: > > [echo] Running ant for module : common > > > > prepare: > > > > pom: > > [java] unable to locate pom for lib/slf4j-api-1.6.1.jar > > > > BUILD FAILED > > /home/adk/projects/qpid-dcommit/qpid/java/build.xml:66: The > > following error occurred while executing this line: > > /home/adk/projects/qpid-dcommit/qpid/java/build.xml:58: The > > following error occurred while executing this line: > > /home/adk/projects/qpid-dcommit/qpid/java/module.xml:210: The > > following error occurred while executing this line: > > /home/adk/projects/qpid-dcommit/qpid/java/common.xml:126: Java > > returned: 1 > > > > Total time: 8 seconds > > > Someone who knows what this is meant to do needs to look at it - I > believe Emmanuel contributed the script in the first place? This > seems like the easiest way to accomplish what we want. And, if the > POM files inherit from 'apache:apache:8' (I don't think they do, > currently) and we set up a few other things properly, then 'mvn > release' should just do the Right Thing as far as getting things into > the official ASF repo, if I understand these correctly: > > http://www.apache.org/dev/publishing-maven-artifacts.html > http://www.apache.org/dev/repository-faq.html > > The alternative is to manually create a set of POM files which behave > as described above, that are published as part of the 'release' ant > task. > > I have (sort of) done this as part of my work creating a buildable > Maven project (which I should really publish on a branch or > something) but those POM files are probably more than we need for > this release. I suppose I could look at them and pare things down so > they are just usable for publishing release artefacts? However, what > artifacts do we want to publish? Should we publish the client and > broker as single JARs, rather than including the common and > management-common JARs separately? > > My POM files, and Emmanuel's script, do the latter, including common > and so on as separate artefacts: > > http://people.apache.org/~ebourg/qpid/maven/ > > Andrew. > -- > -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ; > -- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ; > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
