Re: Building Eclipse plugins with Maven 2
I definitely miss something here, that is how to create a product configuration from an existing source-plugin module (that builds fine by the way). I don't know enough about Eclipse RCP and product configuration to be able to adapt the process to this particular maven setup. Has anyone already managed to do that? 2007/11/19, Sebastien ARBOGAST [EMAIL PROTECTED]: Thanks a lot for all your help Michal. I was afraid of renaming of renaming the name of those projects without changing the name of tha packages inside them (which I cannot do), but it worked. Well at least it compiles and tests pass. Now I would like to check that it runs. In the original project, the one I'm mavenizing, I have a .product file that I could run directly inside Eclipse to launch my RCP application. Should I keep this file? And if yes, where is it best to put it? root of the main plugin or src/main/resources? 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: I managed to get through the previous issue by creating artificial SNAPSHOT versions of the dependencies Maven asked for. But now I'm facing yet another strange issue. The build fails on a message saying that org.eclipse.test_3.2.0 plugin is missing in eclipse/plugins, but just before that, it does a cleanup on the eclipse installation and deletes a lot of plugins, including org.eclipse.test_3.2.0. I'm afraid your artificial module solution won't work here. psteclipse does the testing by copying your plugins into the Eclipse directory and deleting them after testing has been done. It finds the plugins to delete by the prefix, so if your own plugins start with org.eclipse it's very likely that psteclipse will delete some of Eclipse;s internals, hence the missing dependencies. The only solution I see for you here is changing the naming of your plugins. It's not that big of a problem, since Eclipse offers very decent refactoring features to do that across different projects. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Thanks a lot for all your help Michal. I was afraid of renaming of renaming the name of those projects without changing the name of tha packages inside them (which I cannot do), but it worked. Well at least it compiles and tests pass. Now I would like to check that it runs. In the original project, the one I'm mavenizing, I have a .product file that I could run directly inside Eclipse to launch my RCP application. Should I keep this file? And if yes, where is it best to put it? root of the main plugin or src/main/resources? 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: I managed to get through the previous issue by creating artificial SNAPSHOT versions of the dependencies Maven asked for. But now I'm facing yet another strange issue. The build fails on a message saying that org.eclipse.test_3.2.0 plugin is missing in eclipse/plugins, but just before that, it does a cleanup on the eclipse installation and deletes a lot of plugins, including org.eclipse.test_3.2.0. I'm afraid your artificial module solution won't work here. psteclipse does the testing by copying your plugins into the Eclipse directory and deleting them after testing has been done. It finds the plugins to delete by the prefix, so if your own plugins start with org.eclipse it's very likely that psteclipse will delete some of Eclipse;s internals, hence the missing dependencies. The only solution I see for you here is changing the naming of your plugins. It's not that big of a problem, since Eclipse offers very decent refactoring features to do that across different projects. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Sebastien Arbogast wrote: Obviously, I'm missing something with version numbers here, as: - the version in the POM for com.mycompany.framework.common is 1.0-SNAPSHOT - the resulting version in the manifest after running psteclipse:eclipse-plugin is 1.0 - the version com.mycompany.framework.eclipse.rcp is looking for is 1.0.0-SNAPSHOT Well, I had trouble with versions initially as well. Here's the way to handle your issue: 1. The binary plugin that is being depended on should be added to the MANIFEST.MF file through Eclipse (in the dependent plugin) and NOT in the dependent's POM file, ie. A - is binary B - depends on A so A is added as a plugin dependency in B's MANIFEST.MF. 2. When adding A to B's MANIFEST supply a version - Eclipse expects here a 3-part number (ie. x.x.x, like 1.0.0), so even if you write 1.0 it WILL CHANGE IT to 1.0.0. 3. psteclipse will parse the MANIFEST of B at compile time, find the dependency on A and add the -SNAPSHOT suffix, so... 4. A's version as declared in the POM should actually be: version1.0.0-SNAPSHOT/version -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13789763 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [psteclipse:update {execution: update}]
[INFO] Defaulting prefixes to the single prefix 'org.eclipse.'.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [psteclipse:testPackage {execution: test-package}]
[INFO] Building jar:
C:\dev\myapp-maven\eclipse\org.eclipse.core.databinding\target\pde-test\org.eclipse.core.databinding-1.0.0-SNAPSHOT.jar
[INFO] [psteclipse:test]
[INFO] Defaulting Eclipse home directory to 'C:\Documents and
Settings\e027723\eclipse'.
[INFO] Defaulting prefixes to the single prefix 'org.eclipse.'.
[INFO] Validating target Eclipse environment in 'C:\Documents and
Settings\e027723\eclipse'...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The required Eclipse test framework plugin
'org.eclipse.test_3.2.0' was not found in 'C:\Documents and
Settings\e027723\eclipse\plugins'
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 9 seconds
[INFO] Finished at: Fri Nov 16 16:28:38 CET 2007
[INFO] Final Memory: 8M/16M
[INFO]
Why the heck does psteclipse remove what it needs later?
2007/11/16, Sebastien ARBOGAST [EMAIL PROTECTED]:
Ok, that's what I feared. Then I'm pretty much stuck here. The thing
is that this plugin was extracted from a pre-release of Eclipse 3.3,
its source was modified and now the code can't use the final version
that is bundled with Eclipse 3.3 because it depends on modifications.
So the only solution that I see for the moment is to try to get rid of
this plugin.
Thanks for your insight on psteclipse.
2007/11/16, eSonic [EMAIL PROTECTED]:
Sebastien Arbogast wrote:
Yes, that's what I did and once again, I stepped further and stalled.
Now the issue is that I have a source-plugin depending on
org.eclipse.core.runtime. The dependecy is specified in the manifest
and I've specified the version I'm depending on (3.3.100), the one
that has been scraped and deployed to my local repository.
Yet when I try to build this source-plugin, it's looking for version
3.3.100-SNAPSHOT instead of 3.3.100.
Any idea? Could this be linked to the fact that my source-plugin's
name is something like org.eclipse... ?
This almost certainly is the cause of the problem. In terms of psteclipse,
your plugin's prefix should be distinct from org.eclipse., otherwise
psteclipse cannot tell which dependencies are from Eclipse and which are
your modules under development.
The assumption here (and the usual convention) is that the prefix for
plugins is the reverse domain name of the company or organization, ie. mine
could be:
com.buggybrain.plugin1
com.buggybrain.plugin2
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793981
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sébastien Arbogast
http://www.sebastien-arbogast.com
--
Sébastien Arbogast
http://www.sebastien-arbogast.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Ok, that's what I feared. Then I'm pretty much stuck here. The thing is that this plugin was extracted from a pre-release of Eclipse 3.3, its source was modified and now the code can't use the final version that is bundled with Eclipse 3.3 because it depends on modifications. So the only solution that I see for the moment is to try to get rid of this plugin. Thanks for your insight on psteclipse. 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: Yes, that's what I did and once again, I stepped further and stalled. Now the issue is that I have a source-plugin depending on org.eclipse.core.runtime. The dependecy is specified in the manifest and I've specified the version I'm depending on (3.3.100), the one that has been scraped and deployed to my local repository. Yet when I try to build this source-plugin, it's looking for version 3.3.100-SNAPSHOT instead of 3.3.100. Any idea? Could this be linked to the fact that my source-plugin's name is something like org.eclipse... ? This almost certainly is the cause of the problem. In terms of psteclipse, your plugin's prefix should be distinct from org.eclipse., otherwise psteclipse cannot tell which dependencies are from Eclipse and which are your modules under development. The assumption here (and the usual convention) is that the prefix for plugins is the reverse domain name of the company or organization, ie. mine could be: com.buggybrain.plugin1 com.buggybrain.plugin2 -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793981 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Thanks a lot. It works great and I'm progressing. Now the code compiles and when Maven tries to run the test, I get the following message: [ERROR] BUILD ERROR [INFO] [INFO] The required startup jar file was not found in 'C:\Documents and Settings\e027723\eclipse' Apparently psteclipse is looking for a startup.jar file in eclipse home directory but I'm using Eclipse 3.1.1 and there is no such file in there. Is psteclipse incompatible with Eclipse 3.3? 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: Obviously, I'm missing something with version numbers here, as: - the version in the POM for com.mycompany.framework.common is 1.0-SNAPSHOT - the resulting version in the manifest after running psteclipse:eclipse-plugin is 1.0 - the version com.mycompany.framework.eclipse.rcp is looking for is 1.0.0-SNAPSHOT Well, I had trouble with versions initially as well. Here's the way to handle your issue: 1. The binary plugin that is being depended on should be added to the MANIFEST.MF file through Eclipse (in the dependent plugin) and NOT in the dependent's POM file, ie. A - is binary B - depends on A so A is added as a plugin dependency in B's MANIFEST.MF. 2. When adding A to B's MANIFEST supply a version - Eclipse expects here a 3-part number (ie. x.x.x, like 1.0.0), so even if you write 1.0 it WILL CHANGE IT to 1.0.0. 3. psteclipse will parse the MANIFEST of B at compile time, find the dependency on A and add the -SNAPSHOT suffix, so... 4. A's version as declared in the POM should actually be: version1.0.0-SNAPSHOT/version -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13789763 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
I think I found my answer: http://eclipsenuggets.blogspot.com/2007/04/starting-eclipse-3.html It seems like I'm gonna have to modify psteclipse a little bit. 2007/11/16, Sebastien ARBOGAST [EMAIL PROTECTED]: Thanks a lot. It works great and I'm progressing. Now the code compiles and when Maven tries to run the test, I get the following message: [ERROR] BUILD ERROR [INFO] [INFO] The required startup jar file was not found in 'C:\Documents and Settings\e027723\eclipse' Apparently psteclipse is looking for a startup.jar file in eclipse home directory but I'm using Eclipse 3.1.1 and there is no such file in there. Is psteclipse incompatible with Eclipse 3.3? 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: Obviously, I'm missing something with version numbers here, as: - the version in the POM for com.mycompany.framework.common is 1.0-SNAPSHOT - the resulting version in the manifest after running psteclipse:eclipse-plugin is 1.0 - the version com.mycompany.framework.eclipse.rcp is looking for is 1.0.0-SNAPSHOT Well, I had trouble with versions initially as well. Here's the way to handle your issue: 1. The binary plugin that is being depended on should be added to the MANIFEST.MF file through Eclipse (in the dependent plugin) and NOT in the dependent's POM file, ie. A - is binary B - depends on A so A is added as a plugin dependency in B's MANIFEST.MF. 2. When adding A to B's MANIFEST supply a version - Eclipse expects here a 3-part number (ie. x.x.x, like 1.0.0), so even if you write 1.0 it WILL CHANGE IT to 1.0.0. 3. psteclipse will parse the MANIFEST of B at compile time, find the dependency on A and add the -SNAPSHOT suffix, so... 4. A's version as declared in the POM should actually be: version1.0.0-SNAPSHOT/version -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13789763 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
I still have an important issue: in fact I'm trying to mavenize an existing Eclipse RCP project. I have a source-plugin with a few dependencies, as shown in the manifest below: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Rcp Plug-in Bundle-SymbolicName: com.mycompany.framework.eclipse.rcp Bundle-Version: 1.0.0 Bundle-Vendor: mycompany Bundle-Localization: plugin Require-Bundle: org.eclipse.ui, org.eclipse.core.databinding.beans, org.eclipse.jface.databinding, org.eclipse.draw2d, org.eclipse.ui.ide, org.eclipse.core.runtime, org.apache.log4j, com.mycompany.framework.common, org.springframework.spring, org.eclipse.core.databinding, com.mycompany.security.crypto.smartcard Eclipse-RegisterBuddy: org.apache.commons, org.apache.log4j, org.spring, com.mycompany.framework.common Export-Package: ... Eclipse-BuddyPolicy: registered Eclipse-LazyStart: false And when I run mvn install in the root directory for all eclipse plugins, I get the following message (and others like it): [INFO] Failed to resolve artifact. Missing: -- 1) com.mycompany:com.mycompany.framework.common:pom:1.0.0-SNAPSHOT Path to dependency: 1) com.mycompany:com.mycompany.framework.eclipse.rcp:source-plugin:1.0-SNAPSHOT 2) com.mycompany:com.mycompany.framework.common:pom:1.0.0-SNAPSHOT Yet in the same directory, I've got a binary plugin with the following manifest: Export-Package: ... Bundle-Vendor: Princeton Softech Inc. Bundle-ClassPath: lib\mycompany-framework-common-1.0-SNAPSHOT.jar, lib\org.eclipse.swt.win32.win32.x86-3.3.0.jar Bundle-Version: 1.0 Eclipse-BuddyPolicy: registered Bundle-Localization: plugin Bundle-Name: com.mycompany.framework.common Bundle-ManifestVersion: 2 Bundle-SymbolicName: com.mycompany.framework.common And the following POM: Manifest-Version: 1.0 ?xml version=1.0? project parent artifactIdcom.mycompany.eclipse.plugin/artifactId groupIdcom.mycompany.eclipse/groupId version1.0.0/version /parent modelVersion4.0.0/modelVersion groupIdcom.mycompany/groupId artifactIdcom.mycompany.framework.common/artifactId namecom.mycompany.framework.common/name version1.0-SNAPSHOT/version packagingbinary-plugin/packaging dependencies dependency groupIdcom.mycompany/groupId artifactIdmycompany-framework-common/artifactId version1.0-SNAPSHOT/version /dependency /dependencies /project Obviously, I'm missing something with version numbers here, as: - the version in the POM for com.mycompany.framework.common is 1.0-SNAPSHOT - the resulting version in the manifest after running psteclipse:eclipse-plugin is 1.0 - the version com.mycompany.framework.eclipse.rcp is looking for is 1.0.0-SNAPSHOT I have trouble figuring out what's the logic behind all this. Can you help me? 2007/11/15, Sebastien ARBOGAST [EMAIL PROTECTED]: Yes, I confirm that it works. Thanks a lot 2007/11/14, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-psteclipse-plugin:1.1.0:testPackage': Unable to find the mojo 'org.ap ache.maven.plugins:maven-psteclipse-plugin:1.1.0:testPackage' in the plugin 'org .apache.maven.plugins:maven-psteclipse-plugin' org/codehaus/plexus/archiver/ArchiverException Hmm, I might have the step to help. Go to your local Maven repository, the directory where the psteclipse plugin stays (org/apache/maven/plugins/maven-psteclipse-plugin/version/), open the file with the .pom extension and add these: dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-archiver/artifactId version2.2/version /dependency /dependencies I might have been too optimistic when writing how to install the psteclipse plugin and I thinkg the automatic pom generation doesn't create these by default. Let me know if this works and I'll update the article. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13749166 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: Building Eclipse plugins with Maven 2
Yes, that's what I did and once again, I stepped further and stalled. Now the issue is that I have a source-plugin depending on org.eclipse.core.runtime. The dependecy is specified in the manifest and I've specified the version I'm depending on (3.3.100), the one that has been scraped and deployed to my local repository. Yet when I try to build this source-plugin, it's looking for version 3.3.100-SNAPSHOT instead of 3.3.100. Any idea? Could this be linked to the fact that my source-plugin's name is something like org.eclipse... ? 2007/11/16, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: It seems like I'm gonna have to modify psteclipse a little bit. Not really. It's enough to do what the link you provided suggests - copy the jar from the plugins directory into Eclipse's main directory as startup.jar and psteclipse will work just fine. I already wrote to Peter asking to work on the issue and have psteclipse support the new jar placement in some near version of the plugin. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793438 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Sebastien Arbogast wrote: It seems like I'm gonna have to modify psteclipse a little bit. Not really. It's enough to do what the link you provided suggests - copy the jar from the plugins directory into Eclipse's main directory as startup.jar and psteclipse will work just fine. I already wrote to Peter asking to work on the issue and have psteclipse support the new jar placement in some near version of the plugin. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793438 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Sebastien Arbogast wrote: Yes, that's what I did and once again, I stepped further and stalled. Now the issue is that I have a source-plugin depending on org.eclipse.core.runtime. The dependecy is specified in the manifest and I've specified the version I'm depending on (3.3.100), the one that has been scraped and deployed to my local repository. Yet when I try to build this source-plugin, it's looking for version 3.3.100-SNAPSHOT instead of 3.3.100. Any idea? Could this be linked to the fact that my source-plugin's name is something like org.eclipse... ? This almost certainly is the cause of the problem. In terms of psteclipse, your plugin's prefix should be distinct from org.eclipse., otherwise psteclipse cannot tell which dependencies are from Eclipse and which are your modules under development. The assumption here (and the usual convention) is that the prefix for plugins is the reverse domain name of the company or organization, ie. mine could be: com.buggybrain.plugin1 com.buggybrain.plugin2 -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793981 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Sebastien Arbogast wrote: I managed to get through the previous issue by creating artificial SNAPSHOT versions of the dependencies Maven asked for. But now I'm facing yet another strange issue. The build fails on a message saying that org.eclipse.test_3.2.0 plugin is missing in eclipse/plugins, but just before that, it does a cleanup on the eclipse installation and deletes a lot of plugins, including org.eclipse.test_3.2.0. I'm afraid your artificial module solution won't work here. psteclipse does the testing by copying your plugins into the Eclipse directory and deleting them after testing has been done. It finds the plugins to delete by the prefix, so if your own plugins start with org.eclipse it's very likely that psteclipse will delete some of Eclipse;s internals, hence the missing dependencies. The only solution I see for you here is changing the naming of your plugins. It's not that big of a problem, since Eclipse offers very decent refactoring features to do that across different projects. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Yes, I confirm that it works. Thanks a lot 2007/11/14, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-psteclipse-plugin:1.1.0:testPackage': Unable to find the mojo 'org.ap ache.maven.plugins:maven-psteclipse-plugin:1.1.0:testPackage' in the plugin 'org .apache.maven.plugins:maven-psteclipse-plugin' org/codehaus/plexus/archiver/ArchiverException Hmm, I might have the step to help. Go to your local Maven repository, the directory where the psteclipse plugin stays (org/apache/maven/plugins/maven-psteclipse-plugin/version/), open the file with the .pom extension and add these: dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-archiver/artifactId version2.2/version /dependency /dependencies I might have been too optimistic when writing how to install the psteclipse plugin and I thinkg the automatic pom generation doesn't create these by default. Let me know if this works and I'll update the article. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13749166 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newIn stance(JavaComponentFactory.java:44) ... 24 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Nov 14 15:34:20 CET 2007 [INFO] Final Memory: 3M/7M [INFO] Any idea of what this could be? 2007/11/13, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: Obviously some bits and pieces are missing. I actually made it work after some serious fighting. Here are the remaining pieces, which were missing from the article: http://www.buggybrain.com/2007/10/building-eclipse-plugins-with-maven-2.html -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13726555 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
OK, I really need this to work because I'm fed up with ant maintenance and manual dependency management. I've tried to start all over again. I think the problem might have come from the fact that I was not using the original version of the mojos described by the author of the article, but one that I found on m2eclipse repository. Do I downloaded the original version linked in the article, but when I tried to build it, it failed because it doesn't find maven-pst parent project. Does anyone know where I can fin that project? 2007/10/23, Sebastien ARBOGAST [EMAIL PROTECTED]: I checked out the last version I could find in the m2eclipse project: http://svn.codehaus.org/m2eclipse/maven-pst That's the one I'm using with a few modifications to the POM in order to build against Maven 2.0.7 and Eclipse 3.3.1 Now here are the error messages that I get: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.myapp.eclipse:org.springframework.spring:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.springframework.spring:pom:1.0 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 3) com.myapp.eclipse:org.apache.log4j:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.apache.log4j:pom:1.0 4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH OT 5) com.myapp.eclipse:org.eclipse.ui:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.ui \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui:jar:1.0 6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.core.runtime \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS HOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1 .0-SNAPSHOT 9) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 10) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0 11) com.myapp.eclipse:org.eclipse.core.databinding.beans:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding.beans:pom:1.0 -- 11 required artifacts are missing. for artifact: com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-plugin:1.0- SNAPSHOT from the specified remote repositories: central ( http://repo1.maven.org/maven2), eclipse (http://repo1.maven.org/eclipse) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Tue Oct 23 10:16:38 CEST 2007 [INFO] Final Memory: 10M/19M [INFO] 2007/10/23, Torsten Schlabach [EMAIL PROTECTED]:
Re: Building Eclipse plugins with Maven 2
I finally found some lead to progress. I managed to build and install the original version of the mojos. Then I found something: it's all a problem of dependency versions. In my source-plugin module manifest dependencies, I did not specify any version for the plugins on which I depend, which caused the modified pom to reference 1.0 version by default. Now I added a version for the plugins that are in my workspace (source-plugin et binary-plugin) and it's looking for the right versions. But I still have a problem for plugins that are supposed to be provided by Eclipse itself. It seems that they are not deployed to my local repository or it's looking in the wrong directories: 1) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0 Path to dependency: 1) com.mycompany.eclipse:com.mycompany.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0 Obviously some bits and pieces are missing. 2007/10/26, Sebastien ARBOGAST [EMAIL PROTECTED] : OK, I really need this to work because I'm fed up with ant maintenance and manual dependency management. I've tried to start all over again. I think the problem might have come from the fact that I was not using the original version of the mojos described by the author of the article, but one that I found on m2eclipse repository. Do I downloaded the original version linked in the article, but when I tried to build it, it failed because it doesn't find maven-pst parent project. Does anyone know where I can fin that project? 2007/10/23, Sebastien ARBOGAST [EMAIL PROTECTED] : I checked out the last version I could find in the m2eclipse project: http://svn.codehaus.org/m2eclipse/maven-pst That's the one I'm using with a few modifications to the POM in order to build against Maven 2.0.7 and Eclipse 3.3.1 Now here are the error messages that I get: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.myapp.eclipse:org.springframework.spring:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.springframework.spring:pom:1.0 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 3) com.myapp.eclipse:org.apache.log4j:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.apache.log4j:pom:1.0 4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH OT 5) com.myapp.eclipse:org.eclipse.ui:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.ui \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui:jar:1.0 6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.core.runtime \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS HOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1 .0-SNAPSHOT 9) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 10) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0 Path to dependency: 1)
Re: Building Eclipse plugins with Maven 2
you can see an example of an eclipse plugin build with maven at http://q4e.googlecode.com/svn/branches/built-with-maven/embedder/ On 10/26/07, Sebastien ARBOGAST [EMAIL PROTECTED] wrote: I finally found some lead to progress. I managed to build and install the original version of the mojos. Then I found something: it's all a problem of dependency versions. In my source-plugin module manifest dependencies, I did not specify any version for the plugins on which I depend, which caused the modified pom to reference 1.0 version by default. Now I added a version for the plugins that are in my workspace (source-plugin et binary-plugin) and it's looking for the right versions. But I still have a problem for plugins that are supposed to be provided by Eclipse itself. It seems that they are not deployed to my local repository or it's looking in the wrong directories: 1) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0 Path to dependency: 1) com.mycompany.eclipse:com.mycompany.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0 Obviously some bits and pieces are missing. 2007/10/26, Sebastien ARBOGAST [EMAIL PROTECTED] : OK, I really need this to work because I'm fed up with ant maintenance and manual dependency management. I've tried to start all over again. I think the problem might have come from the fact that I was not using the original version of the mojos described by the author of the article, but one that I found on m2eclipse repository. Do I downloaded the original version linked in the article, but when I tried to build it, it failed because it doesn't find maven-pst parent project. Does anyone know where I can fin that project? 2007/10/23, Sebastien ARBOGAST [EMAIL PROTECTED] : I checked out the last version I could find in the m2eclipse project: http://svn.codehaus.org/m2eclipse/maven-pst That's the one I'm using with a few modifications to the POM in order to build against Maven 2.0.7 and Eclipse 3.3.1 Now here are the error messages that I get: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.myapp.eclipse:org.springframework.spring:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.springframework.spring:pom:1.0 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 3) com.myapp.eclipse:org.apache.log4j:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.apache.log4j:pom:1.0 4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH OT 5) com.myapp.eclipse:org.eclipse.ui:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.ui \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui:jar:1.0 6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org .eclipse.core.runtime \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS HOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1 .0-SNAPSHOT 9)
Building Eclipse plugins with Maven 2
I'm trying to apply the instructions given in the Eclipse Corner article ( http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html) in order to build several Eclipse plugins using Maven 2.0.4. In the first part of the article there is something about a Deploy Mojo that would scrape my Eclipse installation and deploy all the jars to my local repository. But when I try to run mvn install at the level of my super POM, I get error messages because Eclipse jar dependencies are missing. Has anyone managed to build Eclipse plugins with this article? Any idea of what I might have forgotten? BTW, I've attached my super POM. -- Sébastien Arbogast http://www.sebastien-arbogast.com ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.myapp.eclipse/groupId artifactIdcom.myapp.eclipse.plugin/artifactId packagingpom/packaging version1.0.0/version nameEclipse Plug-ins/name descriptionThis is the Supe POM for all eclipse plugins inside myapp/description build resources resource directorysrc/main/java/directory includes include**/*.properties/include include**/*.xml/include /includes /resource resource directory./directory includes includeplugin.xml/include includeplugin.properties/include includemodel/**/include includeicons/**/include /includes /resource /resources plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId configuration instrumentation excludes excludecom/myapp/**/model/**/impl/*.class/exclude excludecom/myapp/**/model/**/util/*.class/exclude excludecom/myapp/**/pojo/*.class/exclude excludecom/myapp/**/Messages.class/exclude excludecom/myapp/**/wizard/*.class/exclude excludecom/myapp/**/actions/*.class/exclude excludecom/cloudgarden/resource/**/*.class/exclude /excludes /instrumentation /configuration executions execution goals goalclean/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-psteclipse-plugin/artifactId version1.0.0-SNAPSHOT/version extensionstrue/extensions configuration logModificationstrue/logModifications testFrameworkVersion3.3.1/testFrameworkVersion /configuration executions execution idtest-package/id phasetest-compile/phase goals goaltestPackage/goal /goals /execution execution idupdate/id phaseprocess-resources/phase goals goalupdate/goal /goals /execution execution idupdate-site-classpath/id phasepre-site/phase goals goalupdate/goal /goals /execution /executions /plugin plugin artifactIdmaven-eclipse-plugin/artifactId configuration projectnatures projectnatureorg.eclipse.jdt.core.javanature/projectnature projectnatureorg.eclipse.pde.PluginNature/projectnature /projectnatures buildcommands buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand buildcommandorg.eclipse.pde.ManifestBuilder/buildcommand buildcommandorg.eclipse.pde.SchemaBuilder/buildcommand /buildcommands classpathContainers classpathContainerorg.eclipse.pde.core.requiredPlugins/classpathContainer /classpathContainers /configuration /plugin /plugins /build profiles profile idorg.eclipse.swt.win32/id activation os namewindows xp/name archx86/arch /os /activation dependencies dependency groupIdorg.eclipse.swt.win32.win32/groupId artifactIdx86/artifactId version3.3.0-v3346/version typejar/type /dependency /dependencies /profile profile idorg.eclipse.swt.linux/id activation os namelinux/name archi386/arch /os /activation dependencies dependency groupIdcom.princetonsoftech.eclipse/groupId artifactIdorg.eclipse.swt.gtk.linux.x86/artifactId version3.3.1/version typejar/type /dependency /dependencies /profile /profiles properties org.eclipse.core.runtimejar/org.eclipse.core.runtime org.eclipse.jfacejar/org.eclipse.jface org.eclipse.uijar/org.eclipse.ui org.eclipse.datatools.connectivitypom/org.eclipse.datatools.connectivity org.eclipse.datatools.modelbase.dbdefinitionpom/org.eclipse.datatools.modelbase.dbdefinition org.eclipse.datatools.modelbase.sqlpom/org.eclipse.datatools.modelbase.sql org.eclipse.datatools.connectivity.sqm.corejar/org.eclipse.datatools.connectivity.sqm.core org.eclipse.datatools.connectivity.sqm.core.uipom/org.eclipse.datatools.connectivity.sqm.core.ui
Re: Building Eclipse plugins with Maven 2
I checked out the last version I could find in the m2eclipse project: http://svn.codehaus.org/m2eclipse/maven-pst That's the one I'm using with a few modifications to the POM in order to build against Maven 2.0.7 and Eclipse 3.3.1 Now here are the error messages that I get: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) com.myapp.eclipse:org.springframework.spring:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.springframework.spring:pom:1.0 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0 3) com.myapp.eclipse:org.apache.log4j:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.apache.log4j:pom:1.0 4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH OT 5) com.myapp.eclipse:org.eclipse.ui:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse -DartifactId=org .eclipse.ui \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui:jar:1.0 6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myapp.eclipse -DartifactId=org .eclipse.core.runtime \ -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0 7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0 8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS HOT Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1 .0-SNAPSHOT 9) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0 10) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0 11) com.myapp.eclipse:org.eclipse.core.databinding.beans:pom:1.0 Path to dependency: 1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl ugin:1.0-SNAPSHOT 2) com.myapp.eclipse:org.eclipse.core.databinding.beans:pom:1.0 -- 11 required artifacts are missing. for artifact: com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-plugin:1.0- SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), eclipse (http://repo1.maven.org/eclipse) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Tue Oct 23 10:16:38 CEST 2007 [INFO] Final Memory: 10M/19M [INFO] 2007/10/23, Torsten Schlabach [EMAIL PROTECTED]: Hi Sebastien, I know I once made it work, but I remember I had to download some more recent code than the one which is mentioned on the article. I'd argue that the authors of the article did a great job making me understand what the problem is after all and explaining why they made the design decisions they have made, but it's not exactly a howto IMO. But when I try to run mvn install at the level of my super POM, I get error messages because Eclipse jar dependencies are missing. If I remember that article correctly, their concept was to modify POMs in memory to point to the actual Eclipse installation, but they make some assumptions as to where that should
Re: Building Eclipse plugins with Maven 2
Hi Sebastien, I know I once made it work, but I remember I had to download some more recent code than the one which is mentioned on the article. I'd argue that the authors of the article did a great job making me understand what the problem is after all and explaining why they made the design decisions they have made, but it's not exactly a howto IMO. But when I try to run mvn install at the level of my super POM, I get error messages because Eclipse jar dependencies are missing. If I remember that article correctly, their concept was to modify POMs in memory to point to the actual Eclipse installation, but they make some assumptions as to where that should be. What section of the article to you refer to? Can you post an error message you're getting? Regards, Torsten Sebastien ARBOGAST schrieb: I'm trying to apply the instructions given in the Eclipse Corner article (http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html) in order to build several Eclipse plugins using Maven 2.0.4. In the first part of the article there is something about a Deploy Mojo that would scrape my Eclipse installation and deploy all the jars to my local repository. But when I try to run mvn install at the level of my super POM, I get error messages because Eclipse jar dependencies are missing. Has anyone managed to build Eclipse plugins with this article? Any idea of what I might have forgotten? BTW, I've attached my super POM. -- Sébastien Arbogast http://www.sebastien-arbogast.com ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.myapp.eclipse/groupId artifactIdcom.myapp.eclipse.plugin/artifactId packagingpom/packaging version1.0.0/version nameEclipse Plug-ins/name descriptionThis is the Supe POM for all eclipse plugins inside myapp/description build resources resource directorysrc/main/java/directory includes include**/*.properties/include include**/*.xml/include /includes /resource resource directory./directory includes includeplugin.xml/include includeplugin.properties/include includemodel/**/include includeicons/**/include /includes /resource /resources plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId configuration instrumentation excludes excludecom/myapp/**/model/**/impl/*.class/exclude excludecom/myapp/**/model/**/util/*.class/exclude excludecom/myapp/**/pojo/*.class/exclude excludecom/myapp/**/Messages.class/exclude excludecom/myapp/**/wizard/*.class/exclude excludecom/myapp/**/actions/*.class/exclude excludecom/cloudgarden/resource/**/*.class/exclude /excludes /instrumentation /configuration executions execution goals goalclean/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-psteclipse-plugin/artifactId
[m2] Building Eclipse plugins using Maven 2
I have started looking at what would need to be done in order to build Eclipse plugins using Maven 2. The general idea is that POM files could be generated using information in the plugins' manifest.mf, plugin.xml and build.properties files. At first glance, the required information consists of the dependencies (out of the manifest or plugin.xml), the sources and resources (from build.properties). One of the first problems that arises is physical layout. An eclipse workspace with a set of plugins that need to be considered at the same time, these plugins do not necessarily reside in the same location on disk. We will want to treat these plugins as modules/ under a common parent. The first question then is for each module, do we copy all the sources resources into the normal maven layout, or do we create only the pom.xml and point to the original locations using the sourceDirectory/ and resourcedirectory/ tags. Because an eclipse plugin can result in more than one jar file, we may then have nested modules for each additional jar. There will also be dependencies on plugins that exist in a target eclipse installation instead of in the workspace. Jars for these plugins would need to be placed into the local repository. POM files would also need to be generated for these to specify their interdependencies. The install phase would be different from the normal m2 install. We would need to gather the jars and any additional resources into the standard eclipse features plugins directories. I have not yet looked into this. I would welcome any comments people have, -Andrew
Re: [m2] Building Eclipse plugins using Maven 2
This would be a wonderful idea. I'd particularly welcome easy ways to run JUnit tests on plugins from maven. good luck, Benedict Andrew Niefer wrote: I have started looking at what would need to be done in order to build Eclipse plugins using Maven 2. The general idea is that POM files could be generated using information in the plugins' manifest.mf, plugin.xml and build.properties files. At first glance, the required information consists of the dependencies (out of the manifest or plugin.xml), the sources and resources (from build.properties). One of the first problems that arises is physical layout. An eclipse workspace with a set of plugins that need to be considered at the same time, these plugins do not necessarily reside in the same location on disk. We will want to treat these plugins as modules/ under a common parent. The first question then is for each module, do we copy all the sources resources into the normal maven layout, or do we create only the pom.xml and point to the original locations using the sourceDirectory/ and resourcedirectory/ tags. Because an eclipse plugin can result in more than one jar file, we may then have nested modules for each additional jar. There will also be dependencies on plugins that exist in a target eclipse installation instead of in the workspace. Jars for these plugins would need to be placed into the local repository. POM files would also need to be generated for these to specify their interdependencies. The install phase would be different from the normal m2 install. We would need to gather the jars and any additional resources into the standard eclipse features plugins directories. I have not yet looked into this. I would welcome any comments people have, -Andrew No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.18/91 - Release Date: 06/09/2005
Re: [m2] Building Eclipse plugins using Maven 2
On Wed, 2005-09-07 at 16:58 -0400, Andrew Niefer wrote: I have started looking at what would need to be done in order to build Eclipse plugins using Maven 2. The general idea is that POM files could be generated using information in the plugins' manifest.mf, plugin.xml and build.properties files. At first glance, the required information consists of the dependencies (out of the manifest or plugin.xml), the sources and resources (from build.properties). Might you have an ViewCVS URL of an example plugin, or set of plugins, that we can work against while discussing this? -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Building Eclipse plugins using Maven 2
At 04:58 PM 9/7/2005, Andrew Niefer wrote: I have started looking at what would need to be done in order to build Eclipse plugins using Maven 2. ... snip ... The install phase would be different from the normal m2 install. We would need to gather the jars and any additional resources into the standard eclipse features plugins directories. I have not yet looked into this. Andrew, I'm not sure that I agree with your assessment concerning the requirement to gather the jars and any additional resources into the standard eclipse features and plugins directories. As an example of variant Eclipse configurations, whenever a new version of Ant is released, I always download the new version, remove the old Ant version's jars from my ANT_HOME/lib directory, and install the new version's jars. Then I navigate into the Eclipse preferences for the Ant runtime, and set the references to the necessary jars to the jars in my ANT_HOME/lib. That has worked numerous times without a problem and I have done it more than once, replacing the previous jars that I had referenced with newer ones, or upgrading the Ant versions in the varying versions of Eclipse as they have changed over time. My activities aren't automated, but they could easily be. Certainly one would expect that the Eclipse Foundation and its personnel would have and follow standard installation conventions but I don't see why they must be viewed as sacred. What would seem to be important, from a purely configuration oriented perspective, is that there are well defined default conventions and that in addition to them there may be alternate configuration practices that can be deployed in an automated manner to produce differing but still desirable Eclipse configurations. In fact, if the Eclipse Foundation hasn't already taken steps to do so, the creation of automated installation procedures to create multiple initial configurations might be a value addition to the Eclipse tool set. I know that I have read about non-Eclipse Foundation people doing this to support their own development requirements. Lastly, one of the main values of Maven is its ability to organize and manage development artifacts and maintain them as configuration items. Maven manages its configuration items at a much finer level of granularity than does Eclipse, and again there might be value for the Eclipse product line to move toward Maven's conventions rather than vice versa. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Building Eclipse plugins using Maven 2
Jason van Zyl [EMAIL PROTECTED] wrote on 09/07/2005 05:29:45 PM: Might you have an ViewCVS URL of an example plugin, or set of plugins, that we can work against while discussing this? It was suggested on the eclipse pde-build mailing list that building the eclipse plugins that make up the RCP would be a good place to start. In fact, Jeff's message, http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00076.html, is a likely a better starting point than mine. The ViewCVS URL for eclipse is http://dev.eclipse.org/viewcvs/index.cgi/ If we started with org.eclipse.osgi which has no external dependencies, org.eclipse.core.runtime depends on osgi, and org.eclipse.swt introduces fragments as an interesting case. -Andrew
Re: [m2] Building Eclipse plugins using Maven 2
What about from a pom.xml, maven can generate manifest.fmhttp://manifest.fmfile. There is already some work done at http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/ -D On 9/7/05, Andrew Niefer [EMAIL PROTECTED] wrote: Jason van Zyl [EMAIL PROTECTED] wrote on 09/07/2005 05:29:45 PM: Might you have an ViewCVS URL of an example plugin, or set of plugins, that we can work against while discussing this? It was suggested on the eclipse pde-build mailing list that building the eclipse plugins that make up the RCP would be a good place to start. In fact, Jeff's message, http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00076.html, is a likely a better starting point than mine. The ViewCVS URL for eclipse is http://dev.eclipse.org/viewcvs/index.cgi/ If we started with org.eclipse.osgi which has no external dependencies, org.eclipse.core.runtime depends on osgi, and org.eclipse.swt introduces fragments as an interesting case. -Andrew
