Basically. I had to have both a parent version and a regular version
parent
artifactIdsubco/artifactId
groupIdorg.mainco.subco/groupId
version55.0.0/version
/parent
namemyproject/name
urlhttp://maven.apache.org/url
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
On 26 November 2013 14:59, Malte Skoruppa skoru...@cs.uni-saarland.dewrote:
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
Specifying a plugin version number is generally a good idea as the
'latest-and-greatest' may break your build at an unexpected time (usually the
day before you need to deliver a product) or worse build differently such that
the product breaks. While due diligence is done to ensure that only
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
Not quite. I want a specific error message printed when a user specifies a
test class to run, and the class does not exist.
I updated my surefire version to 2.12 and got the same behavior as before.
On Mon, Nov 25, 2013 at 4:28 PM, Robert Scholte rfscho...@apache.orgwrote:
IIUC this has been
Hey Randy,
Ok... you convinced me about that: specifying a plugin version number is
generally a good idea. :)
I am not so intent on having the 'latest-and-greatest' plugin as you
might think. It's more that I would like to stick to the default
configuration unless I have good reason not to
On 26 November 2013 15:59, Malte Skoruppa skoru...@cs.uni-saarland.dewrote:
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
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
Think of it not as 'if I configure one thing, I must configure another thing',
but more as 'if I configure one thing, I must provide complete information
about the thing I configure'. Complete information being information that does
not has a stable default. As was pointed out, core
On Tue, Nov 26, 2013 at 05:05:40PM +0100, Malte Skoruppa wrote:
[snip]
I am not so intent on having the 'latest-and-greatest' plugin as you
might think. It's more that I would like to stick to the default
configuration unless I have good reason not to do so. It's really just
that I find it
Regardless of the plug-in version, you want to specify the Java version
that you want.
The defaults have traditionally been very far behind the current version
of Java.
There are bugs or deficiencies in the older versions of the plug-in
which is why new versions were created.
It is a good
Dear mailinglist,
is there any way to exclude files that do not have an extension from filtering
in an WAR overlay? As far as I can see you can only explicitly define
file-extensions within the nonFilteredFileExtensions element. In my setting
there are binaries that don't have a file-extension
On Tuesday, November 26, 2013, Malte Skoruppa wrote:
is there some way for me to achieve the following three things at the same
time:
(1) have Maven compile my source files with -source 1.4 (or anything
higher than 1.3)
(2) *not* specify the maven-compiler-plugin version to use; instead,
Hi:
When i compile the source code of CloudStack4.3( compile by Maven3.0.5 )
and i receive the following PluginResolutionException problem :
[INFO]
[ERROR] Failed to execute goal
Could not transfer artifact org.codehaus.plexus:plexus-archiver:jar:1.2
from/to central
(http://repo.maven.apache.org/maven2): Connection to
http://repo.maven.apache.org
refused: Connection timed out - [Help 1]
...
[ERROR] For more information about the errors and possible solutions,
Hello Laird,
the only pity with using properties is that they are not namespaced most of
the time (the maven.compiler.* ones being an exception here), output is
claimed at least by three mojos IIRC. And skipTests is almost a general one
but you may not easily specify that you do not want to run
17 matches
Mail list logo
