Hello,

 

Long time Ruby user, first time 'Buildr' ;)

 

I am converting a Maven application so that it uses Buildr and have
found 2 different ways to  compile all dependencies into a jar, but each
has their issues:

https://gist.github.com/981589 

'Only one project name at a time' error when using 'project.name'
variable

https://gist.github.com/981589/62d9beb2aa98c71b1a93fc1f93d9f895cef0e239 

deps variable is not set

have to hard code project name into uberjar task

 

http://stackoverflow.com/questions/1279419/buildr-package-dependencies-i
nto-a-single-jar 

does not handle paths with spaces 

deletes manifest file

 

I personally like how dependencies are handled with the stack overflow
solution, but  instead of fixing their solution for my needs it just
seems like my time would be better spent modifying buildr to handle this
situation automatically.

So before I get started working on this:

1.       Is this something that the Buildr community would be interested
in, if I were to provide the code?  

2.       I was thinking of implementing something on top of the package
method like package(:jar).with :manifest=>{},:singleJar, but there is
probably a better way (open to suggestions)

3.       Is there an example, or a starting point on how I should
implement this?

 

Brandon

Reply via email to