プロジェクト

全般

プロフィール

Vote #66560

完了

Rails 3 support

Admin Redmine さんが4年以上前に追加. 4年以上前に更新.

ステータス:
Closed
優先度:
低め
担当者:
-
カテゴリ:
Rails support_44
対象バージョン:
開始日:
2010/02/10
期日:
進捗率:

100%

予定工数:
category_id:
44
version_id:
43
issue_org_id:
4796
author_id:
5
assigned_to_id:
1
comments:
61
status_id:
5
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[Closed]

説明

Migrate Redmine to Rails 3 once Rails is out of beta. Must make sure Redmine plugins are still functional and can be ported easily from Rails 2.x.


journals

Rails 3 final is out (http://weblog.rubyonrails.org/2010/8/29/rails-3-0-it-s-done) !

Someone already did the job : http://github.com/jeremy/redmine !

--------------------------------------------------------------------------------
Any news about this ?
--------------------------------------------------------------------------------
1.2.0 will stick with 2.3.10 (#6887)

Maybe after 1.2.0 release something will be clearer. What is engines support BTW?
--------------------------------------------------------------------------------
John Yani wrote:
> 1.2.0 will stick with 2.3.10 (#6887)
>
> Maybe after 1.2.0 release something will be clearer. What is engines support BTW?

The next release of rails (3.1) will have engines support.
--------------------------------------------------------------------------------
Eric Thomas wrote:
> The next release of rails (3.1) will have engines support.

Source/link? I fear they won't work exactly like the ones in 2.3 did, i.e. we still have to evaluate exactly what changes and how that affects us.
--------------------------------------------------------------------------------
Sources: "rails-engines site":http://rails-engines.org/, "the blog of Piotr Sarnacki":http://piotrsarnacki.com/2010/09/14/mountable-engines/, and I've got some bookmarks about the transition at home.

What's sure for now:
* Rails 3.0 supports _a kind of_ Engines, but there's no mechanism for migrations, nor copying assets automatically (nor overriding views iirc) ; for sure they're not useable in Redmine at this point
* Rails 3.1 Engines will support these kind of things (needs to be precised I know), but all documentation I read on Rails3' engines makes me think that plugin developers would have to package their plugin as a gem
* Redmine cannot support Rails 2.3.x _and_ Rails 3.x at the same time :)
--------------------------------------------------------------------------------
Just a note about .xml format : Rails 3 does not include Builder anymore, it's now one of its dependencies.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Jean-Baptiste Barth wrote:
> * Rails 3.0 supports a kind of Engines, but there's no mechanism for migrations, nor copying assets automatically (nor overriding views iirc) ; for sure they're not useable in Redmine at this point
> * Rails 3.1 Engines will support these kind of things (needs to be precised I know), but all documentation I read on Rails3' engines makes me think that plugin developers would have to package their plugin as a gem

Indeed, Rails 3.1 RC is out and supports migrations as well as moutable apps, see http://weblog.rubyonrails.org/2011/5/22/rails-3-1-release-candidate.

Notes- :

Rails 3 applications include a Gemfile and support the use of Bundler (see http://weblog.rubyonrails.org/2010/8/29/rails-3-0-it-s-done).
Rails 3.1 default scripting lib is now jQuery instead of Prototype.

--------------------------------------------------------------------------------
Is there any update on migrating to Rails 3.x? It's becoming a pain maintaining Redmine as it currently is. Upgrading to 3.0/3.1RC would definitely improve the development process.

I do understand that you are having trouble loosing compatibility to lots of good Redmine plugins, so I suggest you start Redmine + Rails 3.1RC development on a seperate branch and publish Redmine for both Rails versions in a transitional period (maybe 1 year?) giving all plugin developers time to migrate their plugins to a Rails Engine.

Any thoughts?
--------------------------------------------------------------------------------
Fabian Becker wrote:
> It's becoming a pain maintaining Redmine as it currently is.

Can't see why ?

--------------------------------------------------------------------------------
I merged trunk r6097 and following forks.
* https://github.com/goncalossilva/redmine
* https://github.com/marutosi/redmine/tree/rails3-merged
** https://github.com/marutosi/redmine/commit/13077ffdba5150e95a2a0d70eb6135ead8ed254c

I rearranged revisions.
* https://bitbucket.org/marutosi/redmine-rails3-bb-straight-20110620
** https://bitbucket.org/marutosi/redmine-rails3-bb-straight-20110620/changeset/b1cc0367a6b0
* https://github.com/marutosi/redmine/commits/rails3-straight-20110620
** https://github.com/marutosi/redmine/commit/b91eafdb008b0f0b3ff6ab830c9d07cfe393c341

--------------------------------------------------------------------------------

I updated revisions.

h3. Merged

* https://github.com/marutosi/redmine/tree/rails3-merged
** https://github.com/marutosi/redmine/commit/3e126b55cf6895fc923fbf2e3aeadda2d1d54dfa

h3. Straight revisions

* https://github.com/marutosi/redmine/commits/rails3-straight-20110622
** https://github.com/marutosi/redmine/commit/58374b477dd99b7df905b6fdb881aaf45185acf2
* https://bitbucket.org/marutosi/redmine-rails3-bb-straight-20110622
** https://bitbucket.org/marutosi/redmine-rails3-bb-straight-20110622/changeset/caeaaabe8709

--------------------------------------------------------------------------------
You should try to make it work straight with Rails 3.1 (rc4 is the last release) since (I guess) Redmine will never run with 3.0 due to the lack of engine support.

Moreover, you might detect and report some Rails 3.1 rc issues whic could be fixed before release time, making it easier to integrate with RM.

BTW, do you run Rails 3 RM with Ruby 1.9 ?
--------------------------------------------------------------------------------

I start to target Rails 3.1.

h3. Merged

* https://github.com/marutosi/redmine/tree/rails3.1-merged
** https://github.com/marutosi/redmine/commit/d8b96c046d342b82273aa0d63a36fea91b3ed200

h3. Straight revisions

* https://bitbucket.org/marutosi/redmine-rails3.1-bb
** https://bitbucket.org/marutosi/redmine-rails3.1-bb/changeset/fb582ad0e5e3
* https://github.com/marutosi/redmine/tree/rails3.1-20110625
** https://github.com/marutosi/redmine/commit/443313972d57f378197585498690c5f5f22cd4c6

The biggest issue is that ActionDispatch::Routing::Routes at *config/routes.rb* removed on Rails 3.1.
* https://bitbucket.org/marutosi/redmine-rails3.1-bb/changeset/e8800779ffb0
* https://github.com/marutosi/redmine/commit/e864d6dc582ac42aa1ef5d25b7c7810653466ff8

With dummy config/routes.rb, this revisions can boot with "ruby script/rails server",
and run "rake test:units".

--------------------------------------------------------------------------------
RoR team is organizing a hack fest for 3.1 : http://weblog.rubyonrails.org/2011/7/14/rails-3-1-hackfest
--------------------------------------------------------------------------------
I rebased on r6523.

Git:
* https://github.com/marutosi/redmine/commits/rails3.1-straight-20110822
** https://github.com/marutosi/redmine/commit/5f46bcc5ad70db3907a81312c42bff09b93b305d

Mercurial:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20110822-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20110822-hg-git/changeset/1d5fca5d898e
--------------------------------------------------------------------------------
I success to show main menu on Rails 3.1.

Git:

* https://github.com/marutosi/redmine/commits/rails3.1-straight-20110822
** https://github.com/marutosi/redmine/commit/f203473b56b14e2e2d2cbca359e1345389c8b2b5

Mercurial:

* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20110822-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20110822-hg-git/changeset/d68bc29b957b
--------------------------------------------------------------------------------
http://mrjaba.posterous.com/ruby-news-roundup-06-04-2011

> :rhtml and :rxml were finally removed as template handlers.
--------------------------------------------------------------------------------
Nice job on routes =)

Got some nice reading for you: http://www.h-online.com/open/features/From-Rails-2-3-to-3-0-1285884.html

_Edit_: permalink: http://h-online.com/-1285884
--------------------------------------------------------------------------------
Interesting article !

Etienne Massip wrote:
> Nice job on routes =)
>
> Got some nice reading for you: http://www.h-online.com/open/features/From-Rails-2-3-to-3-0-1285884.html
>
> _Edit_: permalink: http://h-online.com/-1285884

--------------------------------------------------------------------------------
If you need any direction, the Spree project has great 3.0 and 3.1 support: http://spreecommerce.com/blog

The "Extension" system they have is great as you just add a line in your Gemfile that points to a github project and vola! extra features :)

BDQ has also created Deface, A view editor that alters views based on css rules: https://github.com/railsdog/deface
--------------------------------------------------------------------------------
3.1 released 3 hours ago: http://twitter.com/#!/rails/status/108740744306634752

Release notes: http://guides.rubyonrails.org/3_1_release_notes.html
--------------------------------------------------------------------------------
Another article from the H: http://h-online.com/-1285887
--------------------------------------------------------------------------------
So, is there any official announcement regarding 3.x support? A plan? Redmine 2.0? I found nothing on Wiki. Is there anyone leading the efforts to this end?

Because I'd like to contribute to make Redmine Rails 3.x compatible. It's not clear if there's a branch for it. I guess any patch regarding this shouldn't go to master branch, isn't it? It seems Toshi is already doing some work on this. How could I be of help regarding this matter?

Second, don't you agree this is not the correct place for posting about these Rails 3.1's new features articles, like Etienne's?

Thank you.
--------------------------------------------------------------------------------
I rebased on r7627.

Git:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111015-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111015-git/changeset/b518355cf567

* https://github.com/marutosi/redmine/tree/rails3.1-straight-20111015
** https://github.com/marutosi/redmine/commit/b518355cf567a6aea40f463a879c752a308c1e32

Mercurial:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111015-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111015-hg-git/changeset/230bb3836ed1

If you run with current database of Redmine 1.2 on Rails 2.3.11,
you need to run "rake db:migrate".

In order to run tests,
you need to install object_daddy for Rails 3.1.
<pre>
ruby script/rails plugin install git://github.com/awebneck/object_daddy.git
</pre>

The revisions are from following repositories.
* https://github.com/redox/redmine
* https://github.com/mhanne/chiliproject/tree/rails-3.1
* https://github.com/thegcat/chiliproject/tree/rails-3.1

Git and Mercurial revisions are synchronized by "hg-git":http://hg-git.github.com/ .
If you want to improve it, you can choose what you like.

--------------------------------------------------------------------------------
As this is now Rails 3.1... and a lot of things will break in the upgrade anyway.

Would it be a good idea to change this to a mountable engine?
(or even a stranded engine so that users can upgrade by just changing the version in the Gemfile.)

I have experience and can help out if you go down this path.

CON: You may want to namespace everything so it plays nice with other mountable engines.
--------------------------------------------------------------------------------
David, do you have experience with the 3.1 full engines?
--------------------------------------------------------------------------------
Felix Schäfer wrote:
> David, do you have experience with the 3.1 full engines?

If by full engines you mean ones with there own logic/models/controllers/migrations that can be added by just adding something to your Gemfile.

Then yes, I use them where ever possible :)

Though I don't have all that much experience with mountable ones yet.. as 3.1 is still new and I don't really have any bread-n-butter projects in my day job that could use the functionality.
--------------------------------------------------------------------------------
David Bennett wrote:
> Felix Schäfer wrote:
> > David, do you have experience with the 3.1 full engines?
>
> If by full engines you mean ones with there own logic/models/controllers/migrations that can be added by just adding something to your Gemfile.
>
> Then yes, I use them where ever possible :)
>
> Though I don't have all that much experience with mountable ones yet.. as 3.1 is still new and I don't really have any bread-n-butter projects in my day job that could use the functionality.

No, that's full engines vs. mountable apps. Mountable apps are self-contained and referenced only in the parent routes.rb to tell which "top-level" URI the mountable app has. Full engines are "nearer" to the 2.3 engines in that they are loaded with the main app, have access to all the same models, controllers, and everything (mountable apps are fully segregated). Both types are/can be packaged as gems though.
--------------------------------------------------------------------------------
I rebased on r7962.

Git:

* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111128-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111128-git/changeset/25af42e581e9

* https://github.com/marutosi/redmine/tree/rails3.1-straight-20111128
** https://github.com/marutosi/redmine/commit/25af42e581e9eb1b83253130e661edcfc50cd810

Mercurial:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111128-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111128-hg-git/changeset/e3236691b1c5

Revisions are from a following repository.
* https://github.com/paneidos/redmine

--------------------------------------------------------------------------------

I rebased on r7967.

Git:

* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111129-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111129-git/changeset/98b79bc74907
* https://github.com/marutosi/redmine/tree/rails3.1-straight-20111129
** https://github.com/marutosi/redmine/commit/98b79bc74907735b148d45e5e9ccb17a31656f10

Mercurial:

* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111129-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111129-hg-git/changeset/70aa2e5132cc

I adapted r7900 labelled_tabular_form_for.
--------------------------------------------------------------------------------
I rebased on r8089.

Git:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111205-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111205-git/changeset/f63cfecfc970
* https://github.com/marutosi/redmine/tree/rails3.1-straight-20111205
** https://github.com/marutosi/redmine/commit/f63cfecfc9708cfd3f838b8444071da3d50a1e10

Mercurial:
* https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111205-hg-git
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111205-hg-git/changeset/adeada76a040

h2. Changes

* rename css to css.erb
* use asset_path instead of hard-coded path

<pre>
<code class="diff">
diff --git a/app/assets/stylesheets/scm.css.erb b/app/assets/stylesheets/scm.css.erb
--- a/app/assets/stylesheets/scm.css.erb
+++ b/app/assets/stylesheets/scm.css.erb
@@ -9,7 +9,7 @@

li.change {
list-style-type:none;
- background-image: url(../images/bullet_black.png);
+ background-image: url(<%= asset_path "bullet_black.png" %>);
background-position: 1px 1px;
background-repeat: no-repeat;
padding-top: 1px;
</code>
</pre>

Revisions are from following repository.
* https://github.com/escline/redmine
--------------------------------------------------------------------------------
I rebased on r8304.

Git:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-git/changeset/10734937ddd8
* Rails 3.2.0.rc1
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-git/changeset/c62200edd4d7

https://github.com/marutosi/redmine/tree/rails3.1-straight-20111220

* Rails 3.1.3
** https://github.com/marutosi/redmine/commit/10734937ddd8
* Rails 3.2.0.rc1
** https://github.com/marutosi/redmine/commit/c62200edd4d7639da893a4c3d5ea6b987daf5b98

Mercurial:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-hg-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-hg-git/changeset/97f974aea9ea
* Rails 3.2.0.rc1
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20111220-hg-git/changeset/af9fdd89cd7d

--------------------------------------------------------------------------------
I rebased on r8480.
Almost all routing tests pass.

Git:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-git/changeset/c44c5c55c9d2
* Rails 3.2.0.rc1
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-git/changeset/90bda5801f9d

https://github.com/marutosi/redmine/tree/rails3.1-straight-20120103

* Rails 3.1.3
** https://github.com/marutosi/redmine/commit/c44c5c55c9d2
* Rails 3.2.0.rc1
** https://github.com/marutosi/redmine/commit/90bda5801f9d

Mercurial:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-hg-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-hg-git/changeset/a940b29a8193
* Rails 3.2.0.rc1
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120103-hg-git/changeset/d4fc04c4ef05

--------------------------------------------------------------------------------
I rebased on r8633.
route.rb is all new Rails3 format.

Git:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-git/changeset/9b87ac4f7d4a
* Rails 3.2.0.rc2
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-git/changeset/8ef3aa076ac3

https://github.com/marutosi/redmine/tree/rails3.1-straight-20120111

* Rails 3.1.3
** https://github.com/marutosi/redmine/commit/9b87ac4f7d4a
* Rails 3.2.0.rc2
** https://github.com/marutosi/redmine/commit/8ef3aa076ac3

Mercurial:

https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-hg-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-hg-git/changeset/38da0d316f07
* Rails 3.2.0.rc2
** https://bitbucket.org/marutosi/redmine-rails3.1-straight-20120111-hg-git/changeset/827d62056e93

--------------------------------------------------------------------------------
Rails 3.2.0 is "out":http://weblog.rubyonrails.org/2012/1/20/rails-3-2-0-faster-dev-mode-routing-explain-queries-tagged-logger-store

Is there any work break down structure of work required to complete porting Redmine to Rails 3? Are there any routine tasks that unexperienced programmer could help with?
--------------------------------------------------------------------------------
I rebased on r8864.

Changes:

* update Rails 3.2.1.
* rails-dev-tweaks supports Rails 3.2.

Git:

https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-git/changeset/b024f722f1e7
* Rails 3.2.1
** https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-git/changeset/9ff1ec404049

https://github.com/marutosi/redmine/commits/rails3-straight-20120213

* Rails 3.1.3
** https://github.com/marutosi/redmine/commit/b024f722f1e7
* Rails 3.2.1
** https://github.com/marutosi/redmine/commit/9ff1ec404049

Mercurial:

https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-hg-git

* Rails 3.1.3
** https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-hg-git/changeset/761b7f104d6d
* Rails 3.2.1
** https://bitbucket.org/marutosi/redmine-rails3-straight-20120213-hg-git/changeset/b57dc3557b3c

--------------------------------------------------------------------------------
I would like to work on this. I am thinking in the lines of forking on github and submitting pull requests whenever I have completed a significant task. Talking of tasks, is there any list of issues/to-do's that I can work on?
--------------------------------------------------------------------------------
Sridhar P wrote:
> I would like to work on this. I am thinking in the lines of forking on github and submitting pull requests whenever I have completed a significant task. Talking of tasks, is there any list of issues/to-do's that I can work on?

I think you can start with cloning and setting up test environment to see what doesn't work. Then if you manually tested all features and everything seems to work, you can run redmine tests and see if there are any failures. I there are no any, you're done.

Then you can think of how to enable users to use Redmine with both Rails 2 and Rails 3. As of now the work is done/coordinated by Toshi. Seems like every week he rebases his work on the latest revision from svn trunk. AFAIK, there are no any todo lists. But you can look into git/hg log. There are many commits marked as "TODO", so you can review these patches to see what's wrong with them.
--------------------------------------------------------------------------------
I have a working copy that runs and passes the full tests suite with Rails 3.1. There's some work to be done in order to provide the current features for Redmine plugins (migrations, view overriding, assets...) but still, most plugins won't be compatible out of the box. And honestly, I'm a bit disappointed with the performance. Redmine is 1.5x to 2x slower than with Rails 2.3. With ruby 1.9.3, it barely runs as fast as current trunk with Rails 2.3 + ruby 1.8.7.

> Then you can think of how to enable users to use Redmine with both Rails 2 and Rails 3.

That's not really an option. There are too many changes in Rails 3 to support both versions with the same code base.
--------------------------------------------------------------------------------
Here are the results of my quick performance tests (Rails 2.3 vs. Rails 3.2):

!response_time.png!
--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> I have a working copy that runs and passes the full tests suite with Rails 3.1.
Could you create branch and commit to it such as source:sandbox/rails-2.3 ?

--------------------------------------------------------------------------------
Did anybody find out how to get wiki working? I've got an error:

can't write unknown attribute `versioned_type'
activerecord (3.2.1) lib/active_record/attribute_methods/write.rb:34:in `write_attribute'
activerecord (3.2.1) lib/active_record/attribute_methods/dirty.rb:67:in `write_attribute'
activerecord (3.2.1) lib/active_record/attribute_methods.rb:31:in `[]='
vendor/plugins/acts_as_versioned/lib/acts_as_versioned.rb:383:in `clone_versioned_model'
vendor/plugins/acts_as_versioned/lib/acts_as_versioned.rb:303:in `save_version_on_create'
app/controllers/wiki_controller.rb:154:in `update'

the problem is in the following line:

vendor/plugins/acts_as_versioned/lib/acts_as_versioned.rb
194: self.versioned_inheritance_column = options[:inheritance_column] || "versioned_#{inheritance_column}"

Somehow versioned_type column is missing.
--------------------------------------------------------------------------------
*Update:*

Seems like it is because Redmine doesn't use rake tasks provided by acts_as_versioned: create_versioned_table and drop_versioned_table

So, I should add migration field for versioned_type myself
--------------------------------------------------------------------------------
Here is a patch to enable wiki editing in Rails 3.2.1 https://github.com/marutosi/redmine/pull/6
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Can u explain ur results? For the first look rails 2.3 and ruby 1.9.3 performns best, and not the newest stack with rails 3.

Jean-Philippe Lang wrote:
> Here are the results of my quick performance tests (Rails 2.3 vs. Rails 3.2):
>
> !response_time.png!

--------------------------------------------------------------------------------
Terence Mill wrote:
> Can u explain ur results? For the first look rails 2.3 and ruby 1.9.3 performns best, and not the newest stack with rails 3.

Indeed, Rails 2.3 performs best as mentionned above. The graph shows the average response times in seconds for a few actions (assets are not involved here). Not much more to explain...

--------------------------------------------------------------------------------
Terence Mill wrote:
> Can u explain ur results? For the first look rails 2.3 and ruby 1.9.3 performns best, and not the newest stack with rails 3.

Here is the detailed explanation:
http://bibwild.wordpress.com/2011/07/12/more-thoughts-on-unbearably-slow-rails3/
Shortly, it is because of extra ruby garbage collection, caused by increased size of the call stack in Rails 3.

--------------------------------------------------------------------------------
Hello good sirs.

Any chance of getting this done finally, especially in light of this (rails 2.3 no longer receives security updates from the core team): https://groups.google.com/d/msg/rubyonrails-talk/ZzL90ec7iAQ/368GA-TeQ6AJ ?

--
Regards,
Alex

--------------------------------------------------------------------------------
The upgrade to Rails 3.0 is planned for Redmine 2.0 that should be the next major release.
--------------------------------------------------------------------------------
Really waiting for this Release, especially Prototype.js has been replaced with jQuery for ajax calls.
--------------------------------------------------------------------------------
Terence Mill wrote:
> Really waiting for this Release, especially Prototype.js has been replaced with jQuery for ajax calls.

"prototype-rails" and "prototype_legacy_helper" provide compatibility.
--------------------------------------------------------------------------------
Terence Mill wrote:
> Really waiting for this Release, especially Prototype.js has been replaced with jQuery for ajax calls.

What difference does this make?

--------------------------------------------------------------------------------
Etienne Massip wrote:
> Terence Mill wrote:
> > Really waiting for this Release, especially Prototype.js has been replaced with jQuery for ajax calls.
>
> What difference does this make?

This is also one of the things I would like to see in Redmine 2.0. Upgrading to Rails 3 however does not imply that Redmine 2.0 will use JQuery. I personally doubt that this effort is also about migrating to JQuery.

If you are using Redmine as is it doesn't matter what framework is being used. But if you want to extend Redmine, it does. So for example I added functionality which uses a JQuery Slides (http://slidesjs.com/). Now my 'extended' Redmine installation uses JQuery and not Prototype for some pages. Using Prototype and JQuery in one website is of course not so nice but necessary because JQuery has a lot more to offer.

--------------------------------------------------------------------------------
Onno van der Straaten wrote:
> Using Prototype and JQuery in one website is of course not so nice but necessary because JQuery has a lot more to offer.

Whatever, Redmine has not Javascript API, jQuery and Prototype can coexist very well and I can't see why using 2 tooling frameworks would be bad.
--------------------------------------------------------------------------------
Hmm i hoped we will get rid of prototype because we wanna integrate our SSo Solution for redmine (which is based on CAS) and the problem with redirect on ajax request direct after an revelidation attempt of the SSO gatway (a java servlet filter in front of web.xml war of a jruby redmine tomcat installation), this redirect of an XMLHttpRequest (fired by prototyp.js i think) is not understood by the browser. This leads to "nothing happening" in the application as long a non ajax request is triggered by the request caused by user click.
Our SSO Gateway in front of the redmine can understand jquery ajax requests and wraps them so that the redirect in the browser works. This does not work for prototype js.

There is no documentation where and how often ajax is used in redmine forms, else we could think about moving this urls by filter out of the sso secure area and workawound the problem.

Etienne Massip wrote:
> Terence Mill wrote:
> > Really waiting for this Release, especially Prototype.js has been replaced with jQuery for ajax calls.
>
> What difference does this make?

--------------------------------------------------------------------------------
Terence Mill wrote:
> Our SSO Gateway in front of the redmine can understand jquery ajax requests and wraps them so that the redirect in the browser works. This does not work for prototype js.

What is done with jQuery making the Ajax request understood that you can't do with Prototype?
--------------------------------------------------------------------------------
Please open a new ticket for any issue related to Rails3 support.
--------------------------------------------------------------------------------


related_issues

relates,Closed,8421,REST API may produce invalid json
relates,Closed,4005,Setup shoulda to make it easier to test
relates,Closed,8989,r6351 causes unexpected chars to be displayed in calendar
relates,Closed,8751,Email notification: bug, when number of recipients more then 8
relates,Closed,6317,Template names conventions
relates,Closed,9252,Regression: application title escaped 2 times
relates,New,9759,HTML minification and compression

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0