On Sat, Jun 19, 2010 at 7:35 PM, Jason van Zyl <[email protected]> wrote:
> Actually the POMs are only missing for the older snapshots, the newer ones > have them. So if you've got snapshots turned off and you've been manually > getting new ones with -U then maybe you have one of the version without a > POM. Or the metadata is no good and is pointing at one of the crap versions > without a POM. Or the scoped changed to provided. > OK, well, let's see. I know the scope hasn't changed to provided. The snapshot build the SNAPSHOT seems to resolve to is drools-compiler-5.1.0.20100619.203626-282.jar. I haven't turned snapshots off. I have occasionally here and there run mvn with the -U switch. I've also completely nuked my org/drools directory tree in my local repository and then run mvn without the -U switch. I wish I could figure this out myself; is there somewhere that describes the "-SNAPSHOT"-to-timestamp resolution process? That might have something to do with it...? Thanks for the assistance. I take it, then, that the correct thing to do is to go to the Drools list and say, fix your deployment process? Best, Laird
