And indeed that's the ID to add to the mirror ! list!
On Fri, Dec 11, 2015 at 9:47 AM, Anders Hammar wrote:
> And by "that id" I mean 'com.springsource.repository.bundles.release'
>
> /Anders (mobile)
> On Dec 11, 2015 15:45, "Anders Hammar" wrote:
>
>> Most likely it is in one of the spring pom
And by "that id" I mean 'com.springsource.repository.bundles.release'
/Anders (mobile)
On Dec 11, 2015 15:45, "Anders Hammar" wrote:
> Most likely it is in one of the spring poms. Can't you search for that id
> in all poms in your local Maven repo?
>
> /Anders (mobile)
> On Dec 11, 2015 15:38, "
://bernd.eckenfels.net
-Original Message-
From: Benson Margulies
To: Maven Users List
Sent: Fr., 11 Dez. 2015 15:38
Subject: Tracking down a
I can't build Apache CXF when my normal Nexus mirror is in place; it
fails to find:
org.springframework:org.springframework.context:2.5.6.SEC01
I c
Most likely it is in one of the spring poms. Can't you search for that id
in all poms in your local Maven repo?
/Anders (mobile)
On Dec 11, 2015 15:38, "Benson Margulies" wrote:
> I can't build Apache CXF when my normal Nexus mirror is in place; it
> fails to find:
>
> org.springframework:org.sp
I can't build Apache CXF when my normal Nexus mirror is in place; it
fails to find:
org.springframework:org.springframework.context:2.5.6.SEC01
I can if I turn off my mirrors. So, I'm trying to determine what repo
I need to add to my Nexus or exclude from my mirrors.
Mirrorless, I see
➜ 2.5.6.S
On Sat, Feb 19, 2011 at 2:01 AM, Benson Margulies wrote:
> OK, mystery solved. I found the relevant dependencyManagement
> statement in a distant parent, leftover from long ago.
>
Can you see if there is already a bug filed that says we should do more to
help the user track these down?
If not, ca
OK, mystery solved. I found the relevant dependencyManagement
statement in a distant parent, leftover from long ago.
On Fri, Feb 18, 2011 at 10:27 AM, Benson Margulies
wrote:
> Running with m3, it still fails, and I see
>
> [DEBUG] org.mortbay.jetty:jetty:jar:7.2.0.v20101020:compile
> (vers
Running with m3, it still fails, and I see
[DEBUG] org.mortbay.jetty:jetty:jar:7.2.0.v20101020:compile
(version managed from 6.1.21)
in the log. So I need to figure out where this 'management' is coming from.
On Fri, Feb 18, 2011 at 10:25 AM, Benson Margulies
wrote:
> I just created a pro
I just created a project with an interesting dependency situation: my
existing code uses jetty 7, while hector from cassandra-land uses
jetty 6.
This should be fine; the group IDs are different.
However, my build fails as follows below. The actual cassandra-all pom
in my local repo, on the other
Thanks.
The case at hand is the -X message for:
[DEBUG] Adding managed dependencies for com.basistech:maven-rex2009task-plugin
[DEBUG] com.basistech:common:jar:4
[DEBUG] com.basistech:ap-segmentation-features:jar:9-SNAPSHOT
[DEBUG] com.basistech.rse:rlp-breaks:jar:1.4.99.5-SNAPSHOT
One of
Benson Margulies wrote:
> mvn -X shows me a dependency on a plugin that I can't explain. This is
> a plugin which, on its, has very few dependencies, and depends on
> explicit dependency declarations. -X is showing me something that
> should not be in there. dependency:tree doesn't look at plugins
mvn -X shows me a dependency on a plugin that I can't explain. This is
a plugin which, on its, has very few dependencies, and depends on
explicit dependency declarations. -X is showing me something that
should not be in there. dependency:tree doesn't look at plugins. Is
there something else which w
12 matches
Mail list logo
