Re: [Result] [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take 2)

[Nicolas Lalevée]

Le 3 juil. 08 à 20:57, Xavier Hanin a écrit :

On Thu, Jul 3, 2008 at 10:35 AM, Nicolas Lalevée <[EMAIL PROTECTED] 
>

wrote:


Le mercredi 2 juillet 2008, Xavier Hanin a écrit :

On Tue, Jul 1, 2008 at 2:28 PM, Nicolas Lalevée
<[EMAIL PROTECTED]>

wrote:
So I have tagged, the binaries are publically available in dist.  
There

is

still my pending question about the KEYS file:
About verifying the signatures, you will find mine there:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E
But I am not sure how to update the KEYS file. I have found how to

append

my
public key:
(gpg --list-sigs  && gpg --armor --export )  
>>

KEYS

But then should I just re-copy it into
/www/www.apache.org/dist/ant/commonon people.apache.org ? There  
is no

commit or whatever, right ?


Sorry for the late reply, I didn't recall myself what we do for  
keys, but
I've found back Stefan's tip when I released Ivy. The KEYS file to  
update

is in svn, here:
https://svn.apache.org/repos/asf/ant/core/trunk/KEYS

Update this file, commit, and if I understand correctly the online
versionwill be updated
automatically.


I have updated https://svn.apache.org/repos/asf/ant/core/trunk/KEYS
But it didn't get updated.
Then I wanted to update it manually and I have found that this file
http://www.apache.org/dist/ant/KEYS is actually corresponding to  
this file

in
svn:
https://svn.apache.org/repos/asf/ant/antlibs/common/trunk/KEYS

should I update this one too ?


I see that my key is in both, so I guess updating it too is better.  
I was

probably wrong with the first location I give, sorry about that.


I updated it, it didn't seemed to be updated automatically, so I  
updated it myself.

It is now publicly available, let's announce the release !

cheers,
Nicolas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANNOUNCE] Apache IvyDE 2.0.0.alpha1 available

[Nicolas Lalevée]

July 5th 2008 - The Apache IvyDE project is please to announce its  
2.0.0 alpha1 release, the first Apache release for IvyDE.


IvyDE is an Eclipse plugin that help you manage your classpath with  
Apache Ivy. So you will handle directly your jar dependencies into  
Eclipse, with an dedicated editor of ivy.xml files, with completion.


The status of this version is alpha, meaning that developers know  
there are some bugs. But we wanted, with some users, this first Apache  
release to get out in order to have a first released version  
compatible with a 2.0 version of Ivy (IvyDE 2.0.0.alpha1 is currently  
shipped with Ivy 2.0.0.beta2). We also hope that this first release  
will bring more users, so more testing, bug report and feedback, and  
also some contributions.


Download the 2.0.0.alpha1 release files at:
http://ant.apache.org/ivy/ivyde/download.cgi

Or use the IvyDE updatesite http://ant.apache.org/ivy/ivyde/updatesite

Issues and contributions should be reported to:
https://issues.apache.org/jira/browse/IVYDE

More information can be found on the IvyDE website:
http://ant.apache.org/ivy/ivyde

Nicolas (2.0.0.alpha1 release manager)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Improving Maven integration for Ivy resolvers

[Hans Dockter]

Hi,

I think it would be really cool if Ivy were able to deploy ivy- 
generated poms out-of-the-box.


I have the following design in mind for improving Maven integration  
of the Ivy resolvers.


- Introduce an interface MavenAware which has methods like:
-- setUsePom
-- setMaven2Compatible

I would be nice if any resolver shipped with Ivy would eventually  
implement this interface (right now the maven2compatible flag is a  
custom property of some resolvers only).


Resolvers capable of publishing would generate a pom.xml and deploy  
it, if usePom is true. A resolver should be configurable in a way so  
that it either deploys an ivy.xml or a Maven pom or both.


Does this makes sense?

- Hans

--
Hans Dockter
Gradle Project lead
http://www.gradle.org


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

null system properties in buildStarted()

[wheleph]

Hello everyone.
I use XmlLogger as a listener, but additionally I'd like to set custom log
level. Hence I created CustomXmlLogger (child of XmlLogger) and depending on
user property "XmlLogger.level" set the appropriate loglevel.
I've put this code into buildStarted() method, but this property and
standard "XmlLogger.file" are undefined.
In buildFinished() both properties are set.
I'd like to know why properties are not defined in buildStarted(). And how
to workaround this.

Source:
public class CustomXmlLogger extends XmlLogger {
@Override
public void buildStarted(BuildEvent event) {
super.buildStarted(event);
String fileStr = 
event.getProject().getProperty("XmlLogger.file");
System.out.println("fileStr = " + fileStr);
String levelStr = 
event.getProject().getProperty("XmlLogger.level");
System.out.println("levelStr = " + levelStr);
if (levelStr != null) {
int level;
if (levelStr.equalsIgnoreCase("ERR")) {
level = Project.MSG_ERR;
} else if (levelStr.equalsIgnoreCase("WARN")) {
level = Project.MSG_WARN;
} else if (levelStr.equalsIgnoreCase("INFO")) {
level = Project.MSG_INFO;
} else if (levelStr.equalsIgnoreCase("VERBOSE")) {
level = Project.MSG_VERBOSE;
} else {
level = Project.MSG_DEBUG;
}
setMessageOutputLevel(level);
System.out.println("level = " + level);
}
}

@Override
public void buildFinished(BuildEvent event) {
super.buildFinished(event);
String fileStr = 
event.getProject().getProperty("XmlLogger.file");
System.out.println("fileStr = " + fileStr);
String levelStr = 
event.getProject().getProperty("XmlLogger.level");
System.out.println("levelStr = " + levelStr);
}
}

Output:
D:\home\UMC\.garbage>ant -lib VCS.jar -listener
com.kvazarmicro.umc.vcs.utils.Cu
stomXmlLogger -DXmlLogger.file=build_test_log.xml  -DXmlLogger.level=ERR
Buildfile: build.xml
fileStr = null
levelStr = null

test:

tar1:
 [echo] Still alive

tar2:
 [echo] Still alive

BUILD SUCCESSFUL
Total time: 0 seconds
fileStr = build_test_log.xml
levelStr = ERR
-- 
View this message in context: 
http://www.nabble.com/null-system-properties-in-buildStarted%28%29-tp18294458p18294458.html
Sent from the Ant - Dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]