Not sure how stack trace will help. I'm thinking that the
maven.dependency.classpath is messed up somehow. I added
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-antrun-plugin</artifactId>
        <version>1.1</version>
        <executions>
          <execution>
            <id>dump maven.dependency.classpath</id>
            <phase>generate-sources</phase>
            <configuration>
              <tasks>
<property name="path.string" refid="maven.dependency.classpath"/>
<echo>${path.string}</echo>
              </tasks>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>

to my top level pom (I have a multi project build) and it spit out
[INFO] [antrun:run {execution: dump maven.dependency.classpath}]
[INFO] Executing tasks
     [echo]
/home/tedx/jwss/XMLConfiguration/activemq:/home/tedx/jwss/XMLConfiguration/activemq-web:
/home/tedx/jwss/XMLConfiguration/jar:/home/tedx/jwss/XMLConfiguration/3.2.2:
/home/tedx/jwss/XMLConfiguration/geronimo-spec

I truncated the output but obviously these paths are completely wrong so no
wonder my ant tasks can't find classes when they are trying to us  these.
What do you see in your maven.dependency.classpath?

On 3/9/06, Mayorgaadame, Alex <[EMAIL PROTECTED]> wrote:
>
> Xavier,
>
> I've seen something similar just yesterday. Can you share your stack
> traces?
>
> mvn goal -X
>
> Also which version of ant is maven using, mine was 1.6.5 and fails like:
>
> Embedded error: The following error occurred while executing this line:
> /home/am74839/sree/esf_samples_build.xml:162: Unable to find a javac
> compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK
>
> Regards,
> Alex
>
> -----Original Message-----
> From: Xavier Toth [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 09, 2006 11:26 AM
> To: Maven Users List
> Subject: [m2] maven-antrun-plugin classpath related behavior changed
>
>
> maven-antrun-plugin executions that had been working are failing with
> classpath related issues (classnotfound). I'm thinking maybe I've picked
> up
> a newer version of the plugin and it's behavior is different. Is anyone
> else
> experiencing these types of problems?
>
> Xavier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to