> If there is a real interest in my participation I would be glad to join. But
...
> a consensus. So do you actually see any chances of a solution for the
> described problem? See, if not, it makes no sense that I add another thread
> on the dev list.
I think there is genuine interest in pursuing
012 20:09
> To: Maven Users List
> Subject: Re: How to put a dependency in the classpath BEFORE jre.jar?
>
> Markus,
>
> If you want to join in on the fun of the development community, please
> join us on the dev list. As you've heard on this thread, your
> particular
chiming in! :-)
Regards
Markus
> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de]
> Sent: Dienstag, 25. September 2012 21:48
> To: Maven Users List
> Subject: Re: How to put a dependency in the classpath BEFORE jre.jar?
>
> I did not read throu
put a javax.* dependency in your plugin
classpath. The only thing which is not allowed is to overwrite native SE stuff.
LieGrue,
strub
- Original Message -
> From: Benson Margulies
> To: Maven Users List
> Cc:
> Sent: Tuesday, September 25, 2012 8:08 PM
> Subject: Re: How
Markus,
If you want to join in on the fun of the development community, please
join us on the dev list. As you've heard on this thread, your
particular concern smacks into a messy conundrum about our desire to
avoid breaking other people's tools that read poms -- no matter how
poorly coded. Howeve
Java EE 6, while Java SE 6 only has "@Resource"
without the field "lookup". So my code simply does not build, as long as
javaee6.jar ist a simple dependency in the user classpath. I need to have it
in the bootstrap classpath. This is why this thread is called "How to put a
No need for
_any_ POM schema change! Maven could simply set up the root classpath
fully automatically that way!
Just like one day Eclipse learned the difference between "JRE" and
the
general term "Platform", Maven 4 has to learn this concept, too.
Maybe I should file a RFE for this?
Regards
Mark
but for all kinds of
> "Platforms"
> > like
> > .NET and Flash etc.). Using this interface, Maven could resolve the
> > question "Is this dependency to be put in the root classpath, or in
> > the user classpath?" automatically. Maven simply needs to ask the
&
'System' for the same dependency! No need for _any_ configuration in
the POM! No need for _any_ POM schema change! Maven could simply set up the
root classpath fully automatically that way!
Just like one day Eclipse learned the difference between "JRE" and the
general term "Platform&
need to support endorsed libraries. As
> >> all
> >> compilers might have different configuration switches, and selection of
> the
> >> particular compiler might be out of scope of the POM (i. e. defined in
> >> company pom for example), it simply is no sophisticated solution to
&g
forms the "JRE 6 Platform" (including some general
>> "Platform"
>> interface common not only for the JREs but for all kinds of "Platforms"
>> like
>> .NET and Flash etc.). Using this interface, Maven could resolve the
>> question
>
JRE 5 might answer with 'User' while JRE 6 might answer
> with 'System' for the same dependency! No need for _any_ configuration in
> the POM! No need for _any_ POM schema change! Maven could simply set up the
> root classpath fully automatically that way!
>
> Just l
fourni.
> From: mar...@headcrashing.eu
> To: users@maven.apache.org
> Subject: RE: How to put a dependency in the classpath BEFORE jre.jar?
> Date: Sat, 22 Sep 2012 11:19:44 +0200
>
> Stephen,
>
> if we would never address problems that seem hard to fix at first sig
n "JRE" and the
general term "Platform", Maven 4 has to learn this concept, too.
Maybe I should file a RFE for this?
Regards
Markus
> -----Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Samstag, 22. September 2012 00:0
if Maven 3 offers a better solution
> >
> > http://www.mindbug.org/2009/02/adding-endorsements-to-mavens-
> > plugins.html
> >
> > Claves
> >
> > -Original Message-----
> > From: Markus Karg [mailto:k...@quipsy.de ]
> > Sent: 20 Septe
ed as
true.
> -Original Message-
> From: Claves Do Amaral [mailto:claves.doama...@igmarkets.com]
> Sent: Donnerstag, 20. September 2012 10:30
> To: Maven Users List
> Subject: RE: How to put a dependency in the classpath BEFORE jre.jar?
>
> If I understand the proble
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: 20 September 2012 09:22
To: users@maven.apache.org
Subject: How to put a dependency in the classpath BEFORE jre.jar?
I have a dependency on javaee.jar, which provides newer versions for classes
found in JRE's jr
So there is no pure Maven support for this?
> -Original Message-
> From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
> Behalf Of Anders Hammar
> Sent: Donnerstag, 20. September 2012 11:46
> To: Maven Users List
> Subject: Re: How to put a dependenc
I *think* you should be able to do this by specifying an endorsed
directory to be used. This would be standard Java procedure, nothing
Maven specific.
Something like the following in the config of (for example) the
compiler plugin config:
-Djava.endorsed.dirs=blabla
Should be possible to do somet
I have a dependency on javaee.jar, which provides newer versions for
classes found in JRE's jre.jar (particularly the @Resource annotation).
But javaee.jar is always appended to the classpath, while to be able to
load the newer version, I need to PREFIX it before jre.jar instead. How
can I configur
20 matches
Mail list logo
