Hi Alex,

> I haven't had time to look into this today

No problem, the buildfile had a bug anyway, here is the corrected version:
define "merge-fail" do
   project.version = "1.0.0"
   define "webshop-war" do
     images = zip(_(:target, 
"images.zip")).include(project.parent._("config","images", "**"))
     war = package(:war)
     war.enhance([images]) # workaround for BUILDR-605
     war.path("images").merge(images)
   end
end

I should say, that I ran the tests under Linux (Ubuntu 12.04 LTS) and 
with buildr version 1.4.7.
Under Windows 7 with the same buildr version I could not reproduce the 
problem.

>   ... I suspect the
> non-deterministic behavior is due to putting things in a hash map.  Will
> see if we can fix or if there's a workaround.  Stay tuned.

Yes, I think you are quite right with that. I did a trace of these 
builds and there is indeed some variation between them. If you want, I 
can paste the trace logs here, too. Maybe that already is enough for you 
to see what is going on.

Cheers, Ingo =;->

Hi Ingo,

I haven't had time to look into this today ... I suspect the
non-deterministic behavior is due to putting things in a hash map.  Will
see if we can fix or if there's a workaround.  Stay tuned.

alex


On Tue, May 21, 2013 at 5:25 AM, Ingo Schmidt <antispam@der-ingo.de> wrote:

> Hi,
>
> once again I have a problem with merging.
>
> Consider the following extremely simple project layout:
> /config/images/logo.png
> /webshop-war/src/main/webapp/**images/logo.png
>
> And the buildfile looks like this:
> define "merge-fail" do
>     project.version = "1.0.0"
>     define "webshop-war" do
>         images = zip(_(:target, images.zip)).include(project.**parent)
>         war = package(:war)
>         war.enhance([images]) # workaround for BUILDR-605
>         war.path("images").merge(**images)
>     end
> end
>
> When running "buildr clean package" I can observe the following behaviour:
> Sometimes the logo from the config folder is included in the WAR file,
> sometimes the one from webshop-war/images.
>
> I have not found out as to why this happens. Sometimes you get the same
> result 20 times in a row, so do run as often until you finally see this
> behaviour.
>
> Could someone explain me what this is?
>
> Any ideas for a workaround?
> What I would like to achieve is the following:
> If there is a picture in the config folder, use that one, otherwise use
> the default one inside webshop-war/images. What is the correct way of doing
> this? I am really stuck now...
>
>
>
> Cheers, Ingo =;->
>

Hi,

once again I have a problem with merging.

Consider the following extremely simple project layout:
/config/images/logo.png
/webshop-war/src/main/webapp/images/logo.png

And the buildfile looks like this:
define "merge-fail" do
     project.version = "1.0.0"
     define "webshop-war" do
         images = zip(_(:target, images.zip)).include(project.parent)
         war = package(:war)
         war.enhance([images]) # workaround for BUILDR-605
         war.path("images").merge(images)
     end
end

When running "buildr clean package" I can observe the following behaviour:
Sometimes the logo from the config folder is included in the WAR file, 
sometimes the one from webshop-war/images.

I have not found out as to why this happens. Sometimes you get the same 
result 20 times in a row, so do run as often until you finally see this 
behaviour.

Could someone explain me what this is?

Any ideas for a workaround?
What I would like to achieve is the following:
If there is a picture in the config folder, use that one, otherwise use 
the default one inside webshop-war/images. What is the correct way of 
doing this? I am really stuck now...



Cheers, Ingo =;->

Apache Buildr is a build system for Java-based applications, including support
for Scala, Groovy and a growing number of JVM languages and tools.  We wanted
something that's simple and intuitive to use, so we only need to tell it what
to do, and it takes care of the rest.  But also something we can easily extend
for those one-off tasks, with a language that's a joy to use.


New in this release:

  * Added:  BUILDR-648 Add new package(:test_jar) packaging type.
            Submitted by Mike Pettypiece.
  * Fixed:  BUILDR-666 ZipFile.open modifies file regardless of usage.
            Reported by Pepijn Van Eeckhoudt, fix by Alex Boisvert.
  * Change: Moved to using TravisCI to test the Linux variants.
  * Added:  Make the location of the wsdl in generated source configurable
            in the wsgen addon.
  * Added:  When generating the GWT facet for Intellij IDEA modules, use
            the gwt-dev maven artifact dependency if present as the SDK,
            falling back to the existing behaviour if not possible.
  * Added:  Improved support for auto-detection of VCS dirs when creating
            IDEA projects.
  * Added:  Added support for SuperDevMode in gwt addon and upgraded to
            GWT 2.5.1 by default.
  * Change: BUILDR-664 Update Checkstyle addon so that extra_dependencies is
            empty by default. Submitted by Dieter Vrancken.
  * Fixed:  BUILDR-663 require 'buildr' fails for Ruby 2.0.0.
  * Fixed:  BUILDR-665 Java artifacts in build.yaml breaking ArchiveTask.
            Submitted by Antonio Pérez Barrero.
  * Fixed:  BUILDR-662 reported time is much shorter than actual


To learn more about Buildr and get started:
http://buildr.apache.org/

Thanks!
The Apache Buildr Team

Hi Khristian,

Here's a snippet from our buildfile. The main reason I added 
configuration via Ruby objects is to allow configuration to be generated 
in the build script. In the example below this is used to generate 
'keep' directives for every file in a specific directory.

Pepijn

jar = package(:type => :obfuscatedjar).tap do |p|
   p.with :note => false,
          :warn => false,
          :renamesourcefileattribute => package_id,
          :keepparameternames => true,
          :configuration => _('baseconfig.pro'),
          :printmapping => _(:target, "mapping"),
          :printconfiguration => _(:target, package_id + "config")
   p.dependencies.clear
   p.use android.platform_jar

   p.keep :attributes
   p.keep :packagenames
   # Generate a keep entry for each class in the public API tree
   glob(src, "**/*.java").map { |f| f[0..-6].gsub('/', '.') }.each do 
|class_name|
     [class_name, class_name + '$*'].each do |class_pattern|
       p.keep({:access => 'public',
               :name => class_pattern,
               :field => {:access => 'public protected'},
               :method => {:access => 'public protected'},
               :constructor => {:access => 'public protected'}})
     end
   end

   # Keep all classes with native methods.
   p.keep(:classeswithmembers, {:type => 'class', :method => {:access => 
'native'}})

   p.keep(:classmembers, {:type => 'enum', :method => {:access => 
'public static', :name => 'values'}})
   p.keep(:classmembers, {:type => 'enum', :method => {:access => 
'public static', :name => 'valueOf'}})
   p.keep(:classmembernames, {:type => 'class', :method => {:name => 
'class$*'}})
end

On 25-04-13 11:16, Khristian Schönrock wrote:
> Thanks for the tips, Pepijn and Alex!
>
> I didn't manage to get your Proguard task working as it is, so I made a few
> modifications until it worked:
> - Proguard version: updated to 4.8 (internal requirement);
> - Proguard dependency: changed groupId to net.sf.proguard;
> - rt.jar inclusion: substituted it with the version from Alex's script;
> - obfuscate() method: since I keep my Proguard configurations in a separate
> file, I only provided the :configuration option. The " {'keep' => @keep,
> 'whyareyoukeeping' => @whykeeping}..." part of the function didn't seem to
> like it so much, so I removed it. Could you perhaps provide an example of
> how you use your task?
>
> Other than that, it now behaves as expected, and my build runs all the way
> to the end.

Thanks for the tips, Pepijn and Alex!

I didn't manage to get your Proguard task working as it is, so I made a few
modifications until it worked:
- Proguard version: updated to 4.8 (internal requirement);
- Proguard dependency: changed groupId to net.sf.proguard;
- rt.jar inclusion: substituted it with the version from Alex's script;
- obfuscate() method: since I keep my Proguard configurations in a separate
file, I only provided the :configuration option. The " {'keep' => @keep,
'whyareyoukeeping' => @whykeeping}..." part of the function didn't seem to
like it so much, so I removed it. Could you perhaps provide an example of
how you use your task?

Other than that, it now behaves as expected, and my build runs all the way
to the end.


On Mon, Apr 15, 2013 at 6:20 PM, Alex Boisvert <alex.boisvert@gmail.com>wrote:

> Thanks for sharing Pepijn.   Your version has much better bones than the
> one I threw together quickly.
>
> Khristian: I suggest you try it and go/extend from there.
>
>
> On Mon, Apr 15, 2013 at 12:54 AM, Pepijn Van Eeckhoudt <
> pepijn@vaneeckhoudt.net> wrote:
>
> > Hi Khristian,
> >
> > I've made a copy of the Proguard extension I use at work available at
> > https://gist.github.com/**pepijnve/5386437<
> https://gist.github.com/pepijnve/5386437>
> >
> > It's essentially a wrapper for the Proguard Ant task. I've added support
> > for the options that I actually needed. Might not be 100% complete but
> all
> > the essential parts are there.
> >
> > I haven't experienced any issues related to the task calling exit.
> Perhaps
> > exit is not invoked when using Proguard via the Ant task rather then via
> > its own main method.
> >
> > Regards,
> >
> > Pepijn
> >
> >
> > On 12-04-13 14:27, Khristian Schönrock wrote:
> >
> >> Hi Alex,
> >>
> >> thanks for your help! I got my proguard task going as I wanted after a
> few
> >> modifications to your script:
> https://gist.github.com/**derkosak/5371630<
> https://gist.github.com/derkosak/5371630>
> >>
> >> However, I seem to have stumbled upon the "task calls exit(), buildr
> exits
> >> as well" issue. How can I work around this? I've read that forking the
> >> call
> >> does the trick, but couldn't figure out how it is done.
> >>
> >> TIA,
> >> Khristian
> >>
> >>
> >>
> >> On Sat, Apr 6, 2013 at 12:28 AM, Alex Boisvert <alex.boisvert@gmail.com
> >*
> >> *wrote:
> >>
> >>  Hi Khristian,
> >>>
> >>> I hacked something quickly together here:
> >>> https://gist.github.com/**aboisvert/5323180<
> https://gist.github.com/aboisvert/5323180>
> >>>
> >>> I didn't use the Ant task since I thought it was too much trouble
> >>> compared
> >>> to using the Proguard 'main class' and passing argument directly to it.
> >>> Note that this is just a prototype that doesn't support many of the
> >>> proguard options .. basically the bare minimum to get you going.
> >>>
> >>> Hope this helps,
> >>> alex
> >>>
> >>>
> >>>
> >>> On Fri, Apr 5, 2013 at 7:47 AM, Khristian Schönrock <
> >>> smirnegger@gmail.com
> >>>
> >>>> wrote:
> >>>>
> >>>
> >>>  Hello everyone,
> >>>> I'm trying to add a proguard task to my project. So far I've not found
> >>>>
> >>> any
> >>>
> >>>> sort of Proguard-addon for Buildr, so I tried using the Ant task.
> >>>>
> >>>> I tried to mimic the OpenJPA task, and ended up with the following
> code:
> >>>>
> >>>> REQUIRES = [ ...bunch of libraries... ]
> >>>>
> >>>> ant('proguard') do |ant|
> >>>>      ant.taskdef :name=>'proguard',
> >>>>
> >>> :classname=>'proguard.ant.**ProGuardTask',
> >>>
> >>>>        :classpath=>REQUIRES.join(**File::PATH_SEPARATOR)
> >>>>      ant.proguard :configuration=>_('../build/co**nfiguration.pro<
> http://configuration.pro>'),
> >>>> #
> >>>>
> >>> config
> >>>
> >>>> file
> >>>>        :injars=>project('my_project') # snag here
> >>>> end
> >>>>
> >>>> And so I am left with a bunch of intertwining questions:
> >>>>
> >>>> - Since I'm defining the task in a project that should be processed
by
> >>>> proguard, I'm not sure how I should add the project to the classpath.
> >>>> - Moving the proguard task to some other project ("distribution", for
> >>>> example) solves the problem, but proguard complains that I need to
> >>>> define
> >>>> the "-injars" parameter, which I tried unsuccessfully with the :injars
> >>>>
> >>> code
> >>>
> >>>> above.
> >>>> - Since "-injars" is part of the configuration, in the Proguard Ant
> task
> >>>>
> >>> it
> >>>
> >>>> can be defined either in the configuration file ("configuration.pro
> "),
> >>>>
> >>> or
> >>>
> >>>> in the body of the <configuration> tag. Supposing the :configuration
> key
> >>>> maps to this tag, can I add this "tag content"?
> >>>>
> >>>> How do I best configure this?
> >>>>
> >>>> Thanks in advance,
> >>>> Khristian
> >>>>
> >>>>
> >>>
> >>
> >
>

Thanks Peter! I added the @rakefile and repositories lines, and now it
works like a charm. The current version can be found here:
https://gist.github.com/derkosak/5434126


On Sat, Apr 20, 2013 at 1:07 AM, Peter Donald <peter@realityforge.org>wrote:

> Hi,
>
> On Fri, Apr 19, 2013 at 6:41 PM, Khristian Schönrock
> <smirnegger@gmail.com> wrote:
> > I wrote a small ruby app that works as a "artifact repository" of sorts,
> > and allows me to query my local repository and/or to download artifacts
> on
> > demand. I'm using Buildr to access and manipulate the artifacts.
> > I've got the "query" part down, but the "download on demand" bit is
> giving
> > me a bit of trouble. What I tried is:
> >
> > -----------------
> > require 'rubygems'
> > require 'buildr'
> >
> > def search_for_artifact(spec)
> >   art=Buildr.artifact(spec)
> >   art.invoke unless art==nil
> > end
> > -----------------
> >
> > This works when the artifact is already present, but fails when it must
> be
> > downloaded with "Internal Error: attempting to access local setting
> before
> > buildfile located". How can I use this functionality without a buildfile?
>
> The ugliest way is to set a private variable inside the buildr
> application so it works around the lack of a build file. An example of
> this in action is at;
>
> https://gist.github.com/realityforge/5423856
>
> --
> Cheers,
>
> Peter Donald
>

Hi,

On Fri, Apr 19, 2013 at 6:41 PM, Khristian Schönrock
<smirnegger@gmail.com> wrote:
> I wrote a small ruby app that works as a "artifact repository" of sorts,
> and allows me to query my local repository and/or to download artifacts on
> demand. I'm using Buildr to access and manipulate the artifacts.
> I've got the "query" part down, but the "download on demand" bit is giving
> me a bit of trouble. What I tried is:
>
> -----------------
> require 'rubygems'
> require 'buildr'
>
> def search_for_artifact(spec)
>   art=Buildr.artifact(spec)
>   art.invoke unless art==nil
> end
> -----------------
>
> This works when the artifact is already present, but fails when it must be
> downloaded with "Internal Error: attempting to access local setting before
> buildfile located". How can I use this functionality without a buildfile?

The ugliest way is to set a private variable inside the buildr
application so it works around the lack of a build file. An example of
this in action is at;

https://gist.github.com/realityforge/5423856

-- 
Cheers,

Peter Donald

Hello,
I wrote a small ruby app that works as a "artifact repository" of sorts,
and allows me to query my local repository and/or to download artifacts on
demand. I'm using Buildr to access and manipulate the artifacts.
I've got the "query" part down, but the "download on demand" bit is giving
me a bit of trouble. What I tried is:

-----------------
require 'rubygems'
require 'buildr'

def search_for_artifact(spec)
  art=Buildr.artifact(spec)
  art.invoke unless art==nil
end
-----------------

This works when the artifact is already present, but fails when it must be
downloaded with "Internal Error: attempting to access local setting before
buildfile located". How can I use this functionality without a buildfile?

Thanks,
Khristian

Yep thats what I'm asking, thanks
On Apr 18, 2013 6:05 AM, "Peter Donald" <peter@realityforge.org> wrote:

> Hi,
>
> I am not sure what you are asking. Are you asking whether you can fast
> fail the tests for a project, the first time a test in the project
> fails? If that is what you are asking, I am not sure. Buildr uses the
> underlying junit task from ant and as far as I can tell , that is not
> a feature supported by that tool?
>
> [1] http://ant.apache.org/manual/Tasks/junit.html
>
> On Wed, Apr 17, 2013 at 3:10 PM, Jason Hoogland <hoogland@gmail.com>
> wrote:
> > With fail_on_failure it looks like you can control whether buildr will
> fail
> > a test task upon a junit test failure.  But is there a way to stop the
> > execution of further test suites upon a test failure?
> >
> > hoogs
>
>
>
> --
> Cheers,
>
> Peter Donald
>

Hi,

I am not sure what you are asking. Are you asking whether you can fast
fail the tests for a project, the first time a test in the project
fails? If that is what you are asking, I am not sure. Buildr uses the
underlying junit task from ant and as far as I can tell , that is not
a feature supported by that tool?

[1] http://ant.apache.org/manual/Tasks/junit.html

On Wed, Apr 17, 2013 at 3:10 PM, Jason Hoogland <hoogland@gmail.com> wrote:
> With fail_on_failure it looks like you can control whether buildr will fail
> a test task upon a junit test failure.  But is there a way to stop the
> execution of further test suites upon a test failure?
>
> hoogs



-- 
Cheers,

Peter Donald

With fail_on_failure it looks like you can control whether buildr will fail
a test task upon a junit test failure.  But is there a way to stop the
execution of further test suites upon a test failure?

hoogs

Peter,

Yes have observed, but I removed the problem by replacing System.exit
statements in the java with exceptions.  But thanks for the tip.

hoogs


On Wed, Apr 17, 2013 at 11:27 AM, Peter Donald <peter@realityforge.org>wrote:

> On Tue, Apr 16, 2013 at 11:59 PM, Jason Hoogland <hoogland@gmail.com>
> wrote:
> > If the jvm during junit tests forks abnormally, standard output won;t be
> > shown becaused its buffered.  Apparently this can be switched off (e.g.
> > http://comments.gmane.org/gmane.comp.apache.maven.issues/28714,
> >
> http://grokbase.com/t/hadoop/zookeeper-user/10b4h71k09/junit-tests-do-not-produce-logs-if-the-jvm-crashes
> > ).
> >
> > Any ideas on whether/how this might be done with buildr?
>
> Have you observed buffering in Buildr? I would not have thought this
> is a problem with the Junit integration built in as it uses the
> default reports and not any of the ones the buffering. Even if that
> was the cvase you can pass system properties and jvm parameters to the
> test JVM that will control this behavior.
>
> test.using :properties => {"myvar" => "x"}, :java_args => :{"myvar" => "x"}
>
>
>
> --
> Cheers,
>
> Peter Donald
>

On Tue, Apr 16, 2013 at 11:59 PM, Jason Hoogland <hoogland@gmail.com> wrote:
> If the jvm during junit tests forks abnormally, standard output won;t be
> shown becaused its buffered.  Apparently this can be switched off (e.g.
> http://comments.gmane.org/gmane.comp.apache.maven.issues/28714,
> http://grokbase.com/t/hadoop/zookeeper-user/10b4h71k09/junit-tests-do-not-produce-logs-if-the-jvm-crashes
> ).
>
> Any ideas on whether/how this might be done with buildr?

Have you observed buffering in Buildr? I would not have thought this
is a problem with the Junit integration built in as it uses the
default reports and not any of the ones the buffering. Even if that
was the cvase you can pass system properties and jvm parameters to the
test JVM that will control this behavior.

test.using :properties => {"myvar" => "x"}, :java_args => :{"myvar" => "x"}



-- 
Cheers,

Peter Donald

If the jvm during junit tests forks abnormally, standard output won;t be
shown becaused its buffered.  Apparently this can be switched off (e.g.
http://comments.gmane.org/gmane.comp.apache.maven.issues/28714,
http://grokbase.com/t/hadoop/zookeeper-user/10b4h71k09/junit-tests-do-not-produce-logs-if-the-jvm-crashes
).

Any ideas on whether/how this might be done with buildr?

hoogs

Thanks for sharing Pepijn.   Your version has much better bones than the
one I threw together quickly.

Khristian: I suggest you try it and go/extend from there.


On Mon, Apr 15, 2013 at 12:54 AM, Pepijn Van Eeckhoudt <
pepijn@vaneeckhoudt.net> wrote:

> Hi Khristian,
>
> I've made a copy of the Proguard extension I use at work available at
> https://gist.github.com/**pepijnve/5386437<https://gist.github.com/pepijnve/5386437>
>
> It's essentially a wrapper for the Proguard Ant task. I've added support
> for the options that I actually needed. Might not be 100% complete but all
> the essential parts are there.
>
> I haven't experienced any issues related to the task calling exit. Perhaps
> exit is not invoked when using Proguard via the Ant task rather then via
> its own main method.
>
> Regards,
>
> Pepijn
>
>
> On 12-04-13 14:27, Khristian Schönrock wrote:
>
>> Hi Alex,
>>
>> thanks for your help! I got my proguard task going as I wanted after a few
>> modifications to your script: https://gist.github.com/**derkosak/5371630<https://gist.github.com/derkosak/5371630>
>>
>> However, I seem to have stumbled upon the "task calls exit(), buildr exits
>> as well" issue. How can I work around this? I've read that forking the
>> call
>> does the trick, but couldn't figure out how it is done.
>>
>> TIA,
>> Khristian
>>
>>
>>
>> On Sat, Apr 6, 2013 at 12:28 AM, Alex Boisvert <alex.boisvert@gmail.com>*
>> *wrote:
>>
>>  Hi Khristian,
>>>
>>> I hacked something quickly together here:
>>> https://gist.github.com/**aboisvert/5323180<https://gist.github.com/aboisvert/5323180>
>>>
>>> I didn't use the Ant task since I thought it was too much trouble
>>> compared
>>> to using the Proguard 'main class' and passing argument directly to it.
>>> Note that this is just a prototype that doesn't support many of the
>>> proguard options .. basically the bare minimum to get you going.
>>>
>>> Hope this helps,
>>> alex
>>>
>>>
>>>
>>> On Fri, Apr 5, 2013 at 7:47 AM, Khristian Schönrock <
>>> smirnegger@gmail.com
>>>
>>>> wrote:
>>>>
>>>
>>>  Hello everyone,
>>>> I'm trying to add a proguard task to my project. So far I've not found
>>>>
>>> any
>>>
>>>> sort of Proguard-addon for Buildr, so I tried using the Ant task.
>>>>
>>>> I tried to mimic the OpenJPA task, and ended up with the following code:
>>>>
>>>> REQUIRES = [ ...bunch of libraries... ]
>>>>
>>>> ant('proguard') do |ant|
>>>>      ant.taskdef :name=>'proguard',
>>>>
>>> :classname=>'proguard.ant.**ProGuardTask',
>>>
>>>>        :classpath=>REQUIRES.join(**File::PATH_SEPARATOR)
>>>>      ant.proguard :configuration=>_('../build/co**nfiguration.pro<http://configuration.pro>'),
>>>> #
>>>>
>>> config
>>>
>>>> file
>>>>        :injars=>project('my_project') # snag here
>>>> end
>>>>
>>>> And so I am left with a bunch of intertwining questions:
>>>>
>>>> - Since I'm defining the task in a project that should be processed by
>>>> proguard, I'm not sure how I should add the project to the classpath.
>>>> - Moving the proguard task to some other project ("distribution", for
>>>> example) solves the problem, but proguard complains that I need to
>>>> define
>>>> the "-injars" parameter, which I tried unsuccessfully with the :injars
>>>>
>>> code
>>>
>>>> above.
>>>> - Since "-injars" is part of the configuration, in the Proguard Ant task
>>>>
>>> it
>>>
>>>> can be defined either in the configuration file ("configuration.pro"),
>>>>
>>> or
>>>
>>>> in the body of the <configuration> tag. Supposing the :configuration
key
>>>> maps to this tag, can I add this "tag content"?
>>>>
>>>> How do I best configure this?
>>>>
>>>> Thanks in advance,
>>>> Khristian
>>>>
>>>>
>>>
>>
>

Thanks Kevin,

The final solution I came up with uses OneJar.  There is a modest startup
delay of the order of 1s, but no significant runtime penalty.  Packaging
takes about 1.5s versus about 30s for flattening the jars out into
classes.  I'm not sure why that is, but its vastly better for the code dev
cycle.

MYJAR = '/path/to/myjar.jar'
ONEJAR = 'lib/one-jar-boot-0.97.jar'

DEPS =
[
  ARGS4J,
  JASYPT,
  WEB,
  ORIENTDB
].flatten

repositories.remote << 'http://repo1.maven.org/maven2'

define 'MyProject' do

  project.version = VERSION_NUMBER
  project.group = 'mygroup'
  compile.options.target = '1.7'

  define 'server' do
    compile.with DEPS, MYJAR
    package(:jar)
  end

  package(:jar).path("lib").tap do |p|
    p.include DEPS.each {|d| p.include artifact(d).to_s}
    p.include MYJAR
  end
  package(:jar).path("main").tap do |p|
    p.include project('server').package(:jar)
  end
  package(:jar).merge(ONEJAR)
  package(:jar).with :manifest=>manifest.merge(
    'One-Jar-Main-Class'=>'com.myproject.control.Start',
    'Main-Class'=>'com.simontuffs.onejar.Boot'
  )

end

Thanks everyone for your help.  Can I just make a comment about the Buildr
API documentation, which I'm guessing is a generic Ruby doc format?  I just
don't get it at all, I've relied totally on the Quick Start on the webpage,
and these few examples.  I have no Ruby background, but know Python (and
the C languages).  For example, if I want to know what methods are
associated with "package" I just can't figure that out.  Maybe its me.
hoogs


On Mon, Apr 15, 2013 at 9:19 PM, Kevin Smith <kevin.s@qualitycode.com>wrote:

> On 04/15/2013 06:49 AM, Jason Hoogland wrote:
>
>> Sorry, and any ideas on dealing with manifest.mf overwrite?
>>
>
> Here is a fragment from our buildr script:
>
>    p.with :manifest=>{'Main-Class'=>'**org.martus.client.swingui.**
> Martus'}
>      p.include(File.join(_('source'**, 'test', 'java'), '**/*.mlp'))
> p.merge(project('martus-jar-**verifier').package(:jar)).**
> exclude('META-INF/MANIFEST.MF'**)
>
> It merges in a jar build by a different sub-script, omitting that other
> manifest.
>
> Kevin
>
>

On 04/15/2013 06:49 AM, Jason Hoogland wrote:
> Sorry, and any ideas on dealing with manifest.mf overwrite?

Here is a fragment from our buildr script:

    p.with :manifest=>{'Main-Class'=>'org.martus.client.swingui.Martus'}
      p.include(File.join(_('source', 'test', 'java'), '**/*.mlp'))
p.merge(project('martus-jar-verifier').package(:jar)).exclude('META-INF/MANIFEST.MF')

It merges in a jar build by a different sub-script, omitting that other 
manifest.

Kevin

Sorry, and any ideas on dealing with manifest.mf overwrite?
On Apr 15, 2013 6:27 PM, "Peter Donald" <peter@realityforge.org> wrote:

> On Mon, Apr 15, 2013 at 6:41 PM, Jason Hoogland <hoogland@gmail.com>
> wrote:
>
> > Peter,
> >
> > Going back to your original suggestion (the second option) e.g.
> > https://github.com/realityforge/spydle/blob/master/buildfile#L19, how
> > would
> > you merge the contents of a local jar file?
> >
>
> Add a line such as
>
> jar.merge('../some/local/library.jar')
>
>
> >
> > hoogs
> >
> >
> > On Sun, Apr 14, 2013 at 9:58 AM, Peter Donald <peter@realityforge.org
> > >wrote:
> >
> > > On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> > > wrote:
> > >
> > > > I'm trying to do what my old ant build.xml does, namely:
> > > > 1. compile my src code into classes
> > > > 2. packages them into a jar
> > > > 3. adds the dependency jars to this jar
> > > > 4. includes "Main-Class" and "Class-Path" attributes to
> > > > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> > > >
> > >
> > > I am not sure I exactly follow. Do you want to include the jars as
> nested
> > > jars or just include the files form the jar in the final jar?
> > >
> > > I usually attempt the second option and use code that looks similar to
> > >
> > > https://github.com/realityforge/spydle/blob/master/buildfile#L19
> > >
> > > to achieve this goal.
> > >
> > >  HTH (And sorry if I am missing what you are trying to do),
> > >
> > > Peter Donald
> > >
> >
>
>
>
> --
> Cheers,
>
> Peter Donald
>

On Mon, Apr 15, 2013 at 6:41 PM, Jason Hoogland <hoogland@gmail.com> wrote:

> Peter,
>
> Going back to your original suggestion (the second option) e.g.
> https://github.com/realityforge/spydle/blob/master/buildfile#L19, how
> would
> you merge the contents of a local jar file?
>

Add a line such as

jar.merge('../some/local/library.jar')


>
> hoogs
>
>
> On Sun, Apr 14, 2013 at 9:58 AM, Peter Donald <peter@realityforge.org
> >wrote:
>
> > On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> > wrote:
> >
> > > I'm trying to do what my old ant build.xml does, namely:
> > > 1. compile my src code into classes
> > > 2. packages them into a jar
> > > 3. adds the dependency jars to this jar
> > > 4. includes "Main-Class" and "Class-Path" attributes to
> > > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> > >
> >
> > I am not sure I exactly follow. Do you want to include the jars as nested
> > jars or just include the files form the jar in the final jar?
> >
> > I usually attempt the second option and use code that looks similar to
> >
> > https://github.com/realityforge/spydle/blob/master/buildfile#L19
> >
> > to achieve this goal.
> >
> >  HTH (And sorry if I am missing what you are trying to do),
> >
> > Peter Donald
> >
>



-- 
Cheers,

Peter Donald

Peter,

Going back to your original suggestion (the second option) e.g.
https://github.com/realityforge/spydle/blob/master/buildfile#L19, how would
you merge the contents of a local jar file?

hoogs


On Sun, Apr 14, 2013 at 9:58 AM, Peter Donald <peter@realityforge.org>wrote:

> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> wrote:
>
> > I'm trying to do what my old ant build.xml does, namely:
> > 1. compile my src code into classes
> > 2. packages them into a jar
> > 3. adds the dependency jars to this jar
> > 4. includes "Main-Class" and "Class-Path" attributes to
> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> >
>
> I am not sure I exactly follow. Do you want to include the jars as nested
> jars or just include the files form the jar in the final jar?
>
> I usually attempt the second option and use code that looks similar to
>
> https://github.com/realityforge/spydle/blob/master/buildfile#L19
>
> to achieve this goal.
>
>  HTH (And sorry if I am missing what you are trying to do),
>
> Peter Donald
>

Hi Khristian,

I've made a copy of the Proguard extension I use at work available at 
https://gist.github.com/pepijnve/5386437

It's essentially a wrapper for the Proguard Ant task. I've added support 
for the options that I actually needed. Might not be 100% complete but 
all the essential parts are there.

I haven't experienced any issues related to the task calling exit. 
Perhaps exit is not invoked when using Proguard via the Ant task rather 
then via its own main method.

Regards,

Pepijn

On 12-04-13 14:27, Khristian Schönrock wrote:
> Hi Alex,
>
> thanks for your help! I got my proguard task going as I wanted after a few
> modifications to your script: https://gist.github.com/derkosak/5371630
>
> However, I seem to have stumbled upon the "task calls exit(), buildr exits
> as well" issue. How can I work around this? I've read that forking the call
> does the trick, but couldn't figure out how it is done.
>
> TIA,
> Khristian
>
>
>
> On Sat, Apr 6, 2013 at 12:28 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote:
>
>> Hi Khristian,
>>
>> I hacked something quickly together here:
>> https://gist.github.com/aboisvert/5323180
>>
>> I didn't use the Ant task since I thought it was too much trouble compared
>> to using the Proguard 'main class' and passing argument directly to it.
>> Note that this is just a prototype that doesn't support many of the
>> proguard options .. basically the bare minimum to get you going.
>>
>> Hope this helps,
>> alex
>>
>>
>>
>> On Fri, Apr 5, 2013 at 7:47 AM, Khristian Schönrock <smirnegger@gmail.com
>>> wrote:
>>
>>> Hello everyone,
>>> I'm trying to add a proguard task to my project. So far I've not found
>> any
>>> sort of Proguard-addon for Buildr, so I tried using the Ant task.
>>>
>>> I tried to mimic the OpenJPA task, and ended up with the following code:
>>>
>>> REQUIRES = [ ...bunch of libraries... ]
>>>
>>> ant('proguard') do |ant|
>>>      ant.taskdef :name=>'proguard',
>> :classname=>'proguard.ant.ProGuardTask',
>>>        :classpath=>REQUIRES.join(File::PATH_SEPARATOR)
>>>      ant.proguard :configuration=>_('../build/configuration.pro'), #
>> config
>>> file
>>>        :injars=>project('my_project') # snag here
>>> end
>>>
>>> And so I am left with a bunch of intertwining questions:
>>>
>>> - Since I'm defining the task in a project that should be processed by
>>> proguard, I'm not sure how I should add the project to the classpath.
>>> - Moving the proguard task to some other project ("distribution", for
>>> example) solves the problem, but proguard complains that I need to define
>>> the "-injars" parameter, which I tried unsuccessfully with the :injars
>> code
>>> above.
>>> - Since "-injars" is part of the configuration, in the Proguard Ant task
>> it
>>> can be defined either in the configuration file ("configuration.pro"),
>> or
>>> in the body of the <configuration> tag. Supposing the :configuration key
>>> maps to this tag, can I add this "tag content"?
>>>
>>> How do I best configure this?
>>>
>>> Thanks in advance,
>>> Khristian
>>>
>>
>

Peter,

Works marvellously, and doing it this way is substantially faster to
package with builder, from 20-30s on my machine down to 1.5s.

You've got an unmatched [, and the Class-Path only works for me if the
comma join is replaced by a space.

hoogs


On Sun, Apr 14, 2013 at 6:47 PM, Peter Donald <peter@realityforge.org>wrote:

> On Sun, Apr 14, 2013 at 8:31 PM, Jason Hoogland <hoogland@gmail.com>
> wrote:
>
> > One more question: if the remote artifacts are specified in an array, how
> > would the "jar.include" change? I expect I'll be ok with figuring out
> > building the Class-Path string in a loop but if you have a suggestion for
> > that, it would be great.
> >
>
> Updated the example at
>
> https://gist.github.com/realityforge/5381737
>
> HTH
>
>
> > hoogs
> > On Apr 14, 2013 3:36 PM, "Jason Hoogland" <hoogland@gmail.com> wrote:
> >
> > > Peter,
> > >
> > > Awesome, thank you SO much, looks like the trick. How do you find all
> > > these buildfiles?
> > >
> > > I think i love buildr, bye bye ant, xml!
> > >
> > > hoogs
> > > On Apr 14, 2013 3:02 PM, "Peter Donald" <peter@realityforge.org>
> wrote:
> > >
> > >> Hi,
> > >>
> > >> Now I understand. An example for this is at
> > >>
> > >> https://gist.github.com/realityforge/5381737
> > >>
> > >> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com>
> > >> wrote:
> > >>
> > >> > To break this down to simpler questions:
> > >> >
> > >> > 1. How to access a subset of the jar files buildr remotely
> downloaded?
> > >> > 2. How to include this subset as jars, without modification, within
> a
> > >> new
> > >> > jar package?
> > >> > 3. How to create a Class-Path string, properly formatted, that
> > includes
> > >> > this subset of jars, for use in the final package manifest? (Ruby
> > >> newbie)
> > >> >
> > >> > hoogs
> > >> > On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com>
> > wrote:
> > >> >
> > >> > > Thanks Peter,
> > >> > >
> > >> > > I am having trouble finding useful buildfile examples so will
> check
> > >> this
> > >> > > out.
> > >> > >
> > >> > > I am trying to do the former, nesting the dep jars inside the
> final
> > >> jar.
> > >> > > Then I have only one manifest file to worry about. I find it
a lot
> > >> > cleaner.
> > >> > > Currently my buildfile is doing what you do, just mash all the
dep
> > >> files
> > >> > > together into the jar, the problem i've got there is that the
> > >> MANIFEST.MF
> > >> > > files seem to overwrite each other, but maybe that link will
help.
> > >> > >
> > >> > > hoogs
> > >> > > On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org>
> > >> wrote:
> > >> > >
> > >> > >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <
> > hoogland@gmail.com
> > >> >
> > >> > >> wrote:
> > >> > >>
> > >> > >> > I'm trying to do what my old ant build.xml does, namely:
> > >> > >> > 1. compile my src code into classes
> > >> > >> > 2. packages them into a jar
> > >> > >> > 3. adds the dependency jars to this jar
> > >> > >> > 4. includes "Main-Class" and "Class-Path" attributes
to
> > >> > >> > META-INF/MANIFEST.MF, the latter properly formatted,
e.g.:
> > >> > >> >
> > >> > >>
> > >> > >> I am not sure I exactly follow. Do you want to include the
jars
> as
> > >> > nested
> > >> > >> jars or just include the files form the jar in the final
jar?
> > >> > >>
> > >> > >> I usually attempt the second option and use code that looks
> similar
> > >> to
> > >> > >>
> > >> > >> https://github.com/realityforge/spydle/blob/master/buildfile#L19
> > >> > >>
> > >> > >> to achieve this goal.
> > >> > >>
> > >> > >>  HTH (And sorry if I am missing what you are trying to do),
> > >> > >>
> > >> > >> Peter Donald
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Cheers,
> > >>
> > >> Peter Donald
> > >>
> > >
> >
>
>
>
> --
> Cheers,
>
> Peter Donald
>

here's ours :)

https://github.com/candlepin/candlepin/blob/master/buildfile

sincerely,
jesus rodriguez
On Apr 14, 2013 11:33 AM, "Alex Boisvert" <alex.boisvert@gmail.com> wrote:

> On Sun, Apr 14, 2013 at 3:53 AM, Peter Donald <peter@realityforge.org
> >wrote:
>
> > > A collection of real world build files would help a lot, especially
> when
> > > one is new to buildr.
> > >
> >
> > At one stage there was a git repository somewhere that included a
> > collection of buildfiles.  Not sure where it was exactly ...
> >
>
> https://github.com/phoet/buildr-examples
>

On Sun, Apr 14, 2013 at 3:53 AM, Peter Donald <peter@realityforge.org>wrote:

> > A collection of real world build files would help a lot, especially when
> > one is new to buildr.
> >
>
> At one stage there was a git repository somewhere that included a
> collection of buildfiles.  Not sure where it was exactly ...
>

https://github.com/phoet/buildr-examples

Hi,

On Sun, Apr 14, 2013 at 6:16 PM, Magnus Melander <magnus@huggtand.com>wrote:

> I think the question about where to find real world examples of build
> files is a really valid question.
> I find the buildr documentation great except for that part.
>

That's true.


> A collection of real world build files would help a lot, especially when
> one is new to buildr.
>

At one stage there was a git repository somewhere that included a
collection of buildfiles.  Not sure where it was exactly ...


>
> Btw, since I started to use buildr, I have never looked back.
>

Me too ;)

-- 
Cheers,

Peter Donald

On Sun, Apr 14, 2013 at 8:31 PM, Jason Hoogland <hoogland@gmail.com> wrote:

> One more question: if the remote artifacts are specified in an array, how
> would the "jar.include" change? I expect I'll be ok with figuring out
> building the Class-Path string in a loop but if you have a suggestion for
> that, it would be great.
>

Updated the example at

https://gist.github.com/realityforge/5381737

HTH


> hoogs
> On Apr 14, 2013 3:36 PM, "Jason Hoogland" <hoogland@gmail.com> wrote:
>
> > Peter,
> >
> > Awesome, thank you SO much, looks like the trick. How do you find all
> > these buildfiles?
> >
> > I think i love buildr, bye bye ant, xml!
> >
> > hoogs
> > On Apr 14, 2013 3:02 PM, "Peter Donald" <peter@realityforge.org> wrote:
> >
> >> Hi,
> >>
> >> Now I understand. An example for this is at
> >>
> >> https://gist.github.com/realityforge/5381737
> >>
> >> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com>
> >> wrote:
> >>
> >> > To break this down to simpler questions:
> >> >
> >> > 1. How to access a subset of the jar files buildr remotely downloaded?
> >> > 2. How to include this subset as jars, without modification, within a
> >> new
> >> > jar package?
> >> > 3. How to create a Class-Path string, properly formatted, that
> includes
> >> > this subset of jars, for use in the final package manifest? (Ruby
> >> newbie)
> >> >
> >> > hoogs
> >> > On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com>
> wrote:
> >> >
> >> > > Thanks Peter,
> >> > >
> >> > > I am having trouble finding useful buildfile examples so will check
> >> this
> >> > > out.
> >> > >
> >> > > I am trying to do the former, nesting the dep jars inside the final
> >> jar.
> >> > > Then I have only one manifest file to worry about. I find it a lot
> >> > cleaner.
> >> > > Currently my buildfile is doing what you do, just mash all the dep
> >> files
> >> > > together into the jar, the problem i've got there is that the
> >> MANIFEST.MF
> >> > > files seem to overwrite each other, but maybe that link will help.
> >> > >
> >> > > hoogs
> >> > > On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org>
> >> wrote:
> >> > >
> >> > >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <
> hoogland@gmail.com
> >> >
> >> > >> wrote:
> >> > >>
> >> > >> > I'm trying to do what my old ant build.xml does, namely:
> >> > >> > 1. compile my src code into classes
> >> > >> > 2. packages them into a jar
> >> > >> > 3. adds the dependency jars to this jar
> >> > >> > 4. includes "Main-Class" and "Class-Path" attributes to
> >> > >> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> >> > >> >
> >> > >>
> >> > >> I am not sure I exactly follow. Do you want to include the jars
as
> >> > nested
> >> > >> jars or just include the files form the jar in the final jar?
> >> > >>
> >> > >> I usually attempt the second option and use code that looks similar
> >> to
> >> > >>
> >> > >> https://github.com/realityforge/spydle/blob/master/buildfile#L19
> >> > >>
> >> > >> to achieve this goal.
> >> > >>
> >> > >>  HTH (And sorry if I am missing what you are trying to do),
> >> > >>
> >> > >> Peter Donald
> >> > >>
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Cheers,
> >>
> >> Peter Donald
> >>
> >
>



-- 
Cheers,

Peter Donald

One more question: if the remote artifacts are specified in an array, how
would the "jar.include" change? I expect I'll be ok with figuring out
building the Class-Path string in a loop but if you have a suggestion for
that, it would be great.
hoogs
On Apr 14, 2013 3:36 PM, "Jason Hoogland" <hoogland@gmail.com> wrote:

> Peter,
>
> Awesome, thank you SO much, looks like the trick. How do you find all
> these buildfiles?
>
> I think i love buildr, bye bye ant, xml!
>
> hoogs
> On Apr 14, 2013 3:02 PM, "Peter Donald" <peter@realityforge.org> wrote:
>
>> Hi,
>>
>> Now I understand. An example for this is at
>>
>> https://gist.github.com/realityforge/5381737
>>
>> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com>
>> wrote:
>>
>> > To break this down to simpler questions:
>> >
>> > 1. How to access a subset of the jar files buildr remotely downloaded?
>> > 2. How to include this subset as jars, without modification, within a
>> new
>> > jar package?
>> > 3. How to create a Class-Path string, properly formatted, that includes
>> > this subset of jars, for use in the final package manifest? (Ruby
>> newbie)
>> >
>> > hoogs
>> > On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com> wrote:
>> >
>> > > Thanks Peter,
>> > >
>> > > I am having trouble finding useful buildfile examples so will check
>> this
>> > > out.
>> > >
>> > > I am trying to do the former, nesting the dep jars inside the final
>> jar.
>> > > Then I have only one manifest file to worry about. I find it a lot
>> > cleaner.
>> > > Currently my buildfile is doing what you do, just mash all the dep
>> files
>> > > together into the jar, the problem i've got there is that the
>> MANIFEST.MF
>> > > files seem to overwrite each other, but maybe that link will help.
>> > >
>> > > hoogs
>> > > On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org>
>> wrote:
>> > >
>> > >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com
>> >
>> > >> wrote:
>> > >>
>> > >> > I'm trying to do what my old ant build.xml does, namely:
>> > >> > 1. compile my src code into classes
>> > >> > 2. packages them into a jar
>> > >> > 3. adds the dependency jars to this jar
>> > >> > 4. includes "Main-Class" and "Class-Path" attributes to
>> > >> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
>> > >> >
>> > >>
>> > >> I am not sure I exactly follow. Do you want to include the jars as
>> > nested
>> > >> jars or just include the files form the jar in the final jar?
>> > >>
>> > >> I usually attempt the second option and use code that looks similar
>> to
>> > >>
>> > >> https://github.com/realityforge/spydle/blob/master/buildfile#L19
>> > >>
>> > >> to achieve this goal.
>> > >>
>> > >>  HTH (And sorry if I am missing what you are trying to do),
>> > >>
>> > >> Peter Donald
>> > >>
>> > >
>> >
>>
>>
>>
>> --
>> Cheers,
>>
>> Peter Donald
>>
>

Hi All!
I think the question about where to find real world examples of build files is a really valid
question.
I find the buildr documentation great except for that part.
A collection of real world build files would help a lot, especially when one is new to buildr.

Btw, since I started to use buildr, I have never looked back.

Regards,
Magnus

El 14 apr 2013, a las 09.36, Jason Hoogland escribió:

> Peter,
> 
> Awesome, thank you SO much, looks like the trick. How do you find all these
> buildfiles?
> 
> I think i love buildr, bye bye ant, xml!
> 
> hoogs
> On Apr 14, 2013 3:02 PM, "Peter Donald" <peter@realityforge.org> wrote:
> 
>> Hi,
>> 
>> Now I understand. An example for this is at
>> 
>> https://gist.github.com/realityforge/5381737
>> 
>> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com>
>> wrote:
>> 
>>> To break this down to simpler questions:
>>> 
>>> 1. How to access a subset of the jar files buildr remotely downloaded?
>>> 2. How to include this subset as jars, without modification, within a new
>>> jar package?
>>> 3. How to create a Class-Path string, properly formatted, that includes
>>> this subset of jars, for use in the final package manifest? (Ruby newbie)
>>> 
>>> hoogs
>>> On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com> wrote:
>>> 
>>>> Thanks Peter,
>>>> 
>>>> I am having trouble finding useful buildfile examples so will check
>> this
>>>> out.
>>>> 
>>>> I am trying to do the former, nesting the dep jars inside the final
>> jar.
>>>> Then I have only one manifest file to worry about. I find it a lot
>>> cleaner.
>>>> Currently my buildfile is doing what you do, just mash all the dep
>> files
>>>> together into the jar, the problem i've got there is that the
>> MANIFEST.MF
>>>> files seem to overwrite each other, but maybe that link will help.
>>>> 
>>>> hoogs
>>>> On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org>
>> wrote:
>>>> 
>>>>> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> I'm trying to do what my old ant build.xml does, namely:
>>>>>> 1. compile my src code into classes
>>>>>> 2. packages them into a jar
>>>>>> 3. adds the dependency jars to this jar
>>>>>> 4. includes "Main-Class" and "Class-Path" attributes to
>>>>>> META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
>>>>>> 
>>>>> 
>>>>> I am not sure I exactly follow. Do you want to include the jars as
>>> nested
>>>>> jars or just include the files form the jar in the final jar?
>>>>> 
>>>>> I usually attempt the second option and use code that looks similar to
>>>>> 
>>>>> https://github.com/realityforge/spydle/blob/master/buildfile#L19
>>>>> 
>>>>> to achieve this goal.
>>>>> 
>>>>> HTH (And sorry if I am missing what you are trying to do),
>>>>> 
>>>>> Peter Donald
>>>>> 
>>>> 
>>> 
>> 
>> 
>> 
>> --
>> Cheers,
>> 
>> Peter Donald
>> 

Peter,

Awesome, thank you SO much, looks like the trick. How do you find all these
buildfiles?

I think i love buildr, bye bye ant, xml!

hoogs
On Apr 14, 2013 3:02 PM, "Peter Donald" <peter@realityforge.org> wrote:

> Hi,
>
> Now I understand. An example for this is at
>
> https://gist.github.com/realityforge/5381737
>
> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com>
> wrote:
>
> > To break this down to simpler questions:
> >
> > 1. How to access a subset of the jar files buildr remotely downloaded?
> > 2. How to include this subset as jars, without modification, within a new
> > jar package?
> > 3. How to create a Class-Path string, properly formatted, that includes
> > this subset of jars, for use in the final package manifest? (Ruby newbie)
> >
> > hoogs
> > On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com> wrote:
> >
> > > Thanks Peter,
> > >
> > > I am having trouble finding useful buildfile examples so will check
> this
> > > out.
> > >
> > > I am trying to do the former, nesting the dep jars inside the final
> jar.
> > > Then I have only one manifest file to worry about. I find it a lot
> > cleaner.
> > > Currently my buildfile is doing what you do, just mash all the dep
> files
> > > together into the jar, the problem i've got there is that the
> MANIFEST.MF
> > > files seem to overwrite each other, but maybe that link will help.
> > >
> > > hoogs
> > > On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org>
> wrote:
> > >
> > >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> > >> wrote:
> > >>
> > >> > I'm trying to do what my old ant build.xml does, namely:
> > >> > 1. compile my src code into classes
> > >> > 2. packages them into a jar
> > >> > 3. adds the dependency jars to this jar
> > >> > 4. includes "Main-Class" and "Class-Path" attributes to
> > >> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> > >> >
> > >>
> > >> I am not sure I exactly follow. Do you want to include the jars as
> > nested
> > >> jars or just include the files form the jar in the final jar?
> > >>
> > >> I usually attempt the second option and use code that looks similar to
> > >>
> > >> https://github.com/realityforge/spydle/blob/master/buildfile#L19
> > >>
> > >> to achieve this goal.
> > >>
> > >>  HTH (And sorry if I am missing what you are trying to do),
> > >>
> > >> Peter Donald
> > >>
> > >
> >
>
>
>
> --
> Cheers,
>
> Peter Donald
>

Hi,

Now I understand. An example for this is at

https://gist.github.com/realityforge/5381737

On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland <hoogland@gmail.com> wrote:

> To break this down to simpler questions:
>
> 1. How to access a subset of the jar files buildr remotely downloaded?
> 2. How to include this subset as jars, without modification, within a new
> jar package?
> 3. How to create a Class-Path string, properly formatted, that includes
> this subset of jars, for use in the final package manifest? (Ruby newbie)
>
> hoogs
> On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com> wrote:
>
> > Thanks Peter,
> >
> > I am having trouble finding useful buildfile examples so will check this
> > out.
> >
> > I am trying to do the former, nesting the dep jars inside the final jar.
> > Then I have only one manifest file to worry about. I find it a lot
> cleaner.
> > Currently my buildfile is doing what you do, just mash all the dep files
> > together into the jar, the problem i've got there is that the MANIFEST.MF
> > files seem to overwrite each other, but maybe that link will help.
> >
> > hoogs
> > On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org> wrote:
> >
> >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> >> wrote:
> >>
> >> > I'm trying to do what my old ant build.xml does, namely:
> >> > 1. compile my src code into classes
> >> > 2. packages them into a jar
> >> > 3. adds the dependency jars to this jar
> >> > 4. includes "Main-Class" and "Class-Path" attributes to
> >> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> >> >
> >>
> >> I am not sure I exactly follow. Do you want to include the jars as
> nested
> >> jars or just include the files form the jar in the final jar?
> >>
> >> I usually attempt the second option and use code that looks similar to
> >>
> >> https://github.com/realityforge/spydle/blob/master/buildfile#L19
> >>
> >> to achieve this goal.
> >>
> >>  HTH (And sorry if I am missing what you are trying to do),
> >>
> >> Peter Donald
> >>
> >
>



-- 
Cheers,

Peter Donald

To break this down to simpler questions:

1. How to access a subset of the jar files buildr remotely downloaded?
2. How to include this subset as jars, without modification, within a new
jar package?
3. How to create a Class-Path string, properly formatted, that includes
this subset of jars, for use in the final package manifest? (Ruby newbie)

hoogs
On Apr 14, 2013 10:17 AM, "Jason Hoogland" <hoogland@gmail.com> wrote:

> Thanks Peter,
>
> I am having trouble finding useful buildfile examples so will check this
> out.
>
> I am trying to do the former, nesting the dep jars inside the final jar.
> Then I have only one manifest file to worry about. I find it a lot cleaner.
> Currently my buildfile is doing what you do, just mash all the dep files
> together into the jar, the problem i've got there is that the MANIFEST.MF
> files seem to overwrite each other, but maybe that link will help.
>
> hoogs
> On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org> wrote:
>
>> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
>> wrote:
>>
>> > I'm trying to do what my old ant build.xml does, namely:
>> > 1. compile my src code into classes
>> > 2. packages them into a jar
>> > 3. adds the dependency jars to this jar
>> > 4. includes "Main-Class" and "Class-Path" attributes to
>> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
>> >
>>
>> I am not sure I exactly follow. Do you want to include the jars as nested
>> jars or just include the files form the jar in the final jar?
>>
>> I usually attempt the second option and use code that looks similar to
>>
>> https://github.com/realityforge/spydle/blob/master/buildfile#L19
>>
>> to achieve this goal.
>>
>>  HTH (And sorry if I am missing what you are trying to do),
>>
>> Peter Donald
>>
>

Thanks Peter,

I am having trouble finding useful buildfile examples so will check this
out.

I am trying to do the former, nesting the dep jars inside the final jar.
Then I have only one manifest file to worry about. I find it a lot cleaner.
Currently my buildfile is doing what you do, just mash all the dep files
together into the jar, the problem i've got there is that the MANIFEST.MF
files seem to overwrite each other, but maybe that link will help.

hoogs
On Apr 14, 2013 9:59 AM, "Peter Donald" <peter@realityforge.org> wrote:

> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com>
> wrote:
>
> > I'm trying to do what my old ant build.xml does, namely:
> > 1. compile my src code into classes
> > 2. packages them into a jar
> > 3. adds the dependency jars to this jar
> > 4. includes "Main-Class" and "Class-Path" attributes to
> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
> >
>
> I am not sure I exactly follow. Do you want to include the jars as nested
> jars or just include the files form the jar in the final jar?
>
> I usually attempt the second option and use code that looks similar to
>
> https://github.com/realityforge/spydle/blob/master/buildfile#L19
>
> to achieve this goal.
>
>  HTH (And sorry if I am missing what you are trying to do),
>
> Peter Donald
>

On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <hoogland@gmail.com> wrote:

> I'm trying to do what my old ant build.xml does, namely:
> 1. compile my src code into classes
> 2. packages them into a jar
> 3. adds the dependency jars to this jar
> 4. includes "Main-Class" and "Class-Path" attributes to
> META-INF/MANIFEST.MF, the latter properly formatted, e.g.:
>

I am not sure I exactly follow. Do you want to include the jars as nested
jars or just include the files form the jar in the final jar?

I usually attempt the second option and use code that looks similar to

https://github.com/realityforge/spydle/blob/master/buildfile#L19

to achieve this goal.

 HTH (And sorry if I am missing what you are trying to do),

Peter Donald

I;ve seen
http://stackoverflow.com/questions/1279419/buildr-package-dependencies-into-a-single-jar/1285293#1285293but
I'd prefer a buildr-only solution and it I can't find any good info
regarding inserting the Class-Path in the MANIFEST.MF

I have

DEPS =
[
  ARGS4J,
  JASYPT,
  WEB,
  ORIENTDB,
  '/path/to/local.jar'
]

repositories.remote << 'http://repo1.maven.org/maven2'

define 'My Project' do

  project.version = VERSION_NUMBER
  project.group = 'myGroup'
  compile.options.target = '1.7'

  desc 'Bountius Server'
  define 'deps' do
    package(:jar).merge(DEPS)
  end

  manifest['Main-Class'] = 'com.myProject.control.Start'

  desc 'iMyProject Server'
  define 'server' do
    compile.with DEPS
    package(:jar).merge(DEPS)
  end
end

The server jar created just throws the kitchen sink in, apparently
overwriting the META-ING/MANIFEST.MF with the final artifact MANIFEST.MF
rather than using my manifest settings.

I'm trying to do what my old ant build.xml does, namely:
1. compile my src code into classes
2. packages them into a jar
3. adds the dependency jars to this jar
4. includes "Main-Class" and "Class-Path" attributes to
META-INF/MANIFEST.MF, the latter properly formatted, e.g.:

Class-Path: args4j-2.0.18.jar gson-2.2.2.jar jasypt-1.9.0.jar orient-c
 ommons-1.3.0.jar orientdb-client-1.3.0.jar orientdb-core-1.3.0.jar or
 ientdb-enterprise-1.3.0.jar orientdb-server-1.3.0.jar prodigitum.util
 .jar commons-exec-1.1.jar commons-logging-1.1.1.jar guava-14.0.jar ht
 tpclient-4.2.1.jar httpcore-4.2.1.jar json-20080701.jar selenium-java
 -2.31.0.jar

The resulting jar can be run stand-alone.

I'm open to a better or equivalent way in buildr if someone could possibly
help

Cheers
hoogs

Hi Alex,

thanks for your help! I got my proguard task going as I wanted after a few
modifications to your script: https://gist.github.com/derkosak/5371630

However, I seem to have stumbled upon the "task calls exit(), buildr exits
as well" issue. How can I work around this? I've read that forking the call
does the trick, but couldn't figure out how it is done.

TIA,
Khristian



On Sat, Apr 6, 2013 at 12:28 AM, Alex Boisvert <alex.boisvert@gmail.com>wrote:

> Hi Khristian,
>
> I hacked something quickly together here:
> https://gist.github.com/aboisvert/5323180
>
> I didn't use the Ant task since I thought it was too much trouble compared
> to using the Proguard 'main class' and passing argument directly to it.
> Note that this is just a prototype that doesn't support many of the
> proguard options .. basically the bare minimum to get you going.
>
> Hope this helps,
> alex
>
>
>
> On Fri, Apr 5, 2013 at 7:47 AM, Khristian Schönrock <smirnegger@gmail.com
> >wrote:
>
> > Hello everyone,
> > I'm trying to add a proguard task to my project. So far I've not found
> any
> > sort of Proguard-addon for Buildr, so I tried using the Ant task.
> >
> > I tried to mimic the OpenJPA task, and ended up with the following code:
> >
> > REQUIRES = [ ...bunch of libraries... ]
> >
> > ant('proguard') do |ant|
> >     ant.taskdef :name=>'proguard',
> :classname=>'proguard.ant.ProGuardTask',
> >       :classpath=>REQUIRES.join(File::PATH_SEPARATOR)
> >     ant.proguard :configuration=>_('../build/configuration.pro'), #
> config
> > file
> >       :injars=>project('my_project') # snag here
> > end
> >
> > And so I am left with a bunch of intertwining questions:
> >
> > - Since I'm defining the task in a project that should be processed by
> > proguard, I'm not sure how I should add the project to the classpath.
> > - Moving the proguard task to some other project ("distribution", for
> > example) solves the problem, but proguard complains that I need to define
> > the "-injars" parameter, which I tried unsuccessfully with the :injars
> code
> > above.
> > - Since "-injars" is part of the configuration, in the Proguard Ant task
> it
> > can be defined either in the configuration file ("configuration.pro"),
> or
> > in the body of the <configuration> tag. Supposing the :configuration key
> > maps to this tag, can I add this "tag content"?
> >
> > How do I best configure this?
> >
> > Thanks in advance,
> > Khristian
> >
>

Hi Khristian,

I hacked something quickly together here:
https://gist.github.com/aboisvert/5323180

I didn't use the Ant task since I thought it was too much trouble compared
to using the Proguard 'main class' and passing argument directly to it.
Note that this is just a prototype that doesn't support many of the
proguard options .. basically the bare minimum to get you going.

Hope this helps,
alex



On Fri, Apr 5, 2013 at 7:47 AM, Khristian Schönrock <smirnegger@gmail.com>wrote:

> Hello everyone,
> I'm trying to add a proguard task to my project. So far I've not found any
> sort of Proguard-addon for Buildr, so I tried using the Ant task.
>
> I tried to mimic the OpenJPA task, and ended up with the following code:
>
> REQUIRES = [ ...bunch of libraries... ]
>
> ant('proguard') do |ant|
>     ant.taskdef :name=>'proguard', :classname=>'proguard.ant.ProGuardTask',
>       :classpath=>REQUIRES.join(File::PATH_SEPARATOR)
>     ant.proguard :configuration=>_('../build/configuration.pro'), # config
> file
>       :injars=>project('my_project') # snag here
> end
>
> And so I am left with a bunch of intertwining questions:
>
> - Since I'm defining the task in a project that should be processed by
> proguard, I'm not sure how I should add the project to the classpath.
> - Moving the proguard task to some other project ("distribution", for
> example) solves the problem, but proguard complains that I need to define
> the "-injars" parameter, which I tried unsuccessfully with the :injars code
> above.
> - Since "-injars" is part of the configuration, in the Proguard Ant task it
> can be defined either in the configuration file ("configuration.pro"), or
> in the body of the <configuration> tag. Supposing the :configuration key
> maps to this tag, can I add this "tag content"?
>
> How do I best configure this?
>
> Thanks in advance,
> Khristian
>

Hello everyone,
I'm trying to add a proguard task to my project. So far I've not found any
sort of Proguard-addon for Buildr, so I tried using the Ant task.

I tried to mimic the OpenJPA task, and ended up with the following code:

REQUIRES = [ ...bunch of libraries... ]

ant('proguard') do |ant|
    ant.taskdef :name=>'proguard', :classname=>'proguard.ant.ProGuardTask',
      :classpath=>REQUIRES.join(File::PATH_SEPARATOR)
    ant.proguard :configuration=>_('../build/configuration.pro'), # config
file
      :injars=>project('my_project') # snag here
end

And so I am left with a bunch of intertwining questions:

- Since I'm defining the task in a project that should be processed by
proguard, I'm not sure how I should add the project to the classpath.
- Moving the proguard task to some other project ("distribution", for
example) solves the problem, but proguard complains that I need to define
the "-injars" parameter, which I tried unsuccessfully with the :injars code
above.
- Since "-injars" is part of the configuration, in the Proguard Ant task it
can be defined either in the configuration file ("configuration.pro"), or
in the body of the <configuration> tag. Supposing the :configuration key
maps to this tag, can I add this "tag content"?

How do I best configure this?

Thanks in advance,
Khristian

Apache Buildr is a build system for Java-based applications, including support
for Scala, Groovy and a growing number of JVM languages and tools.  We wanted
something that's simple and intuitive to use, so we only need to tell it what
to do, and it takes care of the rest.  But also something we can easily extend
for those one-off tasks, with a language that's a joy to use.


New in this release:

  * Fixed:  Multiple tests in TestNG 6.x versions were being
incorrectly passed to
            the command line application.


To learn more about Buildr and get started:
http://buildr.apache.org/

Thanks!
The Apache Buildr Team

Nevermind.  Didn't read the wiki that closely.  I needed the following
package enhance
to apply after the artifact was created:

def sign_jar(task)
  task.enhance do
    puts "Signing jar #{task.to_s}"
    signing = Buildr.settings.build['signing']
    store, aka, pass = signing.values_at('keystore', 'alias', 'storepass')
    puts task.to_s
    ant('signjar') do |signjar|
      signjar.signjar :jar=>task.to_s, :alias=>aka,
:keystore=>store,

                      :storepass=>pass
    end
  end
end

Then on the package to enhance I added:

packages.first.enhance &method(:sign_jar)


Thanks!

On Tue, Mar 19, 2013 at 4:37 PM, Anthony Bargnesi <abargnesi@gmail.com>wrote:

> Hey folks,
>
> I am trying to sign a jar after it is packaged so that the target artifact
> is a signed jar.
>
> I created a separate task to do the work:
>
> task :sign_task do
>   signing = Buildr.settings.build['signing']
>   store, aka, pass = signing.values_at('keystore', 'alias', 'storepass')
>   projects.each do |prj|
>     prj.packages.select{ |pkg| pkg.to_s.end_with?('.jar')}.each do |pkg|
>       ant('signjar') do |signjar|
>         signjar.signjar :jar=>pkg, :alias=>aka, :keystore=>store,
>                         :storepass=>pass
>       end
>     end
>   end
> end
>
> but this isn't hooked into the jar's packaging.  How can this be
> accomplished?
>
> Thanks!
> Anthony Bargnesi
>