On May 6, 2009, at 7:49 AM, Craig L Russell wrote:
Thinking a bit more about it, this isn't a parent pom issue. It's a maven settings issue. Somewhere you need to have the jdo.currentVersion set.If I look in the poms under "releases/2.3-ea/dist/m1-ibiblio-rsync-repository/" they all have <currentVersion>${jdo.currentVersion}</currentVersion>This also seems to be what is being pushed about in IBiblio. It just basically seems wrong to me. They should have real versions in when over there. Isuggest an extra step, before the signing*** Update all poms under m1-ibiblio-rsync-repository to be the real version***This was supposed to be fixed by the parent pom. Something musta gone bad...
Michelle engineered this solution. I don't remember the details on where the version is supposed to be set...
Craig Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[email protected] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
