On 31/10/2006, at 7:29 AM, Antoine Levy-Lambert wrote:
Hello Brett,
I am surprised by the concept of making a listener write the
signature.
Since the listener is working (I believe) on the build machine end
and not on the repository end, there must be a mechanism to add the
signature files to the list of files to transfer ? Does the
listener "know" which files to sign (you probably want to sign
jars, wars, zip, tgz and bz2 files, but not the md5 and sha1
files) ? Also where would you tell maven to attach this listener to
the upload process ? in POM files ? or code it in different wagon
providers ?
The listener works the same way as the checksum one in wagon does.
It's just observing the transferred stream, and when the transfer is
complete, contains the appropriate signature. It's up to the client
code to transfer that as a separate file at present.
You'll see this done for the checksums in putRemoteFile here: http://
svn.apache.org/repos/asf/maven/components/trunk/maven-artifact-
manager/src/main/java/org/apache/maven/artifact/manager/
DefaultWagonManager.java
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
