Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>How do you specify a custom compilerId that points to your own ajc compiler (that is make compile:compile use an aspectj compiler other than the plexus one)?</p> </blockquote> <p>I don't know how to specify another <code>compilerId</code> than the <a href="http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html" rel="nofollow noreferrer">"official"</a> ones. Not sure it's possible. </p> <p>My understanding is that <a href="http://jira.codehaus.org/browse/MCOMPILER-107" rel="nofollow noreferrer">http://jira.codehaus.org/browse/MCOMPILER-107</a> would solve your problem (AspectJ 1.6+ does support Java 1. 6 right?). Sadly, it's still open.</p> <blockquote> <p>How do you ignore the failure of compile:compile?</p> </blockquote> <p>The <a href="http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html" rel="nofollow noreferrer"><strong><code>compiler:compile</code></strong></a> goal of the <a href="http://maven.apache.org/plugins/maven-compiler-plugin/" rel="nofollow noreferrer">Maven Compiler plugin</a> has a <a href="http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#failOnError" rel="nofollow noreferrer"><strong><code>failOnError</code></strong></a> optional parameter allowing to <em>Indicate whether the build will continue even if there are compilation errors</em>.</p> <pre class="lang-xml prettyprint-override"><code>&lt;project&gt; ... &lt;build&gt; ... &lt;plugins&gt; ... &lt;plugin&gt; &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt; &lt;version&gt;2.2&lt;/version&gt; &lt;configuration&gt; &lt;failOnError&gt;false&lt;/failOnError&gt; ... &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/build&gt; &lt;/project&gt; </code></pre> <p>This could be a ugly workaround to the above problem.</p> <blockquote> <p>How do you get maven to run the aspectj:compile goal directly, without ever running compile:compile?</p> </blockquote> <p>The problem is that <strong><code>compiler:compile</code></strong> is bound to the <strong><code>compile</code></strong> phase and that you can't remove a <a href="http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings" rel="nofollow noreferrer">default lifecyle binding</a>. So there is maybe another option but the only one I can think of would be to turn everything <em>off</em> by using a <code>&lt;packaging&gt;pom&lt;packaging&gt;</code> and to rebind all the goals manually (at least for these phases: <code>process-resources</code>, <code>compile</code>, <code>process-test-resources</code>, <code>test-compile</code>, <code>test</code>, <code>package</code>). Schematically, something like this:</p> <pre> process-resources resources:resources compile aspectj:compile process-test-resources resources:testResources test-compile compiler:testCompile test surefire:test package ejb:ejb or ejb3:ejb3 or jar:jar or par:par or rar:rar or war:war install install:install deploy deploy:deploy </pre> <p>That could be another ugly workaround. Disclaimer: not tested but should work.</p>
    singulars
    1. This table or related slice is empty.
    1. POMaven: compile aspectj project containing Java 1.6 source
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USnaXa
    1. USPascal Thivent
    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
    1. COYep. That is really annoying. I should be able to say "compile:compile" is replaced with "aspectJ:compile." I can *kind of* do that with the <compilerId> setting. The only problem is when I name "aspectJ" as the compilerId, it uses the plexus version which doesn't support java 1.6 instead of the aspectj plugin. I didn't know you could completely redefine phases through pom packaging! That's very good info, +1! Of course, before doing that, I'd just use solution #3 above and spell out all my goals on my eclipse run config. I'm just wondering what the so called "convention" is for solving this
      singulars
      1. PO
      1. USgMale
    2. COThanks so much for the extra help. I'm going to vote up that codehaus bug when I get more time today. It's sad their default aspect compiler doesn't support java 1.6 which was released over 3 years ago! Later today, I'll probably end up trying the failOnError workaround since compilation fails quickly and quietly due to softened exceptions that the javac compiler sees as unchecked. This seems to be the lesser of all the evils and possibly an "official" workaround for the codehaus/java1.6 problem.
      singulars
      1. PO
      1. USgMale
    3. COOf course, this is only an issue when the code doesn't compile without aspects being woven in. However, that *can* happen often when using AspectJ.
      singulars
      1. PO
      1. USgMale
 

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