You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/02/01 04:26:06 UTC

[jira] Updated: (WSCOMMONS-148) Maven groupId different for maven1 and maven2

     [ https://issues.apache.org/jira/browse/WSCOMMONS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas updated WSCOMMONS-148:
---------------------------------------

    Assignee: Davanum Srinivas

> Maven groupId different for maven1 and maven2
> ---------------------------------------------
>
>                 Key: WSCOMMONS-148
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-148
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: Policy
>            Reporter: David Illsley
>         Assigned To: Davanum Srinivas
>
> The neethis project.xml defines the groupId as org.apache.neethi but pom.xml defines it as org.apache.ws.commons.neethi
> This is causing a problem because Sandesha2 depends on neethi by org.apache.ws.commons.neethi but there are no currently published snapshots (in maven1 repos) under that groupId
> The groupId should be the same in both builds to prevent confusion.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org