Re: Looking for org.apache.poi 3.10-FINAL
Hi Martin, thanks for that. Unfortunately its no help if you don't use Nexus. All the best, DaveLaw On 18.02.2014 02:28, Martin Gainty wrote: MG ...I had a chance to read the FINE manual today and when including remote repositories: Option=Download Remote Indexes This field controls the downloading of the remote indexes. If enabled, Nexus will download the index, if it exists, and use that for its searches as well as serve that up to any clients which ask for the index (like m2eclipse). The default for new proxy repositories is enabled, but all of the default repositories included in Nexus have this option disabled. To change this setting for one of the proxy repositories that ship with Nexus, change the option, save the repository, On 16.02.2014 09:43, David Law wrote: Hi, I'm new to maven thought I'd try it out on the recently checked-in: org.apache.poi3.10-FINAL I'm using m2eclipse standard config with Eclipse Kepler. Repo defaults to: http://repo.maven.apache.org/maven2 The Problem: m2eclipse does not know the org.apache.poi 3.10-FINAL artifact. Now, I guess the problem could be any combination of: a) me b) POI c) maven d) m2eclipse e) eclipse? QUESTION) Can anyone help to localise it? Here's what I've found out so far: 0) repo is: http://repo.maven.apache.org/maven2 1) org.apache.poi 3.10-FINAL was committed @ 09-Feb-2014 11:50 2) as of now repo Timestamp is: 09-Feb-2014 13:50 (nexus.index.timestamp=20140209134945.568 +) (found in http://repo.maven.apache.org/maven2/.index/nexus-maven-repository-index.properties) 3) - so repo has been reindexed since org.apache.poi 3.10-FINAL commit (6 days ago). 4) exit eclipse 5) deleted the index C:\...\Eclipse\workspace\.metadata\.plugins\org.eclipse.m2e.core\nexus 6) start eclipse - updating index 7) org.apache.poi 3.10-FINAL is still not there (that is: here) in my list of artifacts All the best, DaveLaw - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Reflow Maven Skin 1.1.0 Released
Thanks! I haven't tried it with asciidoc, but if you can use it to author content for Maven site with it, it should work as expected. Andrius On Tue, Feb 18, 2014 at 1:41 AM, Mark Derricutt m...@talios.com wrote: Wow - super shiny! Can this work with asciidoc as well? On 18 Feb 2014, at 13:07, Andrius Velykis wrote: Reflow Maven skin builds on Bootstrap and offers responsive design, modern web components, JavaScript goodies and wide customisation options. See it in action and read the documentation at Reflow skin website: - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trouble with javadoc and package name
It's about if you have: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (default-cli) on project coolproject-api: MavenReportException: Error while creating archive: [ERROR] Exit code: 1 - javadoc: warning - No source files for package org.coolproject.api [ERROR] javadoc: warning - No source files for package org.coolproject.api [ERROR] javadoc: warning - No source files for package org.coolproject.api.listeners [ERROR] javadoc: error - No public or protected classes found to document. Java compiler understands sources directories with package-style names like: coolproject-api/java/org.coolproject.api/ and there are no problems with it, but *maven-javadoc-plugin* doesn't. So try to change your physical packages layout to: coolproject-api/java/org/coolproject/api/ -- View this message in context: http://maven.40175.n5.nabble.com/Trouble-with-javadoc-and-package-name-tp79373p5785194.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: wsimport - catalog
Am 2014-02-18 06:48, schrieb Sartaj Hundal: You need to get the XSD that is 'in' the jar file and then reference that retrieval within the XML. http://stackoverflow.com/questions/9280226/referencing-a-xsd-schema-within-jar-file This is what I wrote more than a week ago. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
OutOfMemory exception when using Maven in ant
Hi there, I am trying to incorporate Maven dependency management into my ant build as follows: artifact:dependencies pathId=my.dependencies.class.path dependency groupId=org.lib artifactId=libtools version=1.1.1/ dependency groupId= org.lib artifactId=otherlib version=1.1.1/ remoteRepository refid=archiva.repository/ /artifact:dependencies When I do a clean build, i.e. 'ant clean my-target', I get the following exception: java.lang.OutOfMemoryError: PermGen space Can someone help explain what is going on here and how I might mitigate this problem? Once I have this working for the first classpath, I plan to change all my classpaths to use the repository, but this looks like a bit of a show-stopper. Thanks in advance, Ron
Re: OutOfMemory exception when using Maven in ant
I am trying to incorporate Maven dependency management into my ant build as follows: [del] java.lang.OutOfMemoryError: PermGen space This is a Java problem rather than a Maven or Ant one. It has to do with not enough memory to load all the classes into the PermGen space. You can read up about PermGen space to get more of an idea as well * http://www.oracle.com/technetwork/java/javase/memleaks-137499.html#gbyuu * http://java.dzone.com/articles/busting-permgen-myths See http://stackoverflow.com/questions/88235/dealing-with-java-lang-outofmemoryerror-permgen-space-error for some solutions. It talks about Tomcat, but the problem occurs in command line Java. As a workaround use (or large values than 128M if needed) -XX:MaxPermSize=128M Also look at similar XX options at http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: OutOfMemory exception when using Maven in ant
This looks like an ant problem. You could try to increase the memory defaults in your Java VM. Make them really big and then pare them down if you feel the need to be precise (No value in that technically). Ron On 18/02/2014 5:06 PM, Ron Bets wrote: Hi there, I am trying to incorporate Maven dependency management into my ant build as follows: artifact:dependencies pathId=my.dependencies.class.path dependency groupId=org.lib artifactId=libtools version=1.1.1/ dependency groupId= org.lib artifactId=otherlib version=1.1.1/ remoteRepository refid=archiva.repository/ /artifact:dependencies When I do a clean build, i.e. 'ant clean my-target', I get the following exception: java.lang.OutOfMemoryError: PermGen space Can someone help explain what is going on here and how I might mitigate this problem? Once I have this working for the first classpath, I plan to change all my classpaths to use the repository, but this looks like a bit of a show-stopper. Thanks in advance, Ron -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Help[please]: maven-surefire-plugin with TestNG group dependencies not working....
I'm having a frustrating test dependency issue and I don't know if it is my
configuration or a problem. I've got two test classes in my maven project
using testng:6.8.7 and maven-surefire-plugin:2.16.
The first test class has the following annotation on the test *class* which
should be inherited by the test methods:
* @Test(groups={ functional })*
* public class FuncTest{...}*
on the other test *class*, I have:
* @Test(groups={ load }, dependsOnGroups = { functional })*
* public class LoadTest {...}*
When I run the following:
*mvn test*
I get the error:
*[ERROR] DependencyMap::Method LoadTest depends on nonexistent group
functional*
If I REMOVE the dependsOnGroups... it works. If I do any of the
following but keep the dependsOnGroups option:
* mvn test -Dtest=LoadTest,FuncTest*
* mvn test -Dgroups=functional,load*
* mvn test -Dgroups=functional,load **-Dtest=LoadTest,FuncTest*
it fails with the error above. If I run it outside of Maven by calling
org.testng.TestNG directly, it works fine.
I also tried moving the group definitions/dependencies to the test method
directly, but that didn't change.
*What am I missing? *
Thanks!
--
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
Re: OutOfMemory exception when using Maven in ant
Thanks for the speedy response. I have run across these types of memory exceptions in the past, but given that the build had been working correctly until I added the Maven artifact:dependencies/ bit, I naturally jumped to the conclusion that there was something odd going on. This was exacerbated when the ant error log actually identified the artifact:dependencies/ as the offending line in the build file. I'll play around with the memory parameters and see what happens. Cheers, Ron Btw, is there a reference for all parameters supported by artifact:dependencies/? I have - Original Message - From: baerr...@gmail.com To: users@maven.apache.org Sent: Tuesday, February 18, 2014 6:19:55 PM GMT -05:00 US/Canada Eastern Subject: Re: OutOfMemory exception when using Maven in ant I am trying to incorporate Maven dependency management into my ant build as follows: [del] java.lang.OutOfMemoryError: PermGen space This is a Java problem rather than a Maven or Ant one. It has to do with not enough memory to load all the classes into the PermGen space. You can read up about PermGen space to get more of an idea as well * http://www.oracle.com/technetwork/java/javase/memleaks-137499.html#gbyuu * http://java.dzone.com/articles/busting-permgen-myths See http://stackoverflow.com/questions/88235/dealing-with-java-lang-outofmemoryerror-permgen-space-error for some solutions. It talks about Tomcat, but the problem occurs in command line Java. As a workaround use (or large values than 128M if needed) -XX:MaxPermSize=128M Also look at similar XX options at http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: OutOfMemory exception when using Maven in ant
On 19 February 2014 13:07, Ron Bets ron.b...@oracle.com wrote: Thanks for the speedy response. I have run across these types of memory exceptions in the past, but given that the build had been working correctly until I added the Maven artifact:dependencies/ bit, I naturally jumped to the conclusion that there was something odd going on. This was exacerbated when the ant error log actually identified the artifact:dependencies/ as the offending line in the build file. I'll play around with the memory parameters and see what happens. Cheers, Ron Btw, is there a reference for all parameters supported by artifact:dependencies/? I have You mean this one? http://maven.apache.org/ant-tasks/examples/dependencies.html I'm afraid the two people who have answered your question really dont use Ant, so we dont know much about what you are doing. We use Maven natively rather than Ant with Maven dependency stuff. I'd recommend looking at the freely available books at http://maven.apache.org/articles.html and seeing whether you want to take the full plunge and migrate to Maven completely. Ant has its place, but for managing the Java software development lifecycle I'm obviously biased towards Maven :) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
