If you want to use your WSDL4J and not the one from Axis and because it
seems they have different groupId/artifactId, you should include an
exclusion inside the Axis dependency declaration in order to exclude the
WSDL4J dependency from Axis
Regards
Jeff
On Fri, Nov 30, 2012 at 3:02 AM, Benson M
Thanks Jeff. seems it will solve my problem.
Thanks for your help.
--
View this message in context:
http://maven.40175.n5.nabble.com/why-axis-1-4-jar-is-dependent-upon-wsdl4j-1-5-1-jar-file-in-maven-tp5734252p5734492.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Responding to all, as MVERSIONS-200 is important enough to flag the
potential issue if you are using deprecated properties (the ones that Maven
3 warns you about if you use them)
@Dennis Wheeler: I suspect you have hit
https://jira.codehaus.org/browse/MVERSIONS-200
The "right" thing to do is to u
Hi,
> I have never seen any java application fail just because I run the
> version 7 VM. Even really old code still runs.
A couple of Atlassian applications I work with in our department that
didn't run (fine) with Java 7:
- JIRA <= 5.1.x (5.2 was released ~3 weeks ago)
- Bamboo <= 3.2.x (3.3
Hi list,
yesterday i had an hour to burn and tried maven-remote-resource-plugin
instead.
It just worked as expected.
- cheers,
Philip
On Mon, 2012-11-26 at 13:03 +0100, Philip wrote:
> Hi list,
> i have a multi-module project and would like to share some common
> resources.
> Easily found th
Hello everyone,
I'm am against updating default version to 1.7. My favourite option would
be to use the lowest possible version of JDK and give a warning if version
is not specified explicitly (similar to what resources plugin does with
encoding). I would actually go as far as warning people if th
Very nice!
Ron
On 30/11/2012 7:12 AM, Stephen Connolly wrote:
It's a tad rough, but I'm fed up writing it, and I think it's useful for
people anyway:
http://developer-blog.cloudbees.com/2012/11/maven-profiles-and-maven-way.html
Just some of my random thoughts
-Stephen
--
Ron Wheeler
Presi
On Thu, Nov 29, 2012 at 07:12:37PM +0100, Robert Scholte wrote:
> These patterns were introduced with Ant.
Well, glob matching goes back at least as far as Unix v1
http://en.wikipedia.org/wiki/Glob_%28programming%29
Ant improved on this by adding the double-asterisk that matches any
depth of h
We are not talking about making Maven only run on 7.
We just want to move the default compiler to 6 (at least) or 7.
You can always set it back to 1.3.
It is just odd for new projects to start up with Maven and suddenly find
than Maven wants to use 1.3 to compile code.
Please, no more warnings
I understand that it's not about making Maven run on 7.
The problem is that people build artifacts on 7 (which will become more
often if it's default) and deploy these artifacts to repository, then
people who are using JDK 6 will not be able to compile with this artifacts
(the target JDK is writte
On 30 November 2012 13:42, Aliaksei Lahachou wrote:
> Hello everyone,
>
> I'm am against updating default version to 1.7. My favourite option would
> be to use the lowest possible version of JDK and give a warning if version
> is not specified explicitly
I too am in favour of maintaining the curre
Actually the current behaviour is 1.5 is using Maven Compiler Plugin 2.5 or
newer (might be 2.4 but I'd need to check)
With Maven 3.1.0, the version of the Maven Compiler Plugin that you get if
you have not locked down plugin versions will be upped to a version with
this new default.
So if you do
BTW I favour keeping at 1.5. That is the highest version we can guarantee a
user of Maven 3.1.0's JDK can compile at (because in order to run Maven
2.2.1+ you need Java 1.5) so unless they are using toolchains (which to be
honest, given the lack of bugs reported around toolchains and my knowledge
o
Hello,
I'm trying to make use of plexus-compiler-eclipse by setting
maven-compiler-plugin
3.0
eclipse
org.codehaus.plexus
plexus-compiler-eclipse
2.
2012/11/30 Peter Palmreuther :
> Hello,
>
> I'm trying to make use of plexus-compiler-eclipse by setting
>
>
> maven-compiler-plugin
> 3.0
>
> eclipse
>
>
>
> org.codehaus.plexus
>
You have been getting 1.5 by default for a long time. At least since the
2.3 release of the compiler plugin..
On Fri, November 30, 2012 7:35 am, Tim Pizey wrote:
> On 30 November 2012 13:42, Aliaksei Lahachou wrote:
>> Hello everyone,
>>
>> I'm am against updating default version to 1.7. My favour
Hello,
Am 30.11.2012 um 21:41 schrieb Olivier Lamy :
> 2012/11/30 Peter Palmreuther :
>> [...]
>> Am I configuring maven-compiler-plugin - and plexus-compile-eclipse - the
>> wrong way?
>> Or is plexus-compiler-eclipse not raising these errors as such at all, which
>> would render it quite a bi
17 matches
Mail list logo
