+1 Just a remark : sometime you replace integration-tests by "its" otherwise by "it". Perhaps we could unify them ..... For example you propose to rename core-integration-tests-support to core-it-support and not to core-its-support.
Arnaud On Mon, Sep 22, 2008 at 1:51 AM, Brett Porter <[EMAIL PROTECTED]> wrote: > +1 to all > > I would prefer core-it-suite to core-its, but it's a small thing. > > I additionally think the src/main/resources/* paths could be reduced to > just the issue number (mng-1234), without the description of the problem > (the description can be retained in Java test class). It is the resource > paths that tend to be longer overall and could afford some space saving. > > Let me add a huge thanks for taking this on! > > Cheers, > Brett > > > On 22/09/2008, at 4:11 AM, Benjamin Bentmann wrote: > > Hi, >> >> motivated by a recent user's mail that a checkout of the core ITs failed, >> I would like to suggest the following renames to make contributing a little >> easier. >> >> More precisely, in core-integration-testing/trunk change >> >> core-integration-tests >> -> core-its >> >> core-integration-tests/src/main/java/**/integrationtests/* >> -> core-its/src/main/java/**/its/* >> >> core-integration-tests-support >> -> core-it-support >> >> core-integration-tests-support/core-integration-testing-plugins >> -> core-it-support/core-it-plugins >> >> core-integration-tests-support/core-integration-testing-support >> -> core-it-support/core-it-support >> >> core-integration-tests-support/core-integration-testing-wagon >> -> core-it-support/core-it-wagon >> >> core-integration-tests-support/maven-integration-test-archetype >> -> core-it-support/maven-it-archetype >> >> core-integration-tests-support/maven-integration-test-helper >> -> core-it-support/maven-it-helper >> >> core-integration-tests-support/maven-integration-test-sample >> -> core-it-support/maven-it-sample >> >> i.e. basically replace "integration-test*" with "it". >> >> Since IT seems to be a common acronym among us, I believe the loss in >> expressiveness is small. However, there would be a considerably reduction in >> path length (29 chars for the archetype project). >> >> Of course, the artifactIds of the corresponding project should be aligned >> to. >> >> Not sure how others feel, but IMHO Maven would benefit from some more >> contributions, here is enough work lying around. Since those contributions >> usually happen in people's free time, I consider it important to lower the >> barrier for contributors to get in touch with the project. >> >> What do you think? >> >> >> Benjamin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
