f the free books
were somehow better visually highlighted. Like a big green button that
says "Free!" beside the corresponding book or whatever.
On 12/13/2013 11:34 AM, Malte Skoruppa wrote:
Meanwhile, one doesn't necessarily have to buy a book to learn about
the
Maven lifecycl
Meanwhile, one doesn't necessarily have to buy a book to learn about the
Maven lifecycle. This is also explained on the website:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Yes, but it doesn't go into enough details.
The *free* books do.
This actually surpr
Just scanning http://maven.apache.org and its not obvious by the
content on the page where the books are.
Its over in the menu on the left under Documentation > Books and Resources
I wonder if we should add a section under "Learning about Maven".
When you might have gone looking, where would yo
Hi Javier,
The issue is that when running mvn clean package -U (both from the command
line and within eclipse) on the kepler SR1 only the poms were downloaded but
not the jars. No matter what i try the jars would not get downloaded.
So does this mean that the mvn command fails because Maven refu
Hi,
Rather than putting the parent in the repo, try using maven to install
it.
Awesome! That worked just fine! Now it's building... thanks!
(Please note that I had not put the parent in the repo myself, I just
downloaded a repo which already included that parent... and I did not
have the o
Hey guys,
I want to build a project that I downloaded
(https://sourcecode.valg.no/websvn/listing.php?repname=Internettstemmegivning)
and that is supposed to work fine.
Yet I cannot build even the first module, because Maven tells me it
cannot find the parent POM. The parent POM is there in t
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
none
of them is the uber-pom.
I'd just like to see it; I like to understand how stuff works ;-)
Thanks,
Malte
On 11/26/2013 04:26 PM, Stephen Connolly wrote:
On 26 November 2013 14:59, Malte Skoruppa wrote:
Hi,
I'm new to Maven and I'm currently going through the "Gett
Hi,
I read that as you wanting to only use features of Java 1.3 (madness I say)
which will break once you have Java 8 as its javac will only support down
to -source 1.6 IIRC (but it may be 1.5)
I think it is current and two back that is the new policy that is being
introduced from Java 8 onward
at version.
Remember, Infants are the only people that appreciate a change ;)
FWIW,
Randal Kamradt
- Original Message - Subject: Changing JDK version without specifying maven-compiler-plugin version
From: "Malte Skoruppa"
Date: 11/26/13 7:59 am
To: us
Hi,
thanks for your quick answer.
Generally, I don't want to do that. On the one hand, I would like for
Maven to simply use the latest version of the maven-compiler-plugin that is
available (the default behaviour).
Not the default behaviour any more at least since 2.0.9 IIRC... the
"cor
Hi,
I'm new to Maven and I'm currently going through the "Getting Started"
guide.
While reading, the following question came to me.
As far as I understand, Maven defaults to compiling all Java source
files with compatibility for JDK 1.3 (i.e., -source 1.3).
The guide explains how to change th
12 matches
Mail list logo