Re: xdoc escaping single quotes
wrap the tag in
On Wed, 26 Jan 2005 12:03:59 +0800, Nathan Coast <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have some links in my xdocs that look like this:
>
> onclick="javascript:window.open('http://www.codeczar.com/tomcat/codebar/page/Pages.do');">
>
> when parsed by xdoc, the single quotes are replaced by '
>
> onclick="javascript:window.open('http://www.codeczar.com/tomcat/codebar/page/Pages.do');">
>
> This is fine in moz/firefox but breaks IE. any ideas how to prevent
> this from happening?
>
> cheers
> Nathan
> --
> Nathan Coast
> Managing Director
> Codeczar Ltd
> mob : (852) 9049 5581
> tel : (852) 2834 8733
> fax : (852) 2834 8755
> web : http://www.codeczar.com
>
> -
> 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]
xdoc escaping single quotes
Hi, I have some links in my xdocs that look like this: http://www.codeczar.com/tomcat/codebar/page/Pages.do');"> when parsed by xdoc, the single quotes are replaced by ' http://www.codeczar.com/tomcat/codebar/page/Pages.do');"> This is fine in moz/firefox but breaks IE. any ideas how to prevent this from happening? cheers Nathan -- Nathan Coast Managing Director Codeczar Ltd mob : (852) 9049 5581 tel : (852) 2834 8733 fax : (852) 2834 8755 web : http://www.codeczar.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom conditionals in project.xml
There's no way to order them declaratively. Why does the processing order matter? - Brett On Tue, 25 Jan 2005 17:53:36 -0800 (PST), Doug Knesek <[EMAIL PROTECTED]> wrote: > I'll give it a try. Is there a way to control the > order of the report links if some are specified in > this manner, while others are listed in the POM? > > --- Brett Porter <[EMAIL PROTECTED]> wrote: > > > script in the POM is strongly discouraged. > > > > How about: > > > > > > > name="maven-junit-report-plugin:register" /> > > > > > > in maven.xml? > > > > - Brett > > > > > > On Tue, 25 Jan 2005 13:51:06 -0800 (PST), Doug > > Knesek > > <[EMAIL PROTECTED]> wrote: > > > I want to conditionally turn things on and off in > > my > > > project.xml based on the value of a custom > > property. > > > > > > For example, in my project.properties I defined a > > > property as follows: > > > > > > include_tests = true > > > > > > In my project.xml, I sould like to do something > > like > > > this: > > > > > > ... > > > > > >... > > > > > > maven-junit-report-plugin > > > > > >... > > > > > > > > > It doesn't seem to work. Any ideas? > > > > > > - Doug > > > > > > > > > - > > > 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] > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom conditionals in project.xml
I'll give it a try. Is there a way to control the order of the report links if some are specified in this manner, while others are listed in the POM? --- Brett Porter <[EMAIL PROTECTED]> wrote: > script in the POM is strongly discouraged. > > How about: > > > name="maven-junit-report-plugin:register" /> > > > in maven.xml? > > - Brett > > > On Tue, 25 Jan 2005 13:51:06 -0800 (PST), Doug > Knesek > <[EMAIL PROTECTED]> wrote: > > I want to conditionally turn things on and off in > my > > project.xml based on the value of a custom > property. > > > > For example, in my project.properties I defined a > > property as follows: > > > > include_tests = true > > > > In my project.xml, I sould like to do something > like > > this: > > > > ... > > > >... > > > > maven-junit-report-plugin > > > >... > > > > > > It doesn't seem to work. Any ideas? > > > > - Doug > > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to return/stop a goal in jelly script?
There's no 'stop' tag to stop the current goal for Maven. On Tue, 25 Jan 2005 12:23:10 -0600, Guo, Jiaqi <[EMAIL PROTECTED]> wrote: > In a goal definition in plugin.jelly, can I call something like value="0" /> or http://www.cyclopsgroup.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding to the classpath
Actually, it's very easy to ADD to the classpath. (I'm still trying to figure out how to easily DELETE from it) I've never tried it but I think you use it like so: -Randy Eric Giguere wrote: Hi No, and yes, explanations. No, you cannot add anything in the classpath of java:compile goal unless its a dependency declared in the project.xml and it does not support directories. But I have a solution that involved modifying (a single line) in the java plugin. If you are not afraid of producing your own plugin (very easy believe me), here is the diff between version maven-java-plugin 1.5 (official) and 1.5.1 (my custom version of java plugin): RCS file: /home/cvs/cvsroot/utilities/maven-plugins/maven-java-plugin/plugin.jelly,v retrieving revision 1.1 retrieving revision 1.2 diff -w -b -i -r1.1 -r1.2 100a101 > So basically, in the java:compile goal, you add this new element in the element of the there it is--> ... Then set this property to your directory and you're done. I've proposed this way of solving and also creating a new dependency type: directory! But no news whatsoever and by looking at the original java plugin code, you'll se that there is absolutely no other way to add an entry in the cp. Hope it helps Eric. Litton, Tom - CEPM wrote: Is there any way to add additional directories to the classpath maven uses for compiling? - 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]
Some of my thoughts on Maven
If anyone is curious, I've written a blog entry on Maven. http://kb.wrycan.com/display/WB/2005/01/25/ I had some general thoughts and questions regarding Maven, Ant, Joel Spolsky's "Law of Leaky Abstraction" and "Ruby on Rails" and tried to make a coherent piece out of them. I suppose these disparate subjects are perfect blog fodder. Comments and thoughts are welcome. Please go easy on me as it's my first blog entry ever ;-) Christopher Farnham Senior Consultant at Wrycan, Inc. [EMAIL PROTECTED] http://www.wrycan.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding to the classpath
Hi No, and yes, explanations. No, you cannot add anything in the classpath of java:compile goal unless its a dependency declared in the project.xml and it does not support directories. But I have a solution that involved modifying (a single line) in the java plugin. If you are not afraid of producing your own plugin (very easy believe me), here is the diff between version maven-java-plugin 1.5 (official) and 1.5.1 (my custom version of java plugin): RCS file: /home/cvs/cvsroot/utilities/maven-plugins/maven-java-plugin/plugin.jelly,v retrieving revision 1.1 retrieving revision 1.2 diff -w -b -i -r1.1 -r1.2 100a101 > So basically, in the java:compile goal, you add this new element in the element of the there it is--> ... Then set this property to your directory and you're done. I've proposed this way of solving and also creating a new dependency type: directory! But no news whatsoever and by looking at the original java plugin code, you'll se that there is absolutely no other way to add an entry in the cp. Hope it helps Eric. Litton, Tom - CEPM wrote: Is there any way to add additional directories to the classpath maven uses for compiling? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom conditionals in project.xml
script in the POM is strongly discouraged. How about: in maven.xml? - Brett On Tue, 25 Jan 2005 13:51:06 -0800 (PST), Doug Knesek <[EMAIL PROTECTED]> wrote: > I want to conditionally turn things on and off in my > project.xml based on the value of a custom property. > > For example, in my project.properties I defined a > property as follows: > > include_tests = true > > In my project.xml, I sould like to do something like > this: > > ... > >... > > maven-junit-report-plugin > >... > > > It doesn't seem to work. Any ideas? > > - Doug > > - > 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]
How to return/stop a goal in jelly script?
In a goal definition in plugin.jelly, can I call something like or Thanks Jiaqi http://www.cyclopsgroup.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Custom conditionals in project.xml
I want to conditionally turn things on and off in my project.xml based on the value of a custom property. For example, in my project.properties I defined a property as follows: include_tests = true In my project.xml, I sould like to do something like this: ... ... maven-junit-report-plugin ... It doesn't seem to work. Any ideas? - Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding to the classpath
Is there any way to add additional directories to the classpath maven uses for compiling?
Re: util:avaliable, core:if, core:when questions
Along the same lines - how do you do something if a file isn't avaliable? What I'm doing right now is setting a variable and then check that variable. Is there a cleaner solution? Randy Xu wrote: Is there an easy way to do something if either of two files exist? Something that accomplishes or ? And is there an easier way to do an if/else block other than , /? Thanks. -Randy - 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: Plugin version dependencies?
Check the mailing list, this was answered last week.. Additional info here: http://www.mavenblogs.org/. In short, yes, it works, just add it to your project.xml with type plugin! -Original Message- From: Russ Jubenville [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 10:37 AM To: users@maven.apache.org Subject: Plugin version dependencies? Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version to developers' machines and use that version in their builds. Meanwhile, the old version would remain in the repository, and since the production build's project.xml would still show version 1.6, it would continue to use that version for its build. Any help is greatly appreciated! ..Russ Jubenville # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal # - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
util:avaliable, core:if, core:when questions
Is there an easy way to do something if either of two files exist? Something that accomplishes or ? And is there an easier way to do an if/else block other than , /? Thanks. -Randy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugin version dependencies?
I was under the impression that this would work for a *project* within my build, where that project's artifact might be included in generated jar classpaths, bundled into ears, etc., of other projects. But here I'm talking about a *plugin* that participates in the building of those other projects themselves. It's not that those other project's classes, etc., are dependant on the new version of the plugin, but rather the build process itself is dependent on the new version of the plugin. Can I still use the SNAPSHOT approach in this case? Thanks in advance! ..Russ Jubenville -Original Message- From: Haile, Mussie [mailto:[EMAIL PROTECTED] Sent: January 25, 2005 11:21 To: Maven Users List Subject: RE: Plugin version dependencies? Why don't you use SNAPSHOT for your Dev and the correct version for your production? This way, your developers would get the least version of the build as a SNAPSHOT. L8r. -M- -Original Message- From: Russ Jubenville [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 10:37 AM To: users@maven.apache.org Subject: Plugin version dependencies? Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version to developers' machines and use that version in their builds. Meanwhile, the old version would remain in the repository, and since the production build's project.xml would still show version 1.6, it would continue to use that version for its build. Any help is greatly appreciated! ..Russ Jubenville # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: Plugin version dependencies?
Why don't you use SNAPSHOT for your Dev and the correct version for your production? This way, your developers would get the least version of the build as a SNAPSHOT. L8r. -M- -Original Message- From: Russ Jubenville [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 10:37 AM To: users@maven.apache.org Subject: Plugin version dependencies? Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version to developers' machines and use that version in their builds. Meanwhile, the old version would remain in the repository, and since the production build's project.xml would still show version 1.6, it would continue to use that version for its build. Any help is greatly appreciated! ..Russ Jubenville # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal # - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change dependency properties in maven.xml
Thanks for this reply. That solved my problem. Since, this part of the
build can not be automated in cruisecontrol it is a nice workaround.
Otherwise, a more solid solution would be necessary.
Thanks again.
Dominik
On Tue, 2005-01-25 at 13:48 +0100, Charles-Alexandre Sabourdin wrote:
> My workaround was to create an other project.xml file that inherite from my
> main project then I only have to type mavne -p project-son.xml
> Le mardi 25 Janvier 2005 12:09, Brett Porter a Ãcrit :
> > ok, I've had a look at the code. sorry, unfortunately there isn't any
> > compatible way to modify them until 1.1 is released as the old model
> > doesn't expose the properties object.
> >
> > For Maven 1.0.x, I think this will work, but it will stop working in Maven
> > 1.1: ${dep.addProperty('dependencyType:lib')}
> > ${dep.resolveProperties()}
> >
> > I'd strongly encourage seeking a workaround.
--
Dominik Dahlem <[EMAIL PROTECTED]>
---
Trinity College Dublin
Department of Computer Science,
Dublin 2, Ireland
tel: (+353) 1-608 1539
fax: (+353) 1-677 2204
www: http://www.cs.tcd.ie/Dominik.Dahlem/
---
signature.asc
Description: This is a digitally signed message part
Plugin version dependencies?
Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version to developers' machines and use that version in their builds. Meanwhile, the old version would remain in the repository, and since the production build's project.xml would still show version 1.6, it would continue to use that version for its build. Any help is greatly appreciated! ..Russ Jubenville # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
Re: change dependency properties in maven.xml [u]
My workaround was to create an other project.xml file that inherite from my
main project then I only have to type mavne -p project-son.xml
Le mardi 25 Janvier 2005 12:09, Brett Porter a écrit :
> ok, I've had a look at the code. sorry, unfortunately there isn't any
> compatible way to modify them until 1.1 is released as the old model
> doesn't expose the properties object.
>
> For Maven 1.0.x, I think this will work, but it will stop working in Maven
> 1.1: ${dep.addProperty('dependencyType:lib')}
> ${dep.resolveProperties()}
>
> I'd strongly encourage seeking a workaround.
--
Charles-Alexandre
SABOURDIN
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: remove dependencies from classpath
It seems to works thanks . Le lundi 24 Janvier 2005 16:43, Russ Jubenville a écrit : > Jar plugin: jar.manifest.classpath > > log4j > 1.2.8 > http://jakarta.apache.org/log4j/ > > true > true > > > ... -- Charles-Alexandre SABOURDIN - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nested projects in Eclipse?
--- Michael Schuerig <[EMAIL PROTECTED]> wrote: > You mean you can work with nested projects or you > can import the leaf > subprojects at the top-level? I've tried to import > jelly, > jelly/jelly-tags, and jelly-tag/xml and for the > nested projects Eclipse > complains that they overlap an existing project. I can import leaf projects at top level. ( for my use case - pico/nano & xdoclet plugins this is suffucient ) regards, = [ Konstantin Pribluda ( ko5tik ) ] Plugins for xdoclet-2 are released. check it out at: http://www.sourceforge.net/projects/xdoclet-plugins/ [ http://www.pribluda.de ] __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nested projects in Eclipse?
On Tuesday 25 January 2005 09:23, Konstantin Priblouda wrote: > --- Michael Schuerig <[EMAIL PROTECTED]> wrote: > > I'd like to make some changes in a jakarta commons > > subproject and > > preferrably I'd do this in Eclipse. Now, apparently > > Eclipse doesn't > > like nested projects, just what Maven necessitates. > > Is there a way to > > make both tools happy at the same time? > > I you use mevenide ( mevenide.codehaus.org ) and can > work with nested projects. > > You have first to "maven multiproject:goal > -Dgoal=eclipse" and then you can import subprojects > one by one. You mean you can work with nested projects or you can import the leaf subprojects at the top-level? I've tried to import jelly, jelly/jelly-tags, and jelly-tag/xml and for the nested projects Eclipse complains that they overlap an existing project. Michael -- Michael Schuerig Contests between male toads over females are mailto:[EMAIL PROTECTED] often settled by the depth of the croak. http://www.schuerig.de/michael/--John Maynard Smith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: change dependency properties in maven.xml [u]
ok, I've had a look at the code. sorry, unfortunately there isn't any
compatible way to modify them until 1.1 is released as the old model
doesn't expose the properties object.
For Maven 1.0.x, I think this will work, but it will stop working in Maven 1.1:
${dep.addProperty('dependencyType:lib')}
${dep.resolveProperties()}
I'd strongly encourage seeking a workaround.
Cheers,
Brett
On Tue, 25 Jan 2005 11:01:13 +, Dominik Dahlem
<[EMAIL PROTECTED]> wrote:
> Hi Brett.
>
> I tried that without success. I have the following code:
>
>
>
> ${dep.getProperties().setProperty('dependencyType', 'lib')}
> Added dependencyType ${dep.getProperties()}
>
>
>
> with this output:
>
> [echo] Added dependencyType []
>
> if no properties are specified in the project.xml file and this one:
>
> [echo] Added dependencyType [property:dependencyType:]
>
> if I specify the property dependencyType in the project.xml file but
> leave it empty.
>
> It appears to me that setting properties has no effect at runtime.
> Do you have another idea?
>
> Cheers,
> Dominik
>
>
> On Tue, 2005-01-25 at 21:22 +1100, Brett Porter wrote:
> > IIRC, you had to do ${dep.getProperties().setProperty('foo', 'bar')}
> >
> >
> > On Tue, 25 Jan 2005 10:20:06 +, Dominik Dahlem
> > <[EMAIL PROTECTED]> wrote:
> > > Hi Brett. I did search the archives, but I'm afraid I couldn't find a
> > > working solution. I tried another proposed solution [1], but this one
> > > only considered the dependency path disregarding the properties.
> > >
> > > Any help or pointers is appreciated.
> > > Thanks.
> > > Dominik
> > >
> > > [1] http://www.mail-archive.com/users@maven.apache.org/msg06567.html
> > >
> > >
> > > On Tue, 2005-01-25 at 06:33 +1100, Brett Porter wrote:
> > > > this was discussed recently: was there anything in the archives?
> > > >
> > > >
> > > > On Mon, 24 Jan 2005 15:24:04 +, Dominik Dahlem
> > > > <[EMAIL PROTECTED]> wrote:
> > > > > Hi all.
> > > > >
> > > > > I am in a situation where I'd like to change a property for a
> > > > > dependency
> > > > > at runtime. Depending on which goal I'm running it coud have two
> > > > > different values. So far I tried to change the property with:
> > > > >
> > > > >
> > > > >
> > > > > ${dep.setProperty('dependencyType', 'lib')}
> > > > >
> > > > >
> > > > >
> > > > > The output of
> > > > >
> > > > > ${dep.getProperty('dependencyType')}
> > > > >
> > > > > is empty.
> > > > >
> > > > > Does anyone know whether this is possible?
> > > > > Any help is appreciated.
> > > > >
> > > > > Thanks a million.
> > > > > Dominik
> > > > >
> > > > > --
> > > > > Dominik Dahlem <[EMAIL PROTECTED]>
> > > > > ---
> > > > > Trinity College Dublin
> > > > > Department of Computer Science,
> > > > > Dublin 2, Ireland
> > > > >
> > > > > tel: (+353) 1-608 1539
> > > > > fax: (+353) 1-677 2204
> > > > > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > > > > ---
> > > > >
> > > > >
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > --
> > > Dominik Dahlem <[EMAIL PROTECTED]>
> > > ---
> > > Trinity College Dublin
> > > Department of Computer Science,
> > > Dublin 2, Ireland
> > >
> > > tel: (+353) 1-608 1539
> > > fax: (+353) 1-677 2204
> > > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > > ---
> > >
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> --
> Dominik Dahlem <[EMAIL PROTECTED]>
> ---
> Trinity College Dublin
> Department of Computer Science,
> Dublin 2, Ireland
>
> tel: (+353) 1-608 1539
> fax: (+353) 1-677 2204
> www: http://www.cs.tcd.ie/Dominik.Dahlem/
> ---
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: change dependency properties in maven.xml [u]
Hi Brett.
I tried that without success. I have the following code:
${dep.getProperties().setProperty('dependencyType', 'lib')}
Added dependencyType ${dep.getProperties()}
with this output:
[echo] Added dependencyType []
if no properties are specified in the project.xml file and this one:
[echo] Added dependencyType [property:dependencyType:]
if I specify the property dependencyType in the project.xml file but
leave it empty.
It appears to me that setting properties has no effect at runtime.
Do you have another idea?
Cheers,
Dominik
On Tue, 2005-01-25 at 21:22 +1100, Brett Porter wrote:
> IIRC, you had to do ${dep.getProperties().setProperty('foo', 'bar')}
>
>
> On Tue, 25 Jan 2005 10:20:06 +, Dominik Dahlem
> <[EMAIL PROTECTED]> wrote:
> > Hi Brett. I did search the archives, but I'm afraid I couldn't find a
> > working solution. I tried another proposed solution [1], but this one
> > only considered the dependency path disregarding the properties.
> >
> > Any help or pointers is appreciated.
> > Thanks.
> > Dominik
> >
> > [1] http://www.mail-archive.com/users@maven.apache.org/msg06567.html
> >
> >
> > On Tue, 2005-01-25 at 06:33 +1100, Brett Porter wrote:
> > > this was discussed recently: was there anything in the archives?
> > >
> > >
> > > On Mon, 24 Jan 2005 15:24:04 +, Dominik Dahlem
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hi all.
> > > >
> > > > I am in a situation where I'd like to change a property for a dependency
> > > > at runtime. Depending on which goal I'm running it coud have two
> > > > different values. So far I tried to change the property with:
> > > >
> > > >
> > > >
> > > > ${dep.setProperty('dependencyType', 'lib')}
> > > >
> > > >
> > > >
> > > > The output of
> > > >
> > > > ${dep.getProperty('dependencyType')}
> > > >
> > > > is empty.
> > > >
> > > > Does anyone know whether this is possible?
> > > > Any help is appreciated.
> > > >
> > > > Thanks a million.
> > > > Dominik
> > > >
> > > > --
> > > > Dominik Dahlem <[EMAIL PROTECTED]>
> > > > ---
> > > > Trinity College Dublin
> > > > Department of Computer Science,
> > > > Dublin 2, Ireland
> > > >
> > > > tel: (+353) 1-608 1539
> > > > fax: (+353) 1-677 2204
> > > > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > > > ---
> > > >
> > > >
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > --
> > Dominik Dahlem <[EMAIL PROTECTED]>
> > ---
> > Trinity College Dublin
> > Department of Computer Science,
> > Dublin 2, Ireland
> >
> > tel: (+353) 1-608 1539
> > fax: (+353) 1-677 2204
> > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > ---
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Dominik Dahlem <[EMAIL PROTECTED]>
---
Trinity College Dublin
Department of Computer Science,
Dublin 2, Ireland
tel: (+353) 1-608 1539
fax: (+353) 1-677 2204
www: http://www.cs.tcd.ie/Dominik.Dahlem/
---
signature.asc
Description: This is a digitally signed message part
Re: change dependency properties in maven.xml [u]
IIRC, you had to do ${dep.getProperties().setProperty('foo', 'bar')}
On Tue, 25 Jan 2005 10:20:06 +, Dominik Dahlem
<[EMAIL PROTECTED]> wrote:
> Hi Brett. I did search the archives, but I'm afraid I couldn't find a
> working solution. I tried another proposed solution [1], but this one
> only considered the dependency path disregarding the properties.
>
> Any help or pointers is appreciated.
> Thanks.
> Dominik
>
> [1] http://www.mail-archive.com/users@maven.apache.org/msg06567.html
>
>
> On Tue, 2005-01-25 at 06:33 +1100, Brett Porter wrote:
> > this was discussed recently: was there anything in the archives?
> >
> >
> > On Mon, 24 Jan 2005 15:24:04 +, Dominik Dahlem
> > <[EMAIL PROTECTED]> wrote:
> > > Hi all.
> > >
> > > I am in a situation where I'd like to change a property for a dependency
> > > at runtime. Depending on which goal I'm running it coud have two
> > > different values. So far I tried to change the property with:
> > >
> > >
> > >
> > > ${dep.setProperty('dependencyType', 'lib')}
> > >
> > >
> > >
> > > The output of
> > >
> > > ${dep.getProperty('dependencyType')}
> > >
> > > is empty.
> > >
> > > Does anyone know whether this is possible?
> > > Any help is appreciated.
> > >
> > > Thanks a million.
> > > Dominik
> > >
> > > --
> > > Dominik Dahlem <[EMAIL PROTECTED]>
> > > ---
> > > Trinity College Dublin
> > > Department of Computer Science,
> > > Dublin 2, Ireland
> > >
> > > tel: (+353) 1-608 1539
> > > fax: (+353) 1-677 2204
> > > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > > ---
> > >
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> --
> Dominik Dahlem <[EMAIL PROTECTED]>
> ---
> Trinity College Dublin
> Department of Computer Science,
> Dublin 2, Ireland
>
> tel: (+353) 1-608 1539
> fax: (+353) 1-677 2204
> www: http://www.cs.tcd.ie/Dominik.Dahlem/
> ---
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: change dependency properties in maven.xml [u]
Hi Brett. I did search the archives, but I'm afraid I couldn't find a
working solution. I tried another proposed solution [1], but this one
only considered the dependency path disregarding the properties.
Any help or pointers is appreciated.
Thanks.
Dominik
[1] http://www.mail-archive.com/users@maven.apache.org/msg06567.html
On Tue, 2005-01-25 at 06:33 +1100, Brett Porter wrote:
> this was discussed recently: was there anything in the archives?
>
>
> On Mon, 24 Jan 2005 15:24:04 +, Dominik Dahlem
> <[EMAIL PROTECTED]> wrote:
> > Hi all.
> >
> > I am in a situation where I'd like to change a property for a dependency
> > at runtime. Depending on which goal I'm running it coud have two
> > different values. So far I tried to change the property with:
> >
> >
> >
> > ${dep.setProperty('dependencyType', 'lib')}
> >
> >
> >
> > The output of
> >
> > ${dep.getProperty('dependencyType')}
> >
> > is empty.
> >
> > Does anyone know whether this is possible?
> > Any help is appreciated.
> >
> > Thanks a million.
> > Dominik
> >
> > --
> > Dominik Dahlem <[EMAIL PROTECTED]>
> > ---
> > Trinity College Dublin
> > Department of Computer Science,
> > Dublin 2, Ireland
> >
> > tel: (+353) 1-608 1539
> > fax: (+353) 1-677 2204
> > www: http://www.cs.tcd.ie/Dominik.Dahlem/
> > ---
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Dominik Dahlem <[EMAIL PROTECTED]>
---
Trinity College Dublin
Department of Computer Science,
Dublin 2, Ireland
tel: (+353) 1-608 1539
fax: (+353) 1-677 2204
www: http://www.cs.tcd.ie/Dominik.Dahlem/
---
signature.asc
Description: This is a digitally signed message part
Re: Nested projects in Eclipse?
--- Michael Schuerig <[EMAIL PROTECTED]> wrote: > > I'd like to make some changes in a jakarta commons > subproject and > preferrably I'd do this in Eclipse. Now, apparently > Eclipse doesn't > like nested projects, just what Maven necessitates. > Is there a way to > make both tools happy at the same time? I you use mevenide ( mevenide.codehaus.org ) and can work with nested projects. You have first to "maven multiproject:goal -Dgoal=eclipse" and then you can import subprojects one by one. regards, = [ Konstantin Pribluda ( ko5tik ) ] Plugins for xdoclet-2 are released. check it out at: http://www.sourceforge.net/projects/xdoclet-plugins/ [ http://www.pribluda.de ] __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
