[hibernate-dev] Search build failure
Amin Mohammed-Coleman
aminmc at gmail.com
Sat Feb 6 03:23:06 EST 2010
Hi Sanne
I've just updated HSearch and trying to build via maven and intellij and i'm getting the following:
INFO] Scanning for projects...
[INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss-plugins
[INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss-snapshot-plugins
[INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss
[INFO] artifact org.eclipse.wst.css:core: checking for updates from jboss-snapshot
[INFO] artifact org.eclipse.wst.css:core: checking for updates from repository.jboss.com
[INFO] artifact org.eclipse.wst.css:core: checking for updates from maven-repository.dev.java.net
[INFO] artifact org.eclipse.wst.css:core: checking for updates from central
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range (1.1,2.0)
org.eclipse.wst.css:core:jar:null
from the specified remote repositories:
jboss-snapshot (http://snapshots.jboss.org/maven2),
repository.jboss.com (http://repository.jboss.com/maven2/),
jboss-snapshot-plugins (http://snapshots.jboss.org/maven2),
central (http://repo1.maven.org/maven2),
maven2-snapshots.jboss.org (http://snapshots.jboss.org/maven2),
jboss-plugins (http://repository.jboss.com/maven2),
maven-repository.dev.java.net (http://download.java.net/maven/1),
jboss (http://repository.jboss.com/maven2)
Path to dependency:
1) org.jboss.maven.plugins:maven-jdocbook-plugin:maven-plugin:2.2.0
2) org.hibernate:hibernate-jdocbook-style:jdocbook-style:2.0.0
3) org.jboss:jbossorg-docbook-xslt:jar:1.1.0
4) org.jboss.docs:highlight:jar:1.0.0
5) org.richfaces.docs:highlight:jar:3.1.4.GA
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Sat Feb 06 08:17:24 GMT 2010
[INFO] Final Memory: 5M/79M
[INFO] ------------------------------------------------------------------------
I'll have a close look, obviously I've got a config wrong.
Cheers
Amin
On 6 Feb 2010, at 08:10, Sanne Grinovero wrote:
> Hi Amin,
> according to head it shouldn't be needed to build core, as it's
> currently depending on 3.5.0-Beta-4 :
>
> http://fisheye.jboss.org/browse/Hibernate/search/trunk/pom.xml?r1=18574&r2=18691
>
> Maybe you just need to update? This change is just two days old.
>
> Sanne
>
> 2010/2/6 Amin Mohammed-Coleman <aminmc at gmail.com>:
>> Thanks I'll give that a go!
>>
>> Cheers
>>
>> Amin
>>
>>
>> On 6 Feb 2010, at 07:55, Strong Liu wrote:
>>
>>> try add this to your .bashrc (or others if you're not using unix-like os)
>>>
>>> export MAVEN_OPTS=-Xmx1024m
>>>
>>>
>>> -------------------------------
>>> Best Regards,
>>>
>>> Strong Liu
>>>
>>>
>>>
>>> On Feb 6, 2010, at 3:16 PM, Amin Mohammed-Coleman wrote:
>>>
>>>> Hi All
>>>>
>>>> I'm trying to build core and followed the steps mentioned and I'm getting the following exception:
>>>>
>>>> Failure executing javac, but could not parse the error:
>>>>
>>>>
>>>> The system is out of resources.
>>>> Consult the following stack trace for details.
>>>> java.lang.OutOfMemoryError: Java heap space
>>>> at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385)
>>>> at com.sun.tools.javac.code.Scope.enter(Scope.java:196)
>>>> at com.sun.tools.javac.code.Scope.enter(Scope.java:183)
>>>> at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132)
>>>> at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509)
>>>> at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446)
>>>> at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387)
>>>>
>>>>
>>>> I've added the following to the parent pom.xml (after googling around)
>>>>
>>>> <plugin>
>>>> <groupId>org.apache.maven.plugins</groupId>
>>>> <artifactId>maven-compiler-plugin</artifactId>
>>>> <configuration>
>>>> <source>1.4</source>
>>>> <target>1.4</target>
>>>> <argLine>-Xmx512m</argLine>
>>>> </configuration>
>>>> </plugin>
>>>>
>>>>
>>>> But still no luck. Any help would be appreciated. I'm working on Hibernate Search and need to build core.
>>>>
>>>>
>>>> Thanks
>>>>
>>>> On 4 Jan 2010, at 10:52, Galder Zamarreno wrote:
>>>>
>>>>> If you ever have doubts whether some VM parameters are affecting your
>>>>> test execution, I think you might be able to add a call to
>>>>> http://java.sun.com/j2se/1.5.0/jcp/beta1/apidiffs/java/lang/management/RuntimeMBean.html#getInputArguments()
>>>>> to see what VM parameters have been passed to your test.
>>>>>
>>>>> On 12/21/2009 09:17 PM, Hardy Ferentschik wrote:
>>>>>> Hi,
>>>>>>
>>>>>> turns out that MAVEN_OPTS does not help in this case at all. The surefire
>>>>>> plugin per default uses the forkMode 'once', meaning a new JVM gets created
>>>>>> for running the tests. Command line arguments passed via MAVEN_OPTS only
>>>>>> apply
>>>>>> for the JVM running the build.
>>>>>>
>>>>>> To increase the heap size for surefire you have to pass the JVM options in
>>>>>> the plugin configuration. See
>>>>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-4728
>>>>>>
>>>>>> I added -Xmx1024 globally in the parent pom of Core. I think that's better
>>>>>> than
>>>>>> just adding it to Envers alone.
>>>>>>
>>>>>> I have no idea why no-one else has experienced this issue. Might be some
>>>>>> JVM specific
>>>>>> thing.
>>>>>>
>>>>>> --Hardy
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, 21 Dec 2009 13:28:46 -0300, Adam Warski<adam at warski.org> wrote:
>>>>>>
>>>>>>>
>>>>>>>> -Xmx1024 - that's what I used to have, mainly driven by the fact that
>>>>>>>> once upon
>>>>>>>> a time the docbook plugin needed to work.
>>>>>>>>
>>>>>>>> Btw, I also have the problem if I just try to run the Envers build.
>>>>>>> That's very weird. I just ran all tests, a "clean install" took 1m 30s,
>>>>>>> even with default maven memory settings (so no -Xmx in MAVE_OPTS).
>>>>>>> I'm using Maven 2.2.0 on Java 1.5.0_19 (32 bit - maybe that's the
>>>>>>> problem?)
>>>>>>>
>>>>>>>> Have you only recently added more tests? I used to be able to build
>>>>>>>> everything just fine.
>>>>>>>> Maybe the test suite can be split up? (eg by configuring two instances
>>>>>>>> of the surefire plugin !?)
>>>>>>>> In case it the the report generator, maybe there is a way to configure
>>>>>>>> another generator?
>>>>>>> Well I add some tests from time to time (basically when I fix a bug ;)
>>>>>>> ), but nothing dramatical.
>>>>>>> I'm not too good with maven so I don't really know if it's possible to
>>>>>>> do a split.
>>>>>>>
>>>>>>> Adam
>>>>>>
>>>>>> _______________________________________________
>>>>>> hibernate-dev mailing list
>>>>>> hibernate-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>> _______________________________________________
>>>>> hibernate-dev mailing list
>>>>> hibernate-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> hibernate-dev mailing list
>>>> hibernate-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
More information about the hibernate-dev
mailing list