Can you reproduce the problem in a simplified buildfile and project?
--
Dominic Graefen
Freelance: Interactive Developer / Creative Technologist
devboy.org
On Thursday, October 6, 2011 at 7:30 PM, Alex Boisvert wrote:
> You can't currently disable them (if only I knew why they are generated...)
>
> but you can automatically delete them, e.g.,
>
> package.enhance do
> package.enhance do
> ['pom', 'md5', 'sha1'].each do |ext|
> FileList[_(:target) + "/**/*.#{ext}"].each { |f| rm f }
> end
> end
> end
>
> (the double-enhance block is to ensure the code runs last during the package
> task)
>
> alex
>
> On Thu, Oct 6, 2011 at 10:46 AM, Sprog : Weyert de Boer <[email protected]
> (mailto:[email protected])>wrote:
>
> > Yes, can't I somehow remove them? Now I need to manually clean up our
> > releases folder.
> > Time to go home and try it out :)
> >
> > ----- Original Message -----
> > From: "Alex Boisvert" <[email protected]
> > (mailto:[email protected])>
> > To: [email protected] (mailto:[email protected])
> > Sent: Thursday, 6 October, 2011 6:47:57 PM
> > Subject: Re: How to make Buildr make with subprojects
> >
> > On Thu, Oct 6, 2011 at 7:39 AM, Sprog : Weyert de Boer <[email protected]
> > (mailto:[email protected])
> > > wrote:
> >
> > > Hmm, I guess I will need to try it out this evening then. For me it
> > > generated a bunch of stuff: .pom file, md5 hash file, sha1 hash file. If
> > I
> > > don't get it working tonight I will upload the buildfile somewhere.
> >
> > Are you running "buildr package" ?
> >
> > .pom files will be generated if you run "buildr install", "buildr upload",
> > "buildr release", ...
> >
> > alex
