DRAFT: Project Jigsaw: The Big Picture (part 1)
aheritier at gmail.com
Wed Dec 21 15:56:55 PST 2011
After having participating in Maven for years I think it was a wrong
choice to not have a stronger definition/enforcement of versions.
It is in the central place of the resolution system and it becomes a
nightmare when you have to compare Alpha, beta, RC, CR, ... and many others
versions that we may not imagine.
Nowadays we have also a lot of issues because of the conflict between
OSGi versions and Maven SNAPSHOTs.
I agree to relax some rules like having the ability to not use versions
as far as you don't share modules with others, but after that when modules
have to be shared I think that you need to have something really strict to
propose an efficient resolution mechanism.
About modules definitions it isn't clear for me if sources are/can be
considered as resources and thus shared within modules. We have the case
for example to share sources for GWT but in many others cases (from IDEs,
Related to that I see nothing maven classifiers. The major part of time
this is useful especially at compile/development time to reuse some
variations of a same maven artifact (sources, javadocs, ...) but when
jigsaw will be out I would like to have the ability in Maven (and others
build systems) to reuse jigsaw repositories thus they'll need to be
extensible (the repository layout and the identification/resolution system)
On Wed, Dec 21, 2011 at 12:28 AM, <mark.reinhold at oracle.com> wrote:
> I've started drafting an overview of the current state of Jigsaw.
> The first part is attached below, and also available on the web:
> Comments, questions, and suggestions welcome. Flames will be ignored.
> - Mark
More information about the jigsaw-dev