grr
Hani Suleiman
You've just checked in a idea project file that won't load for people
who aren't using maven and don't have it installed. It's a maven
commit you made, please be careful about what other local
modifications end up getting checked in.
Jesse Kuhnert
I think my stupid plugin did this to me without my knowledge /
consent. (I didn't use it for testng and don't use it for any project
other than one)
Is there a common way people deal with idea files changing underneath
them for things like this? Ie local vs. shared properties? To be safe
I guess I can just make sure that I never commit an idea file to the
repo for testng. (or at least try to remember to un-select them )
F-ing hell...it shouldn't be this complicated...
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Hani Suleiman
file list before committing, in case something slips in by mistake.
Mark Derricutt
Cédric Beust ♔
I tend to move the .ipr and build.xml files into their own "Project Files" change list, so that they don't get commited automatically from the default change list. Seems to work nicely for this sort of thing.
Couldn't you also simply "ignore" them?
--
Cédric
Jesse Kuhnert
of the more important properties er something..?
guess this is one thing eclipse does do better at least.. ;)
Of course all this trouble wouldn't have happened if it weren't for me
and my plugins... (sorry)
Cédric Beust ♔
I'm guessing an svn:ignore would eliminate the ability to share some
of the more important properties er something..?
Can't you just put an ignore on these two files? (that's what we do for .classpath and .project, the Eclipse files).
--
Cédric
Jesse Kuhnert
them or similar but I'm not sure I know how to do it properly other
than svn:ignore .
Looking at my other project's .ipr/.iws files it does seem like at
least one of these files could be ignored..I don't know, it looks like
all the files contain important-ish information. Doing an svn:ignore
would mean forcing everyone else to ignore it as well.
Maybe there's no problem at all ? Even if this curs-ed maven plugin
I'm using does modify the files it perhaps doesn't matter unless you
are using the plugin as well? (which I'm not, I'm guessing it's
writing some state to say that it shouldn't be enabled? f-ing
weird...maybe it's the tapestry plugin ..I did notice that in another
non tapestry/non testng project. Sounds like plugins need a better
global space to write meta to for specific projects that are local to
a single machine only.)
I'll do whatever people want, just not sure what that should be.
On 4/5/07, Cédric Beust ♔ <cbe...@google.com> wrote:
>
>
Jesse Kuhnert
settings from the original project that made me start using idea.
Whatever they had me run must have done some kind of perma fuck
setting on my client so that I've been inadvertently dropping little
bits of maven pooh over all my projects. god I hope no one else
noticed.. :/
I'll fix it..whatever it is. sorry again
Alexandru Popescu ☀
In fact we are not :-). Both Eclipse and IDEA project settings are
versioned, the idea being that so far we've been able to keep it at
the level that somebody checking out the project will be able to set
it in Eclipse/IDEA immediately.
./alex
--
.w( the_mindstorm )p.
TestNG co-founder
EclipseTestNG Creator
> --
> Cédric
>
> >
>