Re: generate-sources target called twice

I think what I may be encountering is a bug with the maven-processor-plugin. I'm only using Maven 2 however, so it is not the most recent version, but I can't upgrade now. Can I create a ticket for it somewhere, along with which I could attach the code? By the way, it seems that I may have

Re: generate-sources target called twice

Anders, I'll look at that, then. This is in the early stages, and I'm following a tutorial on annotation processing, where annotations in code is used to generate code that the compiler will compile on a subsequent pass. If I put the source beneath the target folder, I think the compiler will

Re: generate-sources target called twice

I was able to put my generated code into the target hierarchy without an issue. My custom annotation processor has been modified to skip any re-invocation of its process method. But, I still have a problem during compilation. Even though there is only one generated source file, the plugin

Re: generate-sources target called twice

My application isn't special as it pertains to Maven. The idea is that there are interfaces within my source code that are annotated with a custom annotation. During the generate sources phase, the custom annotation processor that I've written inspects the marked-up interfaces, generates code,

generate-sources target called twice

All, I have a problem with the generate-sources goal is being called twice and I don't know why. I have a super pom that defines the project with several sub-modules. One sub-module has this: build plugins plugin groupIdorg.bsc.maven/groupId

Re: generate-sources target called twice

I don't see anything in the output of the effective pom that uses the word fork What should I look for? I'm fairly new to Maven, so I don't know a lot about configuration... Here is my plugin management section: pluginManagement plugins plugin

Re: Skipping the TAR packaging step

Wayne, Thanks for the reply. I am the resident expert with Maven, so I am the only help I have. If we had someone like you are describing, I would very happy indeed. So far though, things are looking good, but it's like walking through the dark with a flashlight. As for the other formats, I'm

Re: Skipping the TAR packaging step

Thanks, Guillaume. I'll read through the links you've provided carefully to see if I can make this happen. Scott -- View this message in context: http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5154907.html Sent from the Maven - Users mailing list archive at

Re: Skipping the TAR packaging step

Right now the entire project is being refactored, so I don't have much of a choice right now. -- View this message in context: http://maven.40175.n5.nabble.com/Skipping-the-TAR-packaging-step-tp5152958p5156037.html Sent from the Maven - Users mailing list archive at Nabble.com.

Skipping the TAR packaging step

Hello, I'm working on a large project that takes time to compile. I would like to instruct Maven to only build the jar file, but after the build I have a tar, tar.bz2, and a zip file. I am brand new to Maven, but have converted a project to use Maven for the compilation of all component

Re: spring handlers

Dirk, I've never done any groovy scripting, but it looks like it is time to learn. I'm going to adapt what you have provided here. Thanks. Scott -- View this message in context: http://maven.40175.n5.nabble.com/spring-handlers-tp5048978p5052063.html Sent from the Maven - Users mailing list

Re: spring handlers

Thanks for the ideas--I'll have to look into scripting for the future in order to be robust enough to always have the right entries in spring.handlers and spring.schemas. The shade plugin actually wasn't being invoked as I thought it was because I wasn't calling the package target. When I did,

spring handlers

All, I am having an issue that has been encountered before. The issue concerns the inclusion of a file called spring.handlers that exists in multiple spring jars that are included with a project. I'm building a release version of a jar that includes its dependencies, such that there needs to

Re: spring handlers

Thanks for the reply. Here's roughly my setup. I have master project with multiple modules. prj - top level - gui - sv1 - sv2 So prj is the parent projectg, gui, sv1 and sv2 are child modules of prj. The gui module has depencencies on sv1 and sv2, and all three modules have spring

Re: spring handlers

Ok, Benson, maybe that is the way to go then. I'll have to update after posting another question. Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/spring-handlers-tp5048978p5049717.html Sent from the Maven - Users mailing list archive at Nabble.com.