I rolled it back on request. Maven 2 seems to use poms more actively, so having Maven 1 poms there caused them problems, so the initial request was to hack our poms to help them there.
In retrospect though, their mind changed as we're not meant to be tweaking the files on ibiblio etc, so I then rolled them back again. Which is why you can't see evidence of the below :) Hen On Wed, 23 Jun 2004, Mark R. Diggory wrote: > Not quite grokking this, or at least its not what I currently see in the > repository...Can you elaborate? > > http://www.apache.org/dist/java-repository/commons-beanutils/poms/commons-beanutils-1.6.pom > > -M. > > Henri Yandell wrote: > > >>Apparantly it's caused a bit of a problem for the Maven-2 work, so I'm > >>going to modify the poms slightly. > >> > >><currentVersion> will have a <version> next to it. > >><id> will also have <groupId>/<artifactId> next to it for both project and > >>dependencies. > >> > >>Shoudln't break for maven 1 or 2, but means they won't be the same as in > >>cvs. > >> > >>Hen > > -- > Mark Diggory > Software Developer > Harvard MIT Data Center > http://www.hmdc.harvard.edu > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
