maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Hardy <>
Subject Re: [m2] repository changes
Date Sun, 13 Nov 2005 18:14:19 GMT
How come host names are part of the standard naming mechanism?

When I posted issues in jira for poms for JAXB jars, I was under the 
definite impression that it was package names only.

Therefore the JAXB poms in javax/xml contain dependencies such as:

org/relaxng/relaxngDatatype, at relaxngdatatype/relaxngdatatype
javax/xml/xsdlib, at xsdlib/xsdlib
javax/xml/namespace, whereabouts unknown

So which is right? Surely using hostnames can only be a temporary 
solution to be phased out?


Carlos Sanchez on 11/11/05 20:30, wrote:
> The policy is to use package names (or host names) as groupIds, that
> hasn't changed. I don't remember having put things inside org.jboss,
> they're still inside jboss.
> There's a bug about the latter:
> On 11/11/05, Adam Hardy <> wrote:
>>Adam Hardy on 11/11/05 19:42, wrote:
>>>I just upgraded from m2-beta-2 to 2.0 and had a few problems with my
>>>dependencies' groupIds.
>>>I moved my old beta local repository out of the way and let mvn create a
>>>new one.
>>having problems with servlet-api-2.4 as well. I can see it on ibiblio
>>but maven won't touch it or give me a warning or anything, and hence I
>>get a compile error because all javac sees is the 2.3 version. Here's my
>>dependency xml:
>>     <dependency>
>>       <groupId>javax.servlet</groupId>
>>       <artifactId>servlet-api</artifactId>
>>       <version>2.4</version>
>>       <scope>provided</scope>
>>     </dependency>
>>and here's what has ended up on my repo:
>>What should I be doing here?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message