macOS Xcode 3.1, what a headache! Please fix the bugs!!!!

[m3the01]

Seriously, how can such a great/reasonable product go down the drain?

Was software testing done on the recent release?

Everything major seems to work but there are some little things just killing me,

Take for instance java development. It use to be hella easy to change the compiler and such. Now these options have disappeared. I reverted to manually changing them in the build.xml file.

Secondly, on every previous development ive done a grouping of similar files together in group folders. Now in 3.1 there is a src directory that contains all the src files and its impossible to add a group folder to this subfolder.

The best i can manage is create s folder outside of the src sub folder and copy references to the original source files. This is annoying considering one has to hunt through all source files for the one u want to add to add to a group.

This seems like not such a big deal when were talking 10-15 src files, but when u have hundreds of src files and need to regroup it gets seriously annoying needing to hunt through all the files for the ones u want.

Previously u could group in src, which is really nice.

Also ive found that none of the build options like, -Xms256m -Xmx256m, do anything.

What an honest to god joke!

Thank god i dont do any of my C/C++ development in there, can only imagine the nightmare.

Had to vent, spent over 4 hrs configuring things that use to take 5 minutes.

Please fix these little subtleties, they are major important!!

 

[Catfish_Man]

Using Xcode for Java projects has always been a pretty bad idea. It's really designed for C and ObjC first, and C++ a distant second.

 

[lee1210]

Maybe you should submit a bug report/feature request to apple, rather than rant here? Others may sympathize with you here, but aren't going to be able to do much for you.

-Lee

 

[m3the01]

Yeah already done that, just kinda needed to rant a little.

Got a lot of work to do, and blowing 4-5 hours on nothing is really trying.

 

[jeremy.king]

Got a lot of work to do, and blowing 4-5 hours on nothing is really trying.

Then use a real Java IDE - IDEA, Eclipse, or Netbeans.

 

[Cromulent]

Then use a real Java IDE - IDEA, Eclipse, or Netbeans.

Out of those Netbeans seems the most polished.

 

[lazydog]

Secondly, on every previous development ive done a grouping of similar files together in group folders. Now in 3.1 there is a src directory that contains all the src files and its impossible to add a group folder to this subfolder.

I think I know what's going on here. If you create a project from a Java template it creates a source folder in the source tree view for you. This folder is a reference to the source directory in your project directory. It's not a group folder (group folders are displayed in yellow and folder references are blue). A (blue) reference folder lists the contents of a real directory and is 'read only', hence the reason why you cannot drop a group folder into it.

A group folder is just an abstraction in Xcode and doesn't necessarily map to a real directory structure. If you want to organise your source files just organise them into subdirectories in your project source directory. Because the (blue) src folder is a reference it will automatically reflect any changes you make to the structure of your source directory.

The other way is to delete the src folder from your project and add groups, subgroups etc and then add your source files into these. But if you're developing for Java you'd probably want to organise your source files into subdirectories that matched your package hierarchy anyway. So in this respect I think Xcode has got it right by switching to using a src folder reference.

I know I haven't explained the above very well, but I think you'll see what I mean.

By the way, -Xms256m -Xmx256m are runtime options!

b e n