If you reuse the Java implementation through RJB/JRuby (as we do in from_java_properties) then it becomes only a few lines of code so IMO probably not worth a separate gem.
If you rewrite the implementation then you'll want to track bugs ;) alex On Mon, Apr 26, 2010 at 10:09 AM, Antoine Toulme <[email protected]>wrote: > OK so we should do this from Buildr core then ? I was fancying having a > separate gem to do Java properties. I am sure other Ruby devs have to deal > with those. > > Not that the gem would contain much code, much like the manifest one. It's > just best to track bugs and offer a good coverage. > > On Mon, Apr 26, 2010 at 10:05, Alex Boisvert <[email protected] > >wrote: > > > Hi Antoine, > > > > I would comment on the issue if I could (ggrrrrrr!) but make sure you > check > > out buildr/core/util.rb where we monkey-patch the ruby Hash class to add > > from_java_properties(). You can use it as a good starting point / > > building > > block. > > > > alex > > > > > > On Mon, Apr 26, 2010 at 9:53 AM, Antoine Toulme (JIRA) <[email protected] > > >wrote: > > > > > Extend Buildr to write .properties files > > > ---------------------------------------- > > > > > > Key: BUILDR-426 > > > URL: https://issues.apache.org/jira/browse/BUILDR-426 > > > Project: Buildr > > > Issue Type: Bug > > > Reporter: Antoine Toulme > > > Fix For: 1.4.1 > > > > > > > > > Either as part of core, or as a combination of properties file > > > reader/writer gem + a gem for Buildr integration, provide support for > > Buildr > > > to write and read Java properties files (multilined, etc). > > > > > > -- > > > This message is automatically generated by JIRA. > > > - > > > You can reply to this email to add a comment to the issue online. > > > > > > > > >
