It seems this mailing list has not been deactivated... Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
Hello.
Please disable the following infrastructure resources for Apache Avalon as
per the ASF Board resolution:
1. Mailing Lists:
dev@avalon.apache.org
users@avalon.apache.org
cvs@avalon.apache.org
pmc@avalon.apache.org
3. SVN Repository:
https://svn.apache.org/repos/asf/avalon
4. WIKI
http://wiki.apache.org/wiki
These resources should all be made "read only."
I've already made all the Avalon related JIRA projects 'browse only.' We
still need to setup the redirects for the Avalon site, so I'd like to hold
off on any changes to /www/avalon.apache.org. Hopefully we'll have that
all worked out within a day or two.
Thanks.
jaaron
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
You (or someone else) has reset your password.
---------------------------------------------------------------------
Your password has been changed to: S81XJN
You can change your password here:
http://nagoya.apache.org/jira/secure/ViewProfile.jspa
Here are the details of your account:
---------------------------------------------------------------------
Username: avalon
Email: dev@avalon.apache.org
Full Name: Avalon Developers
Password: S81XJN
(You can always retrieve these via the "Forgot Password" link on the signup page)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Issue Subscription
Filter: Avalon Castle Open Issues (4 issues)
Open issues for Avalon Castle
Subscriber: avalon
Project: Avalon Castle
Status: Open, In Progress
Key Summary
AVNSHARP-8 ProxyGenerator throws System.ExecutionEngineException on executing a generated
Guid property
http://nagoya.apache.org/jira/browse/AVNSHARP-8
AVNSHARP-5 Plan and code a implementation for ILoggingManager
http://nagoya.apache.org/jira/browse/AVNSHARP-5
AVNSHARP-4 Review all ILogger in each class
http://nagoya.apache.org/jira/browse/AVNSHARP-4
AVNSHARP-2 Add Avalon# documentation section to http://avalon.apache.org
http://nagoya.apache.org/jira/browse/AVNSHARP-2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Messages like this are IMHO the main reason, why Avalon failed.
Stephen, you should understand, that community always means compromise.
You didn't seem to be able to accept that. In the end, these tensions
lead to the end of Avalon.
Story is over, no need to kick a dead horse. One of the good things
about ASF code _is_, that you can take it somewhere else and go on with
it.
Good luck with Metro/Merlin. But now, please let the dead rest.
Regards
Henning
On Wed, 2004-12-01 at 02:26, Stephen McConnell wrote:
> > -----Original Message-----
> > From: Niclas Hedhman [mailto:niclas@hedhman.org]
>
> > And on behalf of the developers at Avalon, I would like to Thank ALL
> the
> > past Chairs and members of the Avalon PMC, for a all-in-all a job well
>
> > done.
>
> I'm sorry - but you will have to exclude myself from the above
> endorsement.
>
> The Avalon community established a PMC to represent the community
> interests concerning the direction and administration of the Avalon
> project. The community interests were clear - a single platform, one
> specification, a cohesive solution. That decision was not respected by
> the outgoing chair nor the board of directors of the ASF.
>
> That is not the definition of a job-well-done. Instead this is much
> more about the weakness of individuals - in particular the members of
> the board of directors of the ASF and not least of all our outgoing
> chain. However - there is much that can be learnt from this. The
> weaknesses of the BOD can be attributed to their collective
> unwillingness to confront members of their own board. The weakness of
> our Chair was more a question of his personal loyalty to the community.
>
> Irrespective of the above obstacles a real and tangible alternative to
> ASF continues under http://www.dpml.net. The fundamental difference -
> no distinction between the people who contribute and the people who run
> the process.
>
> Stephen.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: community-unsubscribe@apache.org
> For additional commands, e-mail: community-help@apache.org
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
--Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
> -----Original Message----- > From: Greg Stein [mailto:gstein@apache.org] > Sent: 01 December 2004 03:58 > To: pmc@avalon.apache.org; dev@avalon.apache.org; users@avalon.apache.org; > board@apache.org; community@apache.org > Subject: Re: [ANN] Avalon Closed > > On Wed, Dec 01, 2004 at 02:26:43AM +0100, Stephen McConnell wrote: > >... > > The Avalon community established a PMC to represent the community > > interests concerning the direction and administration of the Avalon > > project. > > Um. No. The Apache Software Foundation established the PMC. Its > purpose was to provide the necessary (legal) oversight of the > development of the Avalon project. That oversight is/was necessary to > establish the appropriate legal protection for the committers on the > project and the ASF itself. > > It is the ASF that releases the Avalon code, not the committers. To do > that properly, certain things need to be done for the benefit of all > involved. You may disagree with some of those processes, their > purpose, and how it was done, but that is simply too bad. They need to > exist so that our users can properly trust the code we provide. Greg: My agreement on the subject of the process is already established (I contributed to and voted in favor of the adoption of the process of which we speak). What I disagree to is the actions of the Member of the Board and the Chair in ignoring the decisions of the community and ignoring the adopted processes established under the direction of the board. > > The community interests were clear - a single platform, one > > specification, a cohesive solution. > > No, that was never clear. That was *your* desire, Stephen, and you did > everything you could to steer things in that direction. You alienated > people, you berated people, and you generally made things unpleasant > for anybody that did not have your same "vision". Avalon went through > many phases, and the "single platform" you mention was simply the last > thing standing after your various escapades. Greg - you are a chairman of the ASF. In this capacity you have an obligation to at least to state the truth. This community voted on the subject of Avalon direction. The decision of this community was to move forward with a single platform. That was not the decision of an individual - it was the decision of a community - a decision that you, the other members of the board, and the chair chose to ignore. > > That decision was not respected by > > the outgoing chair nor the board of directors of the ASF. > > The Board had nothing to do with these directions or choices. Our only > (recent) involvment was that the VP in charge of Avalon asked us to > terminate the project, so we did. A board decision taken *without* the endorsement of the Avalon PMC, *without* a vote of the community and clearly in contradiction with the expressed interests of the committers at that time. Let's not try and rewrite history just yet. Stephen. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
Stephen McConnell wrote: > The Avalon community established a PMC to represent the community > interests concerning the direction and administration of the Avalon > project. The community interests were clear - a single platform, one > specification, a cohesive solution. That decision was not respected by > the outgoing chair nor the board of directors of the ASF. The Board had nothing to do with the closure. The "outgoing chair" tried for a long time to resolve it by other changes. The fact is that you decided that your vision was more important than the community's vision, and proceeded to engineer consensus by attrition, both within the community and within the PMC, including asking both myself and another PMC member to resign. Despite that, I continued to work to keep Merlin at the ASF, as did at least one Director who had offered to personally mentor the project. You were not willing to accept any proposals, and prefered to remove Merlin elsewhere. Aaron is right to thank all of those who put blood, sweat and tears into Avalon. > Irrespective of the above obstacles a real and tangible alternative to > ASF continues under http://www.dpml.net. The fundamental difference - > no distinction between the people who contribute and the people who run > the process. In other words, you make the rules and run the show. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
On Wed, Dec 01, 2004 at 02:26:43AM +0100, Stephen McConnell wrote: >... > The Avalon community established a PMC to represent the community > interests concerning the direction and administration of the Avalon > project. Um. No. The Apache Software Foundation established the PMC. Its purpose was to provide the necessary (legal) oversight of the development of the Avalon project. That oversight is/was necessary to establish the appropriate legal protection for the committers on the project and the ASF itself. It is the ASF that releases the Avalon code, not the committers. To do that properly, certain things need to be done for the benefit of all involved. You may disagree with some of those processes, their purpose, and how it was done, but that is simply too bad. They need to exist so that our users can properly trust the code we provide. > The community interests were clear - a single platform, one > specification, a cohesive solution. No, that was never clear. That was *your* desire, Stephen, and you did everything you could to steer things in that direction. You alienated people, you berated people, and you generally made things unpleasant for anybody that did not have your same "vision". Avalon went through many phases, and the "single platform" you mention was simply the last thing standing after your various escapades. > That decision was not respected by > the outgoing chair nor the board of directors of the ASF. The Board had nothing to do with these directions or choices. Our only (recent) involvment was that the VP in charge of Avalon asked us to terminate the project, so we did. Also recently, we directed the Avalon project to step up and deal with the problems that it has had, and to take proper care of its legacy users. But we did not specify any particular solutions. The PMC came up with the solutions. > That is not the definition of a job-well-done. Instead this is much > more about the weakness of individuals - in particular the members of > the board of directors of the ASF and not least of all our outgoing > chain. However - there is much that can be learnt from this. The > weaknesses of the BOD can be attributed to their collective > unwillingness to confront members of their own board. I have no idea what you're talking about here. The Board of Directors of the Apache Software Foundation does not have or need any "confrontation". As a group, we work together very, very well. In the past three years or so that I've been on the Board, I can only recall *two* votes that were not unanimous. We reach consensus very easily, and it isn't because we beat some unnamed board member into submission. > The weakness of > our Chair was more a question of his personal loyalty to the community. I disagree. I very much respect what J Aaron Farr has done for Avalon. You made it a rather difficult task, but he stepped up and dealt with it. He didn't have to, but he did. And he did it because the community needed somebody to deal with the issues. Further, I think that he handled it very, very well. Some of the posts that he has written shows great insight into why great communities are needed here at Apache, and what makes a great community. He's shown that he can also help to shape those communities, despite adversity that was caused by certain folks. At times, he didn't take as much action as I might have, but I fully believe that he had good reasons, and I support the choices he made. Aaron has my respect, and I hope he continues to be involved in other Apache projects. > Irrespective of the above obstacles a real and tangible alternative to > ASF continues under http://www.dpml.net. The fundamental difference - > no distinction between the people who contribute and the people who run > the process. You may not like the process, but the legal backing provided by the ASF for the code that we release needs it. And in the end, our users need that. You are certainly free to create a different model, but it does mean the resulting code will not have the same kinds of assurances the ASF provides, nor will you have an entity that can assume legal liability for your results. It's your choice to make, and for your users to decide whether that is important. Cheers, -g -- gstein@apache.org ... ASF Chairman ... http://www.apache.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
> -----Original Message----- > From: Niclas Hedhman [mailto:niclas@hedhman.org] > And on behalf of the developers at Avalon, I would like to Thank ALL the > past Chairs and members of the Avalon PMC, for a all-in-all a job well > done. I'm sorry - but you will have to exclude myself from the above endorsement. The Avalon community established a PMC to represent the community interests concerning the direction and administration of the Avalon project. The community interests were clear - a single platform, one specification, a cohesive solution. That decision was not respected by the outgoing chair nor the board of directors of the ASF. That is not the definition of a job-well-done. Instead this is much more about the weakness of individuals - in particular the members of the board of directors of the ASF and not least of all our outgoing chain. However - there is much that can be learnt from this. The weaknesses of the BOD can be attributed to their collective unwillingness to confront members of their own board. The weakness of our Chair was more a question of his personal loyalty to the community. Irrespective of the above obstacles a real and tangible alternative to ASF continues under http://www.dpml.net. The fundamental difference - no distinction between the people who contribute and the people who run the process. Stephen. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
On Monday 29 November 2004 22:39, J Aaron Farr wrote: > On a personal note, I want to thank all the developers and users who > have made this experiment and community happen. I look forward to > working with many of you in the new projects forming from Avalon. Thank > you. And on behalf of the developers at Avalon, I would like to Thank ALL the past Chairs and members of the Avalon PMC, for a all-in-all a job well done. Few, if any, Apache projects has spawned so many new technologies and interesting material as Avalon, and perhaps this inventiveness was part of its demise. Once again I want to urge all users of the different technologies that used to be hosted at Avalon, to actively seek out their respective new homes. (see Aaron's mail for details.) Cheers Niclas -- +------//-------------------+ / http://www.dpml.net / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
The Apache Software Foundation Board passed the following resolution
closing Avalon during the 2004 ApacheCon:
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Avalon project
due to the separation of the community into new projects
WHEREAS, the Avalon PMC is unable to further fulfill the
responsibilities of creation, maintenance, and support of the
Avalon software
NOW, THEREFORE, BE IT RESOLVED, that the Apache Avalon Project is
hereby terminated; and be it further
RESOLVED, that the Excalibur PMC be and hereby is tasked with
maintenance of the Avalon framework software; and be it further
RESOLVED, that the Apache Avalon PMC be and hereby is no longer
responsible for the creation and maintenance of software related to
component and service management, based on software licensed to the
Foundation; and be it further
RESOLVED, that the office of "Vice President, Apache Avalon" is
hereby terminated; and be it further
RESOLVED, that the Apache Avalon PMC is hereby terminated.
What does this mean?
--------------------
Avalon is now officially closed. We will be working with the Apache
Infrastructure team to close all Avalon resources over the next few
days. The mailing lists archives will remain available; the SVN and CVS
repositories will become read only; the currently distributed software
will remain available via distribution mirrors; the site will be
reconstructed to present a "closure" message and appropriate redirects.
Example closure message:
http://avalon.apache.org/closed.html
Where will I get support/code/updates for Avalon?
-------------------------------------------------
As previously announced, Avalon Framework, LogKit, and Cornerstone have
been moved to Apache Excalibur (http://excalibur.apache.org) along with
the original ECM and Fortress code. The Excalibur team includes many
experienced Avalon developers and support questions should be directed
there.
Forks of Phoenix and Merlin have started at Codehaus Loom and DPML Metro
respectively. Users of those software packages are encouraged to
investigate these projects.
I strongly urge all subscribers of these Avalon mailing lists to
subscribe to the mailing lists of one or more of the projects mentioned
above:
Excalibur Mailing Lists:
http://excalibur.apache.org/mail-lists.html
DPML Mailing Lists:
http://www.dpml.net/central/about/resources/lists.html
Codehaus Loom Mailing Lists:
http://loom.codehaus.org/Mailing+lists
For more information about the Avalon closure, please review the October
24 announcement:
http://www.mail-archive.com/users%40avalon.apache.org/msg05033.html
I have also attached the October 2004 Avalon PMC report below.
On a personal note, I want to thank all the developers and users who
have made this experiment and community happen. I look forward to
working with many of you in the new projects forming from Avalon. Thank
you.
J Aaron Farr
Apache Avalon PMC Chair
--------------------------------------------------------------------------------
Avalon PMC Report: October 2004
In response to the Board's comments and recommendations of 23 Sept 2004:
"The Board hereby requests that the Avalon PMC step up and properly
manage the Avalon framework. Support your existing users of that
framework, including the other projects at the ASF."
The Avalon PMC, in its current condition, is not capable of complying
with this request. Consequently, the PMC is working with the Excalibur
project to transfer the Avalon framework code and other Avalon
utilities (LogKit and Cornerstone) to Excalibur which has shown a
willingness and capacity to perform such support.
With respect to the Merlin TLP, the proposals have been withdrawn.
The Merlin developers have decided to not further seek TLP status in
the ASF but rather create a fork of Merlin dubbed Metro to be hosted at
DPML.net [1].
Seeing as the development of existing software under Avalon now has or
will soon have new hosts, we recommend to the Board the Avalon project
be closed. With that in mind, the following points should be noted:
1. The Apache James project currently uses Avalon Phoenix which has
not been under active development or support for some time.
There is a fork of Phoenix at Codehaus.org called Loom. A
support solution for James (either hosting Phoenix itself or
migrating to Loom) should be found before Avalon's closure.
2. The Metro fork has been announced but is not yet active. We
would prefer that Avalon not be closed until the fork is active
and Merlin users have been notified.
3. The transfer of code between Avalon and Excalibur has not yet
taken place, though positive votes on the matter have occurred in
both projects.
4. We have not yet determined what site resources if any should remain
available following Avalon's closure. An example "closed" Avalon
site is at http://www.apache.org/~farra/avalon . We are unaware
of any policy or precedent we should turn to for this decision.
Consequently, we ask the Board give the Avalon PMC until the next
Board meeting (14 November 2004) to handle the points above before
official closure of the project. At that time, the Avalon project
resources (site, svn repository, mailing lists, wiki, jira, ...) can
be deactivated or made read-only by the infrastructure group.
We appreciate the patience and support of the Board on this matter.
Thank you.
J Aaron Farr
[1] http://marc.theaimsgroup.com/?l=avalon-dev&m=109782104731231&w=2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Issue Subscription
Filter: Avalon Castle Open Issues (4 issues)
Open issues for Avalon Castle
Subscriber: avalon
Project: Avalon Castle
Status: Open, In Progress
Key Summary
AVNSHARP-8 ProxyGenerator throws System.ExecutionEngineException on executing a generated
Guid property
http://nagoya.apache.org/jira/browse/AVNSHARP-8
AVNSHARP-5 Plan and code a implementation for ILoggingManager
http://nagoya.apache.org/jira/browse/AVNSHARP-5
AVNSHARP-4 Review all ILogger in each class
http://nagoya.apache.org/jira/browse/AVNSHARP-4
AVNSHARP-2 Add Avalon# documentation section to http://avalon.apache.org
http://nagoya.apache.org/jira/browse/AVNSHARP-2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Issue Subscription
Filter: Avalon Castle Open Issues (4 issues)
Open issues for Avalon Castle
Subscriber: avalon
Project: Avalon Castle
Status: Open, In Progress
Key Summary
AVNSHARP-8 ProxyGenerator throws System.ExecutionEngineException on executing a generated
Guid property
http://nagoya.apache.org/jira/browse/AVNSHARP-8
AVNSHARP-5 Plan and code a implementation for ILoggingManager
http://nagoya.apache.org/jira/browse/AVNSHARP-5
AVNSHARP-4 Review all ILogger in each class
http://nagoya.apache.org/jira/browse/AVNSHARP-4
AVNSHARP-2 Add Avalon# documentation section to http://avalon.apache.org
http://nagoya.apache.org/jira/browse/AVNSHARP-2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Just to let you know: I'm changing the Laboratory/Castle pages to direct the users to proper places. Thanks -- Cheers, hammett http://www.digitalcraftsmen.com.br/~hammett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
Hi all, even if Avalon is closing down, we are still using it, so here is a small patch, making the db-hsql facility implementation export the DatabaseService in order to be able to set a dependency on it from other components, so the dbserver get's started up before a dependant client tries to access it. Cheers /peter <<db.txt>> --------------------------------- Peter Neubauer Software Manager ScanCoin Industries AB
> -----Original Message----- > From: Farr, Aaron [mailto:Aaron.Farr@am.sony.com] > So I agree with you Stephen that we should have allowed for the natural > division of Avalon. In the meantime the housekeeping remains to be done: * no pmc vote on the subject of avalon * no community vote on the subject of avalon * no publication of the infamous board report Aaron - it's your job to close this properly. Anything less is a fear of 'what if'. Cheers, Steve. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
There are so many untruths in this email I don't know where to begin. > -----Original Message----- > From: Stephen McConnell [mailto:mcconnell@dpml.net] > > it demonstrates in a quasi natural evolution of communities though > a process of division. And yet in the case of Avalon - the natural > division has been interfered with by a member of the Board of Directors > of the Apache Software Foundation that has a stated objective of killing > the project This is blatantly not true. No one has a stated objective of killing the project. Drop the conspiracy theory. While you really didn't understand it, Stefano was your best friend and ally on the Board. He was honestly working to give Metro a chance. But you never trusted him. Your loss. There was certainly much resistance to a Metro TLP and I tried very hard for many months to help all parties see why natural division of Avalon was a proper course of action. This was argued in the PMC and before the Board. But there were very few proponents. The reasons are varied and there's no point in going into it all now. But it is certainly NOT as simple as you are explaining. In reality, the time for separation was two years ago when Avalon became a TLP. So I agree with you Stephen that we should have allowed for the natural division of Avalon. But you were as much of a roadblock to that as anyone else. > On the point of procedure - the Board of Director may choose to close > down Avalon. The point of interest concerns their justification for > this action. At this time there has been no community decision to do > this (just attacks on individual contributors - largely on private list > to the benefit of Members). First off, it's not up to the community, it's up to the Board. The Board has sole responsibility and authority when it comes to closing down projects. Of course, they will listen to the community and PMC, but in the end it's their decision. In this case, the Board made requests of the Avalon PMC and the PMC is no longer able to comply. Therefore, the Avalon PMC should be dismantled. > At the level of the PMC there have been no > decisions on this point (largely a function of the fact that all the > primary committers have left the PMC in disgust or frustration to the > continued intervention of Apache Members and hove chosen to continue > outside of the foundation). There was a decision. It was a recommendation to the Board to close the project. > There is noting in what I have said that suggests anyone is wrong. I > have suggested that Stefano's actions are not necessarily in-line with > the stated objectives of the foundation - but that's an issue for the > Apache Board of Directors. I have also suggested that Aaron is in a bad > position and I've attempted to point out to him that he could easily be > pushed into a context where he is be used and the bunny to take the > fall. On that point I'm uncomfortable because I was one of the people to > nominate Aaron to the job he's now holding - and nothing you can say > will remove that fact that Aaron is being screwed good and proper by > this organization. Can I say something since I'm the one you say is being made into a "bunny"? I certainly don't feel I'm being "screwed good and proper by this organization." If anything, I feel I have received a tremendous amount of support, especially by the Board, in my efforts here. So, please, don't insult me or my intelligence by claiming I'm simply a pawn of those you believe are after you. > Stefano - ball is in your court. No Stephen, the ball is gone. The game is over. jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
On Sun, 2004-11-14 at 03:46 +0100, Stephen McConnell wrote: (...) > > Five pages of graph theory - proving what? Seriously, what the hell > is > > this? I've noticed big factual errors in the paper, like the size of the Jetspeed blob in the last drawing with names, and the absence of Turbine, which was actually more than double Jetspeed's size at the time. So I would be careful to use these results without having further access to raw data they used Regards -- Santiago Gala <sgala@hisitech.com> High Sierra Technology, SLU
> -----Original Message----- > From: Leo Sutic [mailto:leo.sutic@gmail.com] > Sent: 13 November 2004 16:30 > To: Avalon Developers List > Subject: Re: FW: Organizational analysis of ASF codebases > > Steve, > > you're known for responding with extremely verbose emails that few, if > any, understand the point of. You right - I've written a few longish email in my time. > I think you've outdone yourself now. Nah - that was short - the link my have been longish but the content was interesting and we can hardly make me responsible for the content of the work of someone else (although I really should doubt that if you believe everything you read on the members list). > Five pages of graph theory - proving what? Seriously, what the hell is > this? What it demonstrates in a quasi natural evolution of communities though a process of division. And yet in the case of Avalon - the natural division has been interfered with by a member of the Board of Directors of the Apache Software Foundation that has a stated objective of killing the project. If we contrast the natural progression with the Avalon progression - something is wrong. Why is it that when the community majority wishes to move in a particular direction - one fork of the division is killed? Could it be because of the actions of Stefano following his stated agenda? Could it be a result of the unwillingness of the Chair of the Apache Software Foundation to stand up and stop something that was driven by ignorance of the real facts? Will the Members of the Board of the Apache Software Foundation endorse these actions as part of their role of supporting the community that has contributed in volume to this organization? > If you want to do make a procedural case for the closing of Avalon > being somehow against Apache rules, then make that case. But make it > properly. What rules do you base your argument on? Why do they apply > in this case? On the point of procedure - the Board of Director may choose to close down Avalon. The point of interest concerns their justification for this action. At this time there has been no community decision to do this (just attacks on individual contributors - largely on private list to the benefit of Members). At the level of the PMC there have been no decisions on this point (largely a function of the fact that all the primary committers have left the PMC in disgust or frustration to the continued intervention of Apache Members and hove chosen to continue outside of the foundation). > While you have whined about a lot of things, you have yet to provide a > serious and coherent argument as to why you are right and everybody > else is wrong. There is noting in what I have said that suggests anyone is wrong. I have suggested that Stefano's actions are not necessarily in-line with the stated objectives of the foundation - but that's an issue for the Apache Board of Directors. I have also suggested that Aaron is in a bad position and I've attempted to point out to him that he could easily be pushed into a context where he is be used and the bunny to take the fall. On that point I'm uncomfortable because I was one of the people to nominate Aaron to the job he's now holding - and nothing you can say will remove that fact that Aaron is being screwed good and proper by this organization. > Just hinting around that perhaps, maybe, conceivably, > there might just be something unexplained somewhere, that just maybe, > possibly, might, perhaps be possible to interpreted in a way as to > bolster your argument does not cut it. Stefano - can I quote your protected emails? do any of you you objections if I quote you 'protected' list emails? > We'll listen to reason, not to vague hints. Let's try and close this with at lest a token degree on honesty. Stefano - ball is in your court. Stephen. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
Steve, you're known for responding with extremely verbose emails that few, if any, understand the point of. I think you've outdone yourself now. Five pages of graph theory - proving what? Seriously, what the hell is this? If you want to do make a procedural case for the closing of Avalon being somehow against Apache rules, then make that case. But make it properly. What rules do you base your argument on? Why do they apply in this case? While you have whined about a lot of things, you have yet to provide a serious and coherent argument as to why you are right and everybody else is wrong. Just hinting around that perhaps, maybe, conceivably, there might just be something unexplained somewhere, that just maybe, possibly, might, perhaps be possible to interpreted in a way as to bolster your argument does not cut it. We'll listen to reason, not to vague hints. On Fri, 12 Nov 2004 04:41:45 +0100, Stephen McConnell <mcconnell@dpml.net> wrote: > a bigger question to answer? Yes - why do you disgrace yourself like this? /LS --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/AVALON-5?page=history ]
Niclas Hedhman closed AVALON-5:
-------------------------------
> Patch for scheduler-impl
> ------------------------
>
> Key: AVALON-5
> URL: http://nagoya.apache.org/jira/browse/AVALON-5
> Project: Avalon
> Type: Bug
> Components: CORNERSTONE
> Environment: merlin 3.3.0
> Reporter: Jon Elson-Green
> Attachments: timescheduler.diff
>
> The priority queue for scheduled events fails for large times in the future (such as
a cron event set some months in advance) because it casts the time difference to an int.
> The patch instead returns a -1, 0 or 1 based on the difference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/AVALON-6?page=history ]
Niclas Hedhman closed AVALON-6:
-------------------------------
> The Merlin tutorials simple-webserver does not run ...
> ------------------------------------------------------
>
> Key: AVALON-6
> URL: http://nagoya.apache.org/jira/browse/AVALON-6
> Project: Avalon
> Type: Bug
> Components: CORNERSTONE
> Versions: 4.3.0
> Reporter: Morten Haavaldsen
>
> The tutorial on simple-web has a dependency which does not work.
> The cornerstone-sockets-impl-1.0.0.jar
> It tries to download a version 2 of the cornerstone-sockets-api which does not exist?
> Hope you can help.
> /Morten
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/AVALON-6?page=history ]
Niclas Hedhman resolved AVALON-6:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
See http://excalibur.apache.org for further support.
> The Merlin tutorials simple-webserver does not run ...
> ------------------------------------------------------
>
> Key: AVALON-6
> URL: http://nagoya.apache.org/jira/browse/AVALON-6
> Project: Avalon
> Type: Bug
> Components: CORNERSTONE
> Versions: 4.3.0
> Reporter: Morten Haavaldsen
>
> The tutorial on simple-web has a dependency which does not work.
> The cornerstone-sockets-impl-1.0.0.jar
> It tries to download a version 2 of the cornerstone-sockets-api which does not exist?
> Hope you can help.
> /Morten
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/AVALON-4?page=history ]
Niclas Hedhman closed AVALON-4:
-------------------------------
> CDI capability for Cornerstone-ConnectionManager
> ------------------------------------------------
>
> Key: AVALON-4
> URL: http://nagoya.apache.org/jira/browse/AVALON-4
> Project: Avalon
> Type: Improvement
> Components: CORNERSTONE
> Reporter: Paul Hammant
> Assignee: Paul Hammant
> Attachments: AbstractConnectionManager.java, AvalonLoggerConnectionMonitor.java, CDIConnectionManager.java,
CommonsLoggingConnectionMonitor.java, ConnectionMonitor.java, NullConnectionMonitor.java,
cdi.patch
>
> Attahced patch and java files allow CDI (Constructor Dependency Injection) capability
for Connection Manager.
> This does not take away Avalon-Framework capability, merely suplement the tool with CDI
capability.
> Comments ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/AVALON-4?page=history ]
Niclas Hedhman resolved AVALON-4:
---------------------------------
Resolution: Fixed
Avalon is shutting down.
See http://excalibur.apache.org for further support.
> CDI capability for Cornerstone-ConnectionManager
> ------------------------------------------------
>
> Key: AVALON-4
> URL: http://nagoya.apache.org/jira/browse/AVALON-4
> Project: Avalon
> Type: Improvement
> Components: CORNERSTONE
> Reporter: Paul Hammant
> Assignee: Paul Hammant
> Attachments: AbstractConnectionManager.java, AvalonLoggerConnectionMonitor.java, CDIConnectionManager.java,
CommonsLoggingConnectionMonitor.java, ConnectionMonitor.java, NullConnectionMonitor.java,
cdi.patch
>
> Attahced patch and java files allow CDI (Constructor Dependency Injection) capability
for Connection Manager.
> This does not take away Avalon-Framework capability, merely suplement the tool with CDI
capability.
> Comments ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/CENTRAL-20?page=history ]
Niclas Hedhman resolved CENTRAL-20:
-----------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> merlin-3.3.0-install.exe
> ------------------------
>
> Key: CENTRAL-20
> URL: http://nagoya.apache.org/jira/browse/CENTRAL-20
> Project: Metro Central
> Type: Bug
> Environment: windows 2000
> Reporter: yang hongtao
>
> merlin-3.3.0-install.exe excuted . the quick link is created property is "C:\merlin\docs\starting\tutorials\index.html"
> i think "C:\merlin\docs\starting\tutorial\index.html" is correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/CENTRAL-20?page=history ]
Niclas Hedhman closed CENTRAL-20:
---------------------------------
> merlin-3.3.0-install.exe
> ------------------------
>
> Key: CENTRAL-20
> URL: http://nagoya.apache.org/jira/browse/CENTRAL-20
> Project: Metro Central
> Type: Bug
> Environment: windows 2000
> Reporter: yang hongtao
>
> merlin-3.3.0-install.exe excuted . the quick link is created property is "C:\merlin\docs\starting\tutorials\index.html"
> i think "C:\merlin\docs\starting\tutorial\index.html" is correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-1?page=history ]
Niclas Hedhman closed STUDIO-1:
-------------------------------
> Use kernel/impl to resolve the repository
> -----------------------------------------
>
> Key: STUDIO-1
> URL: http://nagoya.apache.org/jira/browse/STUDIO-1
> Project: Merlin Studio
> Type: Improvement
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Use the Kernel/Impl to resolve Merlins repository
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-2?page=history ]
Niclas Hedhman closed STUDIO-2:
-------------------------------
> Create a Preference page, to edit Merlin.properties and kernel.xml
> ------------------------------------------------------------------
>
> Key: STUDIO-2
> URL: http://nagoya.apache.org/jira/browse/STUDIO-2
> Project: Merlin Studio
> Type: Improvement
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Create a Preferencepage to edit all the values of merlin.properties and kernel xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-1?page=history ]
Niclas Hedhman resolved STUDIO-1:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> Use kernel/impl to resolve the repository
> -----------------------------------------
>
> Key: STUDIO-1
> URL: http://nagoya.apache.org/jira/browse/STUDIO-1
> Project: Merlin Studio
> Type: Improvement
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Use the Kernel/Impl to resolve Merlins repository
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-2?page=history ]
Niclas Hedhman resolved STUDIO-2:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> Create a Preference page, to edit Merlin.properties and kernel.xml
> ------------------------------------------------------------------
>
> Key: STUDIO-2
> URL: http://nagoya.apache.org/jira/browse/STUDIO-2
> Project: Merlin Studio
> Type: Improvement
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Create a Preferencepage to edit all the values of merlin.properties and kernel xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-4?page=history ]
Niclas Hedhman resolved STUDIO-4:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> [egg] Repository Browser
> ------------------------
>
> Key: STUDIO-4
> URL: http://nagoya.apache.org/jira/browse/STUDIO-4
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Niclas has started this. The GUI part is "kind-of" working but requires improvements.
should be made
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-4?page=history ]
Niclas Hedhman closed STUDIO-4:
-------------------------------
> [egg] Repository Browser
> ------------------------
>
> Key: STUDIO-4
> URL: http://nagoya.apache.org/jira/browse/STUDIO-4
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
> Assignee: Andreas Oberhack
>
> Niclas has started this. The GUI part is "kind-of" working but requires improvements.
should be made
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-5?page=history ]
Niclas Hedhman closed STUDIO-5:
-------------------------------
> [egg] Maven Repository Browser Plug-In
> --------------------------------------
>
> Key: STUDIO-5
> URL: http://nagoya.apache.org/jira/browse/STUDIO-5
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
>
> The Repository Browser has a extension point defined, so that additional repositories
or "views" of repositories could be browsed. The Maven is the first, but it is VERY CRUDE
in its info, so I was planning to put in RDF which DESCRIBES a Maven plugin, and the Repository
can read.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-6?page=history ]
Niclas Hedhman closed STUDIO-6:
-------------------------------
> [egg] Component Packaging
> --------------------------
>
> Key: STUDIO-6
> URL: http://nagoya.apache.org/jira/browse/STUDIO-6
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
>
> Currently, there is no official way to "package" a component for publishing. All components
now are too "code-centric" and doesn't go beyond that, into the land of user accessible items.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-5?page=history ]
Niclas Hedhman resolved STUDIO-5:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> [egg] Maven Repository Browser Plug-In
> --------------------------------------
>
> Key: STUDIO-5
> URL: http://nagoya.apache.org/jira/browse/STUDIO-5
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
>
> The Repository Browser has a extension point defined, so that additional repositories
or "views" of repositories could be browsed. The Maven is the first, but it is VERY CRUDE
in its info, so I was planning to put in RDF which DESCRIBES a Maven plugin, and the Repository
can read.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-6?page=history ]
Niclas Hedhman resolved STUDIO-6:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> [egg] Component Packaging
> --------------------------
>
> Key: STUDIO-6
> URL: http://nagoya.apache.org/jira/browse/STUDIO-6
> Project: Merlin Studio
> Type: New Feature
> Reporter: Andreas Oberhack
>
> Currently, there is no official way to "package" a component for publishing. All components
now are too "code-centric" and doesn't go beyond that, into the land of user accessible items.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-7?page=history ]
Niclas Hedhman closed STUDIO-7:
-------------------------------
> [egg] Specification Wizard
> --------------------------
>
> Key: STUDIO-7
> URL: http://nagoya.apache.org/jira/browse/STUDIO-7
> Project: Merlin Studio
> Type: New Feature
> Components: REQUIREMENT
> Reporter: Andreas Oberhack
>
> I strongly believe in the separation of Interfaces from Implementations. A lot stronger
than Stephen (newly convert), and that the development cycle for Specification is somewhat
different from the Implementation. Specification doesn't have UnitTests, it has Compatibility
Tests, which should "follow" the specification to the Implementation phase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-7?page=history ]
Niclas Hedhman resolved STUDIO-7:
---------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> [egg] Specification Wizard
> --------------------------
>
> Key: STUDIO-7
> URL: http://nagoya.apache.org/jira/browse/STUDIO-7
> Project: Merlin Studio
> Type: New Feature
> Components: REQUIREMENT
> Reporter: Andreas Oberhack
>
> I strongly believe in the separation of Interfaces from Implementations. A lot stronger
than Stephen (newly convert), and that the development cycle for Specification is somewhat
different from the Implementation. Specification doesn't have UnitTests, it has Compatibility
Tests, which should "follow" the specification to the Implementation phase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[ http://nagoya.apache.org/jira/browse/STUDIO-8?page=history ]
Niclas Hedhman closed STUDIO-8:
-------------------------------
> [egg] Implementation Wizard
> ---------------------------
>
> Key: STUDIO-8
> URL: http://nagoya.apache.org/jira/browse/STUDIO-8
> Project: Merlin Studio
> Type: New Feature
> Components: REQUIREMENT
> Reporter: Andreas Oberhack
>
> The Implementation wizard asks for an Implementation to create the skeleton for, and
will generate quite a lot automatically, including the runs of Compatibility Tests as well
as Unit tests. And much more...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org