Re: cvs commit: avalon/fortress

[Leo Simons <le...@apache.org>]

well, that didnt work :D

bloritsch@apache.org wrote:
>   Modified:    buildsystem/gump-integration/project
>                         avalon-fortress-container.xml
>
>   hopefully fix the problem with instrument management
>   -
>   -      <depend runtime="true" project="jakarta-bcel"></depend>
>   -
>   +    
>   +      <depend runtime="true" project="avalon-fortress"></depend>
>   +    
>   +      <depend runtime="true" project="bcel"></depend>

 >   -      <depend runtime="true" project="avalon-framework"></depend>
 >   -
 >   +      <depend runtime="true" project="framework"></depend>
 >   +
 >   -      <depend runtime="true" project="avalon-logkit"></depend>
 >   -
 >   +
 >   +      <depend runtime="true" project="logkit"></depend>
 >   +      <depend runtime="true" project="xalan"></depend>

This causes problems (since there's no project named "bcel", nor one 
named "framework", nor one named "avalon-logkit", nor one named xalan).
I'm guessing you regenerated the file using the maven targets, which 
overwrote the manual changes I made. This isn't working very well at all!

>   +    <work nested="/target/classes"></work>
>   +    <work nested="/target/api-classes"></work>
>   +    <work nested="/target/impl-classes"></work>
>   +    <work nested="/target/test-classes"></work>
>    
>   -    <work nested="fortress/container/target/classes"></work>
>   -    <work nested="fortress/container/target/api-classes"></work>
>   -    <work nested="fortress/container/target/impl-classes"></work>
>   -    <work nested="fortress/container/target/test-classes"></work>

 >   -    <home nested="fortress/container"></home>
 >   +    <home></home>

 >   -    <javadoc 
nested="fortress/container/target/docs/apidocs"></javadoc>
 >   +    <javadoc nested="/target/docs/apidocs"></javadoc>

and this is bad as well. I think the problem might be that one needs to 
provide '-Dcomponent.dir=fortress/container'. There should be a check 
for its existence I guess.

What should we do? Find time to invest in fixing the gump plugin so 
autogeneration becomes more dependable, and not move forward, or just 
move forward with moving things over (which I can do tomorrow) and deal 
with this trial-and-error-style?

- Leo



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

Re: notice: cvs moves

[Leo Simons <le...@apache.org>]

Leo Simons wrote:
> somewhere around 14:00 GMT on saturday (I think, depends on how long the 
> party stays fun tonite), avalon-excalibur/fortress contents are going to 
> be restructured and moved to avalon/fortress. Also, current contents of 
> avalon/ will be moved to avalon/framework. CVS history will be kept. 

done, I think. Everthing seems fine on my end...

- Leo



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

Re: notice: cvs moves

[Berin Loritsch <bl...@apache.org>]

Leo Simons wrote:
> Berin Loritsch wrote:
>  > we might want to just go ahead and get this show on the road.
> 
> I concur :D
> 
> Hi gang,
> 
> somewhere around 14:00 GMT on saturday (I think, depends on how long the 
> party stays fun tonite), avalon-excalibur/fortress contents are going to 
> be restructured and moved to avalon/fortress. Also, current contents of 
> avalon/ will be moved to avalon/framework. CVS history will be kept. 
> Brace for impact: perhaps some annoyances (in case you were planning to 
> work on saturday ;) and a gump failure or two. Oh, and you'll be needing 
> maven-beta-9.

This is Phase I of the whole process.  We will be toying with the GUMP
integration to get it to work seemlessly, so that hopefully we can can
do something like this:

$ maven avalon:update-gump

to ensure that the gump descriptor is at the latest and greatest.


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

notice: cvs moves (was: Re: cvs commit: avalon/fortress)

[Leo Simons <le...@apache.org>]

Berin Loritsch wrote:
 > we might want to just go ahead and get this show on the road.

I concur :D

Hi gang,

somewhere around 14:00 GMT on saturday (I think, depends on how long the 
party stays fun tonite), avalon-excalibur/fortress contents are going to 
be restructured and moved to avalon/fortress. Also, current contents of 
avalon/ will be moved to avalon/framework. CVS history will be kept. 
Brace for impact: perhaps some annoyances (in case you were planning to 
work on saturday ;) and a gump failure or two. Oh, and you'll be needing 
maven-beta-9.

- Leo



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

Re: cvs commit: avalon/fortress

[Berin Loritsch <bl...@apache.org>]

Leo Simons wrote:
> well, that didnt work :D
> 

<snip/>

> and this is bad as well. I think the problem might be that one needs to 
> provide '-Dcomponent.dir=fortress/container'. There should be a check 
> for its existence I guess.
> 
> What should we do? Find time to invest in fixing the gump plugin so 
> autogeneration becomes more dependable, and not move forward, or just 
> move forward with moving things over (which I can do tomorrow) and deal 
> with this trial-and-error-style?

:/

Considering the long trial and error problems that are happening, we
might want to just go ahead and get this show on the road.  Building
is very easy with Maven, and dependency resolution is pretty good.
There is no sense in holding up the progress while we try to get GUMP
integration to work.


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