You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Serhiy (JIRA)" <se...@james.apache.org> on 2009/06/17 16:08:07 UTC
[jira] Created: (JAMES-911) Migrate from Avalon to something else
Migrate from Avalon to something else
-------------------------------------
Key: JAMES-911
URL: https://issues.apache.org/jira/browse/JAMES-911
Project: JAMES Server
Issue Type: New Feature
Components: James Core
Affects Versions: Trunk
Reporter: Serhiy
Priority: Critical
Reasons:
1. Apache Avalon project was closed in 2004. There are no software projects without bugs. And Avalon bugs are not resolved for years!
2. You can't find any documentation about Apache Avalon!
I am a java developer and I was interested in Apache James project and even was going to start contributing some code. But when I started to investigate more about James I could not understand how you could use something that is years old, have no active maintenance and development and even don't have any public documentation. I even can't find any details about what exactly Avalon does! I am absolutely positive that there are a lot of modern alternatives to some Avalon. From the other point of view if Avalon was something good it would not have been closed. Avalon is closed and this means that nobody was interested in it and nobody really needed it.
If you want to attract some non payed developers to your open source project it should be interesting for them to work with your project. But there are references from your site to http://avalon.apache.org/ and when new developers see that site it does not encourage him/her to start to dig deeper.
Avalon is dead. You need to move forward!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-911) Migrate from Avalon to something else
Posted by "Bernd Fondermann (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Fondermann updated JAMES-911:
-----------------------------------
Priority: Major (was: Critical)
I feel very much like you do.
Yet, what you are describing is not a bug, and it's not critical. It's legacy.
The code and doc is there, it's in Apache Excalibur, and we can work with it. Not that we want to, but, again, it's not critical.
We discuss these things on our developer mailing list, not on the bug tracker.
You are very welcome to join us there thinking about how to move forward, JIRA just isn't the right place.
Please also note we took steps to overcome our architectural crisis. One is the spring-deployment in trunk.
Others are in discussion, longing for contributors to start working on them.
I encourage you to browse our server-dev mailing list archive to catch up with these discussions.
Also, please be more concrete and specific in the bug tracker in the future. Thanks!
> Migrate from Avalon to something else
> -------------------------------------
>
> Key: JAMES-911
> URL: https://issues.apache.org/jira/browse/JAMES-911
> Project: JAMES Server
> Issue Type: New Feature
> Components: James Core
> Affects Versions: Trunk
> Reporter: Serhiy
>
> Reasons:
> 1. Apache Avalon project was closed in 2004. There are no software projects without bugs. And Avalon bugs are not resolved for years!
> 2. You can't find any documentation about Apache Avalon!
> I am a java developer and I was interested in Apache James project and even was going to start contributing some code. But when I started to investigate more about James I could not understand how you could use something that is years old, have no active maintenance and development and even don't have any public documentation. I even can't find any details about what exactly Avalon does! I am absolutely positive that there are a lot of modern alternatives to some Avalon. From the other point of view if Avalon was something good it would not have been closed. Avalon is closed and this means that nobody was interested in it and nobody really needed it.
> If you want to attract some non payed developers to your open source project it should be interesting for them to work with your project. But there are references from your site to http://avalon.apache.org/ and when new developers see that site it does not encourage him/her to start to dig deeper.
> Avalon is dead. You need to move forward!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-911) Migrate from Avalon to something else
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-911.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0-M1
We now use spring to support JSR250 dependency injections and so no avalon is needed for all this stuff. The only
> Migrate from Avalon to something else
> -------------------------------------
>
> Key: JAMES-911
> URL: https://issues.apache.org/jira/browse/JAMES-911
> Project: JAMES Server
> Issue Type: New Feature
> Components: James Core
> Affects Versions: Trunk
> Reporter: Serhiy
> Assignee: Norman Maurer
> Fix For: 3.0-M1
>
>
> Reasons:
> 1. Apache Avalon project was closed in 2004. There are no software projects without bugs. And Avalon bugs are not resolved for years!
> 2. You can't find any documentation about Apache Avalon!
> I am a java developer and I was interested in Apache James project and even was going to start contributing some code. But when I started to investigate more about James I could not understand how you could use something that is years old, have no active maintenance and development and even don't have any public documentation. I even can't find any details about what exactly Avalon does! I am absolutely positive that there are a lot of modern alternatives to some Avalon. From the other point of view if Avalon was something good it would not have been closed. Avalon is closed and this means that nobody was interested in it and nobody really needed it.
> If you want to attract some non payed developers to your open source project it should be interesting for them to work with your project. But there are references from your site to http://avalon.apache.org/ and when new developers see that site it does not encourage him/her to start to dig deeper.
> Avalon is dead. You need to move forward!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-911) Migrate from Avalon to something else
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer reassigned JAMES-911:
-----------------------------------
Assignee: Norman Maurer
> Migrate from Avalon to something else
> -------------------------------------
>
> Key: JAMES-911
> URL: https://issues.apache.org/jira/browse/JAMES-911
> Project: JAMES Server
> Issue Type: New Feature
> Components: James Core
> Affects Versions: Trunk
> Reporter: Serhiy
> Assignee: Norman Maurer
>
> Reasons:
> 1. Apache Avalon project was closed in 2004. There are no software projects without bugs. And Avalon bugs are not resolved for years!
> 2. You can't find any documentation about Apache Avalon!
> I am a java developer and I was interested in Apache James project and even was going to start contributing some code. But when I started to investigate more about James I could not understand how you could use something that is years old, have no active maintenance and development and even don't have any public documentation. I even can't find any details about what exactly Avalon does! I am absolutely positive that there are a lot of modern alternatives to some Avalon. From the other point of view if Avalon was something good it would not have been closed. Avalon is closed and this means that nobody was interested in it and nobody really needed it.
> If you want to attract some non payed developers to your open source project it should be interesting for them to work with your project. But there are references from your site to http://avalon.apache.org/ and when new developers see that site it does not encourage him/her to start to dig deeper.
> Avalon is dead. You need to move forward!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org