buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ed Smiley <esmi...@ebrary.com>
Subject Re: Playing with project paths
Date Wed, 08 Sep 2010 17:32:38 GMT
If you have a variety of similar projects you can write your own buildfile
generator with its own command line switches, it's not that hard to do.
We've been doing that and you can get pretty sophisticated, but use Buildr's
own built in capabilities to do a lot of the heavy lifting.

On Wed, Sep 8, 2010 at 10:19 AM, Antoine Toulme <antoine@lunar-ocean.com>wrote:

> And that would override the existing Buildfile shamelessly ? Sure, can you
> file a request for enhancement for this one ?
>
> Thanks,
>
> Antoine
>
> 2010/9/8 Khristian Alexander Schönrock <der.kosak@gmail.com>
>
> >  Speaking of it, can I call it even when there is a buildfile in the
> > folder? Something like "buildr --setup" that called this generator on the
> > current folder.
> >
> >
> > Em 08/09/2010 14:10, Antoine Toulme escreveu:
> >
> >  Oh, we haven't touched this generator for quite a long time now. If you
> >> feel
> >> like enhancing it, please send us patches.
> >>
> >> On Wed, Sep 8, 2010 at 09:44, Mark Petrovic<mspetrovic@gmail.com>
>  wrote:
> >>
> >>  I tried to run buildr in the top level to drive auto-creation of a
> >>> buildfile.  It didn't create an entry for subdir, which I thought odd.
> >>>  Here
> >>> is the auto-created buildfile:
> >>>
> >>>
> >>> # Generated by Buildr 1.4.1, change to your liking
> >>> # Version number for this release
> >>> VERSION_NUMBER = "1.0.0"
> >>> # Group identifier for your projects
> >>> GROUP = "TestProject"
> >>> COPYRIGHT = ""
> >>>
> >>> # Specify Maven 2.0 remote repositories here, like this:
> >>> repositories.remote<<  "http://www.ibiblio.org/maven2/"
> >>>
> >>> desc "The Testproject project"
> >>> define "TestProject" do
> >>>
> >>>  project.version = VERSION_NUMBER
> >>>  project.group = GROUP
> >>>  manifest["Implementation-Vendor"] = COPYRIGHT
> >>>
> >>>  define "subproj1" do
> >>>    compile.with # Add classpath dependencies
> >>>    resources
> >>>    test.compile.with # Add classpath dependencies
> >>>    test.resources
> >>>    package(:jar)
> >>>  end
> >>>
> >>>  define "subproj2" do
> >>>    compile.with # Add classpath dependencies
> >>>    resources
> >>>    test.compile.with # Add classpath dependencies
> >>>    test.resources
> >>>    package(:jar)
> >>>  end
> >>>
> >>> end
> >>>
> >>> Here is the top level tree.  Maybe I'm missing something.
> >>>
> >>> $  find .
> >>> ./subdir
> >>> ./subdir/subproj3
> >>> ./subdir/subproj3/src
> >>> ./subdir/subproj3/src/main
> >>> ./subdir/subproj3/src/main/java
> >>> ./subdir/subproj3/src/main/resources
> >>> ./subdir/subproj3/src/test
> >>> ./subdir/subproj3/src/test/java
> >>> ./subdir/subproj3/src/test/resources
> >>> ./subdir/subproj3/target
> >>> ./subdir/subproj3/target/resources
> >>> ./subdir/subproj3/target/test
> >>> ./subdir/subproj3/target/test/resources
> >>> ./subdir/subproj4
> >>> ./subdir/subproj4/src
> >>> ./subdir/subproj4/src/main
> >>> ./subdir/subproj4/src/main/java
> >>> ./subdir/subproj4/src/main/resources
> >>> ./subdir/subproj4/src/test
> >>> ./subdir/subproj4/src/test/java
> >>> ./subdir/subproj4/src/test/resources
> >>> ./subdir/subproj4/target
> >>> ./subdir/subproj4/target/resources
> >>> ./subdir/subproj4/target/test
> >>> ./subdir/subproj4/target/test/resources
> >>> ./subproj1
> >>> ./subproj1/src
> >>> ./subproj1/src/main
> >>> ./subproj1/src/main/java
> >>> ./subproj1/src/main/resources
> >>> ./subproj1/src/test
> >>> ./subproj1/src/test/java
> >>> ./subproj1/src/test/resources
> >>> ./subproj1/target
> >>> ./subproj1/target/resources
> >>> ./subproj1/target/test
> >>> ./subproj1/target/test/resources
> >>> ./subproj2
> >>> ./subproj2/src
> >>> ./subproj2/src/main
> >>> ./subproj2/src/main/java
> >>> ./subproj2/src/main/resources
> >>> ./subproj2/src/test
> >>> ./subproj2/src/test/java
> >>> ./subproj2/src/test/resources
> >>> ./subproj2/target
> >>> ./subproj2/target/resources
> >>> ./subproj2/target/test
> >>> ./subproj2/target/test/resources
> >>>
> >>>
> >>> On Sep 8, 2010, at 9:11 AM, Ed Smiley wrote:
> >>>
> >>>  If you follow the builder convention (assuming Java: src/main/java)
> >>>> you'd
> >>>>
> >>> do
> >>>
> >>>> something like this:
> >>>> root/
> >>>>  buildfile<== generate:
> >>>>
> >>>>  subproj1
> >>>>    src/main/java
> >>>>  subproj2
> >>>>    src/main/java
> >>>>  subdir/
> >>>>     subproj3
> >>>>        src/main/java
> >>>>     subproj4
> >>>>        src/main/java
> >>>> Now, don't write your buildfile, just run Buildr in the root and it'll
> >>>>
> >>> build
> >>>
> >>>> one for you that should work.
> >>>> If you already have a partly working buildfile, just back it up and
> prot
> >>>>
> >>> any
> >>>
> >>>> customizations you want into the buildfile.
> >>>>
> >>>> On Tue, Sep 7, 2010 at 9:39 PM, Travis Jensen<travis.jensen@gmail.com
> >>>> wrote:
> >>>>
> >>>>  I want to have a project structure that looks something like this:
> >>>>>
> >>>>> root/
> >>>>>  buildfile
> >>>>>  subproj1
> >>>>>  subproj2
> >>>>>  subdir/
> >>>>>     subproj3
> >>>>>     subproj4
> >>>>>
> >>>>> How do I tell my buildfile to look in subdir for subproj3 and
> subproj4?
> >>>>>
> >>>>> Thanks.
> >>>>>
> >>>>> tj
> >>>>>
> >>>>> *Travis Jensen*
> >>>>> ***
> >>>>> *Read the Software Maven @ http://softwaremaven.innerbrane.com/
> >>>>> Read my LinkedIn profile @ http://www.linkedin.com/in/travisjensen
> >>>>> Read my Twitter mumblings @ http://twitter.com/SoftwareMaven
> >>>>> Send me email @ travis.jensen@gmail.com
> >>>>>
> >>>>> **What kind of guy calls himself the Software Maven???**
> >>>>>
> >>>>>
> >>> --
> >>> Mark Petrovic
> >>>
> >>>
> >>>
> >>>  --
> > Khristian Schönrock
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message