Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Recently, a m2release plugin came to my attention. Seemed nice. Althought, I would have liked my release process to be completely «pom-tweaking-free». What I mean by that is that we have to provide 4 input parameter to process a complete release:</p> <ol> <li>the release version (ex. 1.0.0)</li> <li>the new development version (ex. 1.0.1-SNAPSHOT)</li> <li>the release tag in SCM (ex. release-1.0.0 or 1.0.0)</li> <li>the tag base path in SCM </li> </ol> <p>The first 2 have acceptable defaults. The version bumping at the bug-fix version digit is perfectly fine for me.</p> <p>Number 4 can be specified in the pom. It won't change.</p> <pre><code>&lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-release-plugin&lt;/artifactId&gt; &lt;configuration&gt; &lt;tagBase&gt;https://example.com/svn/myProject/releases&lt;/tagBase&gt; &lt;/configuration&gt; &lt;/plugin&gt; </code></pre> <p>It's the third one that prevent me from a complete automation of a release at the push of a button. The default release tag label won't do it for us so we have to specify it:</p> <pre><code>&lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-release-plugin&lt;/artifactId&gt; &lt;configuration&gt; &lt;tag&gt;release-${pom.version}&lt;/tag&gt; &lt;tagBase&gt;https://example.com/svn/myProject/releases&lt;/tagBase&gt; &lt;/configuration&gt; &lt;/plugin&gt; </code></pre> <p>Now, while this might be just what I needed, I end up having a svn tag with the -SNAPSHOT at the end. :( So I have to pass the tag parameter in the Hudson job configuration. Furthermore, I have to go change it for each release we make ... which is not exactly what I need.</p> <hr> <p>So, in the end, having a maven2 type project in hudson + the m2release hudson plugin + the maven release plugin correctly configured is the Mother of all the release process I've seen so far. While not perfect, it saved me a lot tiedous work.</p> <p>JS.</p>
    singulars
    1. This table or related slice is empty.
    1. POMaven release via Hudson
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJS Bournival
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe current version of the maven-release-plugin (2.2.1) has a new feature that solves your issue #3. Check out the section 'Overriding the default tag name format' here: http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html
      singulars
      1. PO
      1. USMatthew Jaskula
    2. COIn your pom.xml it is more correct to specify `<tag>release-@{project.version}</tag>`, otherwise it is replaced by SNAPSHOT version my Maven.
      singulars
      1. PO
      1. USdma_k
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload