Re: [VOTE][RESULT] add Nicolas Lalevée as committer
Le jeudi 21 février 2008, Xavier Hanin a écrit : Hi All, With 13 binding +1, 1 non binding, and one accordez moi, I'm pleased to announce that this vote passed successfully. Nicolas, we are honoured to welcome you as a new Apache Ant committer. I will contact you in private to give you some details on what you need to do now to wear your ASF committer hat :-) Welcome aboard! I am honoured to be part of the Apache family. :) Following the tradition let's introduce myself. I am 27 years old, french, and I live in Toulouse, while being in the heart a mediterranean as all my childhood was in front of the see. I started to not only use computers but try to improve them with a Ti-89 calculator [1]. So I started at a very low level with some 68k asm, and then I quickly learned C to avoid some headache. Then I discovered Java in my french engineering school which I found pretty cool in transforming segmentation faults into NPEs. After my graduation I did an internship at Anyware Technologies where I discovered the web applications, the open source and the Apache Foundation via Sylvain Wallez. Thank you Sylvain for introducing me to the Apache projects, but most of all to the community aspect of the foundation. Working on different projects I learned first about Cocoon, then I did some Eclipse plugins. After that I deeply looked into Lucene, also OpenRDF, and learned about Ivy after some maven frustration. I also get interested by Husdon, did an Ivy plugin and became a committer there. Then little on my own (I would like to thank my managers to allow me to do so) I decided to try to make IvyDE work because I was bugging me and a lot of my colleagues, forcing us to use some tricks. I had some difficulties to enter into the Eclipse JDT framework, but some thread on the ivy user mailing list keep me investigating bugs. Now that I know deeper Eclipse, I will continue to improve IvyDE because I think that even if Ant + Ivy can be a standalone core build system, tools for users do make the difference between a application and a great application. Thank you everyone! Nicolas [1] http://www.hibnet.org/ti.php PS: special dedication to my father who wrote me a dedication in his book : you have to contribute to the open source !. Done dad ! ;) Xavier On Wed, Feb 13, 2008 at 10:35 AM, Xavier Hanin [EMAIL PROTECTED] wrote: Hi All, Nicolas Lalevée has contributed a lot of patches to Ivy and IvyDE [1 to 10], and has been actively involved in several discussions, especially about IvyDE. He is always fair when giving his opinion, and often try to help other users. IvyDE is a subproject of Ivy considered as highly important by several users [11], and Nicolas is greatly helping to improve it. So I think he would make a good addition to our developer team, hence this is a vote to make him a new committer. Even though only votes cast by PMC members are binding [12], all votes are welcome and important to us. Here's my vote: +1 Xavier [1] https://issues.apache.org/jira/browse/IVY-704 [2] https://issues.apache.org/jira/browse/IVY-702 [3] https://issues.apache.org/jira/browse/IVY-646 [4] https://issues.apache.org/jira/browse/IVYDE-62 [5] https://issues.apache.org/jira/browse/IVYDE-69 [6] https://issues.apache.org/jira/browse/IVYDE-66 [7] https://issues.apache.org/jira/browse/IVYDE-64 [8] https://issues.apache.org/jira/browse/IVYDE-76 [9] https://issues.apache.org/jira/browse/IVYDE-68 [10] https://issues.apache.org/jira/browse/IVYDE-63 [11] http://www.nabble.com/ivyde-again-td15352211.html#a15352211 [12] http://ant.apache.org/bylaws.html#Decision%20Making -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ -- Nicolas LALEVÉE ANYWARE TECHNOLOGIES Tel : +33 (0)5 61 00 52 90 Fax : +33 (0)5 61 00 51 46 http://www.anyware-tech.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging rev 628990 to the 1.7.x branch
Hi Stefan, I've got the code copied across - though the merge tool didn't so I had to do it manually. I don't suppose this matters but I'd like to know why svn merge did nowt Looking at your commit, you merged a bit more than just my patch from trunk. My guess is that my patch affected some of the changed lines (different Javadocs, for example) and couldn't be merged automatically because that other change wasn't present in the branch's version. We'll also need to modify the WHATSNEW file (I forgot that) and might want to add some @since tags. I'll do it in parallel on both branches, hope you don't mind. No problem, thanks for checking it Kev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Set up folder permission in Windows with Ant
lawardy wrote: Hi, I'm a new user of ant. I am trying to set up a folder and need to set up certain permission on it (read, write and execute permission)Is it possible to do with ant? Any idea of how to do that. 1. this is the kind of question for the ant users list 2. Windows? it doesnt have that usable a permissions model. You need to edit ACLs, which you can do by exec-ing CACLS: cacls /? Displays or modifies access control lists (ACLs) of files CACLS filename [/T] [/E] [/C] [/G user:perm] [/R user [...]] [/P user:perm [...]] [/D user [...]] filename Displays ACLs. /TChanges ACLs of specified files in the current directory and all subdirectories. /EEdit ACL instead of replacing it. /CContinue on access denied errors. /G user:perm Grant specified user access rights. Perm can be: R Read W Write C Change (write) F Full control /R user Revoke specified user's access rights (only valid with /E). /P user:perm Replace specified user's access rights. Perm can be: N None R Read W Write C Change (write) F Full control /D user Deny specified user access. Wildcards can be used to specify more that one file in a command. You can specify more than one user in a command. Abbreviations: CI - Container Inherit. The ACE will be inherited by directories. OI - Object Inherit. The ACE will be inherited by files. IO - Inherit Only. The ACE does not apply to the current file/directory. I would advise you avoid it unless you know what you are going. To create zip/tar files with permissions, use zipfileset and tarfileset filesets with explicitly listed permssions. -- Steve Loughran http://www.1060.org/blogxter/publish/5 Author: Ant in Action http://antbook.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xmlproperties task
What I think you are missing is that the XML hierarchy translates into
the name of the property. This is true whether you use Semantic
Attributes or not, since they do not alter the name.
Your XML file actually defines the same property name over and over
again. If keepRoot were set to true, this would be
properties.property, but since you specify that the root tag should be
ignored, the one property name is named property.
What your XML should look like to get the results you want is:
properties
dispatcher
themepelt/theme
theme-ext.fv/theme-ext
/dispatcher
/properties
Leave keepRoot set to false, and you don't need semanticAttributes
unless you prefer using the value attribute instead of the contents of
the tag or if you want to use Ant references inside the configuration file.
Thorsten Scherler wrote:
Hi all,
we at forrest are in the middle to harmonize the definition of our
properties system and we want to switch to an xml based on
(forrest.properties.xml).
We already use this file in the rest of our application. The format is
as follow:
properties
property name=dispatcher.theme value=pelt/
property name=dispatcher.theme-ext value=.fv/
/properties
Doing a change in our core ant build did not brought the expected
result.
Index: forrest.build.xml
===
--- forrest.build.xml (revision 629705)
+++ forrest.build.xml (working copy)
@@ -77,6 +77,9 @@
!-- people should use -D switch, or antpropertys to override these
--
property name=project.home location=. /
-property file=${project.home}/forrest.properties /
+xmlproperty file=${project.home}/forrest.properties.xml
+ semanticAttributes=true keepRoot=false/
+echoproperties destfile=${project.home}/filter.properties/
The last line is for debugging, but till now I did not get the
properties as I want them.
It will result in something like:
property=pelt,.fv,group,project
property.name=dispatcher.theme,dispatcher.theme-ext,group-name,project-name
However regarding
http://ant.apache.org/manual/CoreTasks/xmlproperty.html if I enable
semanticAttributes and use the above file slightly alternated:
properties
!--
# codename: Dispatcher
# Dispatcher is using a fallback mechanism for theming.
# You can configure the theme name and its extension here
--
property id=dispatcher.theme value=pelt/
property id=dispatcher.theme-ext value=.fv/
...
I expected to find
dispatcher.theme=pelt
but i now only get:
property=pelt,.fv,group,project
My question is, is this a bug or have I overlooked something?
salu2
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
