Just as a "me too" I can say that not checking in the .* files is the way
to go when working in teams. There are many problems it solves. I
completely agree with nick here.
On Apr 7, 2012 8:18 AM, "Nicholas Kwiatkowski" wrote:
> Your Flex 4.6 is not the same as my Flex 4.6. They are close, but t
Your Flex 4.6 is not the same as my Flex 4.6. They are close, but the
problem is I don't have an SDK compiler named "Flex 4.6.0" on my machine (I
have "Flex 4.6.0-23043" and "Flex 4.6.0-23201"). Additionally, I also add
certain compiler arguments to all of my projects. By having it included,
its
Just keep in mind that svn:ignore can't be applied on files already checked in
the repository. These should be manualy removed first and then set svn:ignore.
Tomislav
On 7. 4. 2012., at 13:22, Left Right wrote:
> svn:ignore is a Subversion documented property, whatever sets it is using
> Subv
svn:ignore is a Subversion documented property, whatever sets it is using
Subversion to support it, so it's fine to do that from any client. This
setting also gets transferred to other checkouts, so if you ignore a file
on your end, and I happen to create a file by the same name on my end, it
will
On 4/7/2012 4:11 AM, Tomislav Pokrajcic wrote:
Before committing project from Eclipse try setting svn:ignore for various Eclipse
settings files (Team -> add to svn:ignore).
That way you only commit sources and keep project settings for yourself.
Wouldn't these settings be specific to the SVN
On 4/7/2012 3:38 AM, Justin Mclean wrote:
HI,
Once I set my compiler options to what they are supposed to
be on my machine, the errors cleared up and everything was fine.
I'd assume the SDK wasn't set to a version in the project but just "use
default". This could also cause errors if you had
>
>
>
> Perhaps having some other way of generating an build ant build script
> from the FB project file would be useful?
>
>
I don't see exactly how as the same issues persist, mainly that not
everyone keeps their SDKs in the same place so path fixing etc will still
have to happen.
It's just a c
Before committing project from Eclipse try setting svn:ignore for various
Eclipse settings files (Team -> add to svn:ignore).
That way you only commit sources and keep project settings for yourself.
Cheers,
Tomislav
On 7. 4. 2012., at 04:45, Jeffry Houser wrote:
> On 4/6/2012 10:22 PM, Nich
How I set up the project:
1. I didn't merge the SDKs, instead I imported from both locations the
libraries I needed.
2. My eclipse workspace contains a lot of settings (mostly syntax
highlighting), that I don't want to loose, and it's in an entirely
different place from where I check the source cod
Hi,
> Yep, pretty much why it's an annoyance.
Actually I think it's more of an annoyance if you don't know what the compiler
settings, SDK version, library paths etc etc are.
Even if you don't use Flash Builder the file are still mostly human readable
and contain the required settings.
Altern
HI,
> Once I set my compiler options to what they are supposed to
> be on my machine, the errors cleared up and everything was fine.
I'd assume the SDK wasn't set to a version in the project but just "use
default". This could also cause errors if you had a different SDK set by
default and impor
On 4/6/2012 10:22 PM, Nicholas Kwiatkowski wrote:
I would recommend against it. It forces me to import your project
into my workspace, versus having a new project that I can import
cleanly from SVN.
I don't understand why it forces you to import the project, as opposed
to creating your ow
On Friday, April 6, 2012, Nicholas Kwiatkowski wrote:
> Jeffery,
>
> I would recommend against it. It forces me to import your project into my
> workspace, versus having a new project that I can import cleanly from SVN.
> When I imported your code, it had about 30 errors I had to hunt and peck
>
Jeffery,
I would recommend against it. It forces me to import your project into my
workspace, versus having a new project that I can import cleanly from SVN.
When I imported your code, it had about 30 errors I had to hunt and peck
to find (these were just compiler errors, dealing with having a d
On 4/6/2012 8:15 PM, Omar Gonzalez wrote:
I would of course, suspect Eclipse to lock it's workspace
settings files. By the way, just asking - why do you want to
commit it?
I have no idea what the "Apache" way is regarding this. But,
checking in the Flash Buil
On 4/6/2012 8:04 PM, Left Right wrote:
I have no idea what the "Apache" way is regarding this. But,
checking in the Flash Builder /Eclipse project files will make
it insanely easy for anyone--who uses Flash Builder--to share
the project. They just "import proje
>
>
> I would of course, suspect Eclipse to lock it's workspace settings files.
>> By the way, just asking - why do you want to commit it?
>>
>
> I have no idea what the "Apache" way is regarding this. But, checking in
> the Flash Builder /Eclipse project files will make it insanely easy for
> a
>
> I have no idea what the "Apache" way is regarding this. But, checking in
>> the Flash Builder /Eclipse project files will make it insanely easy for
>> anyone--who uses Flash Builder--to share the project. They just "import
>> projects from another workspace" and it works. It's much easier t
On 4/6/2012 3:59 PM, Left Right wrote:
I had this error happen to me before many times when using Surefire
reports (with Maven builds). It used to locks files, but it can be
just any other program not closing pipes to open files.
So, can you try to move all staged files elsewhere, just for the s
I had this error happen to me before many times when using Surefire reports
(with Maven builds). It used to locks files, but it can be just any other
program not closing pipes to open files.
So, can you try to move all staged files elsewhere, just for the sake of
making sure they can be manipulated
On 4/6/2012 1:42 PM, Left Right wrote:
Are you sure the error is not on your end?
No, I'm not.
All files staged are accessible (read permissions, not locked, not in
the read-only fs)?
Correct; all the files I was trying to commit should be accessible
without issues.
--
Jeffry Houser
Te
Are you sure the error is not on your end? All files staged are accessible
(read permissions, not locked, not in the read-only fs)?
Best.
Oleg
On 4/6/2012 12:44 PM, Alex Harui wrote:
You are using https?
Yes!
On 4/6/12 9:30 AM, "Jeffry Houser" wrote:
I'm not quite sure if this problem is my fault or something else is
going on; but I'm trying to commit something to my whiteboard area; and
a few files in I got a "Generic I/O
You are using https?
On 4/6/12 9:30 AM, "Jeffry Houser" wrote:
>
> I'm not quite sure if this problem is my fault or something else is
> going on; but I'm trying to commit something to my whiteboard area; and
> a few files in I got a "Generic I/O Error" and I'm at a complete loss
> what to d
24 matches
Mail list logo
