> However, they do have some documentation on retaining the 'jar' > packaging, but adding in the OSGi metadata in a separate build phase. > Look for the section in that page entitled "Adding OSGi metadata to > existing projects without changing the packaging type". > > But doesn't Ivy have a way of specifying the packaging type in its > metadata? If not, perhaps we can make the modifications for 1.1.1?
I ran into problems with some customisations I had made in Grails. The JARs work fine with straight Grails, but we need to be careful: it's often recommended to specify an artifact type of 'jar' with Ivy if you don't want the -sources and -javadoc JARs. However, if you do this you don't get the Shiro JARs (because the type is no longer 'jar'). That may affect other people using Ivy with Shiro. I haven't checked with Gradle, but that may be affected too since it uses Ivy under the hood. Anyway, this is something we can certainly think about for 1.1.1 and leave 1.1 as is. Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware
