Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This looks like a definite bug to me.</p> <p>I have the same problem and tested Maven 3.0.1 and 3.0.2. Validate doesn't fail, only the compile step fails. With Maven 3 <code>mvn compile</code> breaks but <code>mvn test-compile</code> works.</p> <p>It appears that the compile phase is looking for test-jar artifacts in the reactor and then repo, but it shouldn't since the dependency is in test scope. Test scope artifacts should be resolved during test-compile, not compile.</p> <p>As a result, I thought this could be worked around by mapping the maven-compiler-plugin's testCompile goal to the compile phase, instead of the default test-compile phase.</p> <p>I added this to my pom, right next to the part that adds the test-jar creation in the upstream pom:</p> <pre><code> &lt;!-- there is a bug in maven causing it to resolve test-jar types at compile time rather than test-compile. Move the compilation of the test classes earlier in the build cycle --&gt; &lt;plugin&gt; &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;default-testCompile&lt;/id&gt; &lt;phase&gt;compile&lt;/phase&gt; &lt;goals&gt; &lt;goal&gt;testCompile&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/execution&gt; &lt;/plugin&gt; </code></pre> <p>But that won't work either because the five phases between compile and test-compile haven't run and set up things like the test classpath.</p> <p>I guess the real workaround until this bug is fixed is to use <code>test-compile</code> in place of <code>compile</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POwhy is "test-jar" dependency required for "mvn compile"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKariem
    1. USScott Carey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POwhy is "test-jar" dependency required for "mvn compile"
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have confirmed that the first maven phase to work is test-compile. process-test-resources fails.
      singulars
      1. PO
      1. USScott Carey
    2. COGlad to hear that I'm not alone in running into this bug. In your case are you also using the `exec:java` plugin - that seemed to be part of the problem for me. If not, are you binding any other plugins to execution phases?
      singulars
      1. PO
      1. USSteve
    3. COWhat I've recently discovered, but have not yet unwound, is that I can cause the problem with a very reduced set of 3 pom files. If these three (my project) inherit from nothing, it works. If they inherit from org.apache:apache it breaks. So one of the plugins defined there is probably breaking it. There is no exec:java plugin there -- but one of those plugins and the exec one probably depend on something else broken upstream. I'll comment here if I can narrow it down.
      singulars
      1. PO
      1. USScott Carey
 

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