Databases
StackOverflow2013
Postsdbo
POCan you refactor Maven pom.xml files into reusable XML fragments?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan you refactor Maven pom.xml files into reusable XML fragments?
    primarykey
    data
    text
    <p>In Maven, is it possible to refactor commonly repeated fragments into a reusable "library" (plugin)? I realize that I can write my own plugins, but often the functionality I want to re-use is already expressed as fragments in a pom.xml, and my natural inclination is that the mechanism of re-use should preserve those fragments <em>as</em> XML.</p> <p><strong>Case in point</strong> I've been using a procedure (<a href="http://wikis.sun.com/display/Jersey/HowToConfigureExtendedWADL" rel="noreferrer">partly described here</a>) for generating a WADL file from Jersey/JAX-RS source code, and then generating developer documentation from that WADL and the source-code's own Javadoc. The procedure on that page describes the execution of two plugins, and I am using a third plugin (org.codehaus.mojo:exec-xsltproc) and my own XSL file to turn the WADL into HTML.</p> <p>I've used this procedure in several Maven projects. The boilerplate comes in at <a href="http://pastie.org/1880764" rel="noreferrer">100 lines of XML</a>. What changes between projects is simply the package name of the source code in question (<code>com.example.myapp.rest</code> in the linked boilerplate). Therefore it is not possible to move this into a parent pom, or any other mechanism that does not allow parametrization.</p> <p><strong>What I want</strong> is to aggregate, template-out, or otherwise refactor those 100 lines (and one XST file) into a common location. I realize that re-usable maven executions are delivered via Maven plugins. Ideally I wouldn't have to write any Java (or Groovy) just to re-express what I have already expressed in XML.</p> <p><strong>Is it possible to refactor Maven pom.xml files <em>as</em> XML?</strong></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMatt Quail
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCan you refactor Maven pom.xml files into reusable XML fragments?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCan you refactor Maven pom.xml files into reusable XML fragments?
      1. USGavilan Comun
      1. VTFavorite
    3. VO
      singulars
      1. POCan you refactor Maven pom.xml files into reusable XML fragments?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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