2 ms·
they don't raise specific technical concerns. they want to have more time to address/disucss stuff about the specification. also maven is not the de facto pack
by merb 9y ago
they don't raise specific technical concerns.
they want to have more time to address/disucss stuff about the specification. also maven is not the de facto package manager. the only thing which might be defacto is the publishing style, however there are many other package manager in the java world.
also a lot of this stuff could've been cleared up way way earlier.
p.s.: even if the one outlined is not a policitcal move, some votes definitly are.
- lvh 9y agoNone of those other package managers have had their issues (mostly the same) addressed either; it's a lowest common denominator: people are complaining that _not even_ Maven has been addressed. Even if it were true that somehow Maven isn't the de facto package manager (I disagree), it is certainly more than big enough that the JCP doesn't get to casually ignore its existence.