I've been trying to use Maven2 to build my JSTL 1.1-based web application, and I had problems locating the Apache Jakarta standard implementation of JSTL 1.1 (AKA standard.jar to most). I finally found it using group id "taglibs" and artifact id "standard" with version "1.1.2". Shouldn't the correct group id be "jakarta.apache.org", with all else being the same? This would abide by the current Maven2 convention.
The groupId per m2 convention should be org.apache.taglibs , however this will require relocation of the existing artifacts. There have been some discussions about this (Jakarta Commons has a similar issue) but nothing concrete yet.
Understood. This would be well documented in a FAQ somewhere under the jakarta.apache.org website until a plan is in place and executed for m2 convention compliance. It would be nice if the FAQ could include a table including the jakarta library (taglibs, etc), the m2 group id, & the m2 artifact id. Is that reasonable as a workaround?
Resolving this. I don't think the Taglibs project ever put anything in Maven, (maybe RDC did?) so it's hit and miss as to what was put in there and I don't have any itch to go work that out (especially as most taglibs are deprecated now). Going forward it'll be sorted out as Maven2 is used as the build. The JSTL implementation needs to figure out how it fits into the Maven world too.