| Re: [wtp-dev] Weekly M-build declared: M200602010238 Wed, 1 Feb 2006 -- 02:38 (UTC) |
| So basically, when each plugin I have is defined as a "maven" project. So maven goals are invoked to compile the source, rather then the PDE builder. Defining a maven project requires defining a project.xml which declares the dependencies to compile. So PDE to locate dependencies to compile looks at the plugin.xml or manifest for the "required plugins", where as I have to redefine those plugins as dependencies in a maven specific project.xml. Now since Eclipse/WTP doesn't upload each of the plugins is a remote maven repository where maven can pull down only the jars it needs for compilation, I download the entire wtp image and extract it. I then use a maven concept of a jar override for each plugin dependency to point to the absolute path to that plugin... maven.jar.org.eclipse.jst.j2ee.web = ${eclipse.home.plugins}/org.eclipse.jst.j2ee.web_${wtp.version}.jar maven.jar.org.eclipse.jst.j2ee.ejb = ${eclipse.home.plugins}/org.eclipse.jst.j2ee.ejb_${wtp.version}.jar maven.jar.org.eclipse.jst.j2ee.jca = ${eclipse.home.plugins}/org.eclipse.jst.j2ee.jca_${wtp.version}.jar This is where the I'm impacted... Before I simply set the wtp.version property, and in some cases, they differ, but before they were either 1.0.0, or 1.0.1. Now for every single wtp dependency each version will be different and different for every build. So each time I pull down a build to compile against I'll have to manually update this hard coded absolute path to the jar. Hope that makes sense. Talking to the maven folks in the past, I know there in discussions with the platform team to have better integration for plugin development. But this introduction of qualifier builds poses another problem that the maven team will need to be informed of. Do you know if and when the Eclipse Platform will be moving their builds to this? - sachin On Feb 1, 2006, at 5:14 PM, David M Williams wrote:
|