I don't know the history about WHY they are seperated, so maybe there
are (or at least there were) valid reason to do so - at least in this
repo. In several plugins the IT are part of the same repo as the code.

In general: I think it's usefull to merge them so that the IT can be run
while building / developing it.

Matthias

Am 08.10.2024 um 08:36 schrieb Guillaume Nodet:
I'd like to discuss merging ITs into maven core repository.
The ITs have already been splitted some time ago between the 3.x branch and
master for testing Maven master.  But I don't really see a good reason to
keep the repositories separated, this makes things more complicated when
modifying maven code and adding ITs.

The following script allow merging the two repositories while keeping both
histories:


brew install git-filter-repo

git clone https://github.com/apache/maven

git clone https://github.com/apache/maven-integration-testing

(cd maven-integration-testing && \

     git filter-repo --to-subdirectory-filter its)

(cd maven && \

     git remote add its ../maven-integration-testing && \

     git fetch its --no-tags && \

     EDITOR=true git merge --allow-unrelated-histories its/master && \

     git remote remove its)

The next step would be to actually include them in a profile and update the
github workflow.
I think they could be refactored to:
   * first perform a full  run on Ubuntu + latest LTS JDK:
      - restore cache
      -  checkout
      -  build with no tests
      - run IT bootstrap (to prime local repo)
      - save cache
      - build again with tests and ITs
   * if this first run succeeds, do the same on other platforms / jdks

The cache is important to add imho.  It seems lately, GH runners have often
problems downloading from maven central, so that would help a lot
increasing the stability.  So using
https://github.com/marketplace/actions/maven-cache or a similar action
would be handy imho.

We should also upload nightlies from GH.
And automate the releases as much as possible....


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to