You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/08/15 08:49:03 UTC

Avalon-Components Directory Structure [was moving components]

Ok,

I think we have enough +1 for moving xmlutils and sourceresolver
from excalibur to avalon-components.

I roughly looked at the dir structure in avalon-components and 
I'm now wondering what's the best structure for moving the
components is.

Currently we have a *-api and a *-impl for each component as a
top level directory and we have a site directory containing the 
docs for all components:
+ "component-xyz"-api
+ "component-xyz"-impl
+ site + xdocs / "component-xyz".xml 

Is this the way we want to have it (just curious no offense)?

Or is this better?

+ "component-xyz" + src - api
                    src - impl
                    src - xdocs

Carsten 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: Avalon-Components Directory Structure [was moving components]

Posted by Stephen McConnell <mc...@apache.org>.

Carsten Ziegeler wrote:

>Stephen McConnell wrote:
>  
>
>>
>>Plugins in maven make the assumption that the project descriptor
>>represents a single unique artifact.  For example, the dependecies that
>>a project has can be used to automate the creation of a manifest for a
>>jar file.  If you consider this example you will quickly discover that
>>the assumptions made by a plugin do not hold when you have multiple
>>artifacts per project.  Yes - you can get around this by creating your
>>own manifest entries and creating a jar file outside of the Maven plugin.
>>
>>I.e. Maven is intended to be used on the basis of one main artifact per
>>project. As soon as you start ignoring this you start breaking plugins
>>left right and center.
>>
>>    
>>
>Ok, so you mean, if I have the two directories "component-api" and
>"component-impl", these are two projects, right? And if I have
>"component/src/api" and "component/src/impl" this is one project?
>

Yep.

Stephen.

>
>Carsten
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


RE: Avalon-Components Directory Structure [was moving components]

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Stephen McConnell wrote:
>
>
>
> Plugins in maven make the assumption that the project descriptor
> represents a single unique artifact.  For example, the dependecies that
> a project has can be used to automate the creation of a manifest for a
> jar file.  If you consider this example you will quickly discover that
> the assumptions made by a plugin do not hold when you have multiple
> artifacts per project.  Yes - you can get around this by creating your
> own manifest entries and creating a jar file outside of the Maven plugin.
>
> I.e. Maven is intended to be used on the basis of one main artifact per
> project. As soon as you start ignoring this you start breaking plugins
> left right and center.
>
Ok, so you mean, if I have the two directories "component-api" and
"component-impl", these are two projects, right? And if I have
"component/src/api" and "component/src/impl" this is one project?

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: Avalon-Components Directory Structure [was moving components]

Posted by Stephen McConnell <mc...@apache.org>.

Carsten Ziegeler wrote:

>Stephen McConnell wrote:
>  
>
>>>Or is this better?
>>>
>>>+ "component-xyz" + src - api
>>>                   src - impl
>>>                   src - xdocs
>>>
>>>      
>>>
>>Breaking out the src directories does not work - the project level 
>>information is different for api and impl.
>>
>>    
>>
>Could you please elaborate a little bit on this?
>  
>

Plugins in maven make the assumption that the project descriptor 
represents a single unique artifact.  For example, the dependecies that 
a project has can be used to automate the creation of a manifest for a 
jar file.  If you consider this example you will quickly discover that 
the assumptions made by a plugin do not hold when you have multiple 
artifacts per project.  Yes - you can get around this by creating your 
own manifest entries and creating a jar file outside of the Maven plugin. 

I.e. Maven is intended to be used on the basis of one main artifact per 
project. As soon as you start ignoring this you start breaking plugins 
left right and center.

Stephen.



>Carsten
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


RE: Avalon-Components Directory Structure [was moving components]

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Stephen McConnell wrote:
> >Or is this better?
> >
> >+ "component-xyz" + src - api
> >                    src - impl
> >                    src - xdocs
> >
> 
> Breaking out the src directories does not work - the project level 
> information is different for api and impl.
> 
Could you please elaborate a little bit on this?

Carsten

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: Avalon-Components Directory Structure [was moving components]

Posted by Stephen McConnell <mc...@apache.org>.

Carsten Ziegeler wrote:

>Ok,
>
>I think we have enough +1 for moving xmlutils and sourceresolver
>from excalibur to avalon-components.
>
>I roughly looked at the dir structure in avalon-components and 
>I'm now wondering what's the best structure for moving the
>components is.
>
>Currently we have a *-api and a *-impl for each component as a
>top level directory and we have a site directory containing the 
>docs for all components:
>+ "component-xyz"-api
>+ "component-xyz"-impl
>+ site + xdocs / "component-xyz".xml 
>
>Is this the way we want to have it (just curious no offense)?
>
>Or is this better?
>
>+ "component-xyz" + src - api
>                    src - impl
>                    src - xdocs
>

Breaking out the src directories does not work - the project level 
information is different for api and impl.

Stephen.

>
>Carsten 
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org