[
https://issues.apache.org/jira/browse/HCATALOG-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531675#comment-13531675
]
Travis Crawford commented on HCATALOG-546:
------------------------------------------
Can you try patching this in and seeing if it fixes the jar issue you're seeing:
{code}
fynn-2:hcatalog-ro travis$ svn diff
Index: build-support/ant/build-common.xml
===================================================================
--- build-support/ant/build-common.xml (revision 1421620)
+++ build-support/ant/build-common.xml (working copy)
@@ -79,7 +79,11 @@
<_junit srcDir="${basedir}/src/test/java"/>
</target>
- <target name="jar" depends="mvn-dependencies,compile,mvn-init">
+ <target name="_check-jar" unless="jar.complete">
+ <available property="jar.complete" file="${build.dir}/.jar.complete"/>
+ </target>
+
+ <target name="jar" depends="_check-jar,mvn-dependencies,compile"
unless="jar.complete">
<echo message="${ant.project.name}"/>
<jar jarfile="${build.dir}/${jar.name}" basedir="${build.classes}">
<metainf dir="${path.to.basedir}"
includes="**/LICENSE.txt,**/NOTICE.txt"/>
@@ -88,6 +92,7 @@
<artifact:pom file="${pom.file}"/>
<artifact:localRepository path="${mvn.local.repo}"/>
</artifact:install>
+ <touch file="${build.dir}/.jar.complete"/>
</target>
<target name="findbugs" depends="init-findbugs,jar">
fynn-2:hcatalog-ro travis$
{code}
Looking through the build logs we see jars being installed into the local maven
repo multiple times during the build. They should be identical each time, but
still its not exactly prostyle.
If this doesn't solve your issue, can you send me the verbose output of what
fails?
> Rework HCatalog's JMS Notifications
> ------------------------------------
>
> Key: HCATALOG-546
> URL: https://issues.apache.org/jira/browse/HCATALOG-546
> Project: HCatalog
> Issue Type: Bug
> Components: notification
> Affects Versions: 0.4.1
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Fix For: 0.4.1
>
> Attachments: HCATALOG-546.branch4.patch, HCATALOG-546.trunk.patch,
> sample.Add.Drop.Database.json, sample.Add.Drop.Partition.json,
> sample.Add.Drop.Table.json
>
>
> In 0.4.1, the NotificationListener listens for metastore operations and emits
> JMS notifications containing the entire metastore-objects
> (Database/Table/Partitions) in Java-serialized form. The assumption at the
> time was that consumers might need access to the whole object. This policy
> poses a couple of problems:
> 1. The notifications are verbose, since it conveys a bunch of information
> that's available from querying the metastore anyway.
> 2. Consumers of these JMS notifications (e.g. Oozie) would now be dependent
> on the Java class definitions of metastore-objects. If they change, Oozie
> would also need to be restarted (with updated libs), to consume the
> notifications.
> Ideally, the notifications should convey only the minimum information that
> identifies the metastore-change unambiguously. (Everything else can be
> queried for.) They should be backward compatible. If new fields are added,
> existing consumers shouldn't break (unless they intend to consume the new
> fields). Also, the notification-format ought to be pluggable.
> For the initial rework, we're proposing to use a JSON-string to represent the
> notification-content. We're also proposing a helper-class for the likes of
> Oozie to use, that converts the strings to POJOs, in a backward-compatible
> fashion.
> I'll attach sample notifications and a tentative patch shortly.
--
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
