On Tue, Mar 15, 2011 at 7:32 PM, Eranda Sooriyabandara
0704...@gmail.com wrote:
Hi all,
Sorry to embarrass you, the fault was on my side. I used a wrong command
when I manually install an artifact. After removing some files from the m2
repository I recovered from the error.
The good news is
Hi all,
Sorry to embarrass you, the fault was on my side. I used a wrong command
when I manually install an artifact. After removing some files from the m2
repository I recovered from the error.
The good news is that after do some manual installing some artifacts now I
have a fully I built trunk.
Hi,
I used the following commands to build the trunk but it failed. Can you
please give some advice on this.
I attached the output of the error which I got with this.
thanks
Eranda
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
Sorry for not entering the commands in previous mail.
The commands I used was,
1. set MAVEN_OPTS=-Xmx128M
2. mvn
thanks
On Mon, Mar 14, 2011 at 12:47 PM, Eranda Sooriyabandara
0704...@gmail.com wrote:
Sorry for not entering the commands in previous mail.
The commands I used was,
1. set MAVEN_OPTS=-Xmx128M
2. mvn
thanks
That's a bit odd that dependency should be coming in through the
following pom entry
Hi Simon,
I am on Ubuntu 10.04.
java version 1.6.0_20.
Apache Maven 2.2.1.
thanks
On Mon, Mar 14, 2011 at 1:17 PM, Eranda Sooriyabandara
0704...@gmail.com wrote:
Hi Simon,
I am on Ubuntu 10.04.
java version 1.6.0_20.
Apache Maven 2.2.1.
thanks
I'm on the same Java but Maven 2.2.0. That's on widows. On Redhat I'm
on slightly back-levels of Java and Maven. Needless to say
On Mon, Mar 14, 2011 at 5:47 AM, Eranda Sooriyabandara
0704...@gmail.com wrote:
Sorry for not entering the commands in previous mail.
The commands I used was,
1. set MAVEN_OPTS=-Xmx128M
2. mvn
thanks
Just to make sure, you use export MAVEN_OPTS (for linux) instead of
set (which is windows)