Strong passed that to the Gradle file() method, which handles the file separators I believe. files() does the same, calling file() for each thing in whatever collection it is given.
I am curious Strong why you explicitly handle classes.jar (apparently for MacOS) when it is already handled? On 03/20/2012 06:16 AM, Hardy Ferentschik wrote: > On Mar 20, 2012, at 11:02, Sanne Grinovero<sa...@hibernate.org> wrote: > >> On 20 March 2012 08:42, Strong Liu<st...@hibernate.org> wrote: >>> On Mar 20, 2012, at 4:32 PM, Sanne Grinovero wrote: >>> >>> Nice, but I guess that won't work on Windows? >>> >>> >>> the file path separator? >> Yes I'm thinking about the file separator, but I didn't try it.. maybe >> it's fine because of some groovy magic. >> For the same reason I'm surprised that the approach we use in Search >> works, not sure why. Maybe windows has the same weirdness as OSX. > I think Maven as well as Groovy apply some magic when it comes to elements on > the classpath. Let's see what the ci jobs tell us. > > --hardy > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > -- > st...@hibernate.org > http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
