带有antlr3-maven-plugin的Maven 3：源生成真的发生在流程源中吗？
我正在使用 Maven 3 的 antlr3-maven-plugin (v.3.3)。由于文档，它只有一个名为 antlr 的目标：
默认绑定到生命周期阶段：generate-sources
但是，当我调用 mvngenerate-sources 时，目标永远不会被调用。我需要调用下一阶段，mvn process-sources 来激活这个目标。到底是怎么回事。
另外，对我来说登录 mvn3 有点糟糕。我什至看不到在哪个阶段调用了哪些目标，我所看到的只是：
[INFO] --- antlr3-maven-plugin:3.3:antlr (default) @ project ---
但即使我使用 -X 标志执行 Maven，也没有关于它发生的阶段的信息！在 mvn2 中总是有有关当前阶段的信息。为什么 Maven 团队会做出减少日志信息的奇怪决定？
I'm using antlr3-maven-plugin (v.3.3) with Maven 3. It has only one goal named antlr wchich, due to documentation:
Binds by default to the lifecycle phase: generate-sources
However when I invoke mvn generate-sources the goal is never invoked. I need to invoke the next phase, mvn process-sources to activate this goal. What is going on.
Also, for me logging in mvn3 kinda sucks. I can't even see wchich goals was invoked in which phases, all I see is something like:
[INFO] --- antlr3-maven-plugin:3.3:antlr (default) @ project ---
But there is not info about the phase it happened, even if I execute Maven with -X flag! In mvn2 there was always info about current phase. Why such strange decision to reduce info in logs was taken by Maven team?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论