- Original message -
> On 01-05-14 00:29, Peter wrote:
> > - Original message -
> > On 30-04-14 02:02, Dennis Reedy wrote:
> >
> > A this point I'm soliciting opinions and thoughts. Note that using
> > Gradle is certainly an option here, the breakout into multi-modules is
> > not t
On 01-05-14 00:29, Peter wrote:
- Original message -
> On 30-04-14 02:02, Dennis Reedy wrote:
>
> > A this point I'm soliciting opinions and thoughts. Note that using
> > Gradle is certainly an option here, the breakout into multi-modules is
> > not tied to Maven, it's based on accep
Thanks Dennis,
The test harness presently includes a number of classes from the the main
build, so it'll depend on them, but not include them.
Jsk-policy also needs investigating.
Cheers,
Peter.
- Original message -
> You can certainly use the approach in qa_refactor. I did make 2 cha
- Original message -
> On 30-04-14 02:02, Dennis Reedy wrote:
>
> > A this point I'm soliciting opinions and thoughts. Note that using
> > Gradle is certainly an option here, the breakout into multi-modules is
> > not tied to Maven, it's based on accepted conventions. I chose Maven
> > bec
You can certainly use the approach in qa_refactor. I did make 2 changes to
the code to make the approach work:
1. Moved com.sun.jini.landlord.LeasedResource into jsk-dl.jar. This was
done to accomodate outrigger-dl.jar's
reliance on com.sun.jini.landlord.LeasedResource from
com.sun.jini.outrigger.
On 30-04-14 20:57, Simon IJskes - QCG wrote:
On 30-04-14 02:02, Dennis Reedy wrote:
Any change we can re-apply your effort on trunk while maintaining
subversion history? i.e. 'svn mv' commands?
if so, we can adjust the ant script to maintain compatibility (as an
intermediate step).
Gr. Si
On 30-04-14 02:02, Dennis Reedy wrote:
A this point I'm soliciting opinions and thoughts. Note that using Gradle
is certainly an option here, the breakout into multi-modules is not tied to
Maven, it's based on accepted conventions. I chose Maven because it was the
quickest (for me) to get going.
