hboutemy commented on PR #47: URL: https://github.com/apache/maven-sources/pull/47#issuecomment-4571302401
re-thinking at it: the directory structure has been done to be stable: it works when we have 2 branches, like Maven 4 vs Maven 3 (with 2 directory names patterns: sometimes the detault remains for Maven 3 and we have a `-4` directory, sometimes it is the opposite: Maven 4 is the default, and we have a `-3`) With Maven core, we now have an additional topic: for each major, there are 2 maintenance branches: - for Maven 3, we have the current active that is now 3.10, and the "security only" that is 3.9: we until now ignored the "security only" branch in the directory structure - for Maven 4, we have 4.0 and 4.1, 2 really active development branches... my proposal now that the analysis is done is: - for Maven 3, keep the stable directory name structure for the current branch (3.10 as of today) and continue ignore the security branch (3.9 as of today) - for Maven 4, let's keep this unusual `maven` + `maven-4.0.x` names: not ideal, but I hope this 4.0 vs 4.1 topic will be temporary... which finally means that we should go to ``` |-- core | |-- build-cache | |-- maven | |-- maven-4.0.x | |-- mvnd | |-- resolver | |-- resolver-ant-tasks | |-- wrapper | `-- 3.x | |-- its | |-- maven-3 | `-- mvnd-1 ``` only `resolver-1` has to be removed, given current Maven 3 (3.10) uses the default Resolver 2 thoughts? before I update the PR content based on this logic -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
