On Fri, Feb 4, 2011 at 6:57 PM, Kenneth Litwak wrote:
> My team leader has said we use Maven, so I have to become good at it. That
> said, I put this in my POM,
>
> javax.servlet
> servlet-api
> ${servletApiVersion}
> provided
>
> and Maven complained that it cou
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, February 04, 2011 4:08 PM
To: Maven Users List
Subject: Re: Generic location for servlet-api.jar
>> My team leader has said we use Maven, so I have to become good at it.
>Why aren't you directing these question
> My team leader has said we use Maven, so I have to become good at it.
Why aren't you directing these questions to your team lead? Or someone
else in your team who knows Maven better since you're new to the tool?
> ${servletApiVersion}
> and Maven complained that it could not find the jav
> maybe windows file leaking.
> The pain of too much people
Or you have an open MS-DOS window that you've cd'ed into target in.
Or you have a running program that lives in target.
Or you deployed a war file from that target directory to Tomcat or
something and its still holding a file handle
My team leader has said we use Maven, so I have to become good at it. That
said, I put this in my POM,
javax.servlet
servlet-api
${servletApiVersion}
provided
and Maven complained that it could not find the javax.servlet artifact. I then
read a page at the
> If this is supposed to tell me that Maven downloads it automatically, it's a
> rather cryptic way of saying that. In fact, I'd never guess that from this.
> I
> don't like "magic" code. I'd rather put my jars in some location and make
> their existence explicitly known.
Maven downloads EVERY
I have to admit that I'm lost as to what exactly you're trying to do
but I've added a few comments below.
On 4 February 2011 14:10, Julien Letrouit wrote:
> Hi,
>
> I am pretty new to maven, so this is probably a silly question.
> My problem is I can't fetch any dependencies of type "POM".
Hi,
I am pretty new to maven, so this is probably a silly question.
My problem is I can't fetch any dependencies of type "POM".
For example, if I try to compile:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://
On Fri, Feb 4, 2011 at 4:44 PM, Kenneth Litwak wrote:
> The POM reference only says this of "provided":
> "provided - this is much like compile, but indicates you expect the JDK or a
> container to provide it at runtime. It is only available on the compilation
> and test classpath, and is not t
> If this is supposed to tell me that Maven downloads it automatically, it's
> a rather cryptic way of saying that. In fact, I'd never guess that from
> this. I don't like "magic" code. I'd rather put my jars in some location
> and make their existence explicitly known.
If you want to do everyt
maybe windows file leaking.
The pain of too much people
2011/2/4 Kenneth Litwak :
> I'm getting an error on "clean".
> "Failed to delete directory: c:\javaprojects\javaapp\SpringWeb\target
> Reason: unable to delete directory
> c:\javaprojects\javaapp\SpringWeb\target
>
> Maven made the dir
I'm getting an error on "clean".
"Failed to delete directory: c:\javaprojects\javaapp\SpringWeb\target
Reason: unable to delete directory
c:\javaprojects\javaapp\SpringWeb\target
Maven made the directory and I can see it. Why is the clean failing?
---
The POM reference only says this of "provided":
"provided - this is much like compile, but indicates you expect the JDK or a
container to provide it at runtime. It is only available on the compilation and
test classpath, and is not transitive."
If this is supposed to tell me that Maven download
> Problem creating jar: Unexpected end of ZLIB input stream at
> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:429)
>
> Surprisingly, as soon as I disable / leave out the tika dependency,
> assembly:assembly works as intended. Unfortunately, this is n
I didn't explicitly create a report plugin. Maybe I should have. I'm not
sure what the difference is between that and a "normal" plugin. Anyway,
the javadoc plugin has an "aggregate" goal which creates a single file
for all sub-modules. That all happens within that one execution of the
plugin. I ha
If I don't misunderstand things you're creating a report plugin? I'm not
familiar with that and it could be different with normal plugins.
Maybe have a look at the javadoc-plugin where javadocs are aggregated [1]?
/Anders
[1] http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.htm
Thanks for the reference. I think what they're saying make sense. I
basically have to create another child module that is dependent on all the
other child modules that run units tests. This new module will run the
consolidation of the unit test reports. However, how do I set up the
dependencies so
I went here:
http://mavencentral.sonatype.com
Searched for "servlet-api".
Clicked on "2.5" for the javax.servlet entry.
It lists the POM dependency to use.
The fact that I found it in the search results tells me it's available
in the Maven Central repo. This means I can declare it in my POM as
On 04/02/2011 6:35 AM, Mate Varga wrote:
That's completely reasonable -- we don't have more than one version in
production at a given time, however.
I would bet that frequently you have 1 in production, 1 in alpha or beta
test and one in development.
Tagging is one of those things that you will
I have the dependency in my POM (and adding it did nothing but break my ability
to call "clean" when I build my war. I still don't know where t put it. I've
analyzed the Maven by Example project and they don't do anything like that
because they are using a Jetty plugin. I created a project wor
More than likely, you can use the "stub" from Central for the build,
and then it is automatically used at runtime from the hosting
container (Tomcat, in this case).
javax.servlet
servlet-api
${servletApiVersion}
provided
Otherwise, deploy that jar to
Folks;
after using assembly / jar-with-dependencies in many internal cases so
far in order to quickly build "fat", runnable jar files, at the moment
I happen to be completely stuck with this. The project to be built is a
.jar artifact, having jcouchdb, apache tika 0.8 and a few other
dependencies
Folks;
after using assembly / jar-with-dependencies in many internal cases so
far in order to quickly build "fat", runnable jar files, at the moment
I happen to be completely stuck with this. The project to be built is a
.jar artifact, having jcouchdb, apache tika 0.8 and a few other
dependencies
All my (admittedly limited) experience of Maven is that the exact
location of everything matters more than anything else. So yes, I have
a servlet-api.jar from Tomcat 7. Where do I put it exactly? Thanks.
Ken
Kenneth D. Litwak, Ph.D.
Azusa Pacific University
901 E. Alosta Ave.
Azusa, CA 917
servlet-api should be scope provided, so as long as it's a correct
servlet-api jar, it won't matter
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 4 Feb 2011 17:13, "Kennet
Hello,
Has anyone noticed that release:perform gives warnings that other phases
don't
When running a "mvn release:prepare release:perform" command the
release:prepare doesn't show any warnings, but the release:peform does.
The warnings I'm getting are:
[INFO] [WARNING] Some problems
In Maven by Example, the servlet-api.jar is supplied by Jetty but I
want to use the jar from Tomcat, which is where I'm going to install my
web abb. So I'm unsure where Maven is going to expect to find a jar
file that it is not downloading as a dependency or plugin. Can someone
advise me please
Hello,
Has anybody seen an issue when using release plugin (release:peform)
via Maven2 on XP it not being able to find
org.apache.commons.codec.DecoderException while trying to generate
JavaDoc? I had javadoc setup under reporting and tried removing that
but it still creates it hits this.
On 02/04/2011 08:43 AM, Wendy Smoak wrote:
On Fri, Feb 4, 2011 at 9:32 AM, Steve Cohen wrote:
No, there is a POM. I believe I ran mvn:install:install-file and I would
guess that you're right that -DgeneratePom=true is the default because I
know I didn't create a POM myself. This POM is quite
I think you haven't fully understood how Maven works, or how Maven should be
used. The basic rule with Maven is that you cannot skip phases. When you
execute a build by specifying a phase, all phases up to and including that
phase is run. The plugins bound to these phases are then executed.
So, if
Hi,
I have a project that I would like to customize the way the maven lifecycle
is processed. Instead of restarting the lifecycle, is there a way to get
maven to continue its lifecycle from a specific phase?
I would like to break up the lifecycle into different stages in our CI
system, while usin
On Fri, Feb 4, 2011 at 9:32 AM, Steve Cohen wrote:
> No, there is a POM. I believe I ran mvn:install:install-file and I would
> guess that you're right that -DgeneratePom=true is the default because I
> know I didn't create a POM myself. This POM is quite simple. Is it too
> simple? Or is this
On 02/04/2011 07:24 AM, Wendy Smoak wrote:
On Fri, Feb 4, 2011 at 8:18 AM, Steve Cohen wrote:
Let's say one of my modules (Module A) depends on Hibernate v, X.Y.Z. If I
change some code in one of my own modules (Module B) that depends on Module
A, the system does not go out to the Internet or o
On Fri, Feb 4, 2011 at 8:18 AM, Steve Cohen wrote:
> Let's say one of my modules (Module A) depends on Hibernate v, X.Y.Z. If I
> change some code in one of my own modules (Module B) that depends on Module
> A, the system does not go out to the Internet or other non-local repository
> to see if Hi
Thank you, Tamás. RTFM and all that. I should have known this.
That solves my immediate problem, but I am still interested in
understanding my problem a little more.
Let's say one of my modules (Module A) depends on Hibernate v, X.Y.Z.
If I change some code in one of my own modules (Module
Folks;
after using assembly / jar-with-dependencies in many internal cases so
far in order to quickly build "fat", runnable jar files, at the moment
I happen to be completely stuck with this. The project to be built is a
.jar artifact, having jcouchdb, apache tika 0.8 and a few other
dependencies
That's completely reasonable -- we don't have more than one version in
production at a given time, however.
On Tue, Feb 1, 2011 at 9:29 PM, Ron Wheeler
wrote:
> On 01/02/2011 11:03 AM, Mate Varga wrote:
>
>> Perforce, and we're strict about comments as well, but we don't really do
>> branching an
An explanation can be found in the Maven 3.x Compatibility Notes:
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-AutomaticPluginVersionResolution
BTW: The version numbers can either be defined in the 'pluginManagement'
and/or in the 'plugins' section
Thanks for the prompt replies :-)
I didn't precise I was not at an Application layer, but in a layer above.
I confirm that on the Application layer, Spring answers really well about
the problematic.
For example, my packaging will produce a complete archive with tomcat
bundled into it.
In the tomc
Hi!
Am Donnerstag 03 Februar 2011, 03:28:54 schrieb nodje:
> Invaluable piece of information Ron, thanks a lot.
>
> I've been searching the archives without success, with 'profile plugin'
> 'failsafe profile', all woudn't yield much relevant results.
> But I'd still be happy if you could point me
40 matches
Mail list logo
