Re: maven compile error message format

2012-04-12 Thread Barrie Treloar
On Thu, Apr 12, 2012 at 2:55 PM, mike digioia mpd...@gmail.com wrote: Thanks Wayne, That is the reason for my two jars, one is source and the other binary. However, this statement does not make sense in all cases, since one can create self-running JAR files with mainclass.mf manifest file to

Re: maven compile error message format

2012-04-12 Thread Wayne Fay
That is the reason for my two jars, one is source and the other binary. However, this statement does not make sense in all cases, since one can create self-running JAR files with mainclass.mf manifest file to run the program with java -jar myProgram.jar. This may include both binary and

Re: maven compile error message format

2012-04-12 Thread Ron Wheeler
Putting the sources in a executable jar just makes it bigger and slower to load at run--time with absolutely no benefit to the execution. Wayne is right that it will not break anything but why do it. People who run programs are not generally the people who read or use source code. People who

Re: maven compile error message format

2012-04-12 Thread Wayne Fay
Putting the sources in a executable jar just makes it bigger and slower to load at run--time with absolutely no benefit to the execution. Wayne is right that it will not break anything but why do it. Actually that is the scary thing... it CAN break things. Go read that old Maven Users email

Re: maven compile error message format

2012-04-12 Thread Ron Wheeler
At least, I got the Wayne is right part correct. Ron On 12/04/2012 11:28 AM, Wayne Fay wrote: Putting the sources in a executable jar just makes it bigger and slower to load at run--time with absolutely no benefit to the execution. Wayne is right that it will not break anything but why do it.

Re: maven compile error message format

2012-04-11 Thread Barrie Treloar
On Wed, Apr 11, 2012 at 4:45 PM, mike digioia mpd...@gmail.com wrote: Can anyone in the world tell me what line number and what error this compiler thinks my error is in source file ServiceDiscovery.java?

Re: maven compile error message format

2012-04-11 Thread mike digioia
ok thnak you very much. This was what I was expecting, however i could not see what the issue was. Here are the lines in the code from line 1 on package com.huawei.cona.android.zeroconf; import java.io.IOException; import jmdns-1.0; import service-1.0; import service.ServiceEvent; import

Re: Re: maven compile error message format

2012-04-11 Thread Thorsten Heit
Hi, ok thnak you very much. This was what I was expecting, however i could not see what the issue was. Here are the lines in the code from line 1 on package com.huawei.cona.android.zeroconf; import java.io.IOException; import jmdns-1.0; import service-1.0; (...) Quite easy: These

Re: Re: Re: maven compile error message format

2012-04-11 Thread Thorsten Heit
Hi, ok thnak you very much. This was what I was expecting, however i could not see what the issue was. Here are the lines in the code from line 1 on package com.huawei.cona.android.zeroconf; import java.io.IOException; import jmdns-1.0; import service-1.0; (...)

Re: maven compile error message format

2012-04-11 Thread Shu
Line 5 column 12 On Wednesday, April 11, 2012 9:15:24 AM UTC+2, mpd wrote: Can anyone in the world tell me what line number and what error this compiler thinks my error is in source file ServiceDiscovery.java?

Re: maven compile error message format

2012-04-11 Thread mike digioia
Hi Barrie, Sorry to take anymore of your time up. But I have not had any success with all the changes I have made to correct this problem. Based on your recommendation I suspect it is a mismatch in what I have in my code and in my pom/environment. I used mvn install to add jar files that I

Re: maven compile error message format

2012-04-11 Thread Barrie Treloar
On Thu, Apr 12, 2012 at 8:22 AM, mike digioia mpd...@gmail.com wrote: Hi Barrie, Sorry to take anymore of your time up. But I have not had any success with all the changes I have made to correct this problem. Based on your recommendation I suspect it is a mismatch in what I have in my code

Re: maven compile error message format

2012-04-11 Thread mike digioia
Thanks I see you don't know what the issue is either. This is not a java programming issue. It is a maven issue. I have been living with the maven manual for a week. But that has not been much time considering what they built. On Wed, Apr 11, 2012 at 4:25 PM, Barrie Treloar baerr...@gmail.com

Re: maven compile error message format

2012-04-11 Thread Barrie Treloar
On Thu, Apr 12, 2012 at 9:12 AM, mike digioia mpd...@gmail.com wrote: Thanks I see you don't know what the issue is either. This is not a java programming issue. It is a maven issue. I have been living with the maven manual for a week. But that has not been much time considering what they

Re: maven compile error message format

2012-04-11 Thread Stephen Connolly
Oh we all know what the issue is. Hint: You don't know what a valid package name is and you don't understand some basic concepts of Java. Trust us, this *is* a java programming issue. This is *not* a maven issue. On 12 April 2012 00:42, mike digioia mpd...@gmail.com wrote: Thanks I see you

Re: maven compile error message format

2012-04-11 Thread Ron Wheeler
I read in my morning mail that you were told how to fix this. import com.huawei.cona.android.jmdns-new; The compiler is not even looking at your maven dependencies. It is telling you that you have a syntax error. jmdns-new is not a legal syntax for a class name in an import statement since it

Re: maven compile error message format

2012-04-11 Thread Wayne Fay
conalab@ching-jen-laptop:~/.m2/repository/com/huawei/cona/android/zeroconf/jmdns/1.0$ mvn install:install-file -Dfile=src.jmdns.jar -Dsources=src.jmdns.jar -DgroupId=src.jmdns -DartifactId=jmdns -Dversion=new -Dpackaging=jar -DgeneratePom=true You have already been sufficiently razed over the

Re: maven compile error message format

2012-04-11 Thread mike digioia
Thanks Wayne, That is the reason for my two jars, one is source and the other binary. However, this statement does not make sense in all cases, since one can create self-running JAR files with mainclass.mf manifest file to run the program with java -jar myProgram.jar. This may include both binary