You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Joshua Allen <ja...@cogeco.ca> on 2002/12/01 01:41:28 UTC
contributing to project
There were no responses to my request of getting this task in Ant. The docs are vague about the process of how a non-committer can
get something into the CVS tree. Is there one?
http://phosphor.sf.net/import-scrubber-3.0.0.zip
The unit tests & docs have been already been written.
-Joshua
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: contributing to project
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Joshua Allen" <ja...@cogeco.ca>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Sunday, December 01, 2002 00:22
Subject: RE: contributing to project
> As it sounds like it's not going to be included I guess this is will be a
purely academic exercise.
well, I dont see any overwhelming demand to bring it into the core, but it
can be a useful task and we will happily link to it. Indeed, we happily link
to all external ant tasks.
> In any case where, I'll put the task in
src/main/org/apache/tools/ant/taskdefs/optional, but where do I put the
xdocs?
I guess I wasnt detailed enough. xdocs/external.xml is the file listing all
external tasks and tools; add an entry for your task there and the web site
can be updated to point to .
>
> A bigger problem is that I don't have write access to the repository so
when I do "cvs add" so it can generate a diff file, it won't
> let me.
>
just run the cvs diff -u command, that will generate the appropriate patch
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: contributing to project
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
Joshua Allen wrote:
> Although I won't need to, cvs won't let you add a new file to the project--even if it's just to create a diff file. So
> contributions from non-committers seem to be limited to modifying existing files only.
But having a "diff" of a new file doesn't make sense. The way new files
are handled are that folks submit the new files along with patches for
the existing files, ideally to Bugzilla as attachments.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: contributing to project
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 1 Dec 2002, Joshua Allen <ja...@cogeco.ca> wrote:
> Although I won't need to, cvs won't let you add a new file to the
> project--even if it's just to create a diff file.
You can trick CVS into thinking you've added a file simply by adding a
line like
/foo/0/dummy timestamp//
to CVS/Entries manually. Here CVS would assume you had added a file
foo and will happily do a cvs diff -u for you.
ISTR there was a suit of scripts that helped to deal with issues like
that (i.e. a cvsadd script that did just what I've described above).
I've lost the link, sorry.
> So contributions from non-committers seem to be limited to modifying
> existing files only.
You can always send in a file (or an archive) in addition to your
patch and tell us where to add the file(s).
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: contributing to project
Posted by Joshua Allen <ja...@cogeco.ca>.
Conor,
Yeah, I'll consider a new name. Actually this project grew out of frustration with other utilities that attempted to do did this,
the sf one you mentioned included. (I'd use them on a large project (100-300 classes) and then it wouldn't compile w/o having to
fix certain things they had done manually. Also, there was no way to reverse what they had done for easier maintenance.)
Although I won't need to, cvs won't let you add a new file to the project--even if it's just to create a diff file. So
contributions from non-committers seem to be limited to modifying existing files only.
-Joshua
-----Original Message-----
From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
Sent: Sunday, December 01, 2002 8:51 AM
To: Ant Developers List
Subject: Re: contributing to project
Joshua,
Are you aware that there already exists an importscrubber project at
sourceforge (http://importscrubber.sourceforge.net/) which includes an Ant
task, which is documented on the Ant external links page
(http://jakarta.apache.org/ant/external.html)? You may want to consider a
new name for your project.
As Steve said, we can't bundle every task with Ant, it just won't scale.
There is a variety of reasons why the current set of included tasks are in
Ant. These reasons range from core OS/JDK features, natural fit, to
cross-vendor tasks, to just plain history. Most new tasks will fit into
these categories or be to do with core Ant functionality.
Joshua Allen wrote:
> As it sounds like it's not going to be included I guess this is will be a purely academic exercise.
>
> In any case where, I'll put the task in src/main/org/apache/tools/ant/taskdefs/optional, but where do I put the xdocs?
If you are going to host this elsewhere, and there is no reason you should
not, you should use your own namespace (net.turingcomplete ?).
The xdocs that Steve referred to is the Ant documentation and he was
suggesting you make a change to external.xml to list your task in the
external links.
>
> A bigger problem is that I don't have write access to the repository so when I do "cvs add" so it can generate a diff file, it
won't
> let me.
>
> cvs [server aborted]: "add" requires write access to the repository
>
You must be a committer to have write access to the CVS repository. What you
would need to do is make the changes to an anoncvs checkout and then
generate a patch file (cvs diff -u). A committer could then apply that patch.
Conor
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: contributing to project
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Joshua,
Are you aware that there already exists an importscrubber project at
sourceforge (http://importscrubber.sourceforge.net/) which includes an Ant
task, which is documented on the Ant external links page
(http://jakarta.apache.org/ant/external.html)? You may want to consider a
new name for your project.
As Steve said, we can't bundle every task with Ant, it just won't scale.
There is a variety of reasons why the current set of included tasks are in
Ant. These reasons range from core OS/JDK features, natural fit, to
cross-vendor tasks, to just plain history. Most new tasks will fit into
these categories or be to do with core Ant functionality.
Joshua Allen wrote:
> As it sounds like it's not going to be included I guess this is will be a purely academic exercise.
>
> In any case where, I'll put the task in src/main/org/apache/tools/ant/taskdefs/optional, but where do I put the xdocs?
If you are going to host this elsewhere, and there is no reason you should
not, you should use your own namespace (net.turingcomplete ?).
The xdocs that Steve referred to is the Ant documentation and he was
suggesting you make a change to external.xml to list your task in the
external links.
>
> A bigger problem is that I don't have write access to the repository so when I do "cvs add" so it can generate a diff file, it won't
> let me.
>
> cvs [server aborted]: "add" requires write access to the repository
>
You must be a committer to have write access to the CVS repository. What you
would need to do is make the changes to an anoncvs checkout and then
generate a patch file (cvs diff -u). A committer could then apply that patch.
Conor
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: contributing to project
Posted by Joshua Allen <ja...@cogeco.ca>.
As it sounds like it's not going to be included I guess this is will be a purely academic exercise.
In any case where, I'll put the task in src/main/org/apache/tools/ant/taskdefs/optional, but where do I put the xdocs?
A bigger problem is that I don't have write access to the repository so when I do "cvs add" so it can generate a diff file, it won't
let me.
cvs [server aborted]: "add" requires write access to the repository
-Joshua
-----Original Message-----
From: Steve Loughran [mailto:steve_l@iseran.com]
Sent: Sunday, December 01, 2002 12:53 AM
To: Ant Developers List
Subject: Re: contributing to project
----- Original Message -----
From: "Joshua Allen" <ja...@cogeco.ca>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Saturday, November 30, 2002 16:41
Subject: contributing to project
> There were no responses to my request of getting this task in Ant. The
docs are vague about the process of how a non-committer can
> get something into the CVS tree. Is there one?
there is in the ant task guidelines
> http://phosphor.sf.net/import-scrubber-3.0.0.zip
If something lives in sforge, we are usually happy for it to stay there,
with doc links from the ant web site and docs. So if you edit the
appropriate files in xdocs, submit the changes as a PATCH we'll point to
you.
Unless you can convince us it is so compelling and critical to all ant users
that we should take on the maintenance and support, which will be hard.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: contributing to project
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Joshua Allen" <ja...@cogeco.ca>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Saturday, November 30, 2002 16:41
Subject: contributing to project
> There were no responses to my request of getting this task in Ant. The
docs are vague about the process of how a non-committer can
> get something into the CVS tree. Is there one?
there is in the ant task guidelines
> http://phosphor.sf.net/import-scrubber-3.0.0.zip
If something lives in sforge, we are usually happy for it to stay there,
with doc links from the ant web site and docs. So if you edit the
appropriate files in xdocs, submit the changes as a PATCH we'll point to
you.
Unless you can convince us it is so compelling and critical to all ant users
that we should take on the maintenance and support, which will be hard.
-steve
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>