Thanks, Benson.
Mohan - those configuration changes didn't seem to have any effect at
all on my project.
It's really only a pain, right now, because I'm trying to "tweak" the
site. I make a small change and to see if it has the effect I want I
have a 12 minute build time. It's a bit frustrating
There is a defect in JIRA for this.
On Sat, Jul 11, 2009 at 4:23 PM, Mohan KR wrote:
> I believe this is a problem, don't know whether it has been fixed. But I'm
> able to
> get around this by setting the plugin configuration
>
> dependencyLocationsEnabled to false
> and
> dependencyDetailsEnable
I believe this is a problem, don't know whether it has been fixed. But I'm able
to
get around this by setting the plugin configuration
dependencyLocationsEnabled to false
and
dependencyDetailsEnabled to false
Thanks,
mohan kr
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hi
It looks to me like the Dependencies report, created during site
generation, is searching external repositories to find the information
it needs. But, it seems like that information should already be in my
local repository, assuming that the code had to be built before we can
generate the site. I
This is getting a little off-topic, but I feel obliged to mention that we
recently open sourced our generalized solution for dealing with the problem of
environmental-specific Spring configuration, known as BoxSpring. Our experience
with both Spring and our prior DI container lead to the conclus
Hm, weird - I still didn't get the other mail... - and that's the second
time that happend...
Peter
2009/7/10 Anders Hammar
> The list is fine. I've received both your messages. You can always
> check if your mail gets through by looking at the Nabble archive.
>
> /
Yup, that is a decision you have to make. But in general, the approach I
have been using is
this:
- You spring-context files rarely should be different for each environment
(if you think hard enough, you
can achieve it :)).
- We externalize all environment specific information from Spring Context
Just to add to Tim's advice, having a repo manager makes it very easy
to add any missing artifact should you need to.
/Anders
On Sat, Jul 11, 2009 at 16:36, Tim O'Brien wrote:
> Instead of just adding the JBoss repository to your repositories in a
> pom.xml. Your best bet here is going to be to
On Fri, Jul 10, 2009 at 1:54 PM, Vincent Fumo wrote:
> I'm converting an old project to maven and I have a question re: spring.
> This project has about 20 spring config files and it reads them all in on
> startup and uses the In addition I have 4 properties files
> (local/dev/qa/prod) that I'd li
I'm still experiencing the same problem.
Any hints?
Jim Mack-2 wrote:
>
> Juergen,
> Ran into this today when a developer accidentally checked in the
> target directory. Other than that mishap, we have not seen this
> behavior, in our war's. We are using maven 2.0.4, hope that helps.
>
Instead of just adding the JBoss repository to your repositories in a
pom.xml. Your best bet here is going to be to install a repository
manager, add all the repositories you need to a repository group, and
then configure your settings.xml to use a single repository group URL.
If you do this, yo
As to your second question, m2eclipse will only index the repositories you tell
it to. Open up the Index View and you'll see the list of repos.
Justin
From: Harper, Brad [mailto:brad.har...@fiserv.com]
Sent: Fri 7/10/2009 6:00 PM
To: Maven Users List
Subject: d
While trying to keep our third-party dependencies current, we found that
[1] reports a version 1.1.1 available for javax.activation:activation
... yet no such artifact version appears to exist in the central maven2
repo.
On the other hand, [2] reports this version for the JavaBeans Activation
F
13 matches
Mail list logo
