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?
Use the groupid, artifactid, version and classifier parameters of the goal
to achieve that
Ji
Le 10 avr. 2012 19:51, Mehul Sanghvi mehul.sang...@gmail.com a écrit :
Hi,
g
Hi,
Below is the output of the maven-install-plugin being executed.
What do I have to do so that I can specify the
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
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
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;
(...)
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?
Yes, You given correct solution to me.
Thank you all.
--
View this message in context:
http://maven.40175.n5.nabble.com/replace-parameters-when-overlaying-in-maven-tp5626856p5632304.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Ok guys, I sorted it out!
In fact my project was using the args4j library (2.0.10), this lib had a
dependency to tools.jar. As the profile solution was not working for me
(guess because it was a dynamic dependency), I finally ended up with
upgrading the args4j lib to 2.0.16 and everything
I was able to compile with no problems on 2.2.1. The only pom.xml changes I
had to make to get this (almost) working on 3.0.4 was to add version
numbers for plugins that didn't have them specified, move plugins under
reporting/reporting into build/build, and run mvn -N install on the
parent pom --
Any thoughts from anyone about either Mike's issues, or mine?
Can you boil it down to 5 sentences? I gave up and I'm sure everyone
else did too. Sorry but that was just total information overload.
Wayne
-
To unsubscribe,
If you add
relativePath../pom.xml/relativePath
Into the parent section of child-alpha, does it resolve any issue your
having? Specifically with having to do mvn -N install on the parent
1st.
On 11 April 2012 16:14, Brain Dump braindump2...@gmail.com wrote:
I was able to compile with no
Or start from scratch with simple pom.xml and nothing in src, then add
src and fix dependencies, build up slowly then diff the resulting pom
and see what's different.
On 11 April 2012 16:25, John Patrick nhoj.patr...@gmail.com wrote:
If you add
relativePath../pom.xml/relativePath
Into the
Hi,
My situation is not really unusual. I have a workaround for it, but
I'm trying to see if there are any other options, ones that fit with
Maven but don't require me to install a repository manager on my home
PC. :)
I zipped up a copy of a project from work, and my maven repository,
and set it
I think suggestion is not to bump version of all the artifacts. And also
Ron explained the approach they took to manage diff artifact version ( if u
understood it correctly ).
-Raj
On Mon, Apr 9, 2012 at 12:57 PM, mike digioia mpd...@gmail.com wrote:
Hi
Maybe I don't understand the
Hey -- sorry about the information overload. I've seen other posts on other
forums where people posted too little information and were asked to post
their source code or run something on full debug, etc., so I tried to be
complete. Didn't mean to overwhelm, and thanks for the responses.
Simply
I've managed to do to get the build to succeed is to (1) remove the
dependency listed within profiles/profiles of child-alpha, or (2) first
For a ton of reasons, including a dependency in a profile is a really
terrible thing to do. The very first thing I would do would be to
remove it.
In
Just to see if it would work, I moved the child-dep-jdk15 dependency out of
profiles and moved it into dependencies/dependencies (outside of
profiles). It still fails with the same stack trace. Any idea why? I can
get the build to pass if I leave out that dependency altogether, but that's
not
Brian,
You can find detail in the manual -
What do we mean by different build environments? Two example build
environments are production and devel-
opment. When you are working in a development environment, your system
might be configured to read from a
development database instance running on
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
Sorry but I looked at this-
*8
You're describing the two possible solutions. Either bump the version
on all artifacts produced, or just deploy the artifact that has
changed (with a new version number). Which way to go depends on
My
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
True .. but the issue is how to restrict it from happening when it comes to
formal builds.
-Raj
On Wed, Apr 11, 2012 at 4:03 PM, mike digioia mpd...@gmail.com wrote:
Sorry but I looked at this-
*8
You're describing the two possible solutions. Either bump the
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
yes that is a much harder question and solution!
On Wed, Apr 11, 2012 at 4:38 PM, Rajwinder Makkar
rmakkaroff...@gmail.comwrote:
True .. but the issue is how to restrict it from happening when it comes to
formal builds.
-Raj
On Wed, Apr 11, 2012 at 4:03 PM, mike digioia mpd...@gmail.com
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
Profiles per-se are “ok”
Adding dependencies in a profile is not.
The problem is when do those profiles get activated, and hence when will
the dependencies get pulled in.
When people have profiles activated by the presence of a file, and then
that pom is resolved from the local repo and not
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
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
I am converting a convoluted ant build to maven. It has a large number of
functional tests, mostly built on either TestNG or the now-deceased author's
private framework, but some on junit. I am running the tests via the antrun
plugin, but it when it hits a junit task, it fails with:
Could not
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
Could not load class (org.apache.tools.ant.taskdefs.optional.junit.
JunitTask) for type junit
I have confirmed that the ant-junit jar is in the classpath (although
I'd have expected all ant task jars to be there automatically). What
do I need to do to get this to work? And no, I cannot
Disclaimer: I don't use Checkstyle as a primary component in my builds.
property name=cacheFile value=${checkstyle.cache.file}/
property name=cacheFile value=${cacheFile}/
Did you try leaving cacheFile out entirely? Did you try setting
value=? Samples at the Checkstyle site show
Aha! Thank you! I searched the antrun plugin docs for info, but it's not there.
What would it take for this to be added as a FAQ? It seems other people have
been running into the same problem.
On Apr 11, 2012, at 10:37 PM, Wayne Fay wrote:
Could not load class
Aha! Thank you! I searched the antrun plugin docs for info, but it's not
there. What would it take for this to be added as a FAQ? It seems
other people have been running into the same problem.
I hate to say RTFM but it is appropriate in this case...
On Thu, Apr 12, 2012 at 12:29 PM, Wayne Fay wayne...@gmail.com wrote:
Disclaimer: I don't use Checkstyle as a primary component in my builds.
property name=cacheFile value=${checkstyle.cache.file}/
property name=cacheFile value=${cacheFile}/
Did you try leaving cacheFile out
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
36 matches
Mail list logo
