Extensions may live on github and can be listed on the wiki. Unfortunately, your attachment disappeared. You can use a gist or open a github repository and point us to it.
Antoine On Fri, Mar 19, 2010 at 16:33, Peter Donald <[email protected]> wrote: > On Tue, Mar 16, 2010 at 11:46 AM, Antoine Toulme > <[email protected]> wrote: > > We don't do bnd but I implemented a plugin to do OSGi. We enforce > > dependencies from the manifest to the Buildfile rather than the contrary. > > It's named buildr4osgi. > > That looks neat. I am just new to OSGi so I am just getting my feet > wet and I like the ease with which bnd creates the jars. So I plan to > stick with that for now. > > On Tue, Mar 16, 2010 at 11:55 AM, Rhett Sutphin > <[email protected]> wrote: > > I use bnd with buildr in this project: > > > > https://ncisvn.nci.nih.gov/svn/psc/trunk/ > > > > Take a look at the buildfile and tasks/bnd.rake > > > > I do not use a custom package type, though if I were doing it again now I > would. > > That was a great example thanks. I finally got back to look at this > and ended up customizing your extension so it worked the same way as > my brain does ;) I basically made a :bundle package type and had bnd > create the jar rather than replacing one created by jar. An example of > using the extension is > > desc 'Bundle of jms utility classes' > define 'link', :layout => CentralLayout.new('link') do > bnd['Export-Package'] = > "#{group}.#{leaf_project_name}.*;version=#{version}" > > package :bundle > compile.with JMS > end > > I have attached a version of the extension so that you can see what I > have done. I plan on continuing to refactor the way properties are > handled so that it easier to share sets of properties between > projects. Any thoughts? > > Also is it a good idea to submit this extension to the project? Or is > there another place where tasks like this should live? > > -- > Cheers, > > Peter Donald >
