cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: Questions on cleaning up trunk
Date Tue, 28 Mar 2006 06:19:11 GMT
Jorg Heymans wrote:
> Reinhard Poetz wrote:
> 
> 
>>* What's the right version for cocoon-core dependencies: 2.2.0-SNAPSHOT
>>or 2.2-SNAPSHOT?
>>
>>2.2.0-SNAPSHOT - we should use the 3-digits pattern IMO
>>
> 
> +1
> 
> 
>>  - Solution 3: Include them in cocoon-mocks/src/mock/java (possibly
>>prefered, since it already exists?)
> 
> 
> +1
> 
> Having a separate block level module just for a few mock classes is
> overkill.
> 
> 
>>If mocks are specific for a particular block, we should put the classes
>>into a separate module. How do we express the dependency so that it
>>compiles with the mocks but runs with the implementation?
> 
> 
> <scope>provided</scope>

ok. Using this scope, I agree with you that one mocks module should usually be 
enough.

>>* Copy/move status.xml
>>  - There are some inconsistencies for the current new blocks
>>  - Some are located in the parent block, some in the impl block
>>  - Where should they be located?
>>  - May there be more than one? e.g. for impl, sample, ...
> 
> 
> Perhaps you could just keep them at the module level for now and split
> them up later when the need arises (eg different implementations for one
> block)

I'd just have one status.xml per module (if we define module as a group of 
-impl, -samples) and would put it into the impl sub-module.

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Mime
View raw message