You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Travis Jensen <tr...@gmail.com> on 2010/09/08 06:39:43 UTC
Playing with project paths
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???**
Re: Playing with project paths
Posted by Travis Jensen <tr...@gmail.com>.
It does. 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???**
On Wed, Sep 8, 2010 at 8:59 AM, Mark Petrovic <ms...@gmail.com> wrote:
> Does this not work?
>
> For
>
> root/
> buildfile
> subproj1
> subproj2
> subdir/
> subproj3
> subproj4
>
>
> desc 'top'
> define 'top' do
>
> desc '1'
> define 'subproj1' do
> end
>
> desc '2'
> define 'subproj2' do
> end
>
> desc 's'
> define 'subdir' do
> desc '3'
> define 'subproj3' do
> end
>
> desc '4'
> define 'subproj4' do
> end
> end
>
> end
>
> $ buildr help:projects
> (in /Users/petrovic/tmp/TestProject, development)
> top # top
> top:subdir # s
> top:subdir:subproj3 # 3
> top:subdir:subproj4 # 4
> top:subproj1 # 1
> top:subproj2 # 2
>
>
>
> On Sep 7, 2010, at 9:39 PM, Travis Jensen wrote:
>
> > I want to have a project structure that looks something like this:
> >
> > r§
> >
> > 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
>
>
>
Re: Playing with project paths
Posted by Mark Petrovic <ms...@gmail.com>.
Does this not work?
For
root/
buildfile
subproj1
subproj2
subdir/
subproj3
subproj4
desc 'top'
define 'top' do
desc '1'
define 'subproj1' do
end
desc '2'
define 'subproj2' do
end
desc 's'
define 'subdir' do
desc '3'
define 'subproj3' do
end
desc '4'
define 'subproj4' do
end
end
end
$ buildr help:projects
(in /Users/petrovic/tmp/TestProject, development)
top # top
top:subdir # s
top:subdir:subproj3 # 3
top:subdir:subproj4 # 4
top:subproj1 # 1
top:subproj2 # 2
On Sep 7, 2010, at 9:39 PM, Travis Jensen wrote:
> I want to have a project structure that looks something like this:
>
> r§
>
> 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
Re: Playing with project paths
Posted by Ed Smiley <es...@ebrary.com>.
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 <an...@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 <de...@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<ms...@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
> >
>
Re: Playing with project paths
Posted by Khristian Alexander Schönrock <de...@gmail.com>.
Sorry, I wasn't thinking such shameful things :P
What I'm really struggling with is this generator not reading my
settings in the buildr.rb file (%userprofile%\.buildr\buildr.rb).
I added all the repositories I need in this file, as the buildr manual
says, but it fails with "no remote repositories defined" when I having
this generator parse my project's poms.
Em 08/09/2010 14:19, Antoine Toulme escreveu:
> 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<de...@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<ms...@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
>>
Re: Playing with project paths
Posted by Antoine Toulme <an...@lunar-ocean.com>.
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 <de...@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<ms...@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
>
Re: Playing with project paths
Posted by Khristian Alexander Schönrock <de...@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<ms...@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
Re: Playing with project paths
Posted by Antoine Toulme <an...@lunar-ocean.com>.
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 <ms...@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
>
>
>
Re: Playing with project paths
Posted by Mark Petrovic <ms...@gmail.com>.
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 <tr...@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
Re: Playing with project paths
Posted by Ed Smiley <es...@ebrary.com>.
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 <tr...@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???**
>