I was wondering if anyone had any objections to merging the data and main modules on trunk into a single module. Basically having main absorb data.
My use case is the mock testing stuff, currently it can't see anything in main which is causing problems. I propose the merge b/c a) it solves my problem and b) I think the merge makes sense for a couple of reasons:
1) data has all the mock test setup, but all the test support classes are in main, there is no practical reason for the separation
2) setting up test dependencies for mock tests is currently a pain b/c modules have to declare both dependencies (test scope dependencies are not transitive)
3) data only has a few utility for data access in it, it does not really warrant a separate module imho.
Thoughts? Objections?
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I was wondering if anyone had any objections to merging the data and main modules on trunk into a single module. Basically having main absorb data.
My use case is the mock testing stuff, currently it can't see anything in main which is causing problems. I propose the merge b/c a) it solves my problem and b) I think the merge makes sense for a couple of reasons:
1) data has all the mock test setup, but all the test support classes are in main, there is no practical reason for the separation
2) setting up test dependencies for mock tests is currently a pain b/c modules have to declare both dependencies (test scope dependencies are not transitive)
3) data only has a few utility for data access in it, it does not really warrant a separate module imho.
Thoughts? Objections?
Works for me, +1
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I was wondering if anyone had any objections to merging the data and
main modules on trunk into a single module. Basically having main absorb
data.
My use case is the mock testing stuff, currently it can’t see anything
in main which is causing problems. I propose the merge b/c a) it solves
my problem and b) I think the merge makes sense for a couple of reasons:
data has all the mock test setup, but all the test support classes
are in main, there is no practical reason for the separation
setting up test dependencies for mock tests is currently a pain b/c
modules have to declare both dependencies (test scope dependencies are
not transitive)
data only has a few utility for data access in it, it does not really
warrant a separate module imho.
Thoughts? Objections?
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
Just a quick note that i have gone ahead with the move. So long data module.
Justin Deoliveira wrote:
Hi all,
I was wondering if anyone had any objections to merging the data and main modules on trunk into a single module. Basically having main absorb data.
My use case is the mock testing stuff, currently it can't see anything in main which is causing problems. I propose the merge b/c a) it solves my problem and b) I think the merge makes sense for a couple of reasons:
1) data has all the mock test setup, but all the test support classes are in main, there is no practical reason for the separation
2) setting up test dependencies for mock tests is currently a pain b/c modules have to declare both dependencies (test scope dependencies are not transitive)
3) data only has a few utility for data access in it, it does not really warrant a separate module imho.
Thoughts? Objections?
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.