[
https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594437#action_12594437
]
David Primmer commented on SHINDIG-235:
---------------------------------------
This brings up the issue that has been mystifying me about the recent move of
dependency info into the dependencyManagment area of the root pom.xml. I don't
understand why something like Abdera would be specified here, when there is
little chance another subproject would use it and even less chance that they'd
want exactly the same version. This is not junit or jetty something like that
where a common place to rev the version would be nice.
So, Is it up to the devs working on the code to determine where their
dependencies should go or some other dependency czar? If it's up to devs, and
speaking for social-api, I'd like abdera moved exclusively into the social-api
pom as it was before. Can I get some feedback here?
> update abdera to 0.5 snapshot and add client lib
> ------------------------------------------------
>
> Key: SHINDIG-235
> URL: https://issues.apache.org/jira/browse/SHINDIG-235
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: David Primmer
>
> upcoming code submits will depend on some bugfixes to abdera and so we'll be
> switching from a 0.4 release candidate snapshot to 0.5 snapshot. update the
> versions in the root pom.xml and add dependencies to
> index/java/social-api/pom.xml for abdera client. 0.5 can be pushed easily and
> we should be safe tracking head.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
