You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stefan Bodewig <bo...@apache.org> on 2005/06/16 11:44:29 UTC
[PATCH][Gump] your definitions break Gump builds
Hi all,
your own project definitions of commons-javaflow, commons-jci and
lately spring break the Gump supplied definitions.
We've been building svn trunk of commons-jci for weeks now, but it
gets listed as failed because it doesn't produce a jar with "your"
name.
spring is an installed package and has been for quite some time, even
before you added a defintion.
The appendend patch simply removes the three project definitions, if
this is not the correct way to deal with it, please at least rename
your projects.
Also, in the case of jci and javaflow, this is a repeated request, see
<http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111468255224092&w=2>.
Please let me know if I'm not following the correct protocol here.
Cheers
Stefan
Index: gump.xml
===================================================================
--- gump.xml (revision 190800)
+++ gump.xml (working copy)
@@ -20,7 +20,7 @@
|
| $Id$
|
- | see http://brutus.apache.org/gump/public/buildLog.html
+ | see http://vmgump.apache.org/gump/public/buildLog.html
| for already existing projects
|
+-->
@@ -1530,18 +1530,6 @@
<jar name="lib/optional/daisy-util-1.1.jar"/>
</project>
- <project name="commons-javaflow">
- <package>org.apache.commons.javaflow</package>
- <home nested="lib/optional"/>
- <jar name="commons-javaflow-0.1-dev.jar"/>
- </project>
-
- <project name="commons-jci">
- <package>org.apache.jci</package>
- <home nested="lib/core"/>
- <jar name="commons-jci-r159148.jar"/>
- </project>
-
<project name="jcr">
<package>javax.jcr</package>
<jar name="lib/optional/jcr-0.16.4.jar"/>
@@ -1553,8 +1541,4 @@
<jar name="lib/optional/jackrabbit-20050422T153417.jar"/>
</project>
- <project name="spring">
- <package>org.springframework</package>
- <jar name="lib/optional/spring-1.1.5.jar"/>
- </project>
</module>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Leo Simons <ma...@leosimons.com>.
On 17-06-2005 05:24, "Stefano Mazzocchi" <st...@apache.org> wrote:
>> Should be quite trivial to add a rule to asf-authorization that grants
>> rw to @gump for just that file, at least I think it allows
>> file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
All pmc chairs have the ability to edit the svn-authorization file in infra
SVN. Other people do too (e.g. The infrastructre team). But really the
request should be from the cocoon PMC to the infra@ mailing list. I'll
probably end up making the changes :)
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Upayavira <uv...@odoko.co.uk>.
Sylvain Wallez wrote:
> Stefano Mazzocchi wrote:
>
>>>> Now, I would be totally in favor of granting the gump committers
>>>> commit access to the cocoon project.
>>>>
>>>
>>> Should be quite trivial to add a rule to asf-authorization that grants
>>> rw to @gump for just that file, at least I think it allows
>>> file-granularity.
>>>
>>
>>
>> Even better. Can we do it or is it something that infra@ has to do?
>>
>>
>
> Does the svn authorization file accept wildcards? That would allow for
> [**/gump.xml]
> @gump=rw
>
> Otherwise, each PMC is responsible for managing its own authorizations
> and chairs have write access to asf-authorization.
From my local tests, no, wildcards don't work. So each PMC would have
to add this line themselves.
Upayavira
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Sylvain Wallez <sy...@apache.org>.
Stefano Mazzocchi wrote:
>>>Now, I would be totally in favor of granting the gump committers
>>>commit access to the cocoon project.
>>>
>>>
>>Should be quite trivial to add a rule to asf-authorization that grants
>>rw to @gump for just that file, at least I think it allows
>>file-granularity.
>>
>>
>
>Even better. Can we do it or is it something that infra@ has to do?
>
>
Does the svn authorization file accept wildcards? That would allow for
[**/gump.xml]
@gump=rw
Otherwise, each PMC is responsible for managing its own authorizations
and chairs have write access to asf-authorization.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [PATCH][Gump] your definitions break Gump builds
Posted by David Crossley <cr...@apache.org>.
Stefano Mazzocchi wrote:
> Stefan Bodewig wrote:
> > On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
> >
> >
> >>it's not a matter of being annoyed enough (we are already!), it's
> >>the fact that cocoon needs that file at build time.
> >
> >
> > Hmm, so why don't you realize that you have a typo in it for many
> > days? Like when you rename a jar but forget to update the descriptor?
>
> because cocoon doesn't use *all* of that data, only parts.
>
> Truth be told, cocoon could have two files, one for gump and one for its
> own build system, but they would contain the same information.
>
> >>Now, I would be totally in favor of granting the gump committers
> >>commit access to the cocoon project.
> >
> > Should be quite trivial to add a rule to asf-authorization that grants
> > rw to @gump for just that file, at least I think it allows
> > file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
PMC chairs can do it.
-David
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>
>>Stefan Bodewig wrote:
>>
>>>On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>>>
>>>
>>>
>>>>it's not a matter of being annoyed enough (we are already!), it's
>>>>the fact that cocoon needs that file at build time.
>>>
>>>
>>>Hmm, so why don't you realize that you have a typo in it for many
>>>days? Like when you rename a jar but forget to update the
>>>descriptor?
>>
>>because cocoon doesn't use *all* of that data, only parts.
>
>
> Unfortunately Gump gets into trouble because of the parts Cocoon
> doesn't use.
I know.
> If you don't use any of the projects you define for jars in your repo,
> maybe you better shouldn't define those projects at all? Instead nag
> the Gump crew to turn them into installed packages.
I personally wouldn't be against such a thing.
>>>>Now, I would be totally in favor of granting the gump committers
>>>>commit access to the cocoon project.
>>>
>>>Should be quite trivial to add a rule to asf-authorization that
>>>grants rw to @gump for just that file, at least I think it allows
>>>file-granularity.
>>
>>Even better. Can we do it or is it something that infra@ has to do?
>
>
> Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC
> made the change.
ok, I'll start a vote.
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>
>>Stefan Bodewig wrote:
>>
>>>On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>>>
>>>
>>>
>>>>it's not a matter of being annoyed enough (we are already!), it's
>>>>the fact that cocoon needs that file at build time.
>>>
>>>
>>>Hmm, so why don't you realize that you have a typo in it for many
>>>days? Like when you rename a jar but forget to update the
>>>descriptor?
>>
>>because cocoon doesn't use *all* of that data, only parts.
>
>
> Unfortunately Gump gets into trouble because of the parts Cocoon
> doesn't use.
I know.
> If you don't use any of the projects you define for jars in your repo,
> maybe you better shouldn't define those projects at all? Instead nag
> the Gump crew to turn them into installed packages.
I personally wouldn't be against such a thing.
>>>>Now, I would be totally in favor of granting the gump committers
>>>>commit access to the cocoon project.
>>>
>>>Should be quite trivial to add a rule to asf-authorization that
>>>grants rw to @gump for just that file, at least I think it allows
>>>file-granularity.
>>
>>Even better. Can we do it or is it something that infra@ has to do?
>
>
> Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC
> made the change.
ok, I'll start a vote.
--
Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
> Stefan Bodewig wrote:
>> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>>
>>
>>>it's not a matter of being annoyed enough (we are already!), it's
>>>the fact that cocoon needs that file at build time.
>>
>>
>> Hmm, so why don't you realize that you have a typo in it for many
>> days? Like when you rename a jar but forget to update the
>> descriptor?
>
> because cocoon doesn't use *all* of that data, only parts.
Unfortunately Gump gets into trouble because of the parts Cocoon
doesn't use.
If you don't use any of the projects you define for jars in your repo,
maybe you better shouldn't define those projects at all? Instead nag
the Gump crew to turn them into installed packages.
>>>Now, I would be totally in favor of granting the gump committers
>>>commit access to the cocoon project.
>>
>> Should be quite trivial to add a rule to asf-authorization that
>> grants rw to @gump for just that file, at least I think it allows
>> file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC
made the change.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
> Stefan Bodewig wrote:
>> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>>
>>
>>>it's not a matter of being annoyed enough (we are already!), it's
>>>the fact that cocoon needs that file at build time.
>>
>>
>> Hmm, so why don't you realize that you have a typo in it for many
>> days? Like when you rename a jar but forget to update the
>> descriptor?
>
> because cocoon doesn't use *all* of that data, only parts.
Unfortunately Gump gets into trouble because of the parts Cocoon
doesn't use.
If you don't use any of the projects you define for jars in your repo,
maybe you better shouldn't define those projects at all? Instead nag
the Gump crew to turn them into installed packages.
>>>Now, I would be totally in favor of granting the gump committers
>>>commit access to the cocoon project.
>>
>> Should be quite trivial to add a rule to asf-authorization that
>> grants rw to @gump for just that file, at least I think it allows
>> file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC
made the change.
Stefan
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Sylvain Wallez <sy...@apache.org>.
Stefano Mazzocchi wrote:
>>>Now, I would be totally in favor of granting the gump committers
>>>commit access to the cocoon project.
>>>
>>>
>>Should be quite trivial to add a rule to asf-authorization that grants
>>rw to @gump for just that file, at least I think it allows
>>file-granularity.
>>
>>
>
>Even better. Can we do it or is it something that infra@ has to do?
>
>
Does the svn authorization file accept wildcards? That would allow for
[**/gump.xml]
@gump=rw
Otherwise, each PMC is responsible for managing its own authorizations
and chairs have write access to asf-authorization.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://apache.org/~sylvain http://anyware-tech.com
Apache Software Foundation Member Research & Technology Director
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Upayavira <uv...@odoko.co.uk>.
Stefano Mazzocchi wrote:
> Stefan Bodewig wrote:
>
>>On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>>
>>
>>
>>>it's not a matter of being annoyed enough (we are already!), it's
>>>the fact that cocoon needs that file at build time.
>>
>>
>>Hmm, so why don't you realize that you have a typo in it for many
>>days? Like when you rename a jar but forget to update the descriptor?
>
>
> because cocoon doesn't use *all* of that data, only parts.
>
> Truth be told, cocoon could have two files, one for gump and one for its
> own build system, but they would contain the same information.
>
>
>>>Now, I would be totally in favor of granting the gump committers
>>>commit access to the cocoon project.
>>
>>
>>Should be quite trivial to add a rule to asf-authorization that grants
>>rw to @gump for just that file, at least I think it allows
>>file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
I've just tried it on a local installation of SVN, and it seems to work
just fine. I believe we can just do it ourselves, although it would be
polite to mention it on infra as it isn't something I've seen done
before, so does establish something of a new policy.
Here's the patch that would be required. It's pretty simple:
Index: asf-authorization
===================================================================
--- asf-authorization (revision 191108)
+++ asf-authorization (working copy)
@@ -339,6 +339,9 @@
@cocoon = rw
@lenya = rw
+[/cocoon/trunk/gump.xml]
+@gump = rw
+
[/forrest]
@forrest = rw
@cocoon = rw
So, we all want this?
Regards, Upayavira
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Leo Simons <ma...@leosimons.com>.
On 17-06-2005 05:24, "Stefano Mazzocchi" <st...@apache.org> wrote:
>> Should be quite trivial to add a rule to asf-authorization that grants
>> rw to @gump for just that file, at least I think it allows
>> file-granularity.
>
> Even better. Can we do it or is it something that infra@ has to do?
All pmc chairs have the ability to edit the svn-authorization file in infra
SVN. Other people do too (e.g. The infrastructre team). But really the
request should be from the cocoon PMC to the infra@ mailing list. I'll
probably end up making the changes :)
LSD
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>
>
>>it's not a matter of being annoyed enough (we are already!), it's
>>the fact that cocoon needs that file at build time.
>
>
> Hmm, so why don't you realize that you have a typo in it for many
> days? Like when you rename a jar but forget to update the descriptor?
because cocoon doesn't use *all* of that data, only parts.
Truth be told, cocoon could have two files, one for gump and one for its
own build system, but they would contain the same information.
>>Now, I would be totally in favor of granting the gump committers
>>commit access to the cocoon project.
>
>
> Should be quite trivial to add a rule to asf-authorization that grants
> rw to @gump for just that file, at least I think it allows
> file-granularity.
Even better. Can we do it or is it something that infra@ has to do?
--
Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>
>
>>it's not a matter of being annoyed enough (we are already!), it's
>>the fact that cocoon needs that file at build time.
>
>
> Hmm, so why don't you realize that you have a typo in it for many
> days? Like when you rename a jar but forget to update the descriptor?
because cocoon doesn't use *all* of that data, only parts.
Truth be told, cocoon could have two files, one for gump and one for its
own build system, but they would contain the same information.
>>Now, I would be totally in favor of granting the gump committers
>>commit access to the cocoon project.
>
>
> Should be quite trivial to add a rule to asf-authorization that grants
> rw to @gump for just that file, at least I think it allows
> file-granularity.
Even better. Can we do it or is it something that infra@ has to do?
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Leo Simons <ma...@leosimons.com>.
On 16-06-2005 17:00, "Stefan Bodewig" <bo...@apache.org> wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>> Now, I would be totally in favor of granting the gump committers
>> commit access to the cocoon project.
>
> Should be quite trivial to add a rule to asf-authorization that grants
> rw to @gump for just that file, at least I think it allows
> file-granularity.
Yes please. We'll add an svn:externals to gump svn if possible and all this
sending patches around can go away (ooh another reason to move everything to
svn!) :-)
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Leo Simons <ma...@leosimons.com>.
On 16-06-2005 17:00, "Stefan Bodewig" <bo...@apache.org> wrote:
> On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
>> Now, I would be totally in favor of granting the gump committers
>> commit access to the cocoon project.
>
> Should be quite trivial to add a rule to asf-authorization that grants
> rw to @gump for just that file, at least I think it allows
> file-granularity.
Yes please. We'll add an svn:externals to gump svn if possible and all this
sending patches around can go away (ooh another reason to move everything to
svn!) :-)
- Leo
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
> it's not a matter of being annoyed enough (we are already!), it's
> the fact that cocoon needs that file at build time.
Hmm, so why don't you realize that you have a typo in it for many
days? Like when you rename a jar but forget to update the descriptor?
> Now, I would be totally in favor of granting the gump committers
> commit access to the cocoon project.
Should be quite trivial to add a rule to asf-authorization that grants
rw to @gump for just that file, at least I think it allows
file-granularity.
Stefan
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Stefano Mazzocchi <st...@apache.org> wrote:
> it's not a matter of being annoyed enough (we are already!), it's
> the fact that cocoon needs that file at build time.
Hmm, so why don't you realize that you have a typo in it for many
days? Like when you rename a jar but forget to update the descriptor?
> Now, I would be totally in favor of granting the gump committers
> commit access to the cocoon project.
Should be quite trivial to add a rule to asf-authorization that grants
rw to @gump for just that file, at least I think it allows
file-granularity.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 16 juin 05, à 14:58, Stefano Mazzocchi a écrit :
> ....Now, I would be totally in favor of granting the gump committers
> commit
> access to the cocoon project...
+1
-Bertrand
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Upayavira <uv...@odoko.co.uk> wrote:
>
>
>>I've committed this patch to Cocoon trunk.
>
>
> Many thanks.
>
>
>>I presume that is the correct place.
>
>
> Until the Cocoon project is annoyed enough by our patches and moves
> the descriptor over to Gump land, I think it is. 8-)
Stefan,
it's not a matter of being annoyed enough (we are already!), it's the
fact that cocoon needs that file at build time.
Now, I would be totally in favor of granting the gump committers commit
access to the cocoon project.
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 16 Jun 2005, Upayavira <uv...@odoko.co.uk> wrote:
>
>
>>I've committed this patch to Cocoon trunk.
>
>
> Many thanks.
>
>
>>I presume that is the correct place.
>
>
> Until the Cocoon project is annoyed enough by our patches and moves
> the descriptor over to Gump land, I think it is. 8-)
Stefan,
it's not a matter of being annoyed enough (we are already!), it's the
fact that cocoon needs that file at build time.
Now, I would be totally in favor of granting the gump committers commit
access to the cocoon project.
--
Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Upayavira <uv...@odoko.co.uk> wrote:
> I've committed this patch to Cocoon trunk.
Many thanks.
> I presume that is the correct place.
Until the Cocoon project is annoyed enough by our patches and moves
the descriptor over to Gump land, I think it is. 8-)
Stefan
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 16 Jun 2005, Upayavira <uv...@odoko.co.uk> wrote:
> I've committed this patch to Cocoon trunk.
Many thanks.
> I presume that is the correct place.
Until the Cocoon project is annoyed enough by our patches and moves
the descriptor over to Gump land, I think it is. 8-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Upayavira <uv...@odoko.co.uk>.
Stefan,
I've committed this patch to Cocoon trunk. I presume that is the correct
place.
Regards, Upayavira
Stefan Bodewig wrote:
> Hi all,
>
> your own project definitions of commons-javaflow, commons-jci and
> lately spring break the Gump supplied definitions.
>
> We've been building svn trunk of commons-jci for weeks now, but it
> gets listed as failed because it doesn't produce a jar with "your"
> name.
>
> spring is an installed package and has been for quite some time, even
> before you added a defintion.
>
> The appendend patch simply removes the three project definitions, if
> this is not the correct way to deal with it, please at least rename
> your projects.
>
> Also, in the case of jci and javaflow, this is a repeated request, see
> <http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111468255224092&w=2>.
> Please let me know if I'm not following the correct protocol here.
>
> Cheers
>
> Stefan
>
> Index: gump.xml
> ===================================================================
> --- gump.xml (revision 190800)
> +++ gump.xml (working copy)
> @@ -20,7 +20,7 @@
> |
> | $Id$
> |
> - | see http://brutus.apache.org/gump/public/buildLog.html
> + | see http://vmgump.apache.org/gump/public/buildLog.html
> | for already existing projects
> |
> +-->
> @@ -1530,18 +1530,6 @@
> <jar name="lib/optional/daisy-util-1.1.jar"/>
> </project>
>
> - <project name="commons-javaflow">
> - <package>org.apache.commons.javaflow</package>
> - <home nested="lib/optional"/>
> - <jar name="commons-javaflow-0.1-dev.jar"/>
> - </project>
> -
> - <project name="commons-jci">
> - <package>org.apache.jci</package>
> - <home nested="lib/core"/>
> - <jar name="commons-jci-r159148.jar"/>
> - </project>
> -
> <project name="jcr">
> <package>javax.jcr</package>
> <jar name="lib/optional/jcr-0.16.4.jar"/>
> @@ -1553,8 +1541,4 @@
> <jar name="lib/optional/jackrabbit-20050422T153417.jar"/>
> </project>
>
> - <project name="spring">
> - <package>org.springframework</package>
> - <jar name="lib/optional/spring-1.1.5.jar"/>
> - </project>
> </module>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [PATCH][Gump] your definitions break Gump builds
Posted by Upayavira <uv...@odoko.co.uk>.
Stefan,
I've committed this patch to Cocoon trunk. I presume that is the correct
place.
Regards, Upayavira
Stefan Bodewig wrote:
> Hi all,
>
> your own project definitions of commons-javaflow, commons-jci and
> lately spring break the Gump supplied definitions.
>
> We've been building svn trunk of commons-jci for weeks now, but it
> gets listed as failed because it doesn't produce a jar with "your"
> name.
>
> spring is an installed package and has been for quite some time, even
> before you added a defintion.
>
> The appendend patch simply removes the three project definitions, if
> this is not the correct way to deal with it, please at least rename
> your projects.
>
> Also, in the case of jci and javaflow, this is a repeated request, see
> <http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111468255224092&w=2>.
> Please let me know if I'm not following the correct protocol here.
>
> Cheers
>
> Stefan
>
> Index: gump.xml
> ===================================================================
> --- gump.xml (revision 190800)
> +++ gump.xml (working copy)
> @@ -20,7 +20,7 @@
> |
> | $Id$
> |
> - | see http://brutus.apache.org/gump/public/buildLog.html
> + | see http://vmgump.apache.org/gump/public/buildLog.html
> | for already existing projects
> |
> +-->
> @@ -1530,18 +1530,6 @@
> <jar name="lib/optional/daisy-util-1.1.jar"/>
> </project>
>
> - <project name="commons-javaflow">
> - <package>org.apache.commons.javaflow</package>
> - <home nested="lib/optional"/>
> - <jar name="commons-javaflow-0.1-dev.jar"/>
> - </project>
> -
> - <project name="commons-jci">
> - <package>org.apache.jci</package>
> - <home nested="lib/core"/>
> - <jar name="commons-jci-r159148.jar"/>
> - </project>
> -
> <project name="jcr">
> <package>javax.jcr</package>
> <jar name="lib/optional/jcr-0.16.4.jar"/>
> @@ -1553,8 +1541,4 @@
> <jar name="lib/optional/jackrabbit-20050422T153417.jar"/>
> </project>
>
> - <project name="spring">
> - <package>org.springframework</package>
> - <jar name="lib/optional/spring-1.1.5.jar"/>
> - </project>
> </module>
>