Does this also mean that when we use the maven deploy plugin, for the
legacy svn repo that JBAS uses, we will modifying the directory
structure for thirdparty jars?
Paul Gier wrote:
I was thinking of making the groupId "org.jboss.javaee"
Then each of the api modules would be under this groupId, and the
parent pom and combined jars would be under org/jboss/javaee/jboss-javaee
Is this directory structure too deep?
Carlo de Wolf wrote:
> Do you mean: groupId: org.jboss and artifactId: javaee?
> In that case, go. Else, huh?
>
> Carlo
>
> On Mon, 2007-08-20 at 09:47 -0500, Paul Gier wrote:
>> I'd like to change the maven groupId for the javaee project to
>> "org.jboss.javaee". Please let me know if this will cause problems
>> for anyone. I will be updating the microntainer dependencies, and
>> any others that I find. If you see any dependencies on javaee,
>> please update them to the new groupId, after I make the change.
>>
>> Thanks!
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Anil Saldhana
Project/Technical Lead,
JBoss Security & Identity Management
JBoss, A division of Red Hat Inc.
http://labs.jboss.com/portal/jbosssecurity/