-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No working CVS SCM connector for m2e 1.3.1 #5
Comments
Hi! Can you please reply to my comment? Kind regards, Christof. |
You will need to patch the metadata for the connector and make a pull request. Not many of us use CVS for our projects anymore so it's difficult to test. |
There is still no CVS connector for m2e in Juno or Kepler. I used http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-cvs/0.13.0/N/0.13.0.201304101743/ and it worked fine in Kepler. This issue is marked as merged; shouldn't it be available in the catalog then? |
These builds have nothing to do with the catalog. If someone else wants to take this and put it in the catalog they can. I may get around to it but these processes are independent. |
Oh I see. I thought it was all automated. Have you done it before Jason? can you point me to a doc or something? maybe i can help |
I have not put anything in the catalog as Igor does that :-) I also build my own Eclipse distribution so I don't use the Marketplace. But if you want to take a look you can start here: http://marketplace.eclipse.org/add_content |
Hi Folks!
Is there a build available which is working with m2e 1.3.1? The newest build I can found is on "http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-cvs/0.13.0/N/0.13.0.201212120356/" but when I try to install it in Juno SR2 with m2e 1.3.1 I receive the following error message: Missing requirement: Maven SCM Handler for CVS 0.13.0.201212120356 (org.sonatype.m2e.cvs 0.13.0.201212120356) requires 'bundle org.eclipse.m2e.core [1.0.0,1.3.0)' but it could not be found.
Best regards,
Christof Luick.
The text was updated successfully, but these errors were encountered: