Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For the war path, you can use built in Maven properties:</p> <pre><code>${project.build.directory}/${project.build.finalName}.${project.packaging} </code></pre> <p>You want to set the deployment path as a custom Maven property. There are a few ways to do this. One is setting it directly in the pom, like this:</p> <pre><code>&lt;properties&gt; &lt;deploy.path&gt;C:/Softwares/apache-tomcat-6.0.33/webapps/Test.war&lt;/deploy.path&gt; &lt;/properties&gt; </code></pre> <p>However, this is still hard coding the path in the pom, just in a variable. </p> <p>Another way is to use the <a href="http://mojo.codehaus.org/properties-maven-plugin/plugin-info.html" rel="nofollow">properties-maven-plugin</a> to read in a properties file. This keeps user specific settings out of the pom, and you can keep your properties file out of source control. However, this is not the preferred Maven way of doing things, and this plugin may no longer be supported in future versions.</p> <p>The Maven way to do this is to store your deploy path in your ~/.m2/settings.xml file. This property would go in a profile, which can be active by default. See <a href="http://maven.apache.org/examples/injecting-properties-via-settings.html" rel="nofollow">this page</a> for an explanation.</p> <p>Once you have your deploy.path variable set, change your copy statement to look like this:</p> <pre><code>&lt;copy file="${project.build.directory}/${project.build.finalName}.${project.packaging}" tofile="${deploy.path}" /&gt; </code></pre> <p>Edit:</p> <p>On a minimal example project, the following properties are all set for me:</p> <pre><code> &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt; &lt;version&gt;1.7&lt;/version&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;compile&lt;/id&gt; &lt;phase&gt;compile&lt;/phase&gt; &lt;configuration&gt; &lt;target&gt; &lt;echo message="project.build.directory: ${project.build.directory}"/&gt; &lt;echo message="project.build.finalName: ${project.build.finalName}"/&gt; &lt;echo message="project.packaging: ${project.packaging}"/&gt; &lt;/target&gt; &lt;/configuration&gt; &lt;goals&gt; &lt;goal&gt;run&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; </code></pre> <p>If those properties aren't set for you, can you post your pom.xml?</p>
    singulars
    1. This table or related slice is empty.
    1. POMaven : Specfying directory paths to pick the file and deploy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USShane
    1. USShane
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMaven : Specfying directory paths to pick the file and deploy
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Shane , as mentioned i will use deploy.path for target directory , how can we specify the source directory ?? because if i echo project.build.directory its null , so is there any property for specifying source directory also ??
      singulars
      1. PO
      1. USPawan
    2. COproject.build.directory, project.build.finalName, project.packaging and various other properties should automatically be defined. See http://www.sonatype.com/books/mvnref-book/reference/resource-filtering-sect-properties.html for a complete list. See my edit above for troubleshooting...
      singulars
      1. PO
      1. USShane
    3. COI have found the answer for my question in comments (We should use source.path ) . Thanks Shane for giving me the starting point .
      singulars
      1. PO
      1. USPawan
 

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