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 2003/03/24 09:45:31 UTC

[GUMP] "concurrent" project in Cocoon's descriptor causes trouble

Hi,

there is a name clash between the "concurrent" projects defined in
projects/dougLea.xml in Gump's CVS module and the one defined in
<http://cvs.apache.org/viewcvs/~checkout~/cocoon-2.1/gump.xml>.

I have no idea what this thing inside Cocoon is about, but please
rename the project.

What we currently get is that Gump merges both project definitions,
the <home> in Coccon's descriptor gets evaluated and we get a single
project named "concurrent" that must hold two jars:

${cocoon}/src/blocks/swf/lib/concurrent.jar
${cocoon}/src/blocks/swf/lib/util.concurrent-1.3.1.jar

which will never work, so all projects depending on either of both
will not get built because of missing prereqs.

Merging the two project definitions is intentional as it allows to
"add" stuff in the workspace, BTW.

Cheers

        Stefan

who'd fix it himself if Cocoon's descriptor was in the jakarta-gump
module ...  8-)

PS: I'm not subscribed to cocoon-dev.


Re: [GUMP] "concurrent" project in Cocoon's descriptor causes trouble

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 24 Mar 2003, Stefano Mazzocchi <st...@apache.org> wrote:

> they represent the same stuff.

Not that there also is a repackaged version somewhere (edu.concurrent
or something).

> I tried to depend on 'dougLea' as the project name implied but
> failed.  I think it's a very bad habit to name the project name
> different from the descriptor file.

Ahh, trap #1.  project != module.  For a module that consists of a
single project, I agree.

Sometimes there may be historic reasons.  The file ant.xml still
contains a project named jakarta-ant, for example.  I'm not sure about
the dougLea file name.

> No problem, I'm removing the dependecy right now.

Thanks!

Stefan

Re: [GUMP] "concurrent" project in Cocoon's descriptor causes trouble

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 24 Mar 2003, Stefano Mazzocchi <st...@apache.org> wrote:

> they represent the same stuff.

Not that there also is a repackaged version somewhere (edu.concurrent
or something).

> I tried to depend on 'dougLea' as the project name implied but
> failed.  I think it's a very bad habit to name the project name
> different from the descriptor file.

Ahh, trap #1.  project != module.  For a module that consists of a
single project, I agree.

Sometimes there may be historic reasons.  The file ant.xml still
contains a project named jakarta-ant, for example.  I'm not sure about
the dougLea file name.

> No problem, I'm removing the dependecy right now.

Thanks!

Stefan

Re: [GUMP] "concurrent" project in Cocoon's descriptor causes trouble

Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> Hi,
> 
> there is a name clash between the "concurrent" projects defined in
> projects/dougLea.xml in Gump's CVS module and the one defined in
> <http://cvs.apache.org/viewcvs/~checkout~/cocoon-2.1/gump.xml>.
> 
> I have no idea what this thing inside Cocoon is about, but please
> rename the project.

they represent the same stuff. I tried to depend on 'dougLea' as the 
project name implied but failed. I think it's a very bad habit to name 
the project name different from the descriptor file. but that's only my 
personal opinion.

> What we currently get is that Gump merges both project definitions,
> the <home> in Coccon's descriptor gets evaluated and we get a single
> project named "concurrent" that must hold two jars:
> 
> ${cocoon}/src/blocks/swf/lib/concurrent.jar
> ${cocoon}/src/blocks/swf/lib/util.concurrent-1.3.1.jar
> 
> which will never work, so all projects depending on either of both
> will not get built because of missing prereqs.
> 
> Merging the two project definitions is intentional as it allows to
> "add" stuff in the workspace, BTW.

No problem, I'm removing the dependecy right now.

> Cheers
> 
>         Stefan
> 
> who'd fix it himself if Cocoon's descriptor was in the jakarta-gump
> module ...  8-)

I know, I know :)


Re: [GUMP] "concurrent" project in Cocoon's descriptor causes trouble

Posted by Stefano Mazzocchi <st...@apache.org>.
Stefan Bodewig wrote:
> Hi,
> 
> there is a name clash between the "concurrent" projects defined in
> projects/dougLea.xml in Gump's CVS module and the one defined in
> <http://cvs.apache.org/viewcvs/~checkout~/cocoon-2.1/gump.xml>.
> 
> I have no idea what this thing inside Cocoon is about, but please
> rename the project.

they represent the same stuff. I tried to depend on 'dougLea' as the 
project name implied but failed. I think it's a very bad habit to name 
the project name different from the descriptor file. but that's only my 
personal opinion.

> What we currently get is that Gump merges both project definitions,
> the <home> in Coccon's descriptor gets evaluated and we get a single
> project named "concurrent" that must hold two jars:
> 
> ${cocoon}/src/blocks/swf/lib/concurrent.jar
> ${cocoon}/src/blocks/swf/lib/util.concurrent-1.3.1.jar
> 
> which will never work, so all projects depending on either of both
> will not get built because of missing prereqs.
> 
> Merging the two project definitions is intentional as it allows to
> "add" stuff in the workspace, BTW.

No problem, I'm removing the dependecy right now.

> Cheers
> 
>         Stefan
> 
> who'd fix it himself if Cocoon's descriptor was in the jakarta-gump
> module ...  8-)

I know, I know :)