You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2003/09/10 12:45:36 UTC
CVS annoyance...
Last update I got, among many other things...
cvs server: merlin-plugin/project.xml is no longer in the repository
In fact, the whole merlin-plug content is gone.
And during compile,
BUILD FAILED
File...... file:/home/niclas/dev/opensource/avalon-sandbox/merlin/
Element... maven:reactor
Line...... 61
Column.... 32
/home/niclas/dev/opensource/avalon-sandbox/merlin/merlin-plugin/target/project.xml
(No such file or directory)
even after I made a "maven clean".
But removing the merlin-plug/target directory, we get beyond this point.
Why does Maven get the idea to look for the xml file? Shouldn't "clean" be
constructed in recursive manner as well and the "target/" directory name be
'volatile'?
--- < > ---
In any event, that is small compared to that the whole of Merlin CVS doesn't
build at all. I get this message;
The build cannot continue because of the following unsatisfied dependencies:
avalon-repository-spi-1.0-beta-1-RC1.jar (no download url specified)
avalon-extension-spi-1.0-RC1.jar (no download url specified)
Will this be resolved soon?
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
>On Thursday 11 September 2003 14:06, Stephen McConnell wrote:
>
>
>>Niclas Hedhman wrote:
>>
>>
>
>
>
>>>Any thoughts in this regard, i.e. making HEAD a bit more stable, and use
>>>branching instead of sandbox (such as the current framework changes).
>>>
>>>
>>Maybe this could be could come in handy - has anyone tried it?
>>http://maven.apache.org/reference/plugins/scm/goals.html
>>
>>
>
>Not me, I'm dead new to Maven, and not sure if I like it or not yet.
>
Maven is a love-it/hate-it sort of relationship.
:-)
--
Stephen J. McConnell
mailto:mcconnell@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 11 September 2003 14:06, Stephen McConnell wrote:
> Niclas Hedhman wrote:
> >Any thoughts in this regard, i.e. making HEAD a bit more stable, and use
> >branching instead of sandbox (such as the current framework changes).
>
> Maybe this could be could come in handy - has anyone tried it?
> http://maven.apache.org/reference/plugins/scm/goals.html
Not me, I'm dead new to Maven, and not sure if I like it or not yet.
Looking at the docs fro SCM, it sounds that it only solves the "release
management", which is slightly different of what I tried to raise.
It should be useful though.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
>On Wednesday 10 September 2003 19:01, Stephen McConnell wrote:
>
>
>>Niclas Hedhman wrote:
>>
>>
>>>Last update I got, among many other things...
>>>
>>>
>>Things are very nearly back to stable state.
>>Individual subproject builds are fine. Just sorting some final things
>>out on the composite build.
>>
>>
>
>Just curious;
>We have here a policy that HEAD always builds correctly, and the complete set
>of Unit tests has to pass to allow commits.
>When starting out on any new task, big or small, a branch is created, and when
>everything works well, the branch is merged to HEAD and if pass then the
>changes committed. We also tag HEAD after commits with TaskID, but that is an
>internal to us thing.
>With 14 developers, we have had 2 instances over 18 months where there was a
>"hick-up", both caused by issuance of wrong CVS commands...
>
>Any thoughts in this regard, i.e. making HEAD a bit more stable, and use
>branching instead of sandbox (such as the current framework changes).
>
Maybe this could be could come in handy - has anyone tried it?
http://maven.apache.org/reference/plugins/scm/goals.html
Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Leo Simons <le...@apache.org>.
Niclas Hedhman wrote:
> Any thoughts in this regard, i.e. making HEAD a bit more stable, and use
> branching instead of sandbox (such as the current framework changes).
Unfortunately, many avalon developers are not very accustomed to working
with CVS branches (even if it is a better tool for managing this kind of
thing :D). So we generally don't; a notable exception being Phoenix CVS.
It's a knowledge issue.
cheers!
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 10 September 2003 19:01, Stephen McConnell wrote:
> Niclas Hedhman wrote:
> >Last update I got, among many other things...
>
> Things are very nearly back to stable state.
> Individual subproject builds are fine. Just sorting some final things
> out on the composite build.
Just curious;
We have here a policy that HEAD always builds correctly, and the complete set
of Unit tests has to pass to allow commits.
When starting out on any new task, big or small, a branch is created, and when
everything works well, the branch is merged to HEAD and if pass then the
changes committed. We also tag HEAD after commits with TaskID, but that is an
internal to us thing.
With 14 developers, we have had 2 instances over 18 months where there was a
"hick-up", both caused by issuance of wrong CVS commands...
Any thoughts in this regard, i.e. making HEAD a bit more stable, and use
branching instead of sandbox (such as the current framework changes).
Cheers,
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: CVS annoyance...
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
>Last update I got, among many other things...
>
Things are very nearly back to stable state.
Individual subproject builds are fine. Just sorting some final things
out on the composite build.
Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org