[ 
https://issues.apache.org/jira/browse/OLINGO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774523#comment-13774523
 ] 

Stephan Klevenz commented on OLINGO-22:
---------------------------------------

This should be fixed before release. 

Suggestion:

groupID    = org.apache.olingo
artifactId = olingo.odata2.*

Consequence: all documentation and samples must adapt to these changes.

                
> Issue with groupId and artifactId
> ---------------------------------
>
>                 Key: OLINGO-22
>                 URL: https://issues.apache.org/jira/browse/OLINGO-22
>             Project: Olingo
>          Issue Type: Bug
>            Reporter: Stephan Klevenz
>            Assignee: Stephan Klevenz
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> The current artifact naming scheme is: {groupId}-{artifactId}-{version}.{ext}
> e.g.: org.apache.olingo.odata2-core-1.0.0-SNAPSHOT.jar
> Unfortunately Maven does not make use of the groupId when artifacts synced 
> from Nexus repository. Artifacts looking like this:
> api-1.0.0-SNAPSHOT.jar
> core-1.0.0-SNAPSHOT.jar
> If projects include these dependencies then it doesn't look nice nor is it 
> unique.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to