SNAPSHOT/maven-artifact-ant-2.0-20050608.072503-1-dep.jar
Installed.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, jus
iles support, but we need to play with that more on our end first.
Looks good, bring it on! :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant,
st :-)
I have a couple more things to ask. Where should the discussion on the
Maven Ant tasks take place IYO?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, j
ke it.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
-
-
To unsubs
ed* to pollute the project files that use it to be able
to work as needed.
In most cases, one would want to use , or
instead of importing buildfiles with s, which should be used
only to reuse and "extend" a base buildfile.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
ed
project as is the case now).
Can't we have this as an addition anyway?
Why?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgott
gh to be used by most
committers, and ftp seems to be the case.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgott
Steve Loughran wrote:
...
What do people think about my plan?
Any possibility of not duplicating code between Maven/MavenWagon and Ant?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
just not do
the task of converting all the docs.
Besides, pure html is much easier to edit, as any decent html editor may do.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get for
l constraints to work properly.
Have you considered the use of an antlib for it?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussi
Matt Benson wrote:
--- Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
Matt Benson wrote:
...
I think we've had requests for automatic
invocations as well, while we're talking about
automatic stuff...
I don't understand, could you please explain a bit
more in detail?
TIA
The
Steve Loughran wrote:
Nicola Ken Barozzi wrote:
Steve Loughran wrote:
...
License is useful, pom may be useful in future...
Do you have a specific idea on this? :->
Not yet, no. But it might be useful to start collecting them.
IMHO it's about defaults.
A simple project always has
Matt Benson wrote:
...
I think we've had requests for automatic
invocations as well, while we're talking about
automatic stuff...
I don't understand, could you please explain a bit more in detail?
TIA
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba
en repository, etc, in one
place and have everything track it. I thought maybe we did this already,
but couldnt see it in the docs or the source.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions
Jesse Glick wrote:
Nicola Ken Barozzi wrote:
While I agree that there is some commonality across many Java
projects (in that Java has a packaging mechanism that utilizes
directories etc. and that these projects commonly produce one or
more JAR files) it seems to me that this approach would either
om other projects
Krysalis Centipede did this years ago, but the project failed.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, s
thing for tasks: if Ant provides a basic buildfile with the common
targets, then users would only need to import it and customize the parts
it needs to customize.
WDOT?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get
working fully.
Now is the time to fix what I have started; we have until Axis1.7 ships
:)
So if you want to merge what I've done with your code, let's go for it.
Same for anyone else who wants to contribute.
(Ex) Incubator Depot? :-) (note: where-if it makes sense)
--
Nicola K
bator/depot/trunk/update/src/java/org/apache/depot/update/ant/sync/?root=Apache-SVN
http://cvs.apache.org/viewcvs.cgi/incubator/depot/trunk/update/src/java/org/apache/depot/update/ant/tool/?root=Apache-SVN
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta m
a/org/apache/alexandria/ant/Attic/XMLListener.java?hideattic=0&view=markup
http://cvs.apache.org/viewcvs.cgi/jakarta-alexandria/proposal/vindico/src/java/org/apache/alexandria/util/Attic/XMLHelper.java?hideattic=0&view=markup
--
Nicola Ken Barozzi [EMAIL PROTECTED]
-
Russell Gold wrote:
On Thu, 26 Aug 2004 17:24:29 +0200, Nicola Ken Barozzi
<[EMAIL PROTECTED]> wrote:
Russell Gold wrote:
Attached is code and unit tests for a task which will download and
manage dependencies from a maven-style remote repository.
If you are interested, Incubator Depo
Russell Gold wrote:
Attached is code and unit tests for a task which will download and
manage dependencies from a maven-style remote repository.
If you are interested, Incubator Depot
http://incubator.apache.org/depot/ has a similar tasl and goals, and we
could work together.
--
Nicola Ken
has been for me :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
or the SQL task
http://issues.apache.org/bugzilla/show_bug.cgi?id=28681
Maybe we should guide people to use this functionality.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, ju
:
${data.sql}
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
s, finally I think so too.
Because of this I have also started a thread on the antworks mailing
list addressing these points.
Thanks all for the discussion! :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get for
Dominique Devienne wrote:
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
Jose Alberto Fernandez wrote:
...
All this restriction in OO inheritance are there to limit
developers capability of writing spaguetti. We still do, but...
Import overriding is not about OO inheritance, it's about t
must use fully qualified names. Why
can't I in Ant? What does this have to do with inheritance?
Ant import is *different* from other mechanisms, so analogies can help
but are not the same thing.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scri
Nicola Ken Barozzi wrote:...
task->target
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code rema
Dominique Devienne wrote:
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
I've looked into the code (gosh, I still remember part of it :-)
The following path is OTOMH, without even compiling, it should be a start.
Implementing this is not the issue...
I know, I haven't replied to /
target.setDepends(depends);
+if (fullTarget!=null) {
+fullTarget.setDepends(depends);
+ }
}
}
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, sc
o have this too.
Also any idea about how difficult it would be to have all properties
defined in imported builds also be "namespaced", to avoid collisions?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forg
versioned repository (should aim to make content long-lasting
and easily repurposed)
6. should aim at complete internationalization of the content
"
Forrest is almost there for the final generation, Lenya is proceeding
well and Slide has just released a new version.
--
Nic
nd out that they were still happy
to even only write them and have them removed, as we get "commit"
notifications that get archived and keep their link public forever.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project ant-embed-optional *no longer* has an issue.
Project State : 'Prerequisite Failed',
iewcvs.cgi/ant/proposal/embed/test.xml?rev=1.9&only_with_tag=MAIN&view=markup
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions g
After the task, what about this, that downloads 'plugins' and
s them?
http://antworks.sourceforge.net/
http://url-to/plugin/"; />
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
n the Ant xdocs proposal :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, ju
t include the code in the codebase, it would be fine too.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just
at piece of software, but IMHO ATM it's more
complicated to use, so I still prefer to see Jira here for now)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get for
/>
name="jxpathSet" />
name="velocityProperties" />
name="jexlProperties" />
--
Nicola Ken Barozzi [EMAI
ex.printStackTrace();
return null;
}
}
[1]
http://cvs.apache.org/viewcvs.cgi/ant/proposal/embed/src/java/org/apache/tools/ant/taskdefs/optional/VelocityProperties.java?view=markup
--
Nicola Ken Barozzi [EMAIL PROTECTED]
anization.namespace.a.init,
first.my.organization.namespace.a.init
b, second.b,
my.organization.namespace.b.init,
second.my.organization.namespace.b.init ]
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
actively working on Ruper2, which is our download manager.
If you want to help, we'll be happy to have you there :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get for
[EMAIL PROTECTED] wrote:
IANAL, but AFAIK no.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
I know AFAIK (as far as i know), but what is IANAL?
I Am Not A Layer :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions
#x27;t have a brand to protect anyhow.
Is it possible for a company to register a name which is used by others
in the same domain earlier?
>
E.g. if Apache uses "Ant" for years; can Microsoft register that name
for another neat tool now?
IANAL, but AFAIK no.
--
Nicola Ken
urely Apache has run into this before, no?
Yup. For example Microsoft has Avalon, and Sony has Cocoon. But our
projects are "Apache Avalon" and "Apache Cocoon".
So it's not *strictly* necessary to change the name, but why risk when
you don't have a brand to protect
ed to play safe.
If nobody is sticking to the name, let's play save and rename it.
Exactly :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta m
eforge.net/projects/vizant/
It has been inactive for a bit now, but I'd be happy to restart to code.
If you or anyone wants to help... :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, ju
peter reilly wrote:
On Friday 03 October 2003 15:54, Dominique Devienne wrote:
...
Not a bad idea! I would just make that:
No new task, but simply a very useful extension to an existing task
container. --DD
This whould make the seqential task actually useful..
:-)))
--
Nicola Ken Barozzi
work without worrying about the import
overriding capabilities.
I don't have the time now, but I really think that if you or someone
else adds an include task to the list, nobody would object. Personally I
favor it, as adding a task does not take away from import.
--
Nicola Ken Barozz
conversion between xls and xml. For more
info, you can contact the jakarta.apache.org/poi/ developer list.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
peter reilly wrote:
On Wednesday 17 September 2003 14:00, Nicola Ken Barozzi wrote:
Stefan Bodewig wrote:
...
I'm not sure. Even if you think the current "flat" import rules are
correct, (1) should be addressed IMHO.
Wait, you said that it prints out:
"Skipped already imp
Stefan Bodewig wrote:
On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
Stefan Bodewig wrote:
I feel this is wrong for two reasons:
(1) The current build file (the one intially loaded) should be
added to the list of already imported files implicitly so it
doesn't
.
What happens is that if at least one of the buildfiles asks to import a
file, that file is added to the list, and other requests are ignored.
So the current behaviour is correct given the actual -flat- import rules.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba
Gus Heck wrote, On 02/09/2003 17.26:
...
From Nicola Ken Barozzi:
>Imports should be reusable bits of builds. But instead they carry the
baggage
>of targets. With macrodef I can finally *create tasks using Ant*.
And so Ant becomes an xml based programming language? Writing tasks in
To me, the current macrodef behaviour seems pretty easy to grok.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just co
certain packages that are supposed to be independent.
I like it. :-)
I have never liked keeping separate directories for things, even if I do
it for the benefit it has in build separation.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent
Gus Heck wrote, On 25/08/2003 18.02:
Nicola Ken Barozzi wrote:
Jose Alberto Fernandez wrote, On 22/08/2003 14.58:
From: Gus Heck [mailto:[EMAIL PROTECTED]
...
If macro definitions are available to sub builds, then your 3rd case
might occur, but I don't think it would be good to allow macr
ave a solution for the case of I would just like
the behavior on both cases to be the same, so to reduce the leaarning
curve.
What about making them part of antlibs too?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten,
ok 3 seconds
Press Enter to continue
q + Enter to quit
targetnames + Enter to change invocation
>q(Enter)
$>_
PS: here is the enhancement's URL:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22428
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- ver
ener[] listeners = this.listeners;
+for (int i = 0; i < listeners.length; i++) {
+listeners[i].messageLogged(event);
}
+loggingMessage = false;
}
/**
@@ -2089,6 +2112,4 @@
public Task getThreadTask(Thread thread) {
return (Task) threadT
becomes
or
or
And
->
or
->
BTW, any name is fine for me as long as it's put in Ant 1.6 ;-)
--
Nicola Ken Barozzi
Will I place these tasks in ant or ant-contrib ?
Peter
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code re
n example of the usage of PropertyHelper.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get for
e but perhaps I could use (an extended) antcall with a refid?
Any suggestions? Does this help anyone?
I don't think I follow you. It seems that you are describing how import
works now, with first-target wins, and access to all the targets with
"fully qualified" names. Look in
de examples are important. Conor convinced me with
code. I convinced and discussed with Costin with code.
Code, code code!
- verba volant, scripta manent -
:-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
Trying to summarize.
Costin Manolache wrote, On 08/08/2003 16.21:
Nicola Ken Barozzi wrote:
...
As has been pointed out in these threads, Ant is a different beast, and
should be treated differenty.
+1
We are talking about OO concepts and inheritance - in context.
Well, we are not. We are
's Guide" (http://www.rubycentral.com/book/tut_modules.html):
...
Maybe it would be possible to borrow some ideas and concepts from Ruby...
Thanks Kunt for the pointer, seems very interesting! :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta man
Jose Alberto Fernandez wrote, On 07/08/2003 16.15:
Some comments on the issues inside:
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
...
Well, IMHO I personally don't see a real, strong, compelling
reason to
have targets have crosstalk between themselves, but I do have
an equally
s
Sorry if the mail becomes long, I have difficulty in deciding what to
snip ;-)
Costin Manolache wrote, On 07/08/2003 15.56:
Nicola Ken Barozzi wrote:
Thanks for the overview, Nicola !
Just to get you up to speed, the current issue is about multiple
inheritance, and how the current system allows
o we deal with the fact that targets that are not
even used have crosstalk between themselves?
And most of all: how to solve the last two points while keeping it
possible for me to retain the use-cases?
As you see, for this usecase, is not strong enough, as I
cannot override, and complete nam
critical to b, but since
they reference a generic "critical", they get the only one that remains
after being redefined. The problem is that I did not redefine it in the
main buildfile!
"
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta
name.
For example, if I have
...
PS: I would still like to be able to use in build
file that do not do any imports, to avoid wrapping long attributes
like the 'depends' one often is.
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
Dominique Devienne wrote, On 01/08/2003 17.38:
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 10:27 AM
To: [EMAIL PROTECTED]
Subject: Re: override
and that renamed targets from a and b should not be
call-able directly from the command
Dominique Devienne wrote, On 01/08/2003 17.14:
-Original Message-
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 9:24 AM
To: Ant Developers List
Subject: Re: override
On Fri, 1 Aug 2003 10:47 pm, Nicola Ken Barozzi wrote:
How can this thing be done while
nd know each other.
How can I do this more declaratively?
Dunno, some musings:
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions ge
renced projects (hmmm, can use for
this, need a better use-case)
This looks clearer now I think :-)
We all have different visions of include-override functionality, and
putting it all in a single target is confusing. Maybe the above division
makes sense and can help.
--
Nicola K
directly, but instead extend it
and add download functionality, I would be interested in switching it to
extending instead and seeing what happens, and then trying
some examples with .
:-D
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent
Conor MacNeill wrote, On 31/07/2003 15.44:
On Thu, 31 Jul 2003 10:23 pm, Nicola Ken Barozzi wrote:
The only thing that comes to mind is that I cannot use super ion
dependencies, which is a nifty feature :-(
Not sure why this would be needed. Just add as the first contained
task. All of the other
en be useful in
an entity includes approach.
Very interesting.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, ju
Jose Alberto Fernandez wrote, On 31/07/2003 13.24:
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
...
Wait a second, does this mean that there is crosstalk between
the lines
1, 2, 3?
Yes, there is crosstalk and at least in XSLT this is a good thing.
It means that you can write a bunch of
my.organization.namespace.a.init
added target first.my.organization.namespace.a.init
[targets: run, a, first.a,
my.organization.namespace.a.init,
first.my.organization.namespace.a.init
b, second.b,
my.organization.namespace.b.init,
second
Dominique Devienne wrote, On 30/07/2003 20.09:
Why don't you put the import *after* the
emailing the list, and the nice thing is that you see the threads well in it.
I am sending this through gmane, and haven't had any problems.
The only thing is that I cannot post to the user list via gmane, but it
has always been like this...
--
Nicola Ken Barozzi [EMAIL PROT
for taking this up, appreciated :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
In some cases I find that using antcall is slow and using dependencies
is impractical. Thus I have come up with this task, that simply executes
a target without any dependency checking:
/**
* Ant tasks that runs a target without creating a new project.
*
* @author Nicola Ken Barozzi [EMAIL
Conor MacNeill wrote, On 30/07/2003 0.10:
On Tue, 29 Jul 2003 05:52 pm, Nicola Ken Barozzi wrote:
Personally, I don't see the real need for it, as the same can be done
with correctly-written @importable files. In the specific, init values
should be included rather than imported.
Can you poi
is the problem, and
"basedir" is normally associated with it.
4. All normal Ant operations (i.e. not imports) are resolved to the
basedir of the outer project. There is no access to other basedirs.
If the above two features were missing, it would be almost of no use.
And yes, in that
Conor MacNeill wrote, On 29/07/2003 9.15:
On Tue, 29 Jul 2003 04:56 pm, Nicola Ken Barozzi wrote:
I think this is all getting too complex for . What you are
describing is project composition where each project maintains its own
context, its own basedir, etc.
AFAIK this is done with
Not quite
d it seems that you are coming too to my conclusions.
The problem, as you correctly note, is not about import per se, but
about false expectations that people try to realize with it.
My question is: what are users trying to do with it that is not in his
scope and cannot be done
x27;s use but warn if it's imported -
The author does not tell you how it's meant to use.
Most probably it's not made to be imported, so if you want
to import it, good luck!
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
In java I declare methods with the parameters they need, in Ant there is
usually no such a check, not even at runtime.
What I can do is
Do you think that this is all that can-should be done in these cases?
Should I add a small description of this usage in the importtask
If you look on the Netbeans site you will find the project page of this
library with instructions on how to use it standalone.
It would be great if Ant used it :-D
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgo
nts and get the resources for the cents, and
install the cents in their own dirs, for us it makes sense to keep the
references relative.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discu
Dominique Devienne wrote, On 24/07/2003 17.23:
Did my other messages answer your questions??? --DD
IIUC we agree.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains
ke of consistency, I now start to think that something
like the following would be needed to make what Conor thinks should happen:
or better
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code re
Conor MacNeill wrote, On 24/07/2003 14.49:
On Thu, 24 Jul 2003 10:26 pm, Nicola Ken Barozzi wrote:
What about:
Sure - pretty much what I thought, maybe a more descriptive attribute name
(overrideprefix). It would default to the imported project name.
A bit long...
What about this, it seems
se absolute imports is not acceptable, IMHO.
IMHO what you propose is the correct behaviour, and the one that users
(me too) would think should happen (least surprise rule).
import is a real cool feature.
Sure enough and also important enough to get right.
+1
--
Nicola Ken Barozzi
ince my experience with is very different, I'd be happy to
check the buildfiles that fail for you and help you work it out :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta ma
1 - 100 of 141 matches
Mail list logo
