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

Hudson commented on GORA-43:
----------------------------

Integrated in gora-trunk #49 (See 
[https://builds.apache.org/job/gora-trunk/49/])
    Commit to address GORA-43 and update to changes.txt. Thanks Chris for the 
direction.

lewismc : 
http://svn.apache.org/viewvc/incubator/gora/trunk/viewvc/?view=rev&root=&revision=1205346
Files : 
* /incubator/gora/trunk/CHANGES.txt
* /incubator/gora/trunk/pom.xml

                
> Forward port 0.1.1 incubating Maven poms to trunk
> -------------------------------------------------
>
>                 Key: GORA-43
>                 URL: https://issues.apache.org/jira/browse/GORA-43
>             Project: Gora
>          Issue Type: Improvement
>          Components: build process
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.2-incubating
>
>         Attachments: GORA-43-v2.patch, GORA-43-v3.patch, GORA-43.patch
>
>
> I improved the Maven poms in 0.1.1-incubating, and trimmed them down to a 
> publishable set of dependencies.
> My improvements:
> 1. reduce the redundancy in the deps section by not repeating deps in each 
> sub-project.
> 2. use explicit dependency and module version #s which are required to not 
> have "moving target" dependencies in the downstream applications and that 
> allow each individual gora-* module to be included on its own (without having 
> to include gora-core). 
> I'd like to forward port these to trunk and then update per trunk's 
> dependencies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to