On Tue, 2002-12-10 at 10:52, Siegfried G�schl wrote:
> I found out that the ${basedir} is set correctly and patched my
> plugins accordingly but my JUNIT test cases loading test data have no
> idea of a {basedir} (yet) ... I haven't looked at the BETWIXT yet.
>
> What are the current ideas of refactoring reactor?!
Simply clean up the inheritance so that it works properly. It should be
leak free and inherit correctly among projects. Once that is done people
can build what they like on top of something small and reliable.
> Would it make
> sense to create a MAVEN process for each depend subprojects and use
> the return value (TBD as far as I know) as indicator of a sucessful
> build?!
Some things in App.java need to be moved to Maven.java in order to get a
set of useful return values. For myself this is necessary for Continuum
which does not run from the command yet needs return values from builds
as the return values are used as signifying tokens to the werkflow
process which controls the build. Once Maven tosses out some useful
return values itself then again people should be able to build decent
tools upon the reactor.
> For my 50+ subprojects thingie the MAVEN build seems to leak memory
> (javac) which trashes my machine and patience ... :-)
I'm in the same boat.
> Thanks
>
> Siegfried Goeschl
> CTO
> =================================
> IT20one GmbH
> mail: [EMAIL PROTECTED]
>
>
> On 10 Dec 2002 at 9:20, Jason van Zyl wrote:
>
> > On Tue, 2002-12-10 at 04:44, Siegfried G�schl wrote:
> > > Hi Warner
> > >
> > > I used reactor for two projects (one small and one big) and hit IMHO
> > > a few limitations
> > >
> > > +) as far as I know it is not possible to inherit JAR files (B7) but
> > > +
> > > I might be wrong (there was a posting)
> >
> > What do you mean inherit JARs?
> >
> > Do you mean use the same version of JAR for an entire build?
> >
> > > +) It is not possible to inherit project.properties and
> > > build.properties from the master project
> > >
> > > +) Reactor use its own working directory and screws up my testcase
> > > since the try to load test resources using a relative path
> >
> > Look at the betwixt tests to see how to do this. The betwixt tests run
> > in the commons reactor and work in and outside the reactor. Any
> > resources that you use in tests need to use the notion of the
> > ${basedir} which maven will set correctly. I was thinking of making a
> > simple set of abstract classes for tests to make this easier but
> > haven't got there yet. But the betwixt AbstractTestCase will give you
> > an idea of what to do to fix this.
> >
> > > +) CheckStyle does not find its property file during a reactor build
> >
> > That's good to know, noted.
> >
> > > +) With 50+ subprojects I have memory problems
> > >
> > >
> > > Therefore I'm triggering my builds not with reactor but still using
> > > POM inheritance and POM interpolation .... and wait for the next
> > > release ... :-)
> > >
> > >
> > > Siegfried Goeschl
> > > CTO
> > > =================================
> > > IT20one GmbH
> > > mail: [EMAIL PROTECTED]
> > > phone: +43-1-9900046
> > > fax: +43-1-52 37 888
> > > www.it20one.at
> > >
> > >
> > > On 9 Dec 2002 at 19:08, Warner Onstine wrote:
> > >
> > > > Hi all,
> > > > I have project that is evolving and I was wondering if using
> > > > reactor will do what I want.
> > > >
> > > > Basically I have two modules in cvs - one for core and one for
> > > > user interface.
> > > >
> > > > The UI will have several sub-directories for each UI that can be
> > > > used with the core. ui - tapestry - web-ognl - cocoa ...etc.
> > > >
> > > > What I would like is to define a top-level project.xml and
> > > > project.properties which adds a dependency for the core jar and
> > > > any other necessary jars. I would also like to define a top-level
> > > > maven.xml so that whoever builds can either build all of the ui
> > > > components or individual ones.
> > > >
> > > > So far, from what I see, this is doable. Now, here's the question:
> > > > Would it be beneficial to use reactor? Or would it be better to
> > > > write my own maven.xml.
> > > >
> > > > -warner
> > > >
> > > > +warner onstine+
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > > > <mailto:[EMAIL PROTECTED]> For
> > > > additional commands, e-mail:
> > > > <mailto:[EMAIL PROTECTED]>
> > > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:[EMAIL PROTECTED]> For
> > > additional commands, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > --
> > jvz.
> >
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://tambora.zenplex.org
> >
> > In short, man creates for himself a new religion of a rational
> > and technical order to justify his work and to be justified in it.
> >
> > -- Jacques Ellul, The Technological Society
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]> For
> > additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
