MyEclipse: How to disable MyEclipse Maven capabilities?
trapongx - Jul 01, 2008 - 06:45 PM
Post subject: How to disable MyEclipse Maven capabilities?
I have SVNed web project created with ME 6.0.1 GA. I have m2eclipse installed and I "Enable Maven Dependencies" using m2eclipse's menu.

Now when I open this project on ME 6.5 I have an issues. m2eclipse doesn't work anymore. No menu, no preference page, and dependencies not linked. I guess ME play a trick with it. How can I stop this.

Even I change
com.genuitec.eclipse.maven.maven2Nature
back to
org.maven.ide.eclipse.maven2Nature
,
it doesn't help. Maven not shown in Package Explorer but in project build path dialog. However, it's empty.

My situation is
- Can't go forward because ME 6.5, as announced, does not support Maven Capabilities on project created by older ME version or other tool. It only support project created by ME 6.5 and needed to have Maven capabilities checked on project creation.
- Can't go backward because m2eclipse not functioning.

I can not head back to use ME 6.0.1 again because my Eclipse is managed by Pulse and it allow latest version of ME only.

!!!!!
support-rkalla - Jul 02, 2008 - 06:53 PM
Post subject: RE: How to disable MyEclipse Maven capabilities?
I think we can clear this up pretty quickly and the confusion is born out of 1 fundamental issue in 6.5: MyEclipse 6.5 includes a custom implementation of m2eclipse, so you can't install m2eclipse along side MyEclipse 6.5 or later.

The first step I would suggest is to remove m2eclipse completely and check your project out.

NOTE: The suggested fix is to create a new project that has Maven enabled on it, and get it all setup correctly with the right dependencies then copy your original project artifacts into it, once it's all setup you can either check that new project into your repo, or copy the entire project contents back (from the Navigator view so it includes all the hidden config files) back to the original project and then make sure it works and check it in.

OR you can try and manually edit the project resource files to enable Maven on that project... this is totally unsupported and I would expect that it may not work... but you are welcome to try it. I wouldn't suggest checking anything back in if you do this *until* you have completely confirmed that it worked.

To get an idea of all the resources you need, create a new maven-ized MyEclipse project that you can refer to for the rest of my instructions. (Also use your Navigator view so you can see everything)

You will need to copy across the maven builder and nature from the .project file. You will need to copy across the specialized .classpath entries as well. You might also want to take a look at the contents of the .settings directory and make sure your pom.xml is there in your project.

AFter that, close and reopen your project, then Clean it (so it rebuilds)... make sure all is right with the world. Add any missing dependencies, etc.

You should be good to go after that.

Sorry for the trouble, at some point we want to add the "Add Maven Capabilities" option, but given how complex Maven setups can be, this opens a can of worms to some extent that have to be fully researched first.
jgrabow2 - Jul 03, 2008 - 09:11 AM
Post subject: The same problem
Hi,

I've got the same problem, but my situation seems to be a little more complicated.

Whole the team i work in uses myeclipse. For that reason to simplify our work we share configuration for myeclipse (.project.xml) in SVN.
It's not possible to force whole the team in one moment to upgrade to 6.5.0 with maven4eclipse as i did.
Now, if i change my
<nature>org.maven.ide.eclipse.maven2Nature</nature>
to
<nature>com.genuitec.eclipse.maven.maven2Nature</nature>
everything works ok for me, but i cannot commit the .project.xml because it's bust for the rest developers.
For this reason it would be much better if i could disable maven4eclipse plugin (or make some kind of aliases for org.maven.ide.eclipse.maven2Nature? or sth?). Or i've got to downgrade myeclipse...

Another serious problem i've got with maven4eclipse is that the 'attach sources' feature does not work on the libraries accessed as maven dependencies from maven4eclipse.

Any suggestions for both above issues would be helpful.

Regards, Jan
support-rkalla - Jul 03, 2008 - 04:24 PM
Post subject: RE: The same problem
Jan,
Why not just make the change locally, for the nature, for your .project file, and then never check that resource back in until the rest of the team has migrated? That will avoid breaking anything for the rest of the team.

There currently is no way to deactivate the Maven4MyEclipse plugin, without manually erasing the plugins and that's an unsupported and untested setup... I'm sure it would break some project wizards if you did that.

I'll have someone from the Maven4MyEclipse team look at the attachment issue, hang tight.
support-eugene - Jul 03, 2008 - 07:24 PM
Post subject: Re: The same problem
jgrabow2 wrote:
Another serious problem i've got with maven4eclipse is that the 'attach sources' feature does not work on the libraries accessed as maven dependencies from maven4eclipse.


Can you explain? What I did:
1. Added Hibernate dependency.
2. Opened random class from the Hibernate jar.
3. Clicked "Attach Sources" in the editor.
4. Selected Jar file.

Evrything seems working.
jgrabow2 - Jul 04, 2008 - 08:04 AM
Post subject:
Thank you for your reply.

What i actually do is not commiting the xml. And it works of course, but i treat it like a temporary workaround. Maybe all the team will upgrade to myeclipse 6.0.1.

Returning to the second problem, i did the same:

1. Added Hibernate dependency.
2. Opened random class from the Hibernate jar.
3. Clicked "Attach Sources" in the editor. (Or open lib's property window and adequate tab)
4. Selected Jar file.
[...]
5. Closed properties window with OK button
5. The classes' sources are not displayed after dbl-clicking on class icon
6. When i'm back to the lib's properties window -> Java Source Attachement -> Location Path it is empty again

It's hard to say if it is my fault, don't now where to find any logs, there is no response that anything went wrong. But what i'm sure is:
- it works for jars added to classpath directly (not using maven plugin)
- it dose not work in maven4eclipse also for all other libs i tried: hibernate, common-beanutils, spring, etc ...
- other team workers report me the same problem in m2 plugin in myeclipse
- i'm sure everthing was ok in eclipse (not myeclipse) maven plugin i used to try some time ago

My workaround was to use jadclipse to decompile classes (there are some consequnces of course - line mismatches, debugging problems - that's why i need Java Source Attachement) but at all it works fine to view srcs.
support-eugene - Jul 04, 2008 - 02:21 PM
Post subject:
For most Hibernate versions you can use "Download source" action to download the source files.

What VCS do you use? Could it be that some file is read-only and thus Eclipse cannot store the path to the file?
daorriss - Jul 20, 2008 - 08:31 PM
Post subject:
I'm going to throw my two cents in here and say the Maven4MyEclipse is rather lacking when compared to the version I can currently download. Or at the very least I find it counter-intuitive compared to m2eclipse. For example: I have a existing Maven-based project that I bring into Eclipse. M4ME doesn't recognize act activate any of it's features. When I try, it instead wipes out the POM file and creates a new one. Perhaps I'm just misunderstanding your implementation....?
support-eugene - Jul 20, 2008 - 09:48 PM
Post subject:
daorriss wrote:
I'm going to throw my two cents in here and say the Maven4MyEclipse is rather lacking when compared to the version I can currently download. Or at the very least I find it counter-intuitive compared to m2eclipse. For example: I have a existing Maven-based project that I bring into Eclipse. M4ME doesn't recognize act activate any of it's features. When I try, it instead wipes out the POM file and creates a new one. Perhaps I'm just misunderstanding your implementation....?


Maven4MyEclipse currently only supports projects created using our wizards. We do not support arbitrary projects at this point.
daorriss - Jul 20, 2008 - 10:17 PM
Post subject:
support-eugene wrote:
daorriss wrote:
I'm going to throw my two cents in here and say the Maven4MyEclipse is rather lacking when compared to the version I can currently download. Or at the very least I find it counter-intuitive compared to m2eclipse. For example: I have a existing Maven-based project that I bring into Eclipse. M4ME doesn't recognize act activate any of it's features. When I try, it instead wipes out the POM file and creates a new one. Perhaps I'm just misunderstanding your implementation....?


Maven4MyEclipse currently only supports projects created using our wizards. We do not support arbitrary projects at this point.


Maven projects are not "arbitrary". The have a consistent and predictable layout. You have effectively made m2eclipse useless with your M4ME implementation. Because of this I'll most likely not move to newer versions of MyEclipse past 6.0.
seanpg - Jul 21, 2008 - 04:22 AM
Post subject:
daorriss wrote:
I'm going to throw my two cents in here and say the Maven4MyEclipse is rather lacking when compared to the version I can currently download. Or at the very least I find it counter-intuitive compared to m2eclipse. For example: I have a existing Maven-based project that I bring into Eclipse. M4ME doesn't recognize act activate any of it's features. When I try, it instead wipes out the POM file and creates a new one. Perhaps I'm just misunderstanding your implementation....?


+1

I have several hundred maven projects that work just fine with m2eclipse but are useless with Maven4MyEclipse.

Hopefully future versions will become compatible but until then i will not upgrade.
dustmachine - Jul 22, 2008 - 03:52 PM
Post subject:
I'm having the same problem. Why do we need a "custom implementation" of m2eclipse? Why do we need custom implementations of anything? I don't mind new features being added to MyEclipse, but if each new version is going to break my existing setup, it begins to become tedius. Especially if there is no easy way to disable a conflicting feature from within the "Manage Your Configuration."

Creating a new project and copying things into it is simply not an option.
dustmachine - Jul 22, 2008 - 05:00 PM
Post subject:
Okay, I have now been able to disable Maven4MyEclipse and have the original m2eclipse working again (on MyEclipse 6.5). I figured what's the worst that can happen? I won't be able to use 6.5?

Here's what I did to manually uninstall Maven4MyEclipse:

1. In the directory C:\Program Files\MyEclipse 6.5\myeclipse\eclipse\features\
- I removed com.genuitec.myeclipse.maven_6.5.0.zmyeclipse650200806 folder
2. In the directory C:\Program Files\MyEclipse 6.5\myeclipse\eclipse\plugins\
- I removed com.genuitec.myeclipse.maven_6.5.0.zmyeclipse650200806 folder
These next two may have only been there because I tried re-installing m2eclipse so if you don't find them don't worry.
3. In the direcory C:\Program Files\MyEclipse 6.5\eclipse\features\
- I looked for and removed any other files and folders that started with "org.maven.*"
4. In the direcory C:\Program Files\MyEclipse 6.5\eclipse\plugins\
- I looked for and removed any other files and folders that started with "org.maven.*"
5. Restart MyEclipse with the "-clean" option. (I modified my quicklaunch shortcut and added -clean at the end of the Target line)
6. Add the codehaus M2Eclipse remote update site: http://m2eclipse.codehaus.org/update/ and install as normal.

This worked for me - your mileage may vary.
support-rkalla - Jul 24, 2008 - 05:35 PM
Post subject:
Hey guys, just coming back around on this issue, we are doing Maven support because you guys needed it and we absolutely want to make sure that we do it right (e.g. that it works for everybody).

6.5 represents our *first* release of a major new feature, we are far from done and if folks are running into specific problems with it we really want to hear from you guys. We are going to keep iterating on that feature set forever, just like every other feature set, so if you can send us specific issues you had with it, or things you liked about it, we can make sure to direct it in such a way that it meets your exact needs.

We didn't just toss this puppy out, wipe our hands and say "ok we're done, let's move on", we really do want to get feedback on what we borked, what rocked and where we could make common operations even easier. We *did* absolutely have to scope down what our initial delivery looked like though so we weren't in R&D for a year with nothing to show for it, so that's why there are some things missing like EAR-support for Maven and adding Maven Capabilities to existing projects that we need to address.

So that being said, you can fire off comments to support@myeclipseide.com ATTN Riyad, with your comments or post them here if that's easier. Please make sure it's mroe than "this sucked" though, it's hard to file a PR in our issue tracker for the dev team with a description like that. The more specific the issues the faster we can turn those into actionable items to address for everybody.

Thanks again for your patience guys, we know for the Maven gurus out there this might be a pot-hole in the road right now and we want to fill it in for you.
daorriss - Jul 24, 2008 - 07:55 PM
Post subject:
Riyad,

The crux of the issue here is that m2Eclipse is very powerful, very flexible and works with existing projects *or* new ones. I can take any maven-based project and just use it. Maven4Myecilpse appears only to work for Newbies at the expense of those of us who already have Maven-based projects. So, for people like me, M4ME offers *none* of the value that M2E does. And as a result I'll probably do what's been recommended above and pry your component out in favor of putting M2E in.
support-rkalla - Jul 24, 2008 - 08:06 PM
Post subject:
DaveO, thank you for the feedback, the drop-in-and-work scenario is absolutely one we have to get right in a future release.

Is this the complaint the rest of you guys have as well, that it won't work with existing projects? If so that would give us a very focused point on which to enhance (which was already on our short list, but atleast know we know this is a show-stopper for the maven gurus).
daorriss - Jul 24, 2008 - 08:10 PM
Post subject:
If you read this thread you'll see that's *exactly* the problem. One of the other posters mentioned 400 maven-based projects. Without being able to add maven support from ME to the project, he can't function within ME 6.5.

I think if you can't fix M4ME at least make it so those of use who want to use M2E can turn off M4E.
msquared - Jul 25, 2008 - 04:08 AM
Post subject:
Like many others here, I find Maven4MyEclipse to be a major step BACKWARDS in functionality from the plain-old m2eclipse plugin.
What in the world were you thinking to actually REMOVE from m2eclipse the standard maven project structure?
Simply defies all belief!

Fortunately I have found that by deleting the items below, MyEclipse6.5 seems to work perfectly fine with the standard m2eclipse plugin instead of Maven4MyEclipse:
The only functional loss is that web deployments no longer filter out scope=provided or test, but I have a workaround for that.

features/com.genuitec.myeclipse.maven_6.5.1.zmyeclipse650200806
plugins/com.genuitec.eclipse.maven_6.5.1.zmyeclipse650200806.jar
plugins/com.genuitec.myeclipse.maven_6.5.1.zmyeclipse650200806
plugins/org.maven.ide.components.archetype_common_2.0.0.20080331-1600
plugins/org.maven.ide.components.maven_embedder_2.1.0.20080410-2200
plugins/org.maven.ide.components.maven_model_edit_1.0.0.20080331-1600
plugins/org.maven.ide.components.maven_scm_1.0.0.20080410-2200
plugins/org.maven.ide.components.nexus_indexer_1.0.0.20080331-1600
plugins/org.maven.ide.components.qname_1.0.0.20080331-1600
plugins/org.maven.ide.eclipse_0.9.3.zmyeclipse650200806.jar
plugins/org.maven.ide.eclipse.central_0.9.1.zmyeclipse650200806.jar
plugins/org.maven.ide.eclipse.scm_0.9.2.zmyeclipse650200806.jar
daorriss - Jul 26, 2008 - 05:55 PM
Post subject:
What's the workaround?
support-rkalla - Jul 28, 2008 - 02:50 PM
Post subject:
Guys,
While the removal of the plugin may work now, it's not a scenario we support or tested... so keep your eyes peeled for odd behavior *if* you decide to go down this path (like Wizards failing, stuff like that). If it works fine for you, then all the better.

Our official workaround for folks that must have m2eclipse support is to step back to 6.0.1 and install it there; I know we covered that, just reminding folks.

And as for the "Why did you remove XYZ from m2eclipse?!" question, I answered it earlier in the thread.
ibrandt - Sep 05, 2008 - 07:27 PM
Post subject:
dustmachine wrote:
Here's what I did to manually uninstall Maven4MyEclipse: ...


Worked for me. Got a one-time error about restoring the workspace on start-up, but that was to be expected. I'm now back to contributing to maven based open-source projects on the side.

[Edit: Oops, missed page 2 of this thread at first. Deleting the list of features and plugins I removed as that's already been posted.]

I look forward to trying a Maven4MyEclipse that can import existing projects...
leej - Sep 05, 2008 - 09:59 PM
Post subject: Link?
Where is the link to 6.0.1?
paolo_denti - Sep 06, 2008 - 02:23 PM
Post subject:
msquared wrote:
Like many others here, I find Maven4MyEclipse to be a major step BACKWARDS in functionality from the plain-old m2eclipse plugin.
What in the world were you thinking to actually REMOVE from m2eclipse the standard maven project structure?
Simply defies all belief!

Fortunately I have found that by deleting the items below, MyEclipse6.5 seems to work perfectly fine with the standard m2eclipse plugin instead of Maven4MyEclipse:
The only functional loss is that web deployments no longer filter out scope=provided or test, but I have a workaround for that
....


daorriss wrote:
What's the workaround?


yes, please, that could be interesting for everybody

thanks
paolo_denti - Sep 06, 2008 - 02:26 PM
Post subject: Re: Link?
leej wrote:
Where is the link to 6.0.1?

+1
i can find the 5.5 and 6.5 but not the 6.0.1
leej - Sep 08, 2008 - 03:28 PM
Post subject: RE: Re: Link?
bump...

Really need the 6.0.1 version for Maven functionality...
support-rkalla - Sep 08, 2008 - 04:16 PM
Post subject: RE: Re: Link?
Sorry guys, it got archived, here you go:
http://downloads.myeclipseide.com/downloads/products/eworkbench/6.0.1GA/MyEclipse_6.0.1GA_E3.3.1_FullStackInstaller.exe

Also, all this should be fixed in 7.0M2 and 7.0GA, so hopefully this "6.0.1+m2eclipse" is a temporary workaround, thanks for being patient.
paolo_denti - Sep 10, 2008 - 04:10 PM
Post subject: Re: RE: Re: Link?
support-rkalla wrote:
Sorry guys, it got archived, here you go:
http://downloads.myeclipseide.com/downloads/products/eworkbench/6.0.1GA/MyEclipse_6.0.1GA_E3.3.1_FullStackInstaller.exe

Also, all this should be fixed in 7.0M2 and 7.0GA, so hopefully this "6.0.1+m2eclipse" is a temporary workaround, thanks for being patient.

could you please post the link for the os x version too ?
thanks
support-rkalla - Sep 26, 2008 - 05:39 PM
Post subject: RE: Re: RE: Re: Link?
Paolo,
Here it is, sorry for the delay:
http://downloads.myeclipseide.com/downloads/products/eworkbench/6.0.1GA/MyEclipse_6.0.1GA_E3.3.1_Installer.zip
carinoh - Oct 06, 2008 - 03:34 PM
Post subject: Disable Maven integration in MyEclipse 7?
I would like a clarification on the subject of disabling Maven capabilities in MyElcipse 7. Are there no supported way to disable Maven in this release? Have you any plan for future release to make this possible?

We have about 200 using MyEclipse 6.0.1 and about 50-100 users with Eclipse 3.3. We will distribute Eclipse 3.4 next week but see no possibility to distribute the next release of MyEcipse 7 due to the Maven integration to MyEclispe. We are using build tools that are not compatible with Maven, and it is not on the horizont to do the conversion to Maven yet.
support-eugene - Oct 06, 2008 - 03:55 PM
Post subject: Re: Disable Maven integration in MyEclipse 7?
carinoh wrote:
I would like a clarification on the subject of disabling Maven capabilities in MyElcipse 7. Are there no supported way to disable Maven in this release? Have you any plan for future release to make this possible?

We have about 200 using MyEclipse 6.0.1 and about 50-100 users with Eclipse 3.3. We will distribute Eclipse 3.4 next week but see no possibility to distribute the next release of MyEcipse 7 due to the Maven integration to MyEclispe. We are using build tools that are not compatible with Maven, and it is not on the horizont to do the conversion to Maven yet.


1. You can disable Maven4MyEclipse on the preference page in MyEclipse 7.0 M2.
2. MyEclipse does not mandate using Maven with your project. It should not conflict with any tools.
ExtremeTrekker - Dec 03, 2008 - 07:10 PM
Post subject: Re: Disable Maven integration in MyEclipse 7?
support-eugene wrote:


1. You can disable Maven4MyEclipse on the preference page in MyEclipse 7.0 M2.
2. MyEclipse does not mandate using Maven with your project. It should not conflict with any tools.


I have disabled Maven4MyEclipse but it still updates the indexes from the maven central repository (central : http://repo1.maven.org/maven2/ in the Maven Indexes view). I don't know what the effect is, except a waste of bandwidth for something I don't need or want.

So how can I disable the maven2 index update?

Thanks,
Paul
support-rkalla - Dec 03, 2008 - 07:34 PM
Post subject: RE: Re: Disable Maven integration in MyEclipse 7?
Paul,

I have no idea. Maven4MyEclipse cannot function correctly without that resolution and I imagine for base m2 that's probably the same.
ernestz - Dec 13, 2008 - 01:47 PM
Post subject: RE: Re: Disable Maven integration in MyEclipse 7?
Following up on this, I too just noticed that ME 6.6 and 7.0 both update these indexes, and seem to create/maintain a file (_1l.cfs) which is almost 64MB. Even if I disable Maven4MyEclipse, ME 6.6 and ME7 waste bandwidth and file space updating some feature I disabled.

Still no way to totally disable Maven7MyEclipse?
support-rkalla - Dec 16, 2008 - 06:49 PM
Post subject: RE: Re: Disable Maven integration in MyEclipse 7?
Not *totally*, but you can go to the Maven4MyEclipse preferences under MyEclipse, and tell it to not update the index on restart and it will never update that file again. The reason it updates it atleast once is because the Maven dependency management is busted without it -- which is a really crumby user experience.
ernestz - Dec 17, 2008 - 02:59 AM
Post subject: RE: Re: Disable Maven integration in MyEclipse 7?
Quote:

The reason it updates it atleast once is because the Maven dependency management is busted without it -- which is a really crumby user experience.


Agreed .... especially if the user does not need or require Maven capabilities.
roby2358 - Dec 30, 2008 - 04:54 PM
Post subject:
In 6.6, I'm not able to run my junit tests. I finally enabled the "m2eclipse" properties in the perferences menu (despite the warning text), but now my junit tests are getting compilation errors and class not found errors.

I hate to say it, but as much as I love MyEclipse, we have so many Maven projects that if I have to choose between MyEclipse and m2eclipse, MyEclipse is out the window.

I'll give it one shot to remove Maven4MyEclipse, but then out goes baby and bathwater all at once.
support-eugene - Dec 31, 2008 - 01:53 PM
Post subject:
roby2358 wrote:
In 6.6, I'm not able to run my junit tests. I finally enabled the "m2eclipse" properties in the perferences menu (despite the warning text), but now my junit tests are getting compilation errors and class not found errors.

I hate to say it, but as much as I love MyEclipse, we have so many Maven projects that if I have to choose between MyEclipse and m2eclipse, MyEclipse is out the window.

I'll give it one shot to remove Maven4MyEclipse, but then out goes baby and bathwater all at once.


Can you provide more information, i.e. what kinds of compilation errors you are getting, etc.?
mlbartonsr - Jul 20, 2009 - 03:44 PM
Post subject: Re: RE: Re: Disable Maven integration in MyEclipse 7?
support-rkalla wrote:
Not *totally*, but you can go to the Maven4MyEclipse preferences under MyEclipse, and tell it to not update the index on restart and it will never update that file again. The reason it updates it atleast once is because the Maven dependency management is busted without it -- which is a really crumby user experience.



I am using ME 7.5
In order to tell it to not update you have to enable Maven. I do not want to enable Maven.
So how do i turn off maven updates and not have maven enabled?
support-eugene - Jul 20, 2009 - 03:50 PM
Post subject: RE: Re: RE: Re: Disable Maven integration in MyEclipse 7?
The anable/disable feature only shows/hides the UI. You can "enable", turn off index download, disable.
mlbartonsr - Jul 20, 2009 - 04:08 PM
Post subject: RE: Re: RE: Re: Disable Maven integration in MyEclipse 7?
Thanks, That worked. I have another question.
What does the offline setting do on the M4ME properties page do?
support-eugene - Jul 20, 2009 - 04:19 PM
Post subject: Re: RE: Re: RE: Re: Disable Maven integration in MyEclipse 7
mlbartonsr wrote:
Thanks, That worked. I have another question.
What does the offline setting do on the M4ME properties page do?


It tells ME to expect that connection might be absent :( It is still not working very well, unfortunately.
wxlund - Oct 01, 2009 - 07:40 AM
Post subject:
i have been completely unable to get maven to work in MyEclipse. I'm finding the notes about m2eclipse not being able to install and I'm experiencing the same messages but how do I use m2eclipse? Not being able to use m2eclipse means dropping MyEclipse at the end of the eval.
mezmo - Oct 07, 2009 - 06:27 PM
Post subject:
"Getting out long stick to poke beehive with"
I've started moving a lot of my stuff over to Netbeans over this issue. Its really a shame, I enjoy working in MyEclipse, but this issue just makes it a non-starter. The Netbeans maven connector, I check out a project that has a pom at its root, and wham, I've got full support. It worked that way pretty much with M2Eclipse too, until you "simplified" it.
Ah well, maybe someday I'll be able to use something OTHER than the database part.
hoshposh - Feb 13, 2010 - 07:23 PM
Post subject: What is the Latest on Using m2eclipse with MyEclipse 8.0?
I am thinking of getting the latest version and was curious to know if MyEclipse 8.0 has better support for the standard m2eclipse plugins?

Cheers,
-Lyndon-
All times are GMT - 6 Hours
Powered by PNphpBB2 © 2003-2004 The PNphpBB Group
Credits