You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/17 18:36:52 UTC
[jira] [Issue Comment Edited] (GORA-43) Forward port 0.1.1
incubating Maven poms to trunk
[ https://issues.apache.org/jira/browse/GORA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152155#comment-13152155 ]
Lewis John McGibbney edited comment on GORA-43 at 11/17/11 5:36 PM:
--------------------------------------------------------------------
A couple of things here.
1) Withe regards to gora-sql tests we have no reference to an internal dependency for this nested under the <dependencyManagement> parent. Is it possible to add something like
{code}
<dependency>
<groupId>org.apache.gora</groupId>
<artifactId>gora-sql</artifactId>
<version>${project.version}</version>
<classifier>tests</classifier>
</dependency>
{code}
2) This is (part of) where we need to edit the location for the upgrade to for the cassandra.version, cassandra.thrift.version & hector.version. This obviously needs to be addressed in a separate issue but it is worth noting here as this issue therefore should block GORA-58 as well as GORA-22 (which we really need to get sorted out).
3) Does the stuff in
{code}
<build>
<testSourceDirectory>${basedir}/src/test/java</testSourceDirectory>
<sourceDirectory>${basedir}/src/main/java</sourceDirectory>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
...
</build>
{code}
need to be updated as well or is this fine as-is?
4) As far as I can see it is mainly stuff in
{code}
<properties>
<osgi.version>4.2.0</osgi.version>
<!-- Hadoop Dependencies -->
<hadoop.version>0.20.2</hadoop.version>
...
{code}
that needs to be updated? Can anyone clarify/confirm?
I understand you are up to your teeth just now Chris, but if you could provide insight into what needs to be addressed above, then I will get right on this. Thanks
was (Author: lewismc):
A couple of things here.
1) Withe regards to gora-sql tests we have no reference to an internal dependency for this nested under the <dependencyManagement> parent. Is it possible to add something like
{code}
<dependency>
<groupId>org.apache.gora</groupId>
<artifactId>gora-sql</artifactId>
<version>${project.version}</version>
<classifier>tests</classifier>
</dependency>
{code}
2) This is (part of) where we need to edit the location for the upgrade to for the cassandra.version, cassandra.thrift.version & hector.version. This obviously needs to be addressed in a separate issue but it is worth noting here as this issue therefore should block GORA-58 as well as GORA-22 (which we really need to get sorted out).
3) Does the stuff in
{code}
<build>
<testSourceDirectory>${basedir}/src/test/java</testSourceDirectory>
<sourceDirectory>${basedir}/src/main/java</sourceDirectory>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
...
</build>
need to be updated as well or is this fine as-is?
4) As far as I can see it is mainly stuff in
{code}
<properties>
<osgi.version>4.2.0</osgi.version>
<!-- Hadoop Dependencies -->
<hadoop.version>0.20.2</hadoop.version>
...
{code}
that needs to be updated? Can anyone clarify/confirm?
I understand you are up to your teeth just now Chris, but if you could provide insight into what needs to be addressed above, then I will get right on this. Thanks
> 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
>
>
> 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