And rolled back to the originals. Fortunately I still had them all in my home dir.
They changed their mind and will deal with it rather than have us mess around with our poms. Hen On Mon, 21 Jun 2004, 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 > > On Mon, 21 Jun 2004, Mark R. Diggory wrote: > > > This is great Henri. I never understood why Maven in its default deploy > > task wouldn't automatically generate or update the POM's as well. > > > > >I've deployed the poms for every commons jar released in the > > >java-repository that my script could find a tag for in CVS. > > > > > >A bunch still missing, and will change release instructions so that > > >it mentions to put a commons-xx-major.minor.bugfix.pom file into the poms/ > > >directory. > > > > > >Reason for this is that by having the pom for each version there, tools > > >can reflect on them. > > > > > >Hen > > > > > > > > >--------------------------------------------------------------------- > > >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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
