I've tried and tried, but I'm missing something. Please help me move to an
automated development system.
Here is the output from my Build:
documentation:
[delete] Deleting directory C:\clearcase_compile_results\javadoc
[mkdir] Created dir: C:\clearcase_compile_results\javadoc
[javadoc]
Yeah, you're right. That's the solution. Thanks. I forgot about that
one.
-Original Message-
From: Frank E. Weiss
Sent: Thu 12/20/2001 6:21 PM
To: Ant Users List
Cc:
Subject: Re: Off topic question?
> So here you'd have
That's essentially what I was thinking. Derive from the base target class,
specify the classname in the element, and have the build.xml file
reader be smart enough to attempt introspection on the derived class if it
encounters non-standard attributes.
Of course, then the
Another comment on this. I noticed this quite a while back. While the
manifest that ends up in the .jar file looks strange with the classpath line
appearing on multiple lines, it doesn't cause any problems in terms of class
not found errors when I deploy a .ear file under WebLogic 6.1. So I've jus
Howdy, all.
The problem: when build.compiler is set to jikes, and there is a
nonexistent directory in the extensions path, jikes barfs. MacOS X
has several directories in the extensions path that do not exist.
The potential hope:
If is set build.compiler to jikes, and then find a way to add t
I think I know what the problem is. If you double click on My Computer you get
a window with a list of folders. Then you drill down by double clicking the
subfolders till you get to your destination.
Now try this: right click on My Computer and select Explore. Now you get a
two-pane explorer wind
I'm trying to do a VSS get on a project containing files that I have checked
out. When I check out the file, it becomes writable. During the VSSget task
(and during a manual run of ss), the following output is printed for this
file:
A writable copy of [filename] already exists
(where filena
Right, but you have to remember to do go back a level after you're done
looking. I don't have to keep the window open. The point is, it just
would be awfully convenient to have the explorer window right there.
Nothing that can't be worked around, of course.
I guess it's another case of Microsof
Alexander Syedin schrieb:
>
> Hello Dirk,
> "tag" attribute is used to provide "-r ${release.tag}" argument to cvs command.
> Documentation seems to be non-ambiguous in description of this attribute:
> "... the tag of the package/module to check out."
I should have been reading more carefully no
oh man, what a dummy.
THANKS and happy x-mas and merry new year.
-duh
- Original Message -
From: "Diane Holt" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001 2:17 PM
Subject: Re: Perforce Optional Tasks
> --- Marcus <[EMAIL PROTECTED]> wro
--- Marcus <[EMAIL PROTECTED]> wrote:
> that is what i thought but then i get:
>
> p:\cpdev\main\src\run_build.xml:27: Problem exec'ing P4 command: error:
> //cpdev//main/src/... - no such file(s).
But that's not because isn't defined -- in fact, it is, and the
above is the output from 'p4', te
I doubt you can do this in W2K. Basically, if you delete the object (folder)
then the explorer viewer is also closed. I don't see why you have to have
that window open. I usually keep explorer open on the desktop. Or you can
keep explorer open one level above the dist folder.
BTW, an easy way to
Yup, there were inconsistencies, which were fixed in jdk1.3. Now, there
arent any. Anyways, can you please tell me if these changes will be part of
the next version of Ant, i.e., Ant1.4.2 or something. I am not sure what
1.5Alpha means, will the next version be 1.5 and such..
And though it might n
Hi Diane,
that is what i thought but then i get:
p:\cpdev\main\src\run_build.xml:27: Problem exec'ing P4 command: error:
//cpdev/
/main/src/... - no such file(s).
at
org.apache.tools.ant.taskdefs.optional.perforce.P4Base.execP4Command(
P4Base.java:180)
at
org.apache.tools.ant.tas
Here's an annoyance of working with ant on Windows 2000. It's not ant's
fault but I wonder if anyone has a workaround:
Typically an ant project will have a "dist" directory into which the
distribution is put. It will also have a "clean" task which will
typically have something like
If you l
This reminds me of a project we have in-house.
First, we created interfaces for all the important classes.
Then, in the XML, we have an optional attribute where the classname may be
specified.
This allows the developers to extend our classes or completely replace them.
So here you'd have
Yes, that worked. Thanks.
Still, it's probably more confusing than it should be. I would think
the syntax should do the same thing as the syntax
but it doesn't. And then there is also the option of specifying
includes and excludes as attributes. This could all be less confusingly
documented
- Original Message -
From: "DONNIE HALE" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001 11:18 AM
Subject: Re: Proper use of (a little off-topic)
Thanks for the info. I understand the point, though I tend to agree with
you - just move the line in the sand
That's not what I want, because if I have:
then the echo messages are going to get spit out even if the task decides that
it has nothing to do (all the .class files are up-to-date).
Thanks though.
Donnie
>>> [EMAIL PROTECTED] 12/20/01 02:29PM >>>
> 2) Can be put inside a ? I d
--- DONNIE HALE <[EMAIL PROTECTED]> wrote:
> 1) I know that tasks are extensible. How about s? So someone
> could post a contributed, enhanced without changing the core.
Don't know, since I don't yet know enough Java to know what distinguishes
a class that is extensible vs. one that isn't -- is
Does:
do what you need? (I'm not sure what correct "pathing" you want.)
Diane
=
([EMAIL PROTECTED])
__
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shoppi
Your suggestion doesn't work. It seems to me that putting a basedir
attribute on the jar task includes anything regardless of what filesets
are included. In fact, my earlier surmise that I could get what I want
by using excludes is wrong - if basedir is specified the excludes do not
work. But w
Hi,
you could have tried this..
-Original Message-
From: Steve Cohen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 20, 2001 1:25 PM
To: [EMAIL PROTECTED]
Subject: jar task question
I wish to create a jar after a build nested at a particular root, but
no
> 2) Can be put inside a ? I didn't see an answer to
> this before, but a test showed that it couldn't. What I'm trying
> to achieve is some feedback to System.out only if a task is executed:
>
>
>
> ...
>
>
> Is there a way to do that?
No echo can not be put inside a task, as it's a task
I wish to create a jar after a build nested at a particular root, but
not including every directory under this root. I know I could probably
do this
with in a fileset but I would rather do it with ;
that way if other stuff is added, I don't have to change my build
file.
However I find this does
Thanks for the info. I understand the point, though I tend to agree with you - just
move the line in the sand past equality but short of all the other things he's worried
about. :)
Since I have your attention, 2 questions (1 related):
1) I know that tasks are extensible. How about s? So someon
yes, but i thought it wa sin the optional.jar and not longer needed?
- Original Message -
From: "James Bullington" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001 10:06 AM
Subject: Re: Perforce Optional Tasks
> I'm not a perforce expert,
Ant 1.5Alpha has the necessary fix to allow multiple
Class-Path attributes to exist in the Manifest file.
The Jar Specification and Manifest Specification by Sun
are inconsistent. These links will show the
inconsistencies:
http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html
http://java.
Hi,
According to the java spec, the manifest entry has two parts: the main
section and the file section. The class-path entry is part of the main
section. And the snippets you guys have attached is for file entries
section.
Name: fileName
entry: com
entry : com/mypackage
In this case, the first en
--- Scott Coleman <[EMAIL PROTECTED]> wrote:
> Thank you and Diane, I was looking at the wrong the task and meant java
> not javac. As I wished to run with some asserts enabled and some
> disabled. Can you tell me where I can get the patch from.
There were two threads in ant-dev:
http://marc.th
>
> Hi,
> I want to provide a manifest file to the jar task. One of my
> entries in the
> manifest file is a bit long.
> Class-Path: lib/asadfsdfsdfsd.jar lib/rdgdfsghsgsdfgsdfsg.jar
> lib/asrfdsfasfsdaf.jar
>
> The jar task, puts in new line characters and additional spaces to the
> entry..and t
This has been reported before, and a reply was that the ant jar taks folows
the Java Spec.
Search the mail archives for responses.
T Master.
- Original Message -
From: "Mallampati, Suresh" <[EMAIL PROTECTED]>
To: "'Ant Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001
Hi,
I want to provide a manifest file to the jar task. One of my entries in the
manifest file is a bit long.
Class-Path: lib/asadfsdfsdfsd.jar lib/rdgdfsghsgsdfgsdfsg.jar
lib/asrfdsfasfsdaf.jar
The jar task, puts in new line characters and additional spaces to the
entry..and this is causing prob
--- James Bullington <[EMAIL PROTECTED]> wrote:
> I'm not a perforce expert, but did you define the taskdef as below?
>
> classname="org.apache.tools.ant.taskdefs.optional.perforce.P4Sync" />
You shouldn't need to -- all the P4 tasks are already defined in the
defaults.properties file.
Diane
--- Marcus <[EMAIL PROTECTED]> wrote:
> So, it would look like this?
>
>
Nope. The "id" for a path is just an identifier you can use to reference
it at other places in your build-file. The elements of the path are
specified using the nested tags.
In order to reference your environment
I'm not a perforce expert, but did you define the taskdef as below?
--Jim
--- Marcus <[EMAIL PROTECTED]> wrote:
> Jim,
>
> I do that and now I get:
> $ ant -buildfile run_build.xml init
> Buildfile: run_build.xml
>
> init:
> [echo] syncing
>
> BUILD FAILED
>
> p:\cpdev\main\src\run_b
--- James Bullington <[EMAIL PROTECTED]> wrote:
> At least the version that I use, Ant version 1.3 compiled on May 11
> 2001, provided by BEA, does not build the classpath.
I don't know doodley about BEA, but I find it hard to believe that the Ant
it's providing isn't doing what it should. What's
At least the version that I use, Ant version 1.3 compiled on May 11
2001, provided by BEA, does not build the classpath.
--Jim
--- Diane Holt <[EMAIL PROTECTED]> wrote:
> --- James Bullington <[EMAIL PROTECTED]> wrote:
> > Did you remember to put these files in your class path? When I
> first
>
--- James Bullington <[EMAIL PROTECTED]> wrote:
> Did you remember to put these files in your class path? When I first
> started to use optional.jar, this was my mistake.
>
> i.e. you need:
>
> CLASSPATH=%CLASSPATH%;/ant/lib/optional.jar;/ant/lib/oro.jar
You shouldn't need to do this -- the w
--- DONNIE HALE <[EMAIL PROTECTED]> wrote:
> Aaah. Out of curiousity, and without trying to start a new religious war
> :), could you summarize the reasons for the rejection? Or perhaps give
> me a keyword that will help me hit the right archived messages?
Basically, it's seen as "too scripty" an
Jim,
I do that and now I get:
$ ant -buildfile run_build.xml init
Buildfile: run_build.xml
init:
[echo] syncing
BUILD FAILED
p:\cpdev\main\src\run_build.xml:29: Could not create task of type: p4Sync.
Commo
n solutions are to use taskdef to declare your task, or, if this is an
optional
tas
I placed this line in a batch file that I execute before I call ant.
--Jim
--- Marcus <[EMAIL PROTECTED]> wrote:
> Hi Jim,
>
> Where in the xml file or in the sys variables?
>
> thx
> -mez
> - Original Message -
> From: "James Bullington" <[EMAIL PROTECTED]>
> To: "Ant Users List" <[EM
Hi Jim,
Where in the xml file or in the sys variables?
thx
-mez
- Original Message -
From: "James Bullington" <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Sent: Thursday, December 20, 2001 9:37 AM
Subject: Re: Perforce Optional Tasks
> Did you remember to put these file
Did you remember to put these files in your class path? When I first
started to use optional.jar, this was my mistake.
i.e. you need:
CLASSPATH=%CLASSPATH%;/ant/lib/optional.jar;/ant/lib/oro.jar
Hope this helps,
Jim
--- Marcus <[EMAIL PROTECTED]> wrote:
> I have put in the optional.jar and t
Jens,
I had cut this version down from my build.xml file as it was using the junit
features and I did not have time to do all the automation (junit, p4,
build,etc) I would like for our 1st release, so I just tired to do this in
an other file and will re-integrate later.
So, it would look like th
Hello Marcus,
it's as Andrew expected: you have defined classpath outside a task
element, where ant interprets it as a task ittself. Classpath can only
be defined inside some task (like javac, java, javadoc...).
If you want to define classpath and use it several times, just replace
your wit
Andy.
I had this working and then started on some other ant sutff and came back to
this and it didn't work, so I think I may have changed something, like you
said, in the classpath setting in system variables.
Here is what my settings are:
ANT_HOME = p:\thirdparty\jvm\ant
JAVA_HOME = p:\thirdpar
Marcus,
> I have put in the optional.jar and the oro.jar file in
> /ant/lib and I still get:
> BUILD FAILED
>
> p:\cpdev\main\src\run_build.xml:23: Could not create task of
> type: classpath.
It sounds like you have a element as a base element rather
than as an element of another task such a
hi
i was shocked to see the that ant was giving error in ejbjar task because i
specified the following in my xml file
META-INF/AuthenticationTokenDetails-weblogic-rdbms-jar.xml
instead of putting it in one line
When i put above in a single line it compiles properly
is it n
Conor MacNeill schrieb:
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, 20 December 2001 1:15 AM
> > To: [EMAIL PROTECTED]
> > Subject: Tagging a release using cvs task
> >
> >
> > Hello List,
> >
> > i try to tag a release using the cvs
Hello Dirk,
"tag" attribute is used to provide "-r ${release.tag}" argument to cvs command.
Documentation seems to be non-ambiguous in description of this attribute:
"... the tag of the package/module to check out."
So, you have to use something like: to accomplish your target.
--
SY. Alexander
Dear all,
Hi I generated ant build.xml file by using EJBCreator-0.4
available at http://opensource.itplus.dk/EJBCreator/index.html
I could perfectly build everything, but I noticed
my javadoc went out as in Japanese language.
I want to generate them in English.
Although I consulted ant docume
52 matches
Mail list logo
