Let me also chime in, telling an "old war story" from my early days in
AspectJ: It used to be a very complex and convoluted Ant multi-module
monster. I never dared to even try and understand the build or
contribute to the project. Then one day, Andy Clement converted the
project to a Maven project, and suddenly I began to understand the
structure better. I started contributing to the project infrastructure,
weeding out the remaining relics of a replicated, scripted build taken
over from Ant, and use *convention over configuration*. Now, you can
just clone the repository, import the Maven project into Eclipse or IDEA
and build it.
We also have some source and binary assemblies, and I never thought
about using .gitignore as a source for excludes, because
-- as was said before, you usually exclude target, the very folder of
most interest for binary assemblies, and
-- whatever is ignored in my .gitignore and resides outside the target
folder, is usually also to be ignored in source assemblies.
If your case is any different, chances are that your directory structure
is suboptimal and non-standard.
IMO, the one-time effort of developers getting to know the new directory
layout is well invested, because sticking to Maven conventions pays off
in so many ways, not just because IDE import is now easier and users can
contribute patches or features more easily due to painless on-boarding.
--
Alexander Kriegisch
https://scrum-master.de
Greg Chabala schrieb am 12.11.2023 06:32 (GMT +07:00):
> I hesitate to bring it up, but this seems as good a time as any.
> You've mentioned several times your intent to massage the Xalan Maven
> build to produce artifacts at parity with the existing Ant build, and
> not just the contents of artifacts but also where they end up in the
> directory structure, for the convenience of those who are used to the
> Ant build.
>
> I foresee that if you are truly successful in this goal, you will have
> thoroughly reimplemented a procedural Ant build, and created a very
> weird Maven build, to the point where you may exclaim 'why did I even
> start this? It took so much work to get Maven to do what I was doing
> easily in Ant!', and Maven users will be confused about why there's
> nothing they expected in the target directory after running compile.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
