directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arvind N <arvind.open...@gmail.com>
Subject Re: issues in compiling latest checked out src..
Date Wed, 08 Sep 2010 16:10:11 GMT
On Wed, Sep 8, 2010 at 9:29 PM, Arvind N <arvind.opensrc@gmail.com> wrote:
> On Wed, Sep 8, 2010 at 9:22 PM, Emmanuel Lécharny <elecharny@apache.org> wrote:
>>
>>> On Wed, Sep 8, 2010 at 9:00 PM, Emmanuel Lécharny<elecharny@apache.org>
>>>  wrote:
>>>>>
>>>>> On Wed, Sep 8, 2010 at 8:24 PM, Emmanuel Lecharny<elecharny@gmail.com>
>>>>>  wrote:
>>>>>>>
>>>>>>> Well when i do a mvn clean install i get the below exception
>>>>>>>
>>>>>>>
>>>>>>> [INFO] Surefire report directory:
>>>>>>> D:\os\apacheDC\directory-checkstyle\target\surefire-reports
>>>>>>> Error occurred during initialization of VM
>>>>>>> Could not reserve enough space for object heap
>>>>>>> Could not create the Java virtual machine.
>>>>>>
>>>>>> Increase the heap size  to -Xmx1024m. It should work.
>>>>>
>>>>> Did not help .. see below trace
>>>>>
>>>>>> What JVM are you using ?
>>>>>> Which Maven version ?
>>>>>
>>>>> D:\os\apacheDC>mvn --version
>>>>> Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530)
>>>>> Java version: 1.6.0_07
>>>>
>>>> You should *really* switch to Java 1.6.0_20.  The Java version you are
>>>> using
>>>> is more than 2 years and a half old...
>>>
>>> maybe i should .. but do you think this could be the issue ??
>>
>> May be not, but *many* issues have been fixed on the JDK since 1.6.0_07. Are
>> you still using Windows 3.0 ? I guess not...
>>>>
>>>> Can you give the command line you use to build the project ?
>>>
>>> the command you said
>>> mvn -e clean install
>>> NOTE: a maven naive user here..
>>
>> mvn clean install
>>
>> Remove the -e, it may introduce some side effects. The verbose mode won't be
>> helpful anyway...
>>
> Does not help... but noticed this .. the surefire pom that got
> downloaded has some weird stuff in it..
> repository\org\apache\maven\surefire\surefire\2.5\surefire-2.5.pom
>
> <!-- use preinstalled JDK 1.3 to build and test -->
>    <profile>
>      <id>jdk1.3</id>
>      <build>
>        <pluginManagement>
>          <plugins>
>            <plugin>
>              <artifactId>maven-compiler-plugin</artifactId>
>              <configuration>
>                <fork>true</fork>
>                <compilerVersion>1.3</compilerVersion>
>                <executable>${JAVA_1_3_HOME}/bin/javac</executable>
>              </configuration>
>            </plugin>
>            <plugin>
>              <artifactId>maven-surefire-plugin</artifactId>
>              <configuration>
>                <forkMode>once</forkMode>
>                <childDelegation>true</childDelegation>
>                <jvm>${JAVA_1_3_HOME}/bin/java</jvm>
>              </configuration>
>            </plugin>
>          </plugins>
>        </pluginManagement>
>      </build>
>    </profile>
>  </profiles>
> </project>
>
> is this normal.. ??
>
> ~A
>

and i see below thing in
repository\org\apache\directory\project\project\18-SNAPSHOT and this
gets written everytime i do a mvn clean install... How can i force
<artifactId>maven-surefire-report-plugin</artifactId> to have arg line
of 1024M ??  like we have done it for
<artifactId>maven-surefire-plugin</artifactId> ??
Just read that surefire plugin does not use MAVEN_OPTS but what is
given in the POM file...

<plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-report-plugin</artifactId>
          <version>2.5</version>
        </plugin>

        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.5</version>
          <configuration>
            <argLine>-Xmx1024m</argLine>
          </configuration>
        </plugin>

Mime
View raw message