[
https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916138#comment-16916138
]
Markus Schuch commented on CONNECTORS-1105:
-------------------------------------------
I think it should be sufficient to add the {{mvn deploy -P apache-mcf-release}}
to the release.bat/.sh script.
The {{create-/update-release-branch.py}} scripts already remove the
{{-SNAPSHOT}} version prefix from the maven POMs.
The {{mvn release:prepare/release:perform}} goals are not suitable, because
they come with their own tagging/checkout process, which cannot be disabled
because it is its central idea of how it works.
Required settings in the local {{~/.m2/settings.xml}}:
{code:java}
<settings>
...
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username> <!-- YOUR APACHE LDAP USERNAME --> </username>
<password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username> <!-- YOUR APACHE LDAP USERNAME --> </username>
<password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
</server>
<server>
<!-- The name of the gpg key to sign the artifacts with -->
<id>your.keyname</id>
<passphrase>passphrase of your gpg key (encrypted)</passphrase>
</server>
...
</servers>
<profiles>
<profile>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<!-- The name of the gpg key to sign the artifacts with -->
<gpg.keyname>your.keyname</gpg.keyname>
</properties>
</profile>
<profiles>
</settings> {code}
After the maven deploy process finished, the deployed artifacts are located in
a temporary staging repository.
See [http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage] how
to promote the artifacts to central or drop them, if something is wrong with
them.
I think we can automate this last step in a later iteration by using the
{{nexus-staging-maven-plugin}}. Refer to
[https://central.sonatype.org/pages/apache-maven.html#nexus-staging-maven-plugin-for-deployment-and-release]
for more details.
Am i missing something?
> Add maven delivery targets to poms
> ----------------------------------
>
> Key: CONNECTORS-1105
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1105
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Build
> Affects Versions: ManifoldCF 1.8
> Reporter: Karl Wright
> Assignee: Markus Schuch
> Priority: Major
> Fix For: ManifoldCF next
>
>
> We've been asked to deliver mcf jars and wars to maven central repository by
> some developers. This ticket represents that work.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
