You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Peter Tillotson <sl...@yahoo.co.uk> on 2011/12/13 21:21:25 UTC
Two compile target dirs
I am trying to do a second compilation, actually the key is I'm trying
to have two different classes folders in 1 projects
fd = file('target/tool/classes')
compile {
compile('myProj/src/tool/java').into(fd)
fd.invoke
}
With the above I get a cyclic dependency
Use case for this is
* Packaging API separate from Implementation
* GPL'd driver code separate to server
So I package API in one jar and everything else in another
I could use another project but it is not a huge number files but enough
to want to avoid filters.
is saw
http://buildr.markmail.org/search/?q=list%3Auser+compile+#query:list%3Auser%20compile%20+page:1+mid:mwjwxh2fxu7xhjln+state:results
but didn't understand it.
tnx
p
Re: Two compile target dirs
Posted by Peter Tillotson <sl...@yahoo.co.uk>.
Many thanks - I cracked it but a v useful example
p
________________________________
From: Alex Boisvert <al...@gmail.com>
To: users@buildr.apache.org; Peter Tillotson <sl...@yahoo.co.uk>
Sent: Wednesday, 14 December 2011, 14:24
Subject: Re: Two compile target dirs
If it helps, I've packaged and shared the sample project I used to test the
precompile step here,
http://dl.dropbox.com/u/6893817/buildr-precompile.zip
alex
On Wed, Dec 14, 2011 at 1:35 AM, Peter Tillotson <sl...@yahoo.co.uk>wrote:
> I was trying to work out how and where to wire it in.
>
> My ruby / rake is not the best, but if I'm flogging the right horse I'll
> keep going,
>
> Apologies for metaphor - not a real horse
>
> P
>
>
> ________________________________
> From: Alex Boisvert <al...@gmail.com>
> To: users@buildr.apache.org
> Sent: Tuesday, 13 December 2011, 22:21
> Subject: Re: Two compile target dirs
>
> I think the link provided at the bottom would be the right approach. What
> part of it didn't you understand or didn't work for you?
>
> alex
>
>
> On Tue, Dec 13, 2011 at 12:21 PM, Peter Tillotson <slatemine@yahoo.co.uk
> >wrote:
>
> > I am trying to do a second compilation, actually the key is I'm trying
> > to have two different classes folders in 1 projects
> >
> > fd =
> file('target/tool/classes')
> > compile {
> > compile('myProj/src/tool/java').into(fd)
> > fd.invoke
> > }
> > With the above I get a cyclic dependency
> >
> > Use case for this is
> > * Packaging API separate from Implementation
> > * GPL'd driver code separate to server
> >
> > So I package API in one jar and everything else in another
> >
> > I could use another project but it is not a huge number files but enough
> > to want to avoid filters.
> >
> > is saw
> >
> >
> >
> http://buildr.markmail.org/search/?q=list%3Auser+compile+#query:list%3Auser%20compile%20+page:1+mid:mwjwxh2fxu7xhjln+state:results
> >
> > but didn't understand
> it.
> >
> > tnx
> >
> > p
> >
> >
>
Re: Two compile target dirs
Posted by Alex Boisvert <al...@gmail.com>.
If it helps, I've packaged and shared the sample project I used to test the
precompile step here,
http://dl.dropbox.com/u/6893817/buildr-precompile.zip
alex
On Wed, Dec 14, 2011 at 1:35 AM, Peter Tillotson <sl...@yahoo.co.uk>wrote:
> I was trying to work out how and where to wire it in.
>
> My ruby / rake is not the best, but if I'm flogging the right horse I'll
> keep going,
>
> Apologies for metaphor - not a real horse
>
> P
>
>
> ________________________________
> From: Alex Boisvert <al...@gmail.com>
> To: users@buildr.apache.org
> Sent: Tuesday, 13 December 2011, 22:21
> Subject: Re: Two compile target dirs
>
> I think the link provided at the bottom would be the right approach. What
> part of it didn't you understand or didn't work for you?
>
> alex
>
>
> On Tue, Dec 13, 2011 at 12:21 PM, Peter Tillotson <slatemine@yahoo.co.uk
> >wrote:
>
> > I am trying to do a second compilation, actually the key is I'm trying
> > to have two different classes folders in 1 projects
> >
> > fd =
> file('target/tool/classes')
> > compile {
> > compile('myProj/src/tool/java').into(fd)
> > fd.invoke
> > }
> > With the above I get a cyclic dependency
> >
> > Use case for this is
> > * Packaging API separate from Implementation
> > * GPL'd driver code separate to server
> >
> > So I package API in one jar and everything else in another
> >
> > I could use another project but it is not a huge number files but enough
> > to want to avoid filters.
> >
> > is saw
> >
> >
> >
> http://buildr.markmail.org/search/?q=list%3Auser+compile+#query:list%3Auser%20compile%20+page:1+mid:mwjwxh2fxu7xhjln+state:results
> >
> > but didn't understand
> it.
> >
> > tnx
> >
> > p
> >
> >
>
Re: Two compile target dirs
Posted by Peter Tillotson <sl...@yahoo.co.uk>.
I was trying to work out how and where to wire it in.
My ruby / rake is not the best, but if I'm flogging the right horse I'll keep going,
Apologies for metaphor - not a real horse
P
________________________________
From: Alex Boisvert <al...@gmail.com>
To: users@buildr.apache.org
Sent: Tuesday, 13 December 2011, 22:21
Subject: Re: Two compile target dirs
I think the link provided at the bottom would be the right approach. What
part of it didn't you understand or didn't work for you?
alex
On Tue, Dec 13, 2011 at 12:21 PM, Peter Tillotson <sl...@yahoo.co.uk>wrote:
> I am trying to do a second compilation, actually the key is I'm trying
> to have two different classes folders in 1 projects
>
> fd =
file('target/tool/classes')
> compile {
> compile('myProj/src/tool/java').into(fd)
> fd.invoke
> }
> With the above I get a cyclic dependency
>
> Use case for this is
> * Packaging API separate from Implementation
> * GPL'd driver code separate to server
>
> So I package API in one jar and everything else in another
>
> I could use another project but it is not a huge number files but enough
> to want to avoid filters.
>
> is saw
>
>
> http://buildr.markmail.org/search/?q=list%3Auser+compile+#query:list%3Auser%20compile%20+page:1+mid:mwjwxh2fxu7xhjln+state:results
>
> but didn't understand
it.
>
> tnx
>
> p
>
>
Re: Two compile target dirs
Posted by Alex Boisvert <al...@gmail.com>.
I think the link provided at the bottom would be the right approach. What
part of it didn't you understand or didn't work for you?
alex
On Tue, Dec 13, 2011 at 12:21 PM, Peter Tillotson <sl...@yahoo.co.uk>wrote:
> I am trying to do a second compilation, actually the key is I'm trying
> to have two different classes folders in 1 projects
>
> fd = file('target/tool/classes')
> compile {
> compile('myProj/src/tool/java').into(fd)
> fd.invoke
> }
> With the above I get a cyclic dependency
>
> Use case for this is
> * Packaging API separate from Implementation
> * GPL'd driver code separate to server
>
> So I package API in one jar and everything else in another
>
> I could use another project but it is not a huge number files but enough
> to want to avoid filters.
>
> is saw
>
>
> http://buildr.markmail.org/search/?q=list%3Auser+compile+#query:list%3Auser%20compile%20+page:1+mid:mwjwxh2fxu7xhjln+state:results
>
> but didn't understand it.
>
> tnx
>
> p
>
>