Now stop using it so it can be removed one day! (this will ultimately break when we move to a hierarchical directory structure that is predicated on using . in groupIds to set the structure - ala java packages)
Cheers,
Ben
Ben Walding wrote:
It was disabled again shortly after beta9, for that and a few other reasons.
Brett Porter wrote:
Sorry, I was too broad.
groupId is fine - you are right. It is artifactId with a '.' that is a problem.
Extension-Name is what is provided in the JAR manifest when generated. Its broken in a couple of places in -beta-9.
Cheers, Brett
Martin Skopp wrote:
On Mon, 2003-05-19 at 09:33, Brett Porter wrote:
Hi,
Due to the extension mechanism metadata in JARs, mm.mysql is an invalid artifact name.
Since this is the only offender, can this be renamed to mm-mysql on ibiblio and '.' made illegal in an artifactId/groupId?
Don't know this "extension mechanism" - what is it? I have "com.myname" here in my inhouse repo without problems.
From the docs I understand that the <groupId> is especially used to
specify such prefixes like "org.apache" or "com.sun" etc. So - the '.' should not be illegal?!?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
