beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niels Ull Harremoës (JIRA) <j...@apache.org>
Subject [jira] Commented: (BEEHIVE-1161) Problem with sandbox beehive-compiler-apt when using default maven repository location on Windows
Date Wed, 06 Dec 2006 08:19:21 GMT
    [ http://issues.apache.org/jira/browse/BEEHIVE-1161?page=comments#action_12455915 ] 
            
Niels Ull Harremoës commented on BEEHIVE-1161:
----------------------------------------------

The work around was to reconfigure maven to use another local repository path by changing
conf\settings.xml to contain 
  <localRepository>c:/program files/maven-2.0.4/repository</localRepository>

By the way, people who had their project in "C:\Documents and Settings\nuh\ideaProjects\MyProject"
had the same problem, even though their 
repository was in c:/program files/maven-2.0.4/repository  

Those of us who used c:\projects\MyProject saw no problems.

Our project is actually two levels with a parent POM and a child pom, but I think this is
irrelevant?
The toplevel pom manages the beehive versions (using <dependencyManagement>) and also
contains 

  <build>
    <pluginManagement>
      <plugins>
       <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <configuration>
            <source>1.5</source>
            <target>1.5</target>
          </configuration>
       <dependencies>
	      <!-- This dependency must be here, so that subprojects can use the apt compiler
-->
          <dependency>
            <groupId>org.apache.beehive</groupId>
            <artifactId>beehive-compiler-apt</artifactId>
            <version>1.0-SNAPSHOT</version>
            <scope>runtime</scope>
          </dependency>
        </dependencies>		  
        </plugin>
        ...


The child pom contains 

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <compilerId>apt</compilerId>
          <source>1.5</source>
          <target>1.5</target>
          <fork>true</fork>
          <verbose>true</verbose>
          <compilerArguments>
            <sourcepath>src/main/java;src/test/java</sourcepath>
            <s>target/srcgen</s>
            <APTweb.content.root>src/main/webapp</APTweb.content.root>
          </compilerArguments>
        </configuration>
       </plugin>



> Problem with sandbox beehive-compiler-apt when using default maven repository location
on Windows
> -------------------------------------------------------------------------------------------------
>
>                 Key: BEEHIVE-1161
>                 URL: http://issues.apache.org/jira/browse/BEEHIVE-1161
>             Project: Beehive
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>         Environment: Windows XP, maven 2.0.4
>            Reporter: Niels Ull Harremoës
>
> When having the maven repository in its default location ( e.g. C:\Documents and Settings\nuh\.m2\repository),
the plugin fails with the error:
> [INFO] Compilation failure
> Failure executing javac,  but could not parse the error:
> If the maven repository is configured to be elsewhere, e.g. c:\program files\maven-2.0.4\repository,
it works fine??
> Here's the relevant part of the pom:
>    <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-compiler-plugin</artifactId>
>         <configuration>
>           <compilerId>apt</compilerId>
>           <source>1.5</source>
>           <target>1.5</target>
>           <fork>true</fork>
>           <verbose>true</verbose>
>           <compilerArguments>
>             <sourcepath>src/main/java;src/test/java</sourcepath>
>             <s>target/srcgen</s>
>             <APTweb.content.root>src/main/webapp</APTweb.content.root>
>           </compilerArguments>
>         </configuration>
>         <dependencies>
>           <dependency>
>             <groupId>org.apache.beehive</groupId>
>             <artifactId>beehive-compiler-apt</artifactId>
>             <version>1.0-SNAPSHOT</version>
>             <scope>runtime</scope>
>           </dependency>
>         </dependencies>
>       </plugin>
> BTW, this was really painful to find - it worked great for some developers, and failed
with no error messages for the rest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message