FeaturesPluginsDocs & SupportCommunityPartners

NetBeans Forums

 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
  

Problem upgrading to Rails 2.3.2

 
Post new topic   Reply to topic    NetBeans Forums -> Ruby Users
View previous topic :: View next topic  
Author Message
larry



Joined: 14 Oct 2008
Posts: 7
PostPosted: Fri May 22, 2009 1:57 am    Post subject: Problem upgrading to Rails 2.3.2 Reply with quote
Hi,

I've been using Netbeans for quite some time and love it - thanks to all of the people who work on it.

I'm setting up a new (Linux) environment. I installed a version of Ruby that had version 2.3.2 of Rails. My current implementation was 2.2.2 and it was in my project's /vendor/rails directory. I use Subversion for source control and have been using the new Netbeans 6.7 (Beta) IDE for a few weeks with no problem.

I figured it was time to upgrade my /vendor/rails from 2.2.2 to 2.3.2, so in Netbeans I did a Run/Debug Rake Task > rails:freeze:gems. It seemed to work fine, as the output from running the rake task shows:

Code:

(in /home/larry/NetBeansProjects/StupidTuesday)
rm -rf vendor/rails
Freezing to the gems for Rails 2.3.2
mkdir -p vendor/rails
cd vendor/rails
mv activesupport-2.3.2 activesupport
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activesupport-2.3.2'
mv activerecord-2.3.2 activerecord
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activerecord-2.3.2'
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionpack-2.3.2'
mv actionpack-2.3.2 actionpack
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionmailer-2.3.2'
mv actionmailer-2.3.2 actionmailer
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activeresource-2.3.2'
mv activeresource-2.3.2 activeresource
Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/rails-2.3.2'
cd -


I figured it was best to commit this before running rails:update, but when I tried doing that I get the following message:
Code:

'/home/larry/NetBeansProjects/StupidTuesday/vendor/rails' is not a working copy
Can't open file '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/.svn/entries': No such file or directory


But I can see the new /vendor/rails directory and all of its subdirectories, and they are marked as [New] in the Netbeans projects window.

Any suggestions on what I can do? I've spent about an hour on something that I thought was going to take 2 minutes, and it's kind of frustrating.

Thanks,
Larry
Back to top
View user's profile Send private message
Erno Mononen
Posted via mailing list.
PostPosted: Fri May 22, 2009 11:24 am    Post subject: Problem upgrading to Rails 2.3.2 Reply with quote
Hi Larry,

I don't know much about subversion, but seems like a bug either in the
svn plugin or in svn itself. Can you please file an issue for this at
http://www.netbeans.org/issues/enter_bug.cgi against the subversion
component?

BTW, can you commit from the command line? Does restarting or running
the IDE with a clean userdir (pls see
http://wiki.netbeans.org/FaqAlternateUserdir) make any difference?

Thanks,
Erno


larry wrote:
Quote:
Hi,



I've been using Netbeans for quite some time and love it - thanks to all of the people who work on it.



I'm setting up a new (Linux) environment. I installed a version of Ruby that had version 2.3.2 of Rails. My current implementation was 2.2.2 and it was in my project's /vendor/rails directory. I use Subversion for source control and have been using the new Netbeans 6.7 (Beta) IDE for a few weeks with no problem.



I figured it was time to upgrade my /vendor/rails from 2.2.2 to 2.3.2, so in Netbeans I did a Run/Debug Rake Task > rails:freeze:gems. It seemed to work fine, as the output from running the rake task shows:




Code:


(in /home/larry/NetBeansProjects/StupidTuesday)

rm -rf vendor/rails

Freezing to the gems for Rails 2.3.2

mkdir -p vendor/rails

cd vendor/rails

mv activesupport-2.3.2 activesupport

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activesupport-2.3.2'

mv activerecord-2.3.2 activerecord

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activerecord-2.3.2'

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionpack-2.3.2'

mv actionpack-2.3.2 actionpack

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/actionmailer-2.3.2'

mv actionmailer-2.3.2 actionmailer

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/activeresource-2.3.2'

mv activeresource-2.3.2 activeresource

Unpacked gem: '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/rails-2.3.2'

cd -







I figured it was best to commit this before running rails:update, but when I tried doing that I get the following message:


Code:


'/home/larry/NetBeansProjects/StupidTuesday/vendor/rails' is not a working copy

Can't open file '/home/larry/NetBeansProjects/StupidTuesday/vendor/rails/.svn/entries': No such file or directory







But I can see the new /vendor/rails directory and all of its subdirectories, and they are marked as [New] in the Netbeans projects window.



Any suggestions on what I can do? I've spent about an hour on something that I thought was going to take 2 minutes, and it's kind of frustrating.



Thanks,

Larry











Back to top
larry



Joined: 14 Oct 2008
Posts: 7
PostPosted: Fri May 22, 2009 6:40 pm    Post subject: Reply with quote
Hi Erno,

Thanks for your interest in this matter. It turns out that is a relative pain in the *&^% to upgrade Rails if you've vendored it in your project directory. The culprit? Subversion.

Most books/forums/blogs simply discuss how to originally freeze Rails. But when you go hunting for problems with upgrading Rails that's under Subversion source control - well, you quickly find out you are not alone.

After reading a bunch of posts, and for a number of my own reasons, I decided to no longer vendor Rails, i.e. I simply use the gems that are located in my Ruby installation.

Thanks again, Erno.

-- Larry
Back to top
View user's profile Send private message
Erno Mononen
Posted via mailing list.
PostPosted: Mon May 25, 2009 7:10 am    Post subject: Problem upgrading to Rails 2.3.2 Reply with quote
Hi Larry,

Thanks for following up on this, and good to know the IDE is off the hook :)

Cheers,
Erno


larry wrote:
Quote:
Hi Erno,



Thanks for your interest in this matter. It turns out that is a relative pain in the *&^% to upgrade Rails if you've vendored it in your project directory. The culprit? Subversion.



Most books/forums/blogs simply discuss how to originally freeze Rails. But when you go hunting for problems with upgrading Rails that's under Subversion source control - well, you quickly find out you are not alone.



After reading a bunch of posts, and for a number of my own reasons, I decided to no longer vendor Rails, i.e. I simply use the gems that are located in my Ruby installation.



Thanks again, Erno.



-- Larry











Back to top
Display posts from previous:   
Post new topic   Reply to topic    NetBeans Forums -> Ruby Users All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum


Powered by phpBB