Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Creating a local ivy repository is straight forward, maven is not required. Here's an example of publishing some text files using ivy as a standalone program. </p> <p>I have 3 files I want to publish:</p> <pre><code>src/English.txt src/Spanish.txt src/Irish.txt </code></pre> <p>The ivy file <em>src/ivy.xml</em> details the name of the module and a list of the artifacts being published. (Release index)</p> <pre><code>&lt;ivy-module version="2.0"&gt; &lt;info organisation="myorg" module="hello"/&gt; &lt;publications&gt; &lt;artifact name="English" ext="txt" type="doc"/&gt; &lt;artifact name="Irish" ext="txt" type="doc"/&gt; &lt;artifact name="Spanish" ext="txt" type="doc"/&gt; &lt;/publications&gt; &lt;/ivy-module&gt; </code></pre> <p>You'll also need an ivy settings file to tell ivy where the repository is located</p> <pre><code>&lt;ivysettings&gt; &lt;property name="repo.dir" value=".../repo"/&gt; &lt;settings defaultResolver="internal"/&gt; &lt;resolvers&gt; &lt;filesystem name="internal"&gt; &lt;ivy pattern="${repo.dir}/[module]/ivy-[revision].xml" /&gt; &lt;artifact pattern="${repo.dir}/[module]/[artifact]-[revision].[ext]" /&gt; &lt;/filesystem&gt; &lt;/resolvers&gt; &lt;/ivysettings&gt; </code></pre> <p>Finally run ivy to publish the released version 1.0:</p> <pre><code>java -jar $IVY -settings config/ivysettings.xml \ -ivy src/ivy.xml \ -publish internal \ -publishpattern "src/[artifact].[ext]" \ -revision 1.0 \ -status release \ -overwrite </code></pre> <p>Note the publish pattern. It tells ivy where the files to be published are located. </p> <h2>Added: Publishing from within ANT</h2> <pre><code>&lt;target name="publish" depends="clean,package" description="Publish this build into repository"&gt; &lt;ivy:publish pubrevision="${pub.version}" status="${pub.status}" resolver="${pub.resolver}" &gt; &lt;artifacts pattern="${build.dir}/dist/[artifact].[ext]"/&gt; &lt;/ivy:publish&gt; &lt;/target&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POgood ivy tutorial for local repository?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMark O'Connor
    1. USMark O'Connor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POgood ivy tutorial for local repository?
      singulars
      1. PTQuestion
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONice answer! Do you know where we can get the same 'publish' information in an Ant task? The "official" documentation of the tasks is confusing.
      singulars
      1. PO
      1. USRalph
    2. COYes, I use the ivy publish task all the time, publishing to my Nexus Maven repository. What's missing really on the ivy site is more example documentation. I find it's fine for reference once you've figured out how ivy works :-(
      singulars
      1. PO
      1. USMark O'Connor
    3. CODon't say it is easy, because it is not. If it would be easy, I would have found out myself how to do it.
      singulars
      1. PO
      1. USArne
 

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