john.vint wrote:
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.
Lets assume a person is working on two different
On Sat, Oct 30, 2010 at 2:34 AM, john.vint johnvin...@gmail.com wrote:
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.
in context:
http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3242262.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
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.
Why the constant commercials for the m2eclipse plugin? Instead why not
ask
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
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.
maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plugin fails
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
We're not stopping you from taking it. Put it in Github and hack away.
On Oct 28, 2010, at 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
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
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
I am the one who said for all intents, m-e-p is dead based entirely
on JIRA activity and releases, as well as the existence of newer (and
largely perceived
2010/10/28 Wayne Fay wayne...@gmail.com:
So how does one get ownership of the plugin? I've contributed 2
This is open source so no one is stopping you from creating a fork.
Sorry to jump in but, in the Apache Committers' FAQ I read:
I agree, there are many plugins that Maven developers just don't look after and
they should be ejected and taken out of the org.maven.plugins name space.
Anything there people assume are maintained which simply is not the case.
On Oct 28, 2010, at 10:58 AM, Antonio Petrelli wrote:
2010/10/28
On 28/10/2010 9:35 AM, Martijn Dashorst wrote:
On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
It is hard to get enthusiastic about maintaining old software that has been
replaced by better stuff that is free.
maven-eclipse-plugin works roughly 100% of the
Yup, it's in ASF svn, and if the project isn't willing to own it, they
should attic it.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On 27/10/2010 1:28 PM, Wayne Fay 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
.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3237890.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
16 matches
Mail list logo
