Replace org.mnode.ical4j:ical4j-vcard:0.9.6a-BW-SNAPSHOT with release

[nblair]

Just like the scenario with bw-ical4j-cl, we need a release of the following dependency:

<dependency>
        <groupId>org.mnode.ical4j</groupId>
        <artifactId>ical4j-vcard</artifactId>
        <version>0.9.6a-BW-SNAPSHOT</version>
</dependency>

@douglm can you produce the source for this dependency? We'll need either to get the changes merged into the upstream project, or we'll have to fork it. If forking, would importing the fork as a module of bw-util be sensible? It would prevent the need for the separate release cycle.

This issue blocks #1.

[douglm]

This is sort of the same as the other ical4j.

It's already out on github as

https://github.com/Bedework/bw-ical4j-vcard

I'm hoping to keep this visible as a separate project.

Will you be able to gve me some of the details on how this this whole
release thing is put together so that I can be more useful?

Would a call help.

I think I understand some of the process here but it's some of the
details I'm lacking

On 10/17/15 22:36, Nicholas Blair wrote:

Just like the scenario with bw-ical4j-cl, we need a release of the
following dependency:

| org.mnode.ical4j
ical4j-vcard
0.9.6a-BW-SNAPSHOT |

@douglm https://github.com/douglm can you produce the source for this
dependency? We'll need either to get the changes merged into the
upstream project, or we'll have to fork it. If forking, would importing
the fork as a module of bw-util be sensible? It would prevent the need
for the separate release cycle.

This issue blocks #1 #1.

—
Reply to this email directly or view it on GitHub
#2.

[nblair]

Now that we've got the example with bw-ical4j-cl, I think in order to help you get the details you'll submit the pull requests and I'll be the happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only activated when the maven-release-plugin is running (see https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots and staging repositories.

(The details of the above are laid out here: http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been merged, you'll need permissions to execute the release.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

You'll also need a GPG key on your workstation that's distributed, they have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and I'll PR a section to the README.

[douglm]

Ok - I'll give this a go with the vcard stuff.

I am on a mac and it does appear that almost everything to do with
development is tricky

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

—
Reply to this email directly or view it on GitHub
#2 (comment).

[douglm]

In the end i created a pull request on github.

I was trying to do it in intellij and it all seemed rather confusing

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

—
Reply to this email directly or view it on GitHub
#2 (comment).

[douglm]

inline

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

Not merged I guess but correct

If you don't have an account with Sonatype, start here:

I do - it's douglm

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

Available:

https://sks-keyservers.net/pks/lookup?op=vindex&search=mikeadouglass%40gmail.com

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

I happen to have gpg2 installed - tested end to end encryption with an
icloud guy

So I have gpg keychain as well - I even have a ketpair generated

—
Reply to this email directly or view it on GitHub
#2 (comment).

[douglm]

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

I notice you tagged ical4j. Should I add tags to ical4j-vcard or does it
not matter much.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

Do I create a ticket asking for access?

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

So I read through their stuff. It appears I need to amend my profile to
include all sort of stuff like the pass-phrase. Isn't that somewhat
insecure?

—
Reply to this email directly or view it on GitHub
#2 (comment).

[nblair]

1. I did not tag; the maven release plugin creates the tag.
2. Yes, you need to create a ticket asking for access. You can mention me
   (@nblair) as they'll ask for someone else with access to attest.
3. There are a couple of ways to configure gpg2 and Maven to work together
   during the release. Yes, one option allows you to configure maven to know
   your pass-phrase, it will only exist in your ~/.m2/settings.xml (not in the
   project). You don't have to do it that way, if you can figure out how to
   get the gpg-agent working properly, and interact with the agent to cache
   your pass phrase BEFORE you run the maven release:prepare goal.

On Wed, Oct 21, 2015 at 10:13 PM Mike Douglass notifications@github.com
wrote:

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  <
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33
  ).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

I notice you tagged ical4j. Should I add tags to ical4j-vcard or does it
not matter much.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

Do I create a ticket asking for access?

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

So I read through their stuff. It appears I need to amend my profile to
include all sort of stuff like the pass-phrase. Isn't that somewhat
insecure?

—
Reply to this email directly or view it on GitHub
#2 (comment).

—
Reply to this email directly or view it on GitHub
#2 (comment).

[douglm]

So I now appear to have the appropriate permissions and I've set my
settings.xml according to their instructions.

Do I just follow the instructions here?

http://central.sonatype.org/pages/apache-maven.html#performing-a-release-deployment

On 10/18/15 21:28, Nicholas Blair wrote:

Now that we've got the example with bw-ical4j-cl, I think in order to
help you get the details you'll submit the pull requests and I'll be the
happy reviewer.

The pom.xml for bw-ical4j-cl has the primary requirements:

• An accurate scm block.
• A non-empty license and developers block.
• source, javadoc, and gpg plugins - tucked in a profile that's only
  activated when the maven-release-plugin is running (see
  Bedework/bw-ical4j-cl@01dafe1
  https://github.com/Bedework/bw-ical4j-cl/commit/01dafe1b38e7ca8d6c74d17ecae105d318b2ae33).
• A distributionManagement block that points to Sonatype's snapshots
  and staging repositories.

(The details of the above are laid out here:
http://central.sonatype.org/pages/apache-maven.html).

Once you've got the Maven bits in the right spots, and they've been
merged, you'll need permissions to execute the release.

If you don't have an account with Sonatype, start here:

https://issues.sonatype.org/secure/Signup!default.jspa

Here's an example of what to ask for:

https://issues.sonatype.org/browse/OSSRH-16401

You'll also need a GPG key on your workstation that's distributed, they
have help for you here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

If you are on a Mac this can be a bit tricky, let me know if you are and
I'll PR a section to the README.

—
Reply to this email directly or view it on GitHub
#2 (comment).