[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-tck-dev] Preparing to hack with ReWrite...
|
On 11/20/22 1:53 AM, Olivier Lamy
wrote:
Hi,
I'm not sure adding more tooling will fix anything (except
making it more complicated by adding more tooling :)).
Good point, the additional `rewrite` tooling would be temporary
until we complete the TCK refactoring.
I have some issues on how the current tckrefactor build
structure (e.g pom content), I have some changes in my branch
with the servlet tck using arquilian. [1]
But I didn't to fix too many things in this branch as the
merge/rebase will be an even worst nightmare for me :)
Some content I have in mind which looks wrong (or I don't
understand the reason) to my (long) Maven experience.
Why having everything in <dependencies> [2] in parent
pom, this mean by example servlet or jsp will have batch or
jms as dependency?
+1 for removing the <dependencies> [2] from the parent pom.
Why having this section with m-enforcer-p [3] is
every poms?
+1 for removing m-enforcer-p [3] from sub-modules.
I don't understand the need of using of
build-helper-m-p [4] in every poms? we probably only need to
have the sources in the standard Maven location.
+1
If your concern is about having a clean build (e.g no
compile issue) in the tckrefactor branch if you need a
volunteer I can have a try for the next few days.
+1, thank you!
Scott
--
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev