Hi, There were inconsistencies when we use the STS with DevS[1]. According to stack trace, exception occurs when trying to initialize, previously loaded 'org.apache.maven.project' package by Spring framework. The 'org.apache.maven.project' package have been exported by DevS 'org.wso2.developerstudio.eclipse.utils' and also 'org.eclipse.m2e'.
osgi> packages org.apache.maven.project org.apache.maven.project; version="2.2.1"*<org.wso2.developerstudio.eclipse.utils_3.7.0 [7918]>* org.eclipse.php.ui_2.0.0.201405160550 [7450] imports org.springframework.ide.eclipse.maven_3.5.1.201404300732-RELEASE [7789] imports org.wso2.developerstudio.appfactory.ui_2.0.0.201405160550 [7834] imports .... org.wso2.developerstudio.eclipse.platform.ui_3.7.0 [7912] imports org.apache.maven.project; version="0.0.0"*<org.eclipse.m2e.maven.runtime_1.4.1.20140328-1501 [7008]>* org.eclipse.m2e.archetype.common_1.4.1.20140328-1501 [6996] imports .... org.springframework.ide.eclipse.boot_3.5.1.201404300732-RELEASE [7781] imports org.springframework.ide.eclipse.roo.ui_3.5.1.201404300732-RELEASE [7794] imports Due to Eclipse Kepler ship with m2e integration, I have removed org.apache.maven.project package export from 'org.wso2.developerstudio.eclipse.utils' and also removed restrictions in DevS plugins to use specific version of 'org.apache.maven.project' . Now both STS and DevS plugins import the 'org.apache.maven.project' from m2e and I haven't experienced the exceptions. Would be there any effect on DevS plugins due to the change of org.apache.maven.project package version? [1] https://wso2.org/jira/browse/TOOLS-2517 Thanks, /Lali -- *Lali Sudaththa Devamanthri* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 895 4922 <http://www.wso2.com>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
