Hi,
I thought the version is defined in
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-core/src/main/resources/META-INF/plexus/default-bindings.xml;h=09ecba441e61d4a997b01af0171815c558548537;hb=maven-3.0.4
(replace hb with the version of your choice :-)).
Hmm, I guess you
My team colleague gets the following error:
_
mvn clean or mvn help:effective-pom gives the following error:
[INFO] Scanning for projects...
Downloading:
https://.../nexus/content/groups/public/.../.../.../xxx-shared/2.0.26-SNAPSHOT/maven-metad
Probably you have the xxx-shared artifact already in your local repository
from an earlier invocation, so it won't get looked up in Nexus, while your
colleague doesn't.
I think your parent part of the pom should look something like this:
xxx.xxx.xxx
xxx-shared
Hi Tommy,
Tommy Svensson wrote:
> My team colleague gets the following error:
>
> _
> mvn clean or mvn help:effective-pom gives the following error:
>
> [INFO] Scanning for projects...
> Downloading:
> https://.../nexus/content/groups/public/.
28 nov 2013 kl. 16:05 skrev Jörg Schaible :
> Hi Tommy,
>
> Tommy Svensson wrote:
>
>> My team colleague gets the following error:
>>
>> _
>> mvn clean or mvn help:effective-pom gives the following error:
>>
>> [INFO] Scanning for projects..
28 nov 2013 kl. 15:39 skrev Nick Stolwijk :
> Probably you have the xxx-shared artifact already in your local repository
> from an earlier invocation, so it won't get looked up in Nexus, while your
> colleague doesn't.
>
> I think your parent part of the pom should look something like this:
>
>
I did remove my local repository files (~/.m2/repository/...) and did an "mvn
install" and got this exact problem myself!
I'm however completely failing to understand why. I tried to add
".. to the "install" module but that made no
difference and since ".." is the one and only relative path to
Hmmm I suspect you may not have read this post:
http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html
(Trigger for suspicion is people referring to an "install" pom... esp when
they put install in quotes)
On 28 November 2013 17:04, Tommy Svensson wrote:
> I did remove
Actually, if maven is failing to see the project being built (itself) it would
explain both that it tries to download its own pom and that the first module
child fails to see the parent.
But what would make it fail to se itself ? It is a valid pom and it is called
pom.xml.
Regards,
Tommy Sve
28 nov 2013 kl. 18:10 skrev Stephen Connolly :
> Hmmm I suspect you may not have read this post:
> http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html
No, I had not. After looking at it I have no idea what you are trying to say
with it.
>
> (Trigger for suspicion is
Sounded like you were using a pom to "install" 3rd party jars into the
local repo for other modules to use... I ack that I could be wildly off
base... but when we see people talking about their "install" pom and
putting "install" in quotes 9 times out of 10 they are trying to hack
installing .jar f
Supposed I've:
in src/main/java/dependency/child.java:
package dependency;
import dependency.parent;
public class child extends parent
{
}
in src/main/java/dependency/parent.java:
package dependency;
public class parent
{
}
How does maven determine that
parent.java must be c
Maven doesn't do anything to determine that.
It's delegated to the used jdk compiler.
--
Olivier
On Nov 29, 2013 12:34 PM, "Larry Evans" wrote:
> Supposed I've:
>
> in src/main/java/dependency/child.java:
>
> package dependency;
> import dependency.parent;
> public class child extends pare
13 matches
Mail list logo