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?
Jacques
From: "Jacopo Cappellato" <[email protected]>
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 Eclipse files are very well maintained by the community (it is clear that the user base is large) and so I
would tend to keep them... also we do not update jars so frequently
3) even if I don't use Eclipse, most editors provide the ability to load a project from an Eclipse project (or similar) so this is
not only a benefit for Eclipse users
All in all I would say, we could keep/tolerate Eclipse specific files (I would get rid of Aptana, unless there is a large user
base); but the implied message is not: "please contribute the configuration for your IDE; the more we have the better is".
Jacopo
On Mar 22, 2012, at 11:40 PM, Jacques Le Roux wrote:
+1, this is also the conclusion I came out (with a slow brain)
Jacques
From: "Scott Gray" <[email protected]>
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's the
way
it should be, the users of a specific IDE should bear the burden of keeping it
up to date, others shouldn't have to worry about
it. If we started including some other IDE's config files I certainly wouldn't
want to have to deal with them.
Regards
Scott
On 23/03/2012, at 10:26 AM, J. Eckard wrote:
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.
Joe
On Mar 22, 2012, at 5:05 PM, [email protected] wrote:
Author: eckardjf
Date: Thu Mar 22 21:05:17 2012
New Revision: 1304061
URL: http://svn.apache.org/viewvc?rev=1304061&view=rev
Log:
update eclipse classpath file to reflect jetty container upgrade
Modified:
ofbiz/trunk/.classpath
Modified: ofbiz/trunk/.classpath
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/.classpath?rev=1304061&r1=1304060&r2=1304061&view=diff
==============================================================================
--- ofbiz/trunk/.classpath (original)
+++ ofbiz/trunk/.classpath Thu Mar 22 21:05:17 2012
@@ -138,12 +138,21 @@
<classpathentry kind="lib"
path="framework/jcr/lib/jackrabbit-spi-commons-2.3.3.jar"/>
<classpathentry kind="lib" path="framework/jcr/lib/jackrabbit-ocm-2.0.jar"
sourcepath="/ocm"/>
<classpathentry kind="lib" path="framework/jcr/lib/jcr-2.0.jar"/>
- <classpathentry kind="lib"
path="framework/jetty/lib/jasper-compiler-5.5.15.jar"/>
- <classpathentry kind="lib"
path="framework/jetty/lib/jasper-runtime-5.5.15.jar"/>
- <classpathentry kind="lib" path="framework/jetty/lib/jetty-6.1.11.jar"/>
- <classpathentry kind="lib"
path="framework/jetty/lib/jetty-ajp-6.1.11.jar"/>
- <classpathentry kind="lib"
path="framework/jetty/lib/jetty-sslengine-6.1.11.jar"/>
- <classpathentry kind="lib"
path="framework/jetty/lib/jetty-util-6.1.11.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/com.sun.el-2.2.0.v201108011116.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-ajp-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-continuation-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-http-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-io-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-security-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-server-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-servlet-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-util-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-webapp-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/jetty-xml-8.1.2.v20120308.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/org.apache.jasper.glassfish-2.2.2.v201112011158.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar"/>
+ <classpathentry kind="lib"
path="framework/jetty/org.eclipse.jdt.core-3.7.1.jar"/>
<classpathentry kind="lib" path="framework/service/lib/axis.jar"/>
<classpathentry kind="lib" path="framework/service/lib/axis-ant.jar"/>
<classpathentry kind="lib" path="framework/service/lib/wsdl4j.jar"/>
