I don't love that as a default! because there are OS which do not yet have
up-to-date Open JDK 7 or JDK 8.
And we do not have influence to the company not delivering as they should,
years after promising that Java is
what we need for future OpenVMS developments. Or has someone knowledge when HP
Hi there,
I'm running into an error when trying to build my project using the shade
plugin. I need to merge some XML-Files, so the interesting part of my pom.xml
looks like this:
plugin
groupIdorg.apache.maven.plugins/groupId
Hi Benjamin,
I'm running into an error when trying to build my project using the
shade plugin. I need to merge some XML-Files, so the interesting
part of my pom.xml looks like this:
*snip*
transformer
Point is, unless you are using java 1.3, until 2.5ish you have had the
source1.5/source and target1.5/target in your pom anyway.
So changing the default from 1.5 to 1.7 will not make life any harder for
you as you'll just be putting back in the source1.5/source and
target1.5/target (assuming you
Leaving aside questions of compatibility, Java 7 as compiler default would
be a poor choice. After all, that would require JRE 7 as a standard for
running Maven, or using one of the Eclipse compilers. Otherwise, that would
be unsupported by the compiler.
On Wed, Nov 28, 2012 at 8:43 PM, Ron
Hi
I am building my project using maven,
I have some german character in my validation-global.xml
When I build it they got converted to some garbage value in
validation.xml.
If I add ? Xml version=1.0 encoding =iso-8859-1 in
validation-global.xml , then after build german character
Yes I am using ISO-8859-1
Thanks
Warm Regards,
Praveen Jain
Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India
From: Martin Eisengardt
[mailto:martin.eisenga...@gmail.com]
Sent: Thursday, November 29, 2012 4:17 PM
To: Maven
That is a fair point. And I concur, that until core ups its minimum JRE
requirement, compiler shouldn't move past that...
Raises the question should core up to 1.6... I don't see a pressing need
yet...
Lambdas are not until 1.8, and we don't do the crazy generics stuff that,
for example, forced
Java 7 has been out for almost a year and a half.
Java 6 was released in 2006
What keeps people on old versions for over 8 years(1.5)?
We have tried to keep up with the times and feel that we got a lot of
performance improvements over time without any pain as we changed versions.
There does
Yes, I knew that NetBeans had its own Maven on board. My external as well as
internal maven work nicely through Windows commandline, but not through
NetBeans. That's the whole problem.
From commandline here follow the internal maven and external maven
installations:
NetBeans onboard internal
I'm trying the changes on a thread about the Annotations not working and I
was able to make it work but encountered this discrepancy.
I can use default-value= but not defaultValue= as part of the Parameter
annotation. It gives out this error:
Failed to execute goal
When I click on the little wrench in the output window of NetBeans, it says
'Maven settings'. So I assume NetBeans uses Maven for that, not cygwin.
-Original Message-
From: Mikhail Kalkov [mailto:mikhail.kal...@purplescout.se]
Sent: woensdag 28 november 2012 11:32
To: Maven Users List
Are you getting any useful info from the Netbeans community?
It does not look like a Maven issue.
Ron
On 29/11/2012 9:58 AM, Froggerbin wrote:
Yes, I knew that NetBeans had its own Maven on board. My external as well as
internal maven work nicely through Windows commandline, but not through
People is stuck for old Java versions due to the fact that for example
organizations are using IBM WebSphere and do not upgrade those
immediately when new version of WAS is released. WAS 6.1 which was
released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7
which has JDK 6
Nothing at all.
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: donderdag 29 november 2012 16:16
To: users@maven.apache.org
Subject: Re: MissingProjectException
Are you getting any useful info from the Netbeans community?
It does not look like a Maven
Hi all,
I have a multiple module build that I run thusly:
mvn --fail-never --batch-mode -U -Dmaven.test.failure.ignore clean install
At the end of the process my build system scans tests results reporting
fail / pass.
module-a had a test error and continued to package its artifacts and move
on
On 29/11/2012 10:17 AM, Markku Saarela wrote:
People is stuck for old Java versions due to the fact that for example
organizations are using IBM WebSphere and do not upgrade those
immediately when new version of WAS is released. WAS 6.1 which was
released in 2006 and just add support for JDK
That is too bad.
We use Eclipse/STS under Windows and have never had any problems like
this, so I am not much use to you.
I suspect that many of the Netbeans users here are running under Linux
so they have not run into this.
On 29/11/2012 10:18 AM, Froggerbin wrote:
Nothing at all.
Hi Ron,
Is it not possible to run Maven in a JRE7 VM and compile code with a
1.3 compiler?
If you have a JRE7 VM available, then sure. If JRE7 is not available for
your platform, then it must remain possible to run Maven with an older JRE,
or else no more Maven for you. I do not know enough
I toke the NetBeans 7.2 / tool / option / java / maven / and
I had to browsed to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin
The I tried a clean build from NetBeans and I got
--
cd E:\Users\C770817\SW-PROJEKTE\SpezplaService;
JAVA_HOME=C:\\Program Files\\Java\\jdk1.6.0_30
On 29/11/2012 12:01 PM, Curtis Rueden wrote:
Hi Ron,
Is it not possible to run Maven in a JRE7 VM and compile code with a
1.3 compiler?
If you have a JRE7 VM available, then sure. If JRE7 is not available
for your platform, then it must remain possible to run Maven with an
older JRE, or
I don't think M2_HOME should have the \bin at the end.
On 29/11/2012 12:18 PM, Stadelmann Josef wrote:
I toke the NetBeans 7.2 / tool / option / java / maven / and
I had to browsed to E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.1\bin
The I tried a clean build from NetBeans and I got
That is what I say, definitely not,
I have tested it, and it produces the error shown in .-2
Josef
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Donnerstag, 29. November 2012 18:29
An: users@maven.apache.org
Betreff: Re: AW:
You only get the new language features from after 1.5 if target 1.5, so
switching core to use the newer features would make core incompatible with
running on 1.5
On 29 November 2012 17:25, Ron Wheeler rwhee...@artifact-software.comwrote:
On 29/11/2012 12:01 PM, Curtis Rueden wrote:
Hi Ron,
You might give 2.13-SNAPSHOT a spin since the termination logic was
improved and a few minor bugs were fixed.
Kristian
module
module-b had a test error, failed the module and moved on to the next module
module-c built normally
I have artifacts for A and C but not B. I see nothing in the
Hello.
Quite a few things in Maven take patterns as input. One example would
be the Assembly plugin, which accepts strings of the form *.java, etc,
in its configuration when referring to files to include/exclude. Is
there a description anywhere of the syntax of these match patterns? Are they
just
These patterns were introduced with Ant.
http://ant.apache.org/manual/dirtasks.html#patterns is probably the best
page describing the usage.
Robert
Op Thu, 29 Nov 2012 18:59:41 +0100 schreef
org.apache.maven.u...@io7m.com:
Hello.
Quite a few things in Maven take patterns as input. One
On 29/11/2012 12:48 PM, Stephen Connolly wrote:
You only get the new language features from after 1.5 if target 1.5,
so switching core to use the newer features would make core
incompatible with running on 1.5
Not sure that I understand how this follows.
The target compiler should not
I was only saying that why organizations are not moving to JDK 7. Lot of
those organizations has policy to use only that JDK also for devepment ,
so you cannot install JDK 7.
I know you can run Maven over Java7 with older projects with some
restrictions.
One is if you project use
Surely the change here is ONLY with the maven-compiler-plugin and
affects what it puts as the --source and --target arguments to javac
when compiler - I don't see why that should affect core?
I admit I'm not really sure how m-c-p relates down into plexus-compiler
and the compiler
Not would but I hazard an argument to say could, there are subtle
API -signature- changes that make targetting older bytecode problematic,
aka from JDK5-6 I believe there were some methods ( class escapes me now
) that used to take a String but now take a CharSequence, source
compatible but
It was a response to I am sure that some of the Maven developers would
like to use some of the new Java features to make the coding easier.
For the Maven (core) developers to take advantage of the newer features, we
would need to up the source level we compile core with. JavaC will allow
source
On 29/11/2012 2:14 PM, Mark Derricutt wrote:
Not would but I hazard an argument to say could, there are subtle
API -signature- changes that make targetting older bytecode
problematic, aka from JDK5-6 I believe there were some methods ( class
escapes me now ) that used to take a String but now
On 29/11/2012 2:27 PM, Stephen Connolly wrote:
It was a response to I am sure that some of the Maven developers
would like to use some of the new Java features to make the coding
easier.
For the Maven (core) developers to take advantage of the newer
features, we would need to up the source
Most serious users of Maven start out by building and releasing a
common parent POM for their corporation or workgroup. This locks down
plugin versions and configures core plugins such as the
maven-compiler-plugin. So the old default to 1.3 was never a very
serious inconvenience, since it's just a
On 29/11/2012 2:58 PM, Benson Margulies wrote:
Most serious users of Maven start out by building and releasing a
common parent POM for their corporation or workgroup. This locks down
plugin versions and configures core plugins such as the
maven-compiler-plugin. So the old default to 1.3 was
On Thu, 29 Nov 2012 19:12:37 +0100
Robert Scholte rfscho...@apache.org wrote:
These patterns were introduced with Ant.
http://ant.apache.org/manual/dirtasks.html#patterns is probably the best
page describing the usage.
Thank you!
HI all, My application is already using wsdl4j-1.6.2.jar and will not support
with wsdl4j-1.5.1.jar file. I have observed that when I have written only
axis1.4 dependency code in my pom.xml like below
/ axis axis 1.4 jar compile
/
(nabble_embed
HI all,
My application is already using wsdl4j-1.6.2.jar and will not support with
wsdl4j-1.5.1.jar file.
I have observed that when I have written only axis1.4 dependency code in my
pom.xml like below
dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
You will have to consult the Axis project. This is because their POM
declares this dependency.
On Thu, Nov 29, 2012 at 7:26 AM, koti koti.a...@gmail.com wrote:
HI all, My application is already using wsdl4j-1.6.2.jar and will not support
with wsdl4j-1.5.1.jar file. I have observed that when I
On Thu, Nov 29, 2012 at 3:41 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
On 29/11/2012 2:58 PM, Benson Margulies wrote:
Most serious users of Maven start out by building and releasing a
common parent POM for their corporation or workgroup. This locks down
plugin versions and
On 29/11/2012 9:06 PM, Benson Margulies wrote:
On Thu, Nov 29, 2012 at 3:41 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
On 29/11/2012 2:58 PM, Benson Margulies wrote:
Most serious users of Maven start out by building and releasing a
common parent POM for their corporation or
42 matches
Mail list logo
