Wrong person.
I was not the person claiming that patches were not being deployed.
Ron
On 28/10/2010 9:36 AM, Benson Margulies wrote:
Ron,
m-e-p works better than M2ECLIPSE in many cases. Further, you have no
proof here that I can see that the m-e-p is dead. To quote the plugin
site:
Last Published: 2010-02-25 | Version: 2.8
If someone posts a patch, I don't think there/s much evidence that it
will be ignored.
--benson
On Thu, Oct 28, 2010 at 8:54 AM, Ron Wheeder
<rwhee...@artifact-software.com> wrote:
On 28/10/2010 5:13 AM, Martijn Dashorst wrote:
So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.
I guess that you could take a copy and continue to maintain it.
If you want to build a team to maintain it and share it, then you probably
want to get the Maven group to cooperate.
If you are the only user/developer, you are off to the races.
Why the constant commercials for the m2eclipse plugin? Instead why not
ask for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?
It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.
Get Eclipse/STS and you have a much more current supported set of code and
everything that you need to develop with Maven.
You can also get training and commercial level support if you want it.
Why would anyone want to invest in older technology?
Ron
Martijn
On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay<wayne...@gmail.com> wrote:
When I run eclipse:eclipse the project name in the .project file will be
the
artifactId (by default) despite the eclipse project name being something
different.
Yes, this is how m-e-p works. The .project file is overwritten by
m-e-p and so you will lose all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
This causes a problem when eclipse tries to build new projects workspace
because the eclipse workspace project is one thing and the .project's
project is something completely different.
This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.
How come the maven-eclipse-plugin will never resolve the workspace
project
name to the .project project name. Or even offer a flag like
<useEclipseProjectName>true</useEclipseProjectName> to override the
original
functionality?
In the last 180 days, there have been zero issues in MECLIPSE resolved.
At the same time, 40 have been updated and 20 were created.
http://jira.codehaus.org/browse/MECLIPSE
For all intents, m-e-p is dead. If you require this functionality,
feel free to hack the plugin to add it and donate your changes back to
be included in a future release -- but bear in mind there may never be
another release. The last release was Feb 23, 2010 and before that was
June 13, 2009.
I suggest upgrading to m2eclipse:
http://m2eclipse.sonatype.org/
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
