Discussion:
It is safer for eclipse.org projects to remove .classpath and .project from git when using tycho ?
(too old to reply)
Cristiano Gavião
2012-06-14 22:54:35 UTC
Permalink
Hi,

Many Eclipse project are being converted to Tycho.

But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and .project
are generated by m2e plugin.

Could Tycho developers give me some words about this?

regards,

Cristiano
Ian Robertson
2012-06-14 23:11:55 UTC
Permalink
What reasons are being given? Are people seeing unpleasant differences
between what they have now and what m2e generates?

- Ian
Post by Cristiano Gavião
Hi,
Many Eclipse project are being converted to Tycho.
But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and
.project are generated by m2e plugin.
Could Tycho developers give me some words about this?
regards,
Cristiano
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.
Cristiano Gavião
2012-06-14 23:46:04 UTC
Permalink
Well, at least for me, all projects that I have being cloned I always
see "Unstaged Changes" in git.

One example, I just cloned Gemini JPA and imported it into my juno ide
@@ -1,7 +1,7 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="src" path="src"/>
- <classpathentry kind="output" path="target/classes"/>
-</classpath>
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>
+ <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="src" path="src/"/>
+ <classpathentry kind="output" path="target/classes"/>
+</classpath>
The same have occurred in my private projects, mainly when my colleagues
uses a different SO platform than me.

we removed all .classpath and .project and added it to .gitignore. Now
is everything working well.
What reasons are being given? Are people seeing unpleasant differences
between what they have now and what m2e generates?
- Ian
Post by Cristiano Gavião
Hi,
Many Eclipse project are being converted to Tycho.
But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and
.project are generated by m2e plugin.
Could Tycho developers give me some words about this?
regards,
Cristiano
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
CONFIDENTIALITY NOTICE: This message is intended only for the use and
review of the individual or entity to which it is addressed and may
contain information that is privileged and confidential. If the
reader of this message is not the intended recipient, or the employee
or agent responsible for delivering the message solely to the intended
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify sender
immediately by telephone or return email. Thank you.
Mickael Istria
2012-06-15 07:22:06 UTC
Permalink
Hi,

If you remove your .project and .classpath to rely on m2e, then you add
a dependency from your project to m2e. You must be sure all
developers/contributors have m2e installed and working in their Eclipse.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
Cristiano Gavião
2012-06-15 09:34:02 UTC
Permalink
Hi Mickael,

I don't think so. Actually, once we start to build using maven/tycho we
created a dependency on maven not in m2e itself.

You just need to use the maven eclipse plugin
(http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html)

regards,

Cristiano
Post by Mickael Istria
Hi,
If you remove your .project and .classpath to rely on m2e, then you
add a dependency from your project to m2e. You must be sure all
developers/contributors have m2e installed and working in their Eclipse.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Aaron Digulla
2012-06-15 22:13:27 UTC
Permalink
Post by Cristiano Gavião
Hi,
Many Eclipse project are being converted to Tycho.
But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and .project
are generated by m2e plugin.
Could Tycho developers give me some words about this?
I hate it when teams cripple their projects in this way. These are
*Eclipse* projects. After downloading/cloning them, I should be able to
open them in my workspace without any additional work.

Also, m2e doesn't always create correct files (or it didn't in the
past). Does m2e support special builders in the .project file? So this
is dangerous, too.

And lastly, when the people doing that aren't careful about their
gitignore settings, the next developer either gets missing files or
project that are always in a modified state.

The only argument which is in favor of deleting these files is that you
shouldn't commit generated files. While this might make sense at first
glance, it can (and does) create lots of problems that are hard to track
down (the "I didn't change anything" kind).

If these were huge files, I might be game but not for something that is
so small and vital and error prone.

Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://blog.pdark.de/
Igor Fedorenko
2012-06-15 22:30:25 UTC
Permalink
To me there is no hard rule which way is better and decision boils down
if particular project considers pom.xml or .project/etc the primary
workspace configuration metadata.

Many/most projects I work on depend on maven/eclipse integration
functionality provided by m2e, things like source code generation, to
give you an example. For such projects it makes sense to let m2e do its
thing and treat eclipse metadata as generated contents.

For projects that use custom builders and/or rely on specific eclipse
plugins, it certainly makes sense to use eclipse workspace metadata as
the primary and treat pom.xml as necessary evil required by tycho.

And I guess there is a bunch of "standard" projects that can go either
way and choice between pom.xml and eclipse metadata becomes a matter of
personal preferences of project developers.

I have yet to see a project that benefits from maven-eclipse-plugin,
but I am biased ;-)

--
Regards,
Igor
Post by Aaron Digulla
Post by Cristiano Gavião
Hi,
Many Eclipse project are being converted to Tycho.
But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and .project
are generated by m2e plugin.
Could Tycho developers give me some words about this?
I hate it when teams cripple their projects in this way. These are
*Eclipse* projects. After downloading/cloning them, I should be able to
open them in my workspace without any additional work.
Also, m2e doesn't always create correct files (or it didn't in the
past). Does m2e support special builders in the .project file? So this
is dangerous, too.
And lastly, when the people doing that aren't careful about their
gitignore settings, the next developer either gets missing files or
project that are always in a modified state.
The only argument which is in favor of deleting these files is that you
shouldn't commit generated files. While this might make sense at first
glance, it can (and does) create lots of problems that are hard to track
down (the "I didn't change anything" kind).
If these were huge files, I might be game but not for something that is
so small and vital and error prone.
Regards,
Cristiano Gavião
2012-06-16 02:20:43 UTC
Permalink
Igor,

In the ancient times (2003 I think), when I've started with maven in my
java projects, plugins like maven-eclipse-plugin have saved me a lot...

now m2e is the one, of course :D

kind regards,

Cristiano
Post by Igor Fedorenko
To me there is no hard rule which way is better and decision boils down
if particular project considers pom.xml or .project/etc the primary
workspace configuration metadata.
Many/most projects I work on depend on maven/eclipse integration
functionality provided by m2e, things like source code generation, to
give you an example. For such projects it makes sense to let m2e do its
thing and treat eclipse metadata as generated contents.
For projects that use custom builders and/or rely on specific eclipse
plugins, it certainly makes sense to use eclipse workspace metadata as
the primary and treat pom.xml as necessary evil required by tycho.
And I guess there is a bunch of "standard" projects that can go either
way and choice between pom.xml and eclipse metadata becomes a matter of
personal preferences of project developers.
I have yet to see a project that benefits from maven-eclipse-plugin,
but I am biased ;-)
--
Regards,
Igor
Post by Aaron Digulla
Post by Cristiano Gavião
Hi,
Many Eclipse project are being converted to Tycho.
But I'm seeing some resistance of some teams to remove .classpath and
.project from source control even knowing that .classpath and .project
are generated by m2e plugin.
Could Tycho developers give me some words about this?
I hate it when teams cripple their projects in this way. These are
*Eclipse* projects. After downloading/cloning them, I should be able to
open them in my workspace without any additional work.
Also, m2e doesn't always create correct files (or it didn't in the
past). Does m2e support special builders in the .project file? So this
is dangerous, too.
And lastly, when the people doing that aren't careful about their
gitignore settings, the next developer either gets missing files or
project that are always in a modified state.
The only argument which is in favor of deleting these files is that you
shouldn't commit generated files. While this might make sense at first
glance, it can (and does) create lots of problems that are hard to track
down (the "I didn't change anything" kind).
If these were huge files, I might be game but not for something that is
so small and vital and error prone.
Regards,
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Continue reading on narkive:
Loading...