Re: bootclasspath as a dependency
Unfortunately there's no built in way to do so. You can still use the
JVM argument options to pass in the option:
http://mojo.codehaus.org/exec-maven-plugin/exec-mojo.html#arguments
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#argLine
To get the correct value, use:
${settings.localRepository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar
(obviously, dependent on the local repository format).
You need to have the artifact in the local repository first - you can
do that via a regular dependency (though be aware it'll be added to
the normal classpaths as well, which may be undesirable).
Alterantively, you can use the dependency plugin to resolve it.
HTH,
Brett
2008/8/12 Alex <[EMAIL PROTECTED]>:
> Hi,
>
>> at which point do you need it in the boot classpath? For your unit
>> tests, or a plugin?
> For unit tests and for the exec-maven-plugin.
>
> Cheers,
> Alex
>
> Brett Porter wrote:
>>
>> at which point do you need it in the boot classpath? For your unit
>> tests, or a plugin?
>>
>> Cheers,
>> Brett
>>
>> 2008/8/12 Alex <[EMAIL PROTECTED]>:
>>>
>>> Hi,
>>>
>>> Is there a way to specify a bootclasspath as a dependency?
>>> I've been looking for it for a while but I haven't found a solution yet.
>>> What I'd like to have would be something as follows:
>>>
>>> pom.xml ->
>>>
>>> javax.xml.bind
>>> jaxb-api
>>> 2.1
>>>
>>>
>>> Meanwhile I've set MANVEN_OPTS, but it would be very nice to use only POM
>>> files.
>>>
>>> export
>>>
>>> MAVEN_OPTS=-Xbootclasspath/p:$HOME/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar
>>>
>>> Thanks in advance
>>>
>>> Alex
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: bootclasspath as a dependency
Hi, > at which point do you need it in the boot classpath? For your unit > tests, or a plugin? For unit tests and for the exec-maven-plugin. Cheers, Alex Brett Porter wrote: at which point do you need it in the boot classpath? For your unit tests, or a plugin? Cheers, Brett 2008/8/12 Alex <[EMAIL PROTECTED]>: Hi, Is there a way to specify a bootclasspath as a dependency? I've been looking for it for a while but I haven't found a solution yet. What I'd like to have would be something as follows: pom.xml -> javax.xml.bind jaxb-api 2.1 Meanwhile I've set MANVEN_OPTS, but it would be very nice to use only POM files. export MAVEN_OPTS=-Xbootclasspath/p:$HOME/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar Thanks in advance Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bootclasspath as a dependency
at which point do you need it in the boot classpath? For your unit tests, or a plugin? Cheers, Brett 2008/8/12 Alex <[EMAIL PROTECTED]>: > Hi, > > Is there a way to specify a bootclasspath as a dependency? > I've been looking for it for a while but I haven't found a solution yet. > What I'd like to have would be something as follows: > > pom.xml -> > > javax.xml.bind > jaxb-api > 2.1 > > > Meanwhile I've set MANVEN_OPTS, but it would be very nice to use only POM > files. > > export > MAVEN_OPTS=-Xbootclasspath/p:$HOME/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar > > Thanks in advance > > Alex > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bootclasspath as a dependency
Hi, Is there a way to specify a bootclasspath as a dependency? I've been looking for it for a while but I haven't found a solution yet. What I'd like to have would be something as follows: pom.xml -> javax.xml.bind jaxb-api 2.1 Meanwhile I've set MANVEN_OPTS, but it would be very nice to use only POM files. export MAVEN_OPTS=-Xbootclasspath/p:$HOME/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar Thanks in advance Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting the javac bootclasspath using dependencies
Whoops! That actually seems to work. Ok, I guess problem is solved! Thanx!
Clifton wrote:
>
> Ok that helps a little. Still I'm looking for the right expression for
> evaluating the dependencies (or even better select dependencies) as a path
> expression. This is what I have so far:
>
> maven-compiler-plugin
>
>1.3
>1.3
>
> ${project.dependencies}
>
>
>
>
>
> Matthew Tordoff wrote:
>>
>> The following page has an example of setting the bootclasspath:
>>
>> http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-comp
>> iler-arguments.html
>>
>> It seems to not use the -D before the parameter, im not sure if this is
>> partly to blame for the problems you are experiencing.
>>
>> Matt
>>
>> -Original Message-
>> From: Clifton [mailto:[EMAIL PROTECTED]
>> Sent: 24 January 2008 15:58
>> To: users@maven.apache.org
>> Subject: Setting the javac bootclasspath using dependencies
>>
>>
>> What's the best, most painless way to set the bootclasspath for the
>> maven-compiler-plugin? I'm trying to break out some shared code between
>> my J2ME midlet module and my servlet module into a shared module that
>> builds a jar. I'd like the compiler to use the midp20 and cldc11 jars on
>> the boot classpath. I just tried checking these jars into artifactory
>> (our local
>> repo) setting a dependency on them and then using the following
>> expression for the compilerArguments tag:
>> "-Dbootclasspath=${project.dependencies}"
>>
>> The expression returns a list of dependencies and doesn't format
>> correctly.
>> Am I missing something?
>> --
>> View this message in context:
>> http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies
>> -tp15067527s177p15067527.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>> The content of this e-mail is confidential and may be privileged. It may
>> be read, copied and used only by the intended recipient and may not be
>> disclosed, copied or distributed. If you received this email in error,
>> please contact the sender immediately by return e-mail or by telephoning
>> +44 20 7260 2000, delete it and do not disclose its contents to any
>> person. You should take full responsibility for checking this email for
>> viruses. Markit reserves the right to monitor all e-mail communications
>> through its network.
>> Markit and its affiliated companies make no warranty as to the accuracy
>> or completeness of any information contained in this message and hereby
>> exclude any liability of any kind for the information contained herein.
>> Any opinions expressed in this message are those of the author and do not
>> necessarily reflect the opinions of Markit.
>> For full details about Markit, its offerings and legal terms and
>> conditions, please see Markit's website at http://www.markit.com
>> <http://www.markit.com/> .
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies-tp15067527s177p15072526.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting the javac bootclasspath using dependencies
Ok that helps a little. Still I'm looking for the right expression for
evaluating the dependencies (or even better select dependencies) as a path
expression. This is what I have so far:
maven-compiler-plugin
1.3
1.3
${project.dependencies}
Matthew Tordoff wrote:
>
> The following page has an example of setting the bootclasspath:
>
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-comp
> iler-arguments.html
>
> It seems to not use the -D before the parameter, im not sure if this is
> partly to blame for the problems you are experiencing.
>
> Matt
>
> -Original Message-
> From: Clifton [mailto:[EMAIL PROTECTED]
> Sent: 24 January 2008 15:58
> To: users@maven.apache.org
> Subject: Setting the javac bootclasspath using dependencies
>
>
> What's the best, most painless way to set the bootclasspath for the
> maven-compiler-plugin? I'm trying to break out some shared code between
> my J2ME midlet module and my servlet module into a shared module that
> builds a jar. I'd like the compiler to use the midp20 and cldc11 jars on
> the boot classpath. I just tried checking these jars into artifactory
> (our local
> repo) setting a dependency on them and then using the following
> expression for the compilerArguments tag:
> "-Dbootclasspath=${project.dependencies}"
>
> The expression returns a list of dependencies and doesn't format
> correctly.
> Am I missing something?
> --
> View this message in context:
> http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies
> -tp15067527s177p15067527.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> The content of this e-mail is confidential and may be privileged. It may
> be read, copied and used only by the intended recipient and may not be
> disclosed, copied or distributed. If you received this email in error,
> please contact the sender immediately by return e-mail or by telephoning
> +44 20 7260 2000, delete it and do not disclose its contents to any
> person. You should take full responsibility for checking this email for
> viruses. Markit reserves the right to monitor all e-mail communications
> through its network.
> Markit and its affiliated companies make no warranty as to the accuracy or
> completeness of any information contained in this message and hereby
> exclude any liability of any kind for the information contained herein.
> Any opinions expressed in this message are those of the author and do not
> necessarily reflect the opinions of Markit.
> For full details about Markit, its offerings and legal terms and
> conditions, please see Markit's website at http://www.markit.com
> <http://www.markit.com/> .
>
> -----
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies-tp15067527s177p15072521.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting the javac bootclasspath using dependencies
The following page has an example of setting the bootclasspath:
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-comp
iler-arguments.html
It seems to not use the -D before the parameter, im not sure if this is
partly to blame for the problems you are experiencing.
Matt
-Original Message-
From: Clifton [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 15:58
To: users@maven.apache.org
Subject: Setting the javac bootclasspath using dependencies
What's the best, most painless way to set the bootclasspath for the
maven-compiler-plugin? I'm trying to break out some shared code between
my J2ME midlet module and my servlet module into a shared module that
builds a jar. I'd like the compiler to use the midp20 and cldc11 jars on
the boot classpath. I just tried checking these jars into artifactory
(our local
repo) setting a dependency on them and then using the following
expression for the compilerArguments tag:
"-Dbootclasspath=${project.dependencies}"
The expression returns a list of dependencies and doesn't format
correctly.
Am I missing something?
--
View this message in context:
http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies
-tp15067527s177p15067527.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The content of this e-mail is confidential and may be privileged. It may be
read, copied and used only by the intended recipient and may not be disclosed,
copied or distributed. If you received this email in error, please contact the
sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete
it and do not disclose its contents to any person. You should take full
responsibility for checking this email for viruses. Markit reserves the right
to monitor all e-mail communications through its network.
Markit and its affiliated companies make no warranty as to the accuracy or
completeness of any information contained in this message and hereby exclude
any liability of any kind for the information contained herein. Any opinions
expressed in this message are those of the author and do not necessarily
reflect the opinions of Markit.
For full details about Markit, its offerings and legal terms and conditions,
please see Markit's website at http://www.markit.com <http://www.markit.com/> .
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Setting the javac bootclasspath using dependencies
What's the best, most painless way to set the bootclasspath for the
maven-compiler-plugin? I'm trying to break out some shared code between my
J2ME midlet module and my servlet module into a shared module that builds a
jar. I'd like the compiler to use the midp20 and cldc11 jars on the boot
classpath. I just tried checking these jars into artifactory (our local
repo) setting a dependency on them and then using the following expression
for the compilerArguments tag: "-Dbootclasspath=${project.dependencies}"
The expression returns a list of dependencies and doesn't format correctly.
Am I missing something?
--
View this message in context:
http://www.nabble.com/Setting-the-javac-bootclasspath-using-dependencies-tp15067527s177p15067527.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven2: Adding dependencies to javac bootclasspath.
I have two jar files that need to be added to javac -bootclasspath before
the jdk's rt.jar file in order for the project to compile. What is the best
way of achieving that using Maven2? I can't find anyway of specifing this in
the dependency section so right now I'm doing the following:
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
C:\...\.m2\repository\path\to\myjar.jar;${java.home}\lib\rt.j
ar
This appears to work okay, though I'm hoping there is a better way. Ideally
I would like to be able to specify in the dependency section which jar files
should go in the bootclasspath. Or somehow be able to refer to the
dependency section from the plugin section so I don't have duplicate
information.
One small improvement would be to replace the repository path with a
variable. Is there a variable I can use so I can do the following:
${repo}\path\to\myjar.jar;${java.home}\lib\rt.jar
By the way, is there anywhere one can find a good list of variables that are
available to pom.xml writers.
Any help greatly appreciated.
/Scott Taylor
Re: bootclasspath jars
No, this is not a use case we've heard of before. In fact, in m2 we don't always fork so it would not have an effect. Perhaps the simplest thing to do is to install the dependency in jre/lib/ext? - Brett On 6/7/05, Matthew Pocock <[EMAIL PROTECTED]> wrote: > Hi, > > I've got a maven project that builds a jar that must always appear in the > bootclasspath. It's a patch for java.nio, and there's now way to get stuff > working with it added to the normal classpath. Is there some way in the > project.xml file to indicate this so that whenever it appears as a > dependancy, it is included in bootclasspath rather than classpath? If not, is > this handled by m2? > > Matthew > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bootclasspath jars
Hi, I've got a maven project that builds a jar that must always appear in the bootclasspath. It's a patch for java.nio, and there's now way to get stuff working with it added to the normal classpath. Is there some way in the project.xml file to indicate this so that whenever it appears as a dependancy, it is included in bootclasspath rather than classpath? If not, is this handled by m2? Matthew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bootclasspath from dependency
On Wednesday 07 July 2004 05:23, Brett Porter wrote:
> try ${pom.getDependencyPath('ajof:ajof')}
this work, thanks
> Probably won't work in a properties file (not sure though) - in which
> case it needs to be in maven.xml
> ...
regards,
Joachim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: bootclasspath from dependency
try ${pom.getDependencyPath('ajof:ajof')}
Probably won't work in a properties file (not sure though) - in which
case it needs to be in maven.xml
On Tue, 6 Jul 2004 13:07:43 +0200, Joachim Bader <[EMAIL PROTECTED]> wrote:
> Hi,
>
> for developing J2ME application it's necessary to overwrite the bootclasspath
> of the compiler.
>
> I do this with a property in my project.properties file:
> maven.compile.compilerargs=-bootclasspath ${basedir}/lib/classes.zip:
> ${basedir}/lib/ajof.zip
>
> disadvantage: I have to keep the bootclasspath files in my project tree.
>
> It would be nice if I can get the bootclasspath files as dependencies from my
> maven repository.
>
> regards,
> Joachim
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
bootclasspath from dependency
Hi,
for developing J2ME application it's necessary to overwrite the bootclasspath
of the compiler.
I do this with a property in my project.properties file:
maven.compile.compilerargs=-bootclasspath ${basedir}/lib/classes.zip:
${basedir}/lib/ajof.zip
disadvantage: I have to keep the bootclasspath files in my project tree.
It would be nice if I can get the bootclasspath files as dependencies from my
maven repository.
regards,
Joachim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Bootclasspath
How does one specify the the bootclasspath to the java task? I don't see it in the java plugin code. I've hard coded my custom bootclasspath into a copy of the plugin. Even better than setting a bootclasspath would be the ability to prepend jars to the bootclasspath specified by javac. I'm on OS X and it does not have $JAVA_HOME/jre/lib or rt.jar. It would be nice if I could just prepend the jars I need to prepend in order to override the XML apis that ship with the JDK. -- Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bootclasspath ?
Thanks Dominik Looked at antenna earlier and was trying to avoid using it so that wouldn't have to pack an extra jar :) On first glance it looks good - will have a play and let you and Thiago know how I get on and any potential improvements You student or faculty there ? Interesting to see Maven used in academia. > -Original Message- > From: Dominik Dahlem [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 07, 2003 4:03 PM > To: [EMAIL PROTECTED] > Cc: Maven User Mailing List (E-mail) > Subject: Re: Bootclasspath ? > > > I don't know, if this is gonna help you. Find attached a j2me plugin. > > A guy called Thiago ([EMAIL PROTECTED]) sent it to me a > while ago. I haven't tested it yet though. > > "It wraps the tasks of the Antenna > (http://antenna.sourceforge.net), and > it needs the 0.9.10 version of antenna in the > $maven.repo.local/antenna/jars/antenna-0.9.10.jar to run > and Wireless Toolkit path set in the variable $wtk.home. Test it and > give me a feedback." > > > Dominik > > > On Tue, 2003-10-07 at 15:47, Mike Gilbert wrote: > > Folks, > > > > I'm doing some work with J2ME and Maven and right now there seems > > to be no way to override the boot classpath unless you override the > > java:compile goal. Am I correct or have I missed something ? > > > > Many thanks for any suggestions, > > > > Mike Gilbert > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003 > > > > > > > > > __ > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bootclasspath ?
I don't know, if this is gonna help you. Find attached a j2me plugin. A guy called Thiago ([EMAIL PROTECTED]) sent it to me a while ago. I haven't tested it yet though. "It wraps the tasks of the Antenna (http://antenna.sourceforge.net), and it needs the 0.9.10 version of antenna in the $maven.repo.local/antenna/jars/antenna-0.9.10.jar to run and Wireless Toolkit path set in the variable $wtk.home. Test it and give me a feedback." Dominik On Tue, 2003-10-07 at 15:47, Mike Gilbert wrote: > Folks, > > I'm doing some work with J2ME and Maven and right now there seems > to be no way to override the boot classpath unless you override the > java:compile goal. Am I correct or have I missed something ? > > Many thanks for any suggestions, > > Mike Gilbert > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003 > > > > __ > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] maven-j2me-plugin-0.1.tar.gz Description: application/compressed-tar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bootclasspath ?
Folks, I'm doing some work with J2ME and Maven and right now there seems to be no way to override the boot classpath unless you override the java:compile goal. Am I correct or have I missed something ? Many thanks for any suggestions, Mike Gilbert --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
