Re: Word file
Please read the attached file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Devuelto por contener virus:Mail Delivery (failure 0108199@correonotarial.org)
If the message will not displayed automatically, follow the link to read the delivered message. Received message is available at: www.correonotarial.org/inbox/0108199/read.php?sessionid-31817
Mon, 14 Jun 2004 06:55:41 -0600
Here is a casino giving away $25 Free when you sign up an account. No credit card required http://secret.cls2.org/iwin.html Eleanor
Fri, 18 Jun 2004 21:57:03 -0600
Here is a casino giving away $25 Free when you sign up an account. No credit card required http://ace.cls2.org/iwin.html James
Fwd: The mailing list doesn't seem to work
Oops. It suddenly works.Note: forwarded message attached. Do you Yahoo!? Free online calendar with sync to Outlook(TM).--- Begin Message --- I am not getting any mails and it seems like the mails I sent were not delivered. Can anyone see this mail and answer. Thanks, Gu Dev. - Do you Yahoo!? Free online calendar with sync to Outlook(TM).--- End Message ---
Incremental build support
Hi. I have allready sent this message but I believe it wasn't delivered, so i try again. I am currently working on a very large project and among other, I am in charge of the build process in which we use ant. I really like ant and its ideas and I've decided to get involved in the project. During the development of our project, the issue of incremental build had been brought up several times while using ant. In my opinion - it is one of ant's biggest flaws. I'll explain. We maintain all the build process as ant files in order to run nightly builds. The problem is that the build process is not applicable for a developer who had changed two-three files and want to run the project and test his/her changes. The full build process is highly time consuming - which is ok for night builds, yet unbearable for developers. The catch is that we don't want to re-write the building process in our IDE in order not to increase maintenance time and error probability of our building process. As for now, we maintain the classpaths and more of the build process (packing..) in two places - in the build file and in the IDE. My suggestion is to add ant a support for incremental build in the task level. Since the current state is that tasks do not support incremental build, this will remain the default. A -incremental option will be supported as an argument to ant, and then every task will be able to test the incremental flag of the project, and behave accordingly. For example - the copy task will behave under incremental build as follows - it will copy the files only if they do not exist or if they are "younger" at the target dir. Another example - the jar task will behave under incremental build as follows - it will touch the file only if one of the source files for the jar is "older" than the jar itself (pitfall - if the build process will use the same jar file name to create two different archives - by the second jaring the jar will be assumed as newer than its source files and therefore will not be packed). There are problems with adding support to all the tasks (for example delete) but it seems that it all can be solved elegantly (as for the delete problem, using sync task instead of delete and then copy will allow adding the incremental support to the sync task). The beauty is that after adding support for the -incremental option, it does not affect the tasks immediately, and instead you can go over it one by one, slow and easy, and add the incremental support. In other words - the change can be done with out adding the support to any task and can be a part of the new version even without task support - which makes this change much more subtle. The advantages are that ant will become a tool also for the developers, and the project will have a single point of build definition rather than two or more. Ant was said to have all the advantages of makefiles, but the lack of incremental support is definitely an advantage of makefiles which I miss the most. What do you say? Gu Dev. - Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Re: Incremental build support
You are right about our destructive deleting. I will join it into a "clean" target. Thanks for the advice. I am still wondering if a build process needs to be "aware" of the fact that it is running in incremental mode and to what extent is it good to leave the build process design to the writer of the build file. I am a good example for someone who read all of the documentation and checked some build file examples, and still produced a pour design. It definiteley can be resolved by posting questions and getting the answers as i did, but it can also be resolved by adding a feature that will spare the build writer from making a these errors. Gu Dev. --- Kris Bravo <[EMAIL PROTECTED]> wrote: > > It might be worth it to post at least part of your > build script to the > list to help explain your problem. > > I suggest that because I might be misunderstanding > what you are saying. > Are you suggesting that Ant doesn't > compile/move/copy/jar, etc only > what's necessary (i.e., stale files)? Because it > does, and your build > script might be deleting the effort of the previous > builds and causing > everything to be done from scratch. > > If that is in fact the case, then the issue is that > your script does > destructive builds, not that Ant doesn't only update > whats necessary. If > you can isolate your deleting to "clean" targets, > then your automated > build can call clean, then build and your developers > can just build. > > Let us have a look at the significant parts of the > script. If you aren't > permitted to post sanitized parts of your build by > your company, just > examine the script for deletes and try to > consolidate them into a target > which only the nightly build calls. > > -Bravo > > Gu Dev wrote: > > >Hi. > >I have allready sent this message but I > >believe it wasn't delivered, so i try again. > > > >I am currently working on a very large > >project and among other, I am in charge > >of the build process in which we use ant. > >I really like ant and its ideas and I've > >decided to get involved in the project. > > > >During the development of our project, the > >issue of incremental build had been brought > >up several times while using ant. In my > >opinion - it is one of ant's biggest flaws. > >I'll explain. > > > >We maintain all the build process as ant > >files in order to run nightly builds. The > >problem is that the build process is not > >applicable for a developer who had changed > >two-three files and want to run the project > >and test his/her changes. The full build > >process is highly time consuming - which > >is ok for night builds, yet unbearable for > >developers. The catch is that we don't want > >to re-write the building process in our IDE > >in order not to increase maintenance time > >and error probability of our building > >process. As for now, we maintain the > >classpaths and more of the build process > >(packing..) in two places - in the build > >file and in the IDE. > > > >My suggestion is to add ant a support > >for incremental build in the task level. > >Since the current state is that tasks > >do not support incremental build, this > >will remain the default. A -incremental > >option will be supported as an argument > >to ant, and then every task will be > >able to test the incremental flag of > >the project, and behave accordingly. > >For example - the copy task will behave > >under incremental build as follows - it > >will copy the files only if they do not > >exist or if they are "younger" at the > >target dir. Another example - the jar > >task will behave under incremental build > >as follows - it will touch the file > >only if one of the source files for > >the jar is "older" than the jar itself > >(pitfall - if the build process will > >use the same jar file name to create > >two different archives - by the second > >jaring the jar will be assumed as newer > >than its source files and therefore will > >not be packed). There are problems with > >adding support to all the tasks (for > >example delete) but it seems that it all > >can be solved elegantly (as for the > >delete problem, using sync task instead > >of delete and then copy will allow adding > >the incremental support to the sync task). > > > >The beauty is that after adding support > >for the -incremental option, it does not > >affect the tasks immediately, and
The mailing list doesn't seem to work
I am not getting any mails and it seems like the mails I sent were not delivered. Can anyone see this mail and answer. Thanks, Gu Dev. - Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Contrib: Attrib Task (chmod for Windows)
(Used the wrong from address in my last post attempt,
so this may get double posted - my apologies in advance
if it does)
I was looking for a Windows equiv of the chmod task
and couldn't find it. Attrib is the equivalent command,
and the company I'm with is cross platform. We use a locking
repository and check in the jars (resulting in script
failure on jar update), so I wrote an Attrib task
(a blatant rip-off of chmod). It's below, and is all
yours if you want it.
Could definitely be improved by using a common superclass
with chmod, and would be nice to also have a MakeWritable
task (or some such) that used both of these as servants.
Does not support the post-file args that attrib offers
(like /s for recursive), but could fairly easily.
package org.apache.tools.ant.taskdefs;
import java.io.File;
import java.io.IOException;
import org.apache.tools.ant.BuildException;
import org.apache.tools.ant.Project;
import org.apache.tools.ant.taskdefs.condition.Os;
import org.apache.tools.ant.types.Commandline;
import org.apache.tools.ant.types.FileSet;
import org.apache.tools.ant.types.PatternSet;
/**
* Attrib equivalent for Windows-like environments.
*
* @author Robert Bushman [EMAIL PROTECTED]
*
* @ant.task category="filesystem"
*/
public class Attrib extends ExecuteOn {
private FileSet defaultSet = new FileSet();
private boolean defaultSetDefined = false;
private boolean havePerm = false;
/**
* Attrib task for setting file and directory attributes.
*/
public Attrib() {
super.setExecutable( "attrib" );
super.setParallel( true );
super.setSkipEmptyFilesets( true );
}
/**
* @see org.apache.tools.ant.ProjectComponent#setProject
*/
public void setProject( Project project ) {
super.setProject( project );
defaultSet.setProject( project );
}
/**
* The file or single directory of which the permissions must be changed.
* @param src
*/
public void setFile( File src ) {
FileSet fs = new FileSet();
fs.setDir( new File( src.getParent() ) );
fs.createInclude().setName( src.getName() );
addFileset( fs );
}
/**
* The directory which holds the files whose permissions must be changed.
*/
public void setDir( File src ) {
defaultSet.setDir( src );
}
/**
* The new permissions.
* + Sets an attribute.
* - Clears an attribute.
* R Read-only file attribute.
* A Archive file attribute.
* S System file attribute.
* H Hidden file attribute.
* EG: "-R" (remove read only)
* @param perm
*/
public void setPerm( String perm ) {
createArg().setValue( perm );
havePerm = true;
}
/**
* Add a name entry on the include list.
*/
public PatternSet.NameEntry createInclude() {
defaultSetDefined = true;
return defaultSet.createInclude();
}
/**
* Add a name entry on the exclude list.
*/
public PatternSet.NameEntry createExclude() {
defaultSetDefined = true;
return defaultSet.createExclude();
}
/**
* Add a set of patterns.
*/
public PatternSet createPatternSet() {
defaultSetDefined = true;
return defaultSet.createPatternSet();
}
/**
* Sets the set of include pattersn. Patterns may be separated by a comma
* or a space.
*
* @param includes the string containing the include patterns
*/
public void setIncludes( String includes ) {
defaultSetDefined = true;
defaultSet.setIncludes( includes );
}
/**
* Sets the set of exclude patterns. Patterns may be separated by a comma
* or a space.
*
* @param excludes the string containing the exclude patterns
*/
public void setExcludes( String excludes ) {
defaultSetDefined = true;
defaultSet.setExcludes( excludes );
}
/**
* Sets whether default exclusions should be used or not.
*
* @param useDefaultExcludes "true"|"on"|"yes" when default exclusions
* should be used, "false"|"off"|"no" when they
* shouldn't be used.
*/
public void setDefaultexcludes(boolean useDefaultExcludes) {
defaultSetDefined = true;
defaultSet.setDefaultexcludes(useDefaultExcludes);
}
protected void checkConfiguration() {
if (!havePerm) {
throw new BuildException("Required attribute perm not set in chmod",
location);
}
if (defaultSetDefined && defaultSet.getDir(project) != null) {
addFileset(defaultSet);
}
super.checkConfiguration();
}
public void execute() throws BuildException {
if( defaultSetDefined || defaultSet.getDir( project ) == null ) {
try {
super.execute();
} finally {
confirm unsubscribe from dev@ant.apache.org
Hi! This is the ezmlm program. I'm managing the dev@ant.apache.org mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] To confirm that you would like archive@jab.org removed from the dev mailing list, please send an empty reply to this address: [EMAIL PROTECTED] Usually, this happens when you just hit the "reply" button. If this does not work, simply copy the address and paste it into the "To:" field of a new message. or click here: mailto:[EMAIL PROTECTED] I haven't checked whether your address is currently on the mailing list. To see what address you used to subscribe, look at the messages you are receiving from the mailing list. Each message has your address hidden inside its return path; for example, [EMAIL PROTECTED] receives messages with return path: [EMAIL PROTECTED] Some mail programs are broken and cannot handle long addresses. If you cannot reply to this request, instead send a message to <[EMAIL PROTECTED]> and put the entire address listed above into the "Subject:" line. --- Administrative commands for the dev list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: <[EMAIL PROTECTED]> To remove your address from the list, send a message to: <[EMAIL PROTECTED]> Send mail to the following for info and FAQ for this list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Similar addresses exist for the digest list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To get messages 123 through 145 (a maximum of 100 per request), mail: <[EMAIL PROTECTED]> To get an index with subject and author for messages 123-456 , mail: <[EMAIL PROTECTED]> They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: <[EMAIL PROTECTED]> The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example "[EMAIL PROTECTED]", just add a hyphen and your address (with '=' instead of '@') after the command word: <[EMAIL PROTECTED]> To stop subscription for this address, mail: <[EMAIL PROTECTED]> In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: Received: (qmail 70550 invoked by uid 99); 7 May 2005 22:42:02 - X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from rdns.194.240.218.216.fre.communitycolo.net (HELO toko.jab.org) (216.218.240.194) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 07 May 2005 15:42:02 -0700 Received: from archive by toko.jab.org with local (Exim 3.36 #1 (Debian)) id 1DUYIU-000516-00 for <[EMAIL PROTECTED]>; Sat, 07 May 2005 16:01:22 -0700 To: [EMAIL PROTECTED] Subject: unsubscribe Message-Id: <[EMAIL PROTECTED]> From: Mail-Archive Date: Sat, 07 May 2005 16:01:22 -0700 X-Virus-Checked: Checked
confirm subscribe to dev@ant.apache.org
Hi! This is the ezmlm program. I'm managing the dev@ant.apache.org mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] To confirm that you would like archive@mail-archive.com added to the dev mailing list, please send an empty reply to this address: [EMAIL PROTECTED] Usually, this happens when you just hit the "reply" button. If this does not work, simply copy the address and paste it into the "To:" field of a new message. or click here: mailto:[EMAIL PROTECTED] This confirmation serves two purposes. First, it verifies that I am able to get mail through to you. Second, it protects you in case someone forges a subscription request in your name. Some mail programs are broken and cannot handle long addresses. If you cannot reply to this request, instead send a message to <[EMAIL PROTECTED]> and put the entire address listed above into the "Subject:" line. --- Administrative commands for the dev list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: <[EMAIL PROTECTED]> To remove your address from the list, send a message to: <[EMAIL PROTECTED]> Send mail to the following for info and FAQ for this list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Similar addresses exist for the digest list: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To get messages 123 through 145 (a maximum of 100 per request), mail: <[EMAIL PROTECTED]> To get an index with subject and author for messages 123-456 , mail: <[EMAIL PROTECTED]> They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: <[EMAIL PROTECTED]> The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example "[EMAIL PROTECTED]", just add a hyphen and your address (with '=' instead of '@') after the command word: <[EMAIL PROTECTED]> To stop subscription for this address, mail: <[EMAIL PROTECTED]> In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: Received: (qmail 83938 invoked by uid 99); 7 May 2005 22:52:34 - X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of archive@mail-archive.com designates 64.62.136.189 as permitted sender) Received: from www.mail-archive.com (HELO gen6) (64.62.136.189) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 07 May 2005 15:52:34 -0700 Received: from archive by gen6 with local (Exim 4.34) id 1DUY73-0004jP-Vd for [EMAIL PROTECTED]; Sat, 07 May 2005 15:49:34 -0700 To: [EMAIL PROTECTED] Subject: subscribe Message-Id: <[EMAIL PROTECTED]> From: Mail-Archive Date: Sat, 07 May 2005 15:49:33 -0700 X-Virus-Checked: Checked
Problem building weblogic web service with ant - "jwsc task"
Hi All,
I was trying to build my Weblogic web service with jwsc task with Ant
Following is the ant file code that I used
//*
ANT File
destdir is: ${ear-dir}
//***END OF FILE
However it fails with the following error output
//
OUTPUT
Buildfile:
C:\bea_922\user_projects\w4WP_workspaces\Untitled\TestProject\build.xml
build-service:
[echo] destdir is: output/helloWorldEar
[jwsc] JWS: processing module /com/RequestInformation
[jwsc] Parsing source files
[jwsc] Parsing source files
[jwsc] 1 JWS files being processed for module /com/RequestInformation
[jwsc] JWS:
C:\bea_922\user_projects\w4WP_workspaces\Untitled\TestProject\src\com\Re
questInformation.java Validated.
[AntUtil.deleteDir] Deleting directory C:\temp\_x85513
BUILD FAILED
java.lang.AssertionError: java.io.IOException
Total time: 19 seconds
END OF OUTPUT
//*
I am new to ant build enviroment so I may be missing out some of the
minute details, so please help me in that direction.
regards
Sanchit Srivastava
Morgan Stanley | Technology
Bldg. 5, Sector 30, Mindspace, Goregaon (West) | Floor 02
Mumbai (Ex Bombay), 400 090 | India
Phone: +91 -22 -6641 0712
[EMAIL PROTECTED]
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
