Re: Build is successful but can't run?

> *Failed to load Main-Class manifest attribute from target/myApp.jar* > > I opened the manifest and the *Main-Class* attribute was entered as > *mainClass.* So I changed it to the former and that got rid of that error. > But now I *still *get the original error. You should specify the fully qual

Re: Build is successful but can't run?

On 2/5/2014 11:40 AM, TenLeftFingers wrote: Hi Mark, Thanks for that. I changed the pom as you suggested. When I ran with java -jar myApp.jar I got the output: *Failed to load Main-Class manifest attribute from target/myApp.jar* A couple of things: 1. the main-class-name was supposed to be y

Re: Build is successful but can't run?

Hi Mark, Thanks for that. I changed the pom as you suggested. When I ran with java -jar myApp.jar I got the output: *Failed to load Main-Class manifest attribute from target/myApp.jar* I opened the manifest and the *Main-Class* attribute was entered as *mainClass.* So I changed it to the former a

Re: Build is successful but can't run?

On 2/5/2014 9:52 AM, TenLeftFingers wrote: When I build my Maven project with dependencies (using Netbeans but pointing to a vanilla Maven installation), I get BUILD SUCCESS. Great! When I try to /run /it in the form of *java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App* I get this:

Re: Build is successful but can't run?

> When I try to /run /it in the form of *java -cp > target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App* I get this: > *java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory* > > How come this dependency fails at this late stage? This line says "run Java with the classpath being my-app.jar and

Build is successful but can't run?

When I build my Maven project with dependencies (using Netbeans but pointing to a vanilla Maven installation), I get BUILD SUCCESS. Great! When I try to /run /it in the form of *java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App* I get this: *java.lang.NoClassDefFoundError: org/slf4j/Lo

Re: Unable to use the maven-release-plugin to release

To fix this I had to add org.apache.maven.scm maven-scm-provider-gitexe 1.9 to the plugin definition of the m-r-p (version 2.4.1). Martijn On Wed, Feb 5, 2014 at 5:44 PM, Martijn Dashorst wrote: > This is still an issue. Can someone please fix the maven-release-plugin to > w

Re: Unable to use the maven-release-plugin to release

This is still an issue. Can someone please fix the maven-release-plugin to work with a decent version of git? Martijn On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte wrote: > Hi, > > it depends on the type of problem you're facing. > > as said before, these are probably the best options: > > -

Re: Maven multi-module site

On 5 Feb 2014, at 13:23, Melvyn de Kort wrote: > Our maximum heap size is already 4G, can't increase that any more I'm > afraid. It could be running out of PermGen space, which is controlled by a different setting: MAVEN_OPTS="-XX:MaxPermSize=256m" > Regards, > > Melvyn de Kort > >

Re: Maven multi-module site

Our maximum heap size is already 4G, can't increase that any more I'm afraid. Regards, Melvyn de Kort On Wed, Feb 5, 2014 at 2:18 PM, Ron Wheeler wrote: > On 05/02/2014 4:22 AM, Melvyn de Kort wrote: > >> Hi all, >> >> We have a large multi-module project with over 90 submodules. >> When we ru

Re: Maven multi-module site

On 05/02/2014 4:22 AM, Melvyn de Kort wrote: Hi all, We have a large multi-module project with over 90 submodules. When we run a mvn site-deploy command, the build will run out of memory. This used to work, but I guess we reached a threshold. Our idea is to split the site command in groups of m

Maven multi-module site

Hi all, We have a large multi-module project with over 90 submodules. When we run a mvn site-deploy command, the build will run out of memory. This used to work, but I guess we reached a threshold. Our idea is to split the site command in groups of modules, or maybe build every module separately.