| Author |
Message |
|
|
Post subject: Standard Subscription deployment to Tomcat fails
Posted: Nov 21, 2008 - 05:19 PM
|
|
Registered Member

Joined: Jul 15, 2008
Posts: 5
|
|
Using either MyEclipse 6.6 or 7.0 M2, I turned off Maven4MyEclipse and enabled m2eclipse. I then imported a maven web project and tried to deploy it to Tomcat 5.5. I get the following:
Problem Occurred
Add Deployment
Reason: Invalid Subscription Level - Discontinuing this MyEclipse operation.
An internal error occurred during: "Add Deployment".
Invalid Subscription Level - Discontinuing this MyEclipse operation.
Then a window asking to upgrade subscription opens up. Why can't I deploy? |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Standard Subscription deployment to Tomcat fails
Posted: Nov 24, 2008 - 08:24 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
Can you go to Windows > Prefs > MyEclipse > Subscription and check if the key is still valid? |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: Standard Subscription deployment to Tomcat fails
Posted: Nov 24, 2008 - 08:33 PM
|
|
Registered Member

Joined: Jul 15, 2008
Posts: 5
|
|
Subscriber: mikia
Product ID: E2MY (MyEclipse Standard Subscription)
License version: 2.7
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20090530
Number of licenses: 1 |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Standard Subscription deployment to Tomcat fails
Posted: Nov 25, 2008 - 07:15 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
I have sent you a *PM*. |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: Same problem
Posted: Jan 26, 2009 - 10:09 AM
|
|
Veteran Member


Joined: Jun 21, 2007
Posts: 2
|
|
Myeclipse 7 is giving me the same error, subscription info as follows:
Subscriber: carlisg
Product ID: E2MY (MyEclipse Standard Subscription)
License version: 2.7
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20090702
Number of licenses: 1 |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Same problem
Posted: Jan 26, 2009 - 07:13 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
carlisg,
Im sorry you ran into this issue. We are looking into this and we shall try to get this fixed asap. |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: Have you fixed this problem?
Posted: Mar 03, 2009 - 07:05 PM
|
|
Joined: Mar 03, 2009
Posts: 2
|
|
I'm getting the same problem when I'm deploying a project. I have a similar one downloaded from a different repository which has no problem with deploying.
I got a similar message when I was playing around trying to fix missing artifact errors and went to Maven 4 import jar file into repository |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Have you fixed this problem?
Posted: Mar 04, 2009 - 05:03 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
karidrgn,
Are you working with a standard license as well? |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: Have you fixed this problem?
Posted: Mar 04, 2009 - 06:22 PM
|
|
Joined: Mar 03, 2009
Posts: 2
|
|
|
|
|
 |
|
|
Post subject: RE: Have you fixed this problem?
Posted: Mar 05, 2009 - 05:31 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
karidrgn,
This is a known issue and Im afraid we dont have a workaround for you. You cannot work with Maven Projects if you have a standard license. Maven support is only available with the Pro subscription. |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Aug 04, 2009 - 12:53 AM
|
|
Registered Member

Joined: Aug 04, 2009
Posts: 2
|
|
I am using 7.5 with a standard license and I am having the same issue. I am trying to deploy a maven project, I get the same result with the m2eclipse features enabled and disabled in the maven4eclipse configuration. The only reason I use MyEclipse is for the deployment feature. This restriction is totally unacceptable, I am now losing functionality which I paid for because of an unrelated feature which is only available under a different license. More to this end there is no method to remove or disable the maven4eclipse component so that the standard m2eclipse plugin can be installed. I am not at all impressed. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Aug 04, 2009 - 07:46 AM
|
|
Registered Member


Joined: Feb 03, 2009
Posts: 3364
|
|
Hi bvanschaayk,
As Nipun said above, you cannot work with Maven Projects if you have a standard license.
And about disabling Maven4MyEclipse, we have an option to enable or disable Maven4MyEclipse or m2eclipse. Go to Windows-->Preferences, expand MyEclipse Enterprise workbench and click on Maven4MyEclipse. You'll see two check boxes, one for Maven4MyEclipse and the other one for m2eclipse. |
_________________ Joy
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Aug 04, 2009 - 01:28 PM
|
|
Registered Member

Joined: Aug 04, 2009
Posts: 2
|
|
Disabling Maven4Eclipse in the preferences still does not allow you to install the standard m2eclipse plugin. I've had to downgrade to MyEclipse 5.5 before Maven4Eclipse was added so I can actually do my work. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Aug 05, 2009 - 06:53 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8013
|
|
bvanschaayk,
Maven web project deployment code is a part of MyEclipse Maven support, not m2eclipse. I.e. there are advanced features like deploying dependencies according to their scope, etc. It requires our pro license as it is pro feature |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|