You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by jbi joe <jo...@daggerpoint.net> on 2007/09/06 11:28:26 UTC
Building nitemare
I attempted to do a incremental build of the latest revision taking each
piece and compiling seperately so that I could get my arms around each
piece.
I found that there are packages that point inside each other that prevent
this modularity. For example; I think its the qt bpel that contains three
packages and only one of them will build apart from the others. I
understand
that it works and is open source, but...... just a little software
engineering
practice can go a long way. Sorry for the rant, but I like ODE and would
like to see it get stark reviews... Please!
thanx
--
View this message in context: http://www.nabble.com/Building-nitemare-tf4390620.html#a12518270
Sent from the Apache Ode Dev mailing list archive at Nabble.com.
Re: Building nitemare
Posted by Maciej Szefler <mb...@intalio.com>.
fair enough, although you should not have any problem compiling if you
simply compile src/main/java/** . unfortunately, there is no easy way to
make sure this does not happen without defining dependency trees, but again,
while not especially attractive, it should not prevent one from compiling.
-mbs
On 9/8/07, jbi joe <jo...@daggerpoint.net> wrote:
>
>
>
> I did test with the bpel-ql dir. It contains 3 packages; eval, tree and
> jcc, with
> a top level package.
> If you try to compile each seperately u will see what I mean. Only one
> will compile without the others being pre-compiled. I was using a
> simple ant build.xml file and NOT rake to test. Perhaps rake is
> intelligent
> enough to pull all the parts together correctly. I was using ant build
> because
> I wanted to take it all apart so I could understand it better.
>
>
> Alex Boisvert wrote:
> >
> > On 9/6/07, jbi joe <jo...@daggerpoint.net> wrote:
> >>
> >> I attempted to do a incremental build of the latest revision taking
> each
> >> piece and compiling seperately so that I could get my arms around each
> >> piece.
> >> I found that there are packages that point inside each other that
> prevent
> >> this modularity. For example; I think its the qt bpel that contains
> >> three
> >> packages and only one of them will build apart from the others.
> >
> >
> > Hi Joe,
> >
> > As far as I can tell, there are no cross-dependencies between the
> modules.
> > A way to tell is to run "rake clean compile" and witness that modules
> are
> > compiled individually and only once.
> >
> > Here's a trimmed output of "rake compile | grep -i compile":
> >
> > Compiling 78 source files in ode:utils:compile
> > Compiling 46 source files in ode:bpel-obj:compile
> > Compiling 94 source files in ode:bpel-schemas:compile
> > Compiling 84 source files in ode:bpel-api:compile
> > Compiling 1 source files in ode:bpel-api-jca:compile
> > Compiling 168 source files in ode:bpel-compiler:compile
> > Compiling 20 source files in ode:bpel-dao:compile
> > Compiling 3 source files in ode:jacob-ap:compile
> > Compiling 47 source files in ode:jacob:compile
> > Compiling 80 source files in ode:bpel-ql:compile
> > Compiling 41 source files in ode:dao-hibernate:compile
> > Compiling 23 source files in ode:bpel-store:compile
> > Compiling 148 source files in ode:bpel-runtime:compile
> > Compiling 17 source files in ode:jca-ra:compile
> > Compiling 4 source files in ode:jca-server:compile
> > Compiling 2 source files in ode:bpel-connector:compile
> > Compiling 13 source files in ode:bpel-epr:compile
> > Compiling 10 source files in ode:scheduler-simple:compile
> > Compiling 25 source files in ode:axis2:compile
> > Compiling 19 source files in ode:dao-jpa:compile
> > Compiling 14 source files in ode:tools:compile
> > Compiling 4 source files in ode:bpel-test:compile
> > Compiling 31 source files in ode:jbi:compile
> >
> > There you have it, the incremental compile order for all modules.
> >
> > alex
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Building-nitemare-tf4390620.html#a12569147
> Sent from the Apache Ode Dev mailing list archive at Nabble.com.
>
>
Re: Building nitemare
Posted by jbi joe <jo...@daggerpoint.net>.
I did test with the bpel-ql dir. It contains 3 packages; eval, tree and
jcc, with
a top level package.
If you try to compile each seperately u will see what I mean. Only one
will compile without the others being pre-compiled. I was using a
simple ant build.xml file and NOT rake to test. Perhaps rake is intelligent
enough to pull all the parts together correctly. I was using ant build
because
I wanted to take it all apart so I could understand it better.
Alex Boisvert wrote:
>
> On 9/6/07, jbi joe <jo...@daggerpoint.net> wrote:
>>
>> I attempted to do a incremental build of the latest revision taking each
>> piece and compiling seperately so that I could get my arms around each
>> piece.
>> I found that there are packages that point inside each other that prevent
>> this modularity. For example; I think its the qt bpel that contains
>> three
>> packages and only one of them will build apart from the others.
>
>
> Hi Joe,
>
> As far as I can tell, there are no cross-dependencies between the modules.
> A way to tell is to run "rake clean compile" and witness that modules are
> compiled individually and only once.
>
> Here's a trimmed output of "rake compile | grep -i compile":
>
> Compiling 78 source files in ode:utils:compile
> Compiling 46 source files in ode:bpel-obj:compile
> Compiling 94 source files in ode:bpel-schemas:compile
> Compiling 84 source files in ode:bpel-api:compile
> Compiling 1 source files in ode:bpel-api-jca:compile
> Compiling 168 source files in ode:bpel-compiler:compile
> Compiling 20 source files in ode:bpel-dao:compile
> Compiling 3 source files in ode:jacob-ap:compile
> Compiling 47 source files in ode:jacob:compile
> Compiling 80 source files in ode:bpel-ql:compile
> Compiling 41 source files in ode:dao-hibernate:compile
> Compiling 23 source files in ode:bpel-store:compile
> Compiling 148 source files in ode:bpel-runtime:compile
> Compiling 17 source files in ode:jca-ra:compile
> Compiling 4 source files in ode:jca-server:compile
> Compiling 2 source files in ode:bpel-connector:compile
> Compiling 13 source files in ode:bpel-epr:compile
> Compiling 10 source files in ode:scheduler-simple:compile
> Compiling 25 source files in ode:axis2:compile
> Compiling 19 source files in ode:dao-jpa:compile
> Compiling 14 source files in ode:tools:compile
> Compiling 4 source files in ode:bpel-test:compile
> Compiling 31 source files in ode:jbi:compile
>
> There you have it, the incremental compile order for all modules.
>
> alex
>
>
--
View this message in context: http://www.nabble.com/Building-nitemare-tf4390620.html#a12569147
Sent from the Apache Ode Dev mailing list archive at Nabble.com.
Re: Building nitemare
Posted by Maciej Szefler <mb...@intalio.com>.
Although it should be pointed out that there are ciruclar dependencies in
the test cases. This is unfortunate, but not too much that can be done about
it.
On 9/6/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> On 9/6/07, jbi joe <jo...@daggerpoint.net> wrote:
> >
> > I attempted to do a incremental build of the latest revision taking each
> > piece and compiling seperately so that I could get my arms around each
> > piece.
> > I found that there are packages that point inside each other that
> prevent
> > this modularity. For example; I think its the qt bpel that contains
> > three
> > packages and only one of them will build apart from the others.
>
>
> Hi Joe,
>
> As far as I can tell, there are no cross-dependencies between the modules.
> A way to tell is to run "rake clean compile" and witness that modules are
> compiled individually and only once.
>
> Here's a trimmed output of "rake compile | grep -i compile":
>
> Compiling 78 source files in ode:utils:compile
> Compiling 46 source files in ode:bpel-obj:compile
> Compiling 94 source files in ode:bpel-schemas:compile
> Compiling 84 source files in ode:bpel-api:compile
> Compiling 1 source files in ode:bpel-api-jca:compile
> Compiling 168 source files in ode:bpel-compiler:compile
> Compiling 20 source files in ode:bpel-dao:compile
> Compiling 3 source files in ode:jacob-ap:compile
> Compiling 47 source files in ode:jacob:compile
> Compiling 80 source files in ode:bpel-ql:compile
> Compiling 41 source files in ode:dao-hibernate:compile
> Compiling 23 source files in ode:bpel-store:compile
> Compiling 148 source files in ode:bpel-runtime:compile
> Compiling 17 source files in ode:jca-ra:compile
> Compiling 4 source files in ode:jca-server:compile
> Compiling 2 source files in ode:bpel-connector:compile
> Compiling 13 source files in ode:bpel-epr:compile
> Compiling 10 source files in ode:scheduler-simple:compile
> Compiling 25 source files in ode:axis2:compile
> Compiling 19 source files in ode:dao-jpa:compile
> Compiling 14 source files in ode:tools:compile
> Compiling 4 source files in ode:bpel-test:compile
> Compiling 31 source files in ode:jbi:compile
>
> There you have it, the incremental compile order for all modules.
>
> alex
>
Re: Building nitemare
Posted by Alex Boisvert <bo...@intalio.com>.
On 9/6/07, jbi joe <jo...@daggerpoint.net> wrote:
>
> I attempted to do a incremental build of the latest revision taking each
> piece and compiling seperately so that I could get my arms around each
> piece.
> I found that there are packages that point inside each other that prevent
> this modularity. For example; I think its the qt bpel that contains
> three
> packages and only one of them will build apart from the others.
Hi Joe,
As far as I can tell, there are no cross-dependencies between the modules.
A way to tell is to run "rake clean compile" and witness that modules are
compiled individually and only once.
Here's a trimmed output of "rake compile | grep -i compile":
Compiling 78 source files in ode:utils:compile
Compiling 46 source files in ode:bpel-obj:compile
Compiling 94 source files in ode:bpel-schemas:compile
Compiling 84 source files in ode:bpel-api:compile
Compiling 1 source files in ode:bpel-api-jca:compile
Compiling 168 source files in ode:bpel-compiler:compile
Compiling 20 source files in ode:bpel-dao:compile
Compiling 3 source files in ode:jacob-ap:compile
Compiling 47 source files in ode:jacob:compile
Compiling 80 source files in ode:bpel-ql:compile
Compiling 41 source files in ode:dao-hibernate:compile
Compiling 23 source files in ode:bpel-store:compile
Compiling 148 source files in ode:bpel-runtime:compile
Compiling 17 source files in ode:jca-ra:compile
Compiling 4 source files in ode:jca-server:compile
Compiling 2 source files in ode:bpel-connector:compile
Compiling 13 source files in ode:bpel-epr:compile
Compiling 10 source files in ode:scheduler-simple:compile
Compiling 25 source files in ode:axis2:compile
Compiling 19 source files in ode:dao-jpa:compile
Compiling 14 source files in ode:tools:compile
Compiling 4 source files in ode:bpel-test:compile
Compiling 31 source files in ode:jbi:compile
There you have it, the incremental compile order for all modules.
alex