You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "David Primmer (JIRA)" <ji...@apache.org> on 2008/05/06 03:11:57 UTC

[jira] Created: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

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.


[jira] Commented: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "David Primmer (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594541#action_12594541 ] 

Cassie Doll commented on SHINDIG-235:
-------------------------------------

David - If people want to run the social code and gadgets code together it makes absolute sense to keep everything on the same version. Also, having abdera in the common dependency management section doesn't hurt anything. It only states which version should be used, and doesn't actually include it unless the sub pom says it needs it. 

Until we have an actual problem with wanting two separate versions I think all of the dependency management should be kept in one place - the parent pom. Having everything together keeps things simple... and its better to delay complicating things until we have an actual code-based reason for doing so. 

I will patch the first change now. 

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch, jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.


[jira] Updated: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "David Primmer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Primmer updated SHINDIG-235:
----------------------------------

    Attachment: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch

this one moves some deps to java/social-api

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch, jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.


[jira] Resolved: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "David Primmer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Primmer resolved SHINDIG-235.
-----------------------------------

    Resolution: Fixed

committed by cassie.

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch, jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.


[jira] Updated: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "David Primmer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Primmer updated SHINDIG-235:
----------------------------------

    Attachment: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch

this modifies the original root pom 

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.


[jira] Commented: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "David Primmer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594665#action_12594665 ] 

David Primmer commented on SHINDIG-235:
---------------------------------------

abdera client is for the functional tests that are coming in the next patch.

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch, jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.


[jira] Commented: (SHINDIG-235) update abdera to 0.5 snapshot and add client lib

Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SHINDIG-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594542#action_12594542 ] 

Cassie Doll commented on SHINDIG-235:
-------------------------------------

btw - what is the client dependency for?

> 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
>         Attachments: jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.deps_moved_from_root.patch, jira235_update_abdera_to_0.5_snapshot_and_add_client_lib.patch
>
>
> 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.