I forgot to mention that the same happens with version 1.6.2.1.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/aUUxcT7iuQEJ.
To post
And you forgot to mention that if folder is not under svn control
everything works perfectly.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengi
It's a bug triggered by the fact that the .svn directories are read-only.
If you make those directories writable the problem *should* go away. Please
try that out and let me know.
Thanks,
Max
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for J
Not sure what you mean by make your .svn directories writable. I develop on
linux and all the .svn folders have rwx for the user under which I develop.
The development server runs as the same user. Should I make the adjustments
for group and others? What about the subfolders inside the .svn fold
Dilbert, see my reply on the ticket.
Max - that comment about svn being writable is nonsense. I wish you guys
would talk to your own support engineers. I tried that solution with my
premier support contact and it doesn't even make sense. svn directories are
always writable. This is a bug, it's
Thanks Rick for the valuable information. I do not like the idea of mixing
jars from different versions just for svn's sake. For now I'll remove GAE
SDK from svn and handle things manually which is a real pain. Hope they fix
this issue soon.
On Thursday, March 1, 2012 3:25:39 PM UTC+1, Rick Man
On Friday, 2 March 2012 08:24:40 UTC+13, dilbert wrote:
>
> Thanks Rick for the valuable information. I do not like the idea of mixing
> jars from different versions just for svn's sake. For now I'll remove GAE
> SDK from svn and handle things manually which is a real pain. Hope they fix
> thi
That's on our roadmap, but I'm waiting for Atlassian OnDemand to start
supporting maven repos for artifact deployment. It's a good goal, but
adding an SDK to subversion shouldn't cause it to break...
On Mar 1, 2:34 pm, Jonathan Chen wrote:
> On Friday, 2 March 2012 08:24:40 UTC+13, dilbert wrote:
Time to migrate to Git! :-)
Jeff
On Thu, Mar 1, 2012 at 9:25 AM, Rick Mangi wrote:
> Dilbert, see my reply on the ticket.
>
> Max - that comment about svn being writable is nonsense. I wish you guys
> would talk to your own support engineers. I tried that solution with my
> premier support con
