I'm sure I was careful to edit the identifiers offered by release:prepare as shown in the release guide, but the commit that Maven tagged as dspace-3.3-rc1 still says "3.3-SNAPSHOT". Now after release:perform I am left with a local repo. that has staged changes from 3.3-SNAPSHOT to 3.3-rc2-SNAPSHOT (which should be what it pushed to dspace-3_x). (Also, the artifacts never showed up in Sonatype's Nexus where I was supposed to find them, probably because they are SNAPSHOTs?)
Lots of people seem to have had this sort of problem, and similar ones. It seems to be dependent on interaction between versions of m-release-p and git, and sometimes on the locale of the process running git or where you have POMs. Some report that going from m-release-p 2.4.2 to 2.5 fixed the problem, others that going from 2.5 to 2.4.2 fixed it. 3.3 is declaring m-release-p 2.3.2. I'm thinking this means that there's no point in trying to fix it in the POM, because it may still be broken for others (perhaps newly so!). So, any ideas of how to fix this up? For now, all it does is leave us with an RC that has a slightly confusing version. But I don't want to carry this problem over to the release. BTW, DSpace 3.3 RC1 is available on Github for your testing pleasure. :-/ -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
