try using the -o (offline mode) option for the mvn command.
Hope that helps.
--
TK
On Aug 18, 2008, at 2:52 PM, goutham wrote:
Hello Good Evening,
I have a small but seriously irritating problem here :)
Whenever i run a maven command such as mvn install or mvn site, it
begins by
looking u
Here's a (not-so-funny?) anecdote...
I have been using Maven in the shop that pays my salary, for better
than 8 months now.
Just today, my friend who works for another company close by, he
asked me "have you ever used Maven?"
I explained how Maven has greatly helped with my company's softwa
I can't download and install
this plugin using the usual mvn commands (can't remember what they
are)?
- Original Message ----
From: Tommy Knowlton <[EMAIL PROTECTED]>
To: Maven Users List
Sent: Friday, 24 August, 2007 4:03:26 PM
Subject: Re: provided dependencies
Wayne
s transitively
provided, so doesn't that mean it still should not be copied to
WEB-INF\lib?
- Original Message
From: Tommy Knowlton <[EMAIL PROTECTED]>
To: Maven Users List
Sent: Friday, 24 August, 2007 1:29:38 PM
Subject: Re: provided dependencies
my guess would be that b
Scope" section of
this page:
http://maven.apache.org/guides/introduction/introduction-to-
dependency-mechanism.html
it seems to say that a provided dependency is transitively
provided, so doesn't that mean it still should not be copied to WEB-
INF\lib?
- Original Message ---
my guess would be that both modules depend transitively on the
javax.servlet in the runtime scope.
but, since guessing is not likely to be very helpful, may I recommend
the maven-dependency-plugin, which can give you a report that may
help you to locate the actual dependency chain that ends
The dependencySet will silently fail to include an artifact that is
not actually in the list of pom.xml .
I believe the option in the assembly descriptor
would have alerted you to the problem, causing the assembly execution
to fail instead of silently failing to include the artifact into t
I'm interested in the answer to this as well.
At one time, I became convinced (by Maven documentation, or my
misunderstanding thereof) that using version ranges, like [1.0.0,)
would be useful in this manner, but as it turns out, most Maven
plugins don't appear to honor ranges (or at least, d
I have a class that is a specialized implementation of a given
interface, and this specialized implementation cannot be distributed
to all customers. I wasn't able to find a way to exclude the class
from the jar, but I was able to exclude it from compilation, by
reflectively loading it if i
e solution!
Thanks,
--
Tommy
On 4/6/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
Try extracting all your dependencies (with versions) and move them
into a section in a shared parent pom. Then
remove the nodes specified in the dependencies in all the
children poms.
Wayne
On 4/6/07, Tom
Hello,
My project team has got on the order of 30 projects that contribute to
a single webapp. Most of the projects produce
jar artifacts, that go into the webapp's
WEB-INF/lib.
The problem I'm having is inconsistency with how Maven resolves (and
names) versioned artifacts... Within WEB-INF/lib,
testing: that workaround is a kludge.
Can anybody explain how I can modify the lifecycle to add a "custom"
lifecycle phase? My is only binding a few lifecycle
phases as it is, but none of the existing (default lifecycle) phase
names means the same thing as what I want done.
Thanks,
-
I'm not positive, but I believe where you said you should say
. I haven't tried this in a POM of my own, but I've been using
the maven-assembly-plugin alot lately, and I think you've got it
exactly right, modulo that one change.
HTH
--
Tommy
On 3/23/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
I solved this problem as follows:
central
Maven Repository Switchboard
default
http://repo1.maven.org/maven2
false
false
central
Maven Plugin Repository
http://repo1.maven.org/maven2
default
false
I'm trying to use indirection again to implement "Don't Repeat
Yourself" but I'm stuck and need some expert help.
I have created a custom artifact type, and now I'm trying to figure
out how to get it to behave "a little more" like the stock jar
artifact type.
A concrete example of the problem is
Hello,
My dev team has been using Maven2 full-time for about 2 months now,
and we're starting to notice a problem that we hadn't really
considered until now. I don't know a "safe" way to deal with it, but
I'm getting very close to having to do something that might be
"unsafe".
The issue is that
Hello,
I'm trying to create an "installer" artifact type, and then depend on
the installer's dependencies in other projects.
The transitive dependencies aren't being exposed in the dependent project.
A concrete example of what's currently Not Working for me is this: I
want to provide a "jdbc-dr
On 3/14/07, Thorsten Heit <[EMAIL PROTECTED]> wrote:
Hi Pablo,
> maybe I forgot to mention that projectA, projectB and projectC aren´t
> children of projectD. They are projects located in whatever location in my
> svn repository.
>
> What I'm trying to achieve is that a Maven2 project could ret
Hello,
I'm trying to build "installer" (by which I mean, a tarball inside of
which is an install.sh as well as whatever other things I decide to
put in) distributions for some of my maven projects.
In some cases, I want to make the installer the only "artifact" of the
build. Problem is, there's
ve approach is going to be difficult to use for
snapshot deploys - unless deploy-file munges the artifact name to add
timestamp when the version has '-SNAPSHOT'. Even if that works, it
still breaks e.g., Continuum.
Cheers,
Jon
Tommy Knowlton wrote:
> I'm trying to produce a POM for bui
I'm trying to produce a POM for building several different artifacts
from the same sources.
In the section, I have accomplished
1) configuring the build tools to do something different for each profile
2) activating the profiles
3) give the profile's artifact a unique name using classifier
confi
Yes, that works. And I also verified that the description of the xml
on the assembly descriptor web page incorrectly indicates that
tag is a child of . (I didn't think I had
hallucinated that...)
Thanks again.
On 2/26/07, Tommy Knowlton <[EMAIL PROTECTED]> wrote:
Thanks, Jo. I
zip
${basedir}
*.sh
install.sh
install.sh
/
true
Cheers
Jo
On 2/26/07, Tommy Knowlton <[EMAIL PROTECTED]> wrote:
>
> I'm trying to use the maven-assembly-plugin to build a zip that
> conta
I'm trying to use the maven-assembly-plugin to build a zip that
contains an install.sh at the top level, along with some arbitrary
other artifacts.
I want the install.sh source to be filtered so that certain build-time
variables will be run-time literals.
I've tried to compose an assembly descri
On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Hi Tommy,
Tommy Knowlton wrote on Thursday, February 08, 2007 3:30 AM:
> On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>> Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
>>
>>> Is
On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
> Is this a bug in the code that resolves ${project} references?
No, this is a feature (that fails miserably when the directory in your
repository does not match the a
Hello,
I've got a parent POM that declares e.g.,
…
http://javabuild2.mycompany.com/${project.artifactId}
(in other words, top-level configuration that varies by the project
that has declared this parent).
Problem is, when I look at the effective POM (mvn help:effective-pom),
it shows up as
Maybe I wasn't thinking about this problem the right way.
It turns out that when I override the Super POM's "central" repository
entry using my project's POM, with false for both
and , maven2 exhibits the desired behavior.
The build now (correctly) fails for artifacts that would have been
obtai
28 matches
Mail list logo