Re: Transitive dependencies and snapshots
On Sat, Jun 19, 2010 at 7:35 PM, Jason van Zyl ja...@sonatype.com 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
Re: Transitive dependencies and snapshots
The newer snapshots look fine, so it looks like they fixed it. Post your POM somewhere and I'll try it the same thing you are. On Jun 20, 2010, at 10:07 AM, Laird Nelson wrote: On Sat, Jun 19, 2010 at 7:35 PM, Jason van Zyl ja...@sonatype.com 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -— Alan Perlis
Re: Checkstyle Plugin doesn't recognize config file URL
Yes that's it thanks a lot!!. On Sat, Jun 19, 2010 at 6:40 PM, lukewpatterson lukewpatter...@gmail.comwrote: Néstor Boscán wrote: ... custom checkstyle configuration file. ... But the plugin generates: Could not find resource URL is this http://jira.codehaus.org/browse/MCHECKSTYLE-129 the problem? remember to take into account this http://jira.codehaus.org/browse/MSITE-443 when trying to set version of that reporting plugin -- View this message in context: http://maven.40175.n5.nabble.com/Checkstyle-Plugin-doesn-t-recognize-config-file-URL-tp510248p510249.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eclipse:eclipse generating wrong version of dynamic web app
On Sat, Jun 12, 2010 at 6:29 AM, David Sharp dshar...@gmail.com wrote: wtpversion is being set to 2.0. The problem is the dynamic web app facet that is being installed is version 2.5, when in fact the version specified in my app's web.xml is version 2.4. As it turns out, this may not even be the cause of my real issue, which is that the Jave EE Modules Dependencie tab thinks that there are invalid values. I thought that this was the cause because of an error message in the eclipse error log, but updating the web application to use version 2.5 so that it matches what eclipse:eclipse generates, doesn't fix the Java EE Module Dependencies problem. Oddly if I open the workspace and projects in Ganymede, everything works fine, it's just not working in Gallileo. When you work out the root cause of the problem and the solution - a summary would be appreciated. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
