Either that, or separate repositories.
The alternative would be to create a more monolithic project with its
project root one level up, so it includes both folders in question.
That seems klunky.
On Wed, Feb 23, 2011 at 6:05 AM, Indicator Veritatis wrote:
> So then how would both the existing pr
So then how would both the existing project, and the library project
be placed under version control? As separate "project roots" in the
repository?
On Feb 22, 1:04 pm, Stephen Jungels wrote:
> Probably the right solution would be to import the src folder
> separately into a library project, and
I too use SVN under Eclipse. I use the Subclipse plugin (which I
assume you use, though you didn't actually say so), and I never, NEVER
put the source path outside the root.
That said, I have to admit, that I don't have a better solution for
you for the problem of reference the same code from mult
Thanks SChaser, worked a charm.
On Oct 16, 7:06 pm, SChaser wrote:
> If you are using the JEE edition of HELIOS, the assists can be speeded
> up by turning off JAX-WS assist in the edit/advanced preference
> (Window->Preferences->Java->Editor->Content Assist->Advanced.
>
> It also appears that th
ECLIPSE is a streaming pile of dung, imho. I use helios because it
doesn't crash nearly a often as galileo.
On Oct 19, 1:24 am, JonFHancock wrote:
> Yeah. I find myself wondering why I am using it instead of Galileo.
>
> The *only* thing I like about it is the interface for installing new
> plu
Yeah. I find myself wondering why I am using it instead of Galileo.
The *only* thing I like about it is the interface for installing new
plugins.
Maybe I'll just switch back...
On Oct 18, 4:36 pm, Zsolt Vasvari wrote:
> Helios is a steaming pile of dunk, IMHO.
>
> On Oct 18, 2:30 pm, JonFHanco
Helios is a steaming pile of dunk, IMHO.
On Oct 18, 2:30 pm, JonFHancock wrote:
> Thank you an infinite number of times!
>
> I was going out of my way to not allow assists in cases where I knew
> it would be slow.
>
> On Oct 16, 12:06 pm, SChaser wrote:
>
>
>
> > If you are using the JEE edition
Thank you an infinite number of times!
I was going out of my way to not allow assists in cases where I knew
it would be slow.
On Oct 16, 12:06 pm, SChaser wrote:
> If you are using the JEE edition of HELIOS, the assists can be speeded
> up by turning off JAX-WS assist in the edit/advanced prefer
Awesome, thanks!
On Oct 16, 1:06 pm, SChaser wrote:
> If you are using the JEE edition of HELIOS, the assists can be speeded
> up by turning off JAX-WS assist in the edit/advanced preference
> (Window->Preferences->Java->Editor->Content Assist->Advanced.
>
> It also appears that the assists cycle
If you are using the JEE edition of HELIOS, the assists can be speeded
up by turning off JAX-WS assist in the edit/advanced preference
(Window->Preferences->Java->Editor->Content Assist->Advanced.
It also appears that the assists cycle through a list of suggestion
sources, starting with a differen
Did a bit of looking around and found that I don't have any of the JAX-
WS plugins installed at all in my Eclipse.
I also noticed that it only happens when I expect code assist on
"Android" based classes. Could it be ADT?
On Sep 14, 9:06 am, gnugu wrote:
> Hi,
> same problem here.
>
> I don't ha
Hi,
same problem here.
I don't have JAX-WS proposals in ContentAssist-Advanced.
I only have "Java Proposals (Task-Focused)" and "SWT Template
Proposals" and "Template Proposals".
Any suggestion?
Thanks.
On Aug 6, 8:14 am, Evan Ruff wrote:
> Hey guys,
>
> Just upgraded to 3.6 after this whole
I was experiencing the same slowness and gave up after some time
trying to tweak the eclipse arguments/options. Now, on Galileo, code
assist is absolutely perfect. Probably not what you were expecting to
hear but it is one way out if you don't have time to spare. The delay
is annoying.
On 8 jul, 0
It's super slow for me also - sometimes the content assist window will
hang for up to ~30s (in Eclipse 3.5, it takes just a few hundred ms max)
meaning that 3.6 is not usable for Android development at the moment (if
there are no workarounds..).
I've found the following bug for Eclipse regarding
This happens with me also, only sometimes. I don't know if this is
Helios or the Android stuff, but developing with Helios has more
nagging issues than Galileo has.
On Aug 6, 10:00 pm, Evan Ruff wrote:
> After upgrading to Helios, my code assist is dog slow as well.
>
> I am currently experiment
After upgrading to Helios, my code assist is dog slow as well.
I am currently experimenting with the location of Eclipse (was on D,
moving to C) as well as the memory args...
E
On Jul 8, 7:27 am, gDev wrote:
> CodeAssistveryslow
>
> any soluation for that?
--
You received this message because
I've been using Helios on Mac OS X. I initially had the XML problem
with the Strings file, but that was fixed when I added
xmlns:android="http://schemas.android.com/apk/res/android"; to the
tab.
On Jul 22, 1:32 am, jeffro wrote:
> Yes, stay on 3.5. You will get a bunch of editor errors when
>
Yes, stay on 3.5. You will get a bunch of editor errors when
attempting to edit XML files.
Visit Trackaroo.com!
Trackmaster - Motorsports Lap Timer
Dynomaster - Performance Dyno
On Jul 21, 12:55 am, hippy wrote:
> On Jul 3, 6:25 am, kihbord wrote:
>
> > Any news? I've upgraded my Eclipse to He
On Jul 3, 6:25 am, kihbord wrote:
> Any news? I've upgraded my Eclipse to Helios and Android ADT plugin is
> now missing on my Eclipse setup.
"Caution: There are known issues with the ADT plugin running with
Eclipse 3.6. Please stay on 3.5 until further notice."
from: http://developer.android.com
Any news? I've upgraded my Eclipse to Helios and Android ADT plugin is
now missing on my Eclipse setup.
On Jun 23, 12:24 pm, BuckeyeDroid wrote:
> As you're probably aware, the Helios release of Eclipse is released on
> June 23rd. Will this be supported by the Android SDK?
>
> Thanks!
--
You re
20 matches
Mail list logo
