-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 thanks for the tip! will try next time.
Daniel Kulp wrote: | On Thursday 24 April 2008, Davanum Srinivas wrote: |> I'll edit the md5's by hand for now. Please file a JIRA for next time. |> FWIW, i really don't like the uncertainities involved with the maven |> deploy to production repo's. | | Yea. And for the most part, we aren't allowed to do that anyway as what | gets deployed should be the exact artifacts that were voted on. | "mvn deploy" would generate new artifacts. | | In anycase, if you do something like: | mvn deploy -Ddeploy.altRepository=central::default::file:/tmp/stage | it will "deploy" to /tmp/stage where you can then examine things and then | manually sync things where you want them. Or use the maven-stage-plugin | to sync them to the "production" area. | | The thing that I do is in my ~/.m2/settings.xml, I have a special profile | that I activate that sets that property, turns on the gpg agent for the | gpg plugin, sets maven.test.skip.exec=true (I already know the tests | pass), and pmd.skip=true (I already know this passes as well). | | Dan | | |> Haven't bothered to figure out how to do |> a staging repo :) |> |> -- dims |> |> On Thu, Apr 24, 2008 at 10:11 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: |>> The md5 files on all the recent XmlSchema builds are corrupt in the |>> maven repo. (and there aren't sha1 files either) Same with the |>> axiom stuff. |>> |>> Basically, they all have a leading "\" on them. Example: |>> \9d1ff1229a42b8a93fc1db8c349ce830 |>> |>> instead of just: |>> 9d1ff1229a42b8a93fc1db8c349ce830 |>> |>> Thus, maven is complaining. |>> |>> Now comes my question: how were these generated? Since those |>> projects are maven based, why wasn't maven just used to deploy and |>> let maven generate the md5/sha1 files? |>> |>> |>> -- |>> J. Daniel Kulp |>> Principal Engineer, IONA |>> [EMAIL PROTECTED] |>> http://www.dankulp.com/blog | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFIENgagNg6eWEDv1kRAuYXAJ9tEolgQbshHh+Ra4KXOSPMnaGqTwCgo61P ah9n2izegq7dbuT7wjJaql8= =l8yk -----END PGP SIGNATURE-----
