Build problem with FlexBuilder 3 Plugin

Question

Hi,
I am using the FlexBuilder 3 plugin with Eclipe Europa. I created a Flex project with J2EE backend and WTP support, so that I have both the Flex stuff and the J2EE stuff within the same project. I imported some mxml, as, and java files I had, and I was able to build and run my app using the default Eclipse build/deploy process. Everything worked except the BlazeDS (messagebroker servlet) part, so I decided to delete the Tomcat server (the Eclipse proxy of it), and start again with a new server config.
This somehow totally broke the build process. Some of the new config used port 8080 instead of 8400. And the only part of my app that was correctly deployed was the java files in the src folder. Properties files were not deployed, jar files were not deployed, even web.xml was not deployed.
After copying files manually into the Eclipse Tomcat proxy, everything worked fine, including object remoting and HTTPService invocation.
Can anyone share their experience with the FlexBuilder plugin for java webapps? What is the correct way to set it all up?
Thanks,
Miguel

Answer 1

Milesy wrote:
Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not foundFor me it worked when I used the settings
<plugins>
  <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <fork>true</fork>
        <executable>${java.home}/../bin/javac</executable>
        <compilerArgument>-proc:none</compilerArgument>
      </configuration>
    </plugin>
</plugins>
...Forking the compiler is perhaps not the best option, but its just for the annotation processor.