Le 22/03/2012 22:26, J. Eckard a écrit :
Do we really want to keep IDE-specific support files in the repository (and
keep them updated by hand in perpetuity)? I ask because it seems like a fragile
(and tedious) process… for instance, I don't use eclipse and I have no idea if
or how this change
If those files were not there when I first used OFBiz, I would not
have known how to set up Eclipse. I agree with Scott - let the Eclipse
users worry about them.
-Adrian
Quoting Scott Gray :
The flip side of the argument would be that everyone who is using
eclipse would then have to maint
Keep it simple. Just keep the files for 1 or 2 IDEs and 1 or 2 VCSs and be
done with it.
I do think we should get rid of Aptana.
Regards
Scott
On 23/03/2012, at 8:40 PM, Nicolas Malin wrote:
> It would be interesting to put all configuration file on tools :
> * tools/ide/eclipse
> * tools/ide
It would be interesting to put all configuration file on tools :
* tools/ide/eclipse
* tools/ide/netbeans
and load configuration by ant ?
Nicolas
Le 23/03/2012 07:49, Jacques Le Roux a écrit :
I put Aptana (better free js Eclipse.plugin editor I found) and
explained at
https://cwiki.apache.org
I put Aptana (better free js Eclipse.plugin editor I found) and explained at
https://cwiki.apache.org/confluence/display/OFBADMIN/Coding+Conventions
So it's also at
https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=7766052
So we could get rid of it, yes
Other opinions?
I have mixed feelings about this:
1) it is not nice to see the IDE specific files in the OFBiz home: .project,
.classpath (for Eclipse) and ofbiz.aptana.js.format.xml (for Aptana)
** off topic question: why do we have the .hgignore file? (ignore file for
Mercurial?)
2) in the same time the Eclip
+1, this is also the conclusion I came out (with a slow brain)
Jacques
From: "Scott Gray"
The flip side of the argument would be that everyone who is using eclipse would
then have to maintain it themselves, not sure that
would be more efficient for the community.
Personally I don't really mi
This needs some thoughts, but it's too late for me, my brain can't cope, ok
trying, nothing guaranteed...
As we are trying to slim down OFBiz, my 1st answer would be yes
On the other hand I appreciate to not have to build anew .classpath each time I
work on a new project
Could not the same been
The flip side of the argument would be that everyone who is using eclipse would
then have to maintain it themselves, not sure that would be more efficient for
the community.
Personally I don't really mind cleaning it up myself when I see an error, takes
a few minutes at most. And I think that'
Do we really want to keep IDE-specific support files in the repository (and
keep them updated by hand in perpetuity)? I ask because it seems like a fragile
(and tedious) process… for instance, I don't use eclipse and I have no idea if
or how this change will affect an existing eclipse project.
10 matches
Mail list logo