[jira] [Commented] (ZOOKEEPER-1963) Make JDK 7 the minimum requirement for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248899#comment-14248899 ] Giridharan Kesavan commented on ZOOKEEPER-1963: --- [~phunt] configured both the jobs to use idk-1.7 from: /home/jenkins/tools/java/jdk1.7.0-64 and also remove the use of nightly repo. > Make JDK 7 the minimum requirement for Zookeeper > > > Key: ZOOKEEPER-1963 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1963 > Project: ZooKeeper > Issue Type: Improvement > Components: build >Affects Versions: 3.5.0 >Reporter: Edward Carter >Assignee: Hongchao Deng > Fix For: 3.5.1 > > Attachments: ZOOKEEPER-1963-v2.patch, ZOOKEEPER-1963.patch > > > JDK 6 stopped receiving public updates in early 2013: > http://www.oracle.com/technetwork/java/eol-135779.html > I propose making JDK 7 the minimum for Zookeeper going forward. One patch > that I've personally submitted already would have been a good fit for Java > 7's try-with-resources statement, and another pending patch fails to build on > versions of Java prior to 7 because a unit test in it uses > InetAddress.getLoopbackAddress(), which would be awkward to replace. I'm > sure there are many other examples. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1402) Upload Zookeeper package to Maven Central
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951130#comment-13951130 ] Giridharan Kesavan commented on ZOOKEEPER-1402: --- [~phunt] Some how I missed this jira. the moment we publish artifact to the Apache Nexus reop, and promoted to release, there is an an automatic sync which take care of pushing release artifacts from Apache Nexus to Maven Central. There is not much that we have to do, except following some pom guidelines. Here are some helpful links: https://maven.apache.org/guides/mini/guide-central-repository-upload.html https://docs.sonatype.org/display/Repository/Central+Sync+Requirements > Upload Zookeeper package to Maven Central > - > > Key: ZOOKEEPER-1402 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1402 > Project: ZooKeeper > Issue Type: Improvement >Affects Versions: 3.3.4 >Reporter: Igor Lazebny >Assignee: Flavio Junqueira >Priority: Minor > Fix For: 3.4.7 > > > It would be great to make Zookeeper package available in Maven Central as > other Apache projects do (Camel, CXF, ActiveMQ, Karaf, etc). > That would simplify usage of this package in maven builds. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-1430:
--
Attachment: ZOOKEEPER-1430-3.5.0-v6.patch
ZOOKEEPER-1430-3.4.6-v6.patch
[~phunt] ${final.name} is nothing but ${name}-${version} and by convention
maven projects doesn't have pom file that are versioned. When publishing the
pom.xml file maven by itself will figureout the version of the pom file and
publish it.
To answer your second question about multiple pom's. it's not b'coz of the pom
name, it's bcoz the way the ant macro def call's the individual publish task.
it consider's every deploy call as separate module and publishes the same pom
file with different build number.
With this v6 patch I have made it a single call and all the artifacts will be
published at one go.
I have tested the patch for clean package, mvn-deploy, and mvn-deploy the
staging as well.
> add maven deploy support to the build
> -
>
> Key: ZOOKEEPER-1430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430
> Project: ZooKeeper
> Issue Type: Task
> Components: build
>Affects Versions: 3.4.4, 3.5.0
>Reporter: Patrick Hunt
>Assignee: Giridharan Kesavan
>Priority: Blocker
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1430-3.4.6-v4.patch,
> ZOOKEEPER-1430-3.4.6-v5.patch, ZOOKEEPER-1430-3.4.6-v6.patch,
> ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430-3.5.0-v4.patch,
> ZOOKEEPER-1430-3.5.0-v5.patch, ZOOKEEPER-1430-3.5.0-v6.patch,
> ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH, ZOOKEEPER-1430-V3.patch,
> ZOOKEEPER-1430-br34-V3.patch, ZOOKEEPER-1430.patch, ZOOKEEPER-1430.patch
>
>
> Infra is phasing out the current mechanism we use to deploy maven artifacts.
> We need to move to repository.apache.org (nexus).
> In particular we need to ensure the following artifacts get published:
> * zookeeper-3.x.y.jar
> * zookeeper-3.x.y-sources.jar
> * zookeeper-3.x.y-tests.jar
> * zookeeper-3.x.y-javadoc.jar
> In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream
> users, such as Hadoop.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-1430: -- Attachment: ZOOKEEPER-1430-3.5.0-v5.patch ZOOKEEPER-1430-3.4.6-v5.patch v5 patch puts back the checksums in place > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.6-v4.patch, > ZOOKEEPER-1430-3.4.6-v5.patch, ZOOKEEPER-1430-3.4.patch, > ZOOKEEPER-1430-3.5.0-v4.patch, ZOOKEEPER-1430-3.5.0-v5.patch, > ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH, ZOOKEEPER-1430-V3.patch, > ZOOKEEPER-1430-br34-V3.patch, ZOOKEEPER-1430.patch, ZOOKEEPER-1430.patch > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819818#comment-13819818 ] Giridharan Kesavan commented on ZOOKEEPER-1430: --- [~phunt] checksums both md5 and sha1 are generated by maven when it publishes to nexus repo. for ex: pls take a look at this url: https://repository.apache.org/content/groups/snapshots/org/apache/zookeeper/zookeeper/3.5.0-SNAPSHOT/ > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.6-v4.patch, ZOOKEEPER-1430-3.4.patch, > ZOOKEEPER-1430-3.5.0-v4.patch, ZOOKEEPER-1430-V1.PATCH, > ZOOKEEPER-1430-V2.PATCH, ZOOKEEPER-1430-V3.patch, > ZOOKEEPER-1430-br34-V3.patch, ZOOKEEPER-1430.patch, ZOOKEEPER-1430.patch > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-1430: -- Attachment: ZOOKEEPER-1430-3.4.6-v4.patch ZOOKEEPER-1430-3.5.0-v4.patch I have uploaded a patch for both 3.4.6 and 3.5.0 with snapshot version numbers and also fixed a typo. this patch uploads 4 jars artifacts for the same pom. zookeeper main jar zookeeper test classifier jar zookeeper source classifier jar zookeeper javadoc classifier jar. This are the jar's that matters. Other's that I see in the link above are the asc's asc and md5 checksum's asc and those are not useful. Please let me know if I'm missing something. > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.6-v4.patch, ZOOKEEPER-1430-3.4.patch, > ZOOKEEPER-1430-3.5.0-v4.patch, ZOOKEEPER-1430-V1.PATCH, > ZOOKEEPER-1430-V2.PATCH, ZOOKEEPER-1430-V3.patch, > ZOOKEEPER-1430-br34-V3.patch, ZOOKEEPER-1430.patch, ZOOKEEPER-1430.patch > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-1430:
--
Attachment: ZOOKEEPER-1430-V3.patch
this v3 patch user gpg profile to get the gpg.passphrase for signing the
artifact when uploading to staging.
Details below:
ant mvn-deploy
- this deploys the snapshot artifact to the nexus snapshot repository
- expects jar files has -SNAPSHOT suffix present in it.
ant mvn-deploy -Dstaging=true
- Essentially this is done when an Release Candidate is pushed.
- This target deploy's release versioned artifact to the nexus staging
profile
- For staging the artifacts, staging repo requires the artifacts be signed
using gpg keys.
- To sign the artifact using gpg keys , one has to provide the gpg
passphrase in plain text in the ~/.m2/settings.xml
If one is worried about leaving plain text password, they can refer to
http://maven.apache.org/guides/mini/guide-encryption.html for encrypting the
passphrase.
Here is the ~/.m2/settings.xml that I used for testing the targets above.
{code:xml}
apache.snapshots.https
XXX
apache.staging.https
XXX
XXX
gpg
XXX
{code}
> add maven deploy support to the build
> -
>
> Key: ZOOKEEPER-1430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430
> Project: ZooKeeper
> Issue Type: Task
> Components: build
>Affects Versions: 3.4.4, 3.5.0
>Reporter: Patrick Hunt
>Assignee: Giridharan Kesavan
>Priority: Blocker
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch,
> ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH,
> ZOOKEEPER-1430-V3.patch
>
>
> Infra is phasing out the current mechanism we use to deploy maven artifacts.
> We need to move to repository.apache.org (nexus).
> In particular we need to ensure the following artifacts get published:
> * zookeeper-3.x.y.jar
> * zookeeper-3.x.y-sources.jar
> * zookeeper-3.x.y-tests.jar
> * zookeeper-3.x.y-javadoc.jar
> In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream
> users, such as Hadoop.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801227#comment-13801227 ] Giridharan Kesavan commented on ZOOKEEPER-1430: --- I'm on it. > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Affects Versions: 3.4.4, 3.5.0 >Reporter: Patrick Hunt >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch, > ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785708#comment-13785708 ] Giridharan Kesavan commented on ZOOKEEPER-1430: --- [~phunt] I have figured a much better way of dealing with the gpg password using mvn settings.xml. Let me get back to you in a day or two with that patch, this would simplify on how we publish artifacts to nexus. > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Blocker > Fix For: 3.4.6, 3.5.0 > > Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch, > ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). > In particular we need to ensure the following artifacts get published: > * zookeeper-3.x.y.jar > * zookeeper-3.x.y-sources.jar > * zookeeper-3.x.y-tests.jar > * zookeeper-3.x.y-javadoc.jar > In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream > users, such as Hadoop. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-1430: -- Attachment: ZOOKEEPER-1430-V2.PATCH remove the duplicate checksum's > add maven deploy support to the build > - > > Key: ZOOKEEPER-1430 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430 > Project: ZooKeeper > Issue Type: Task > Components: build >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch, > ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH > > > Infra is phasing out the current mechanism we use to deploy maven artifacts. > We need to move to repository.apache.org (nexus). -- 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
[jira] [Updated] (ZOOKEEPER-1430) add maven deploy support to the build
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-1430:
--
Attachment: ZOOKEEPER-1430-V1.PATCH
Patrick,
This v1 patch uses maven-ant-task to publish artifacts to snapshot/staging repo
based on the args.
{noformat}
ant mvn-deploy -Dstaging=true
{noformat}
upload artifact's to the apache nexus stating repo. with gpg signing, it would
ask you for your gpg key password to sign the artifact.
{noformat}
ant mvn-deploy
{noformat}
this would upload artifact's to the apache snapshot repo. without signing.
> add maven deploy support to the build
> -
>
> Key: ZOOKEEPER-1430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430
> Project: ZooKeeper
> Issue Type: Task
> Components: build
>Reporter: Patrick Hunt
>Assignee: Patrick Hunt
> Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch,
> ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH
>
>
> Infra is phasing out the current mechanism we use to deploy maven artifacts.
> We need to move to repository.apache.org (nexus).
--
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
[jira] [Updated] (ZOOKEEPER-1187) remove jdk dependency from the rpm spec
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-1187: -- Attachment: zk-1187.patch > remove jdk dependency from the rpm spec > --- > > Key: ZOOKEEPER-1187 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1187 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: zk-1187.patch > > > remove jdk dependency from the rpm spec -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ZOOKEEPER-1187) remove jdk dependency from the rpm spec
remove jdk dependency from the rpm spec --- Key: ZOOKEEPER-1187 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1187 Project: ZooKeeper Issue Type: Improvement Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan remove jdk dependency from the rpm spec -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-999) Create an package integration project
[ https://issues.apache.org/jira/browse/ZOOKEEPER-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054262#comment-13054262 ] Giridharan Kesavan commented on ZOOKEEPER-999: -- hadoop build servers are running ubuntu-9.04 which is really old; ATM Im unable to update or install any package with this version of ubuntu. I had to upgrade the os version to add install any package. Im working on it.. > Create an package integration project > - > > Key: ZOOKEEPER-999 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-999 > Project: ZooKeeper > Issue Type: New Feature > Components: build > Environment: Java 6, RHEL/Ubuntu >Reporter: Eric Yang >Assignee: Eric Yang > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-999-1.patch, ZOOKEEPER-999-2.patch, > ZOOKEEPER-999-3.patch, ZOOKEEPER-999.patch > > > This goal of this ticket is to generate a set of RPM/debian package which > integrate well with RPM sets created by HADOOP-6255. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
