hello Jason,
I had also initialy decided the same.
But later on ,I dropped the idea.
because the first thing we should do is to make this the new home of struts-workflow extension.And for that to work, we should first move all existing stuff from the living logic download page to sourceforge ,without any change.The users should still be able to download from the sourceforge ,without any change in the latest stable release,even though the change you are suggesting is just package name change.
The package name change is also on the agenda,but I think that can be part of next major release,when we plan a major functionality/architecture change.Currently if we want the existing user base to use the SWE and give feedback on the new requirements,we can just keep the code base same.
Initially there are other tasks which we can concentrate on,like getting all stuff including the documentation on source forge.
May be first thign we can start discussing the roadmap/Modifying it.I have also posted a message in Struts dev list to get the current status on this activity in main struts stream.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great.You can get started on the documentation porting stuff.As soon as you have CVS access,you can put it in there.
Also We need to decide iif we want to make a seperate module in CVC for documentation.This will help us to keep the Documentation out of main code release and update it independently.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
shirish,
I grabbed the head from cvs, looks good. However, I believe that we should drop the
com.livinglogic
and replace it with
net.sf
since this is now a sourceforge project. please let me know your thoughts on this.
jason
hello Jason,
I had also initialy decided the same.
But later on ,I dropped the idea.
because the first thing we should do is to make this the new home of struts-workflow extension.And for that to work, we should first move all existing stuff from the living logic download page to sourceforge ,without any change.The users should still be able to download from the sourceforge ,without any change in the latest stable release,even though the change you are suggesting is just package name change.
The package name change is also on the agenda,but I think that can be part of next major release,when we plan a major functionality/architecture change.Currently if we want the existing user base to use the SWE and give feedback on the new requirements,we can just keep the code base same.
Initially there are other tasks which we can concentrate on,like getting all stuff including the documentation on source forge.
May be first thign we can start discussing the roadmap/Modifying it.I have also posted a message in Struts dev list to get the current status on this activity in main struts stream.
makes sense, so a change for 2.0 then?
i can help getting the docs in place on SF, but I don't have write access to CVS yet.
Great.You can get started on the documentation porting stuff.As soon as you have CVS access,you can put it in there.
Also We need to decide iif we want to make a seperate module in CVC for documentation.This will help us to keep the Documentation out of main code release and update it independently.