Order of maven multi module is not maintained for eclipse plugins
Hi,
We have a bunch of eclipse plugin projects, features and update sites. We
have created a master pom where we define the modules:
modules
modulebundles/b1/module
modulefeatures/f1/module
modulep2/site1/module
modulebundles/b2/module
/modules
We wanted to preserve this order and as per Guide to working with Multiple
Modules http://maven.apache.org/guides/mini/guide-multiple-modules.html As
per the link above we assumed that the order will be preserved as per the
order in which the module elements were listed.
Our requirement: site1 produces a site_assembly.zip. We wanted to take this
zip file and wrap into around into a bundle which is what b2 bundle does.
*Our observation:*
1. Maven reactor order which is printed at the beginning of the
multi-module build is proper, however the build for every module is forked.
2. Because of (1) the bundle b2 get built before the site1 project is
build and is able to produce a site assembly zip.
3. We tried adding a dependency in b2's pom.xml to site1 but the build
failed as it tries to build b2 first which has dependency on site1 which
has not been built till now.
4. We observed the same behavior when we had unit test as osgi fragment.
In the order we clearly specified that the host comes before the test
fragment but when the maven build is invoked then it always built the
fragment before the host and it used to fail.
Plugins that are defined in master pom:
plugin
!-- enable tycho build extension --
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-maven-plugin/artifactId
version${tycho-version}/version
extensionstrue/extensions
/plugin
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtarget-platform-configuration/artifactId
version${tycho-version}/version
configuration
disableP2Mirrorstrue/disableP2Mirrors
resolverp2/resolver
target
artifact
groupIdcom.x.y/groupId
artifactIdp2.build.target/artifactId
version${project.version}/version
classifierx/classifier
/artifact
/target
/configuration
/plugin
We are not sure if maven-tycho-plugin interferes with the reactor order, so
any help would be appreciated.
Best Regards,
Madhav
Re: Order of maven multi module is not maintained for eclipse plugins
This is a Tycho specific question, ask on the Tycho user list @ Eclipse
https://dev.eclipse.org/mailman/listinfo/tycho-user
On Jan 25, 2012, at 9:47 AM, Madhav Bhargava wrote:
Hi,
We have a bunch of eclipse plugin projects, features and update sites. We
have created a master pom where we define the modules:
modules
modulebundles/b1/module
modulefeatures/f1/module
modulep2/site1/module
modulebundles/b2/module
/modules
We wanted to preserve this order and as per Guide to working with Multiple
Modules http://maven.apache.org/guides/mini/guide-multiple-modules.html As
per the link above we assumed that the order will be preserved as per the
order in which the module elements were listed.
Our requirement: site1 produces a site_assembly.zip. We wanted to take this
zip file and wrap into around into a bundle which is what b2 bundle does.
*Our observation:*
1. Maven reactor order which is printed at the beginning of the
multi-module build is proper, however the build for every module is forked.
2. Because of (1) the bundle b2 get built before the site1 project is
build and is able to produce a site assembly zip.
3. We tried adding a dependency in b2's pom.xml to site1 but the build
failed as it tries to build b2 first which has dependency on site1 which
has not been built till now.
4. We observed the same behavior when we had unit test as osgi fragment.
In the order we clearly specified that the host comes before the test
fragment but when the maven build is invoked then it always built the
fragment before the host and it used to fail.
Plugins that are defined in master pom:
plugin
!-- enable tycho build extension --
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-maven-plugin/artifactId
version${tycho-version}/version
extensionstrue/extensions
/plugin
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtarget-platform-configuration/artifactId
version${tycho-version}/version
configuration
disableP2Mirrorstrue/disableP2Mirrors
resolverp2/resolver
target
artifact
groupIdcom.x.y/groupId
artifactIdp2.build.target/artifactId
version${project.version}/version
classifierx/classifier
/artifact
/target
/configuration
/plugin
We are not sure if maven-tycho-plugin interferes with the reactor order, so
any help would be appreciated.
Best Regards,
Madhav
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Managing depedencies of required eclipse-plugins with maven
Hello, I'm new to maven, started reading a lot about how it works now but am still quite unsure if it can do what I'd like to have based on it's dependency-management. Which is: being able to tell which eclipse-plugins should be distributed with an eclipse-plugin I try to develop. The goal is that maven being called on a target-system will fetch the self-developed plugin from somewhere together with all needed jar's and eclipse plugins and have them installed into eclipse, making sure that the eclipse provides all plugins which are necessary for running the developed eclipse-plugin. While it seems possible to have jar's deployed for example (sidenote: how can they be integrated into the eclipse-project properly?), I only saw an eclipse-plugin for maven which creates an eclipse project from a source-directory, which works fine. But regarding the dependency-plugin of maven I do not seem to find any information if it can handle such things like getting eclipse-plugins and having them integrated. Is this possible (with reasonable effort) at all? If so, how? (even pointing me to a location where I could read about that further would be helpful) Is there some maven-repository which provides eclipse-plugins and allows them to integrate them with a project as a dependency? If so, does it offer to handle version-numbers of plugins even? kind regards Martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
About unit test for eclipse-plugins
Hi, All I am new to maven3-beta and want to see how it works with eclipse. I use maven3-beta to compile my eclipse plugins and it compiles successfully. However, when I write a simple JUnit test file to test it. It gives the following information: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.016 sec FAILURE! test(SimpleTest) Time elapsed: 0.016 sec ERROR! java.lang.NoClassDefFoundError: org/eclipse/core/runtime/IAdaptable ... How should I avoid this error. Do I need to change POM? Best regards Yang Yang
Install eclipse plugins to local repository
I am trying to install the eclipse plugins under my eclipse installation directory to my local maven repository. These are the steps that I follow: 1. mvn eclipse:to-maven -DeclipseDir=C:\Opt\Eclipse 2. Now, I want to update the group id in the pom files created in the above step. For example, for org.eclipse.core.runtime, I want to change the group id from org.eclipse.core to com.mycompany.tools.eclipse, artifact id from runtime to org.eclipse.core.runtime. I would also want to make similar changes to the dependency elements in this pom. I want to make this change before I run mvn install:install-file such that these will be stored in my local repository in a separate layout than the default one: .m2\repository\com\mycompany\tools\eclipse\org.eclipse.core.runtime\3.5.0 rather than .m2\repository\org\eclipse\core\runtime\3.5.0 Is there a way that I can automate this step no. 2? Any help will be much appreciated. Thanks! This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Builing Eclipse plugins with Maven2 ?
Hi, we have some Eclipse Plugin projects, that are based on libraries build with Maven. Now, I want to build these eclipse plugins with Maven, too. I´ve read about Tycho, maven-bundle-plugin, pde-maven.plugin and so on. Is there any recommendation from anyone? I don´t want to spent a lot of time in making my own experiences with all of them Thanx for any advice, if someone is also building eclipse-plugins with Maven (coming from the pom.xml side) Torsten
Re: Builing Eclipse plugins with Maven2 ?
On Fri, Jun 26, 2009 at 9:09 PM, torsten.reinh...@gi-de.com wrote: Hi, we have some Eclipse Plugin projects, that are based on libraries build with Maven. Now, I want to build these eclipse plugins with Maven, too. I´ve read about Tycho, maven-bundle-plugin, pde-maven.plugin and so on. Is there any recommendation from anyone? I don´t want to spent a lot of time in making my own experiences with all of them Thanx for any advice, if someone is also building eclipse-plugins with Maven (coming from the pom.xml side) Torsten pde will work (I have used it) but there is no longer a maintainer for that project. It is also a bit tedious to sort out getting it working. tycho is meant to be the better replacement but I have not tried it (and it didn't look obvious how to use it). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Creating Eclipse plugins with Maven
Hi, I'm looking for a way to build an Eclipse plugin using Maven. So I want to have a pom.xml for the Eclipse plugin, which gives me the possibility to generate a .project file. When I use the M2Eclipse plugin in Eclipse, I'm able to select packaging = eclipse-plugin. But when I run: $ mvn eclipse:eclipse (I want a .project file), I'm getting this error: [ERROR] BUILD ERROR [INFO] [INFO] Cannot find lifecycle mapping for packaging: 'eclipse-plugin'. Component descriptor cannot be found in the component repository: org.apache.mav en.lifecycle.mapping.LifecycleMappingeclipse-plugin. Is it possible to create Eclipse Plugin Projects with Maven? Or is the only way using http://docs.codehaus.org/display/M2ECLIPSE/Building+tycho? Regards, Jochen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Build Eclipse plugins with Maven
Hi All, I am just wondering what is the best way to build a set of Eclipse plugins using Maven? Via Google I discovered Tycho, but what I do not like about Tycho is that it is essentially a separate, experimental Maven 3 installation, rather than a plugin for Maven 2. Unfortunately this approach will not work well with some of our continuous integration and publication systems so I have to rule it out. Apart from Tycho, then, what is the recommended approach? -- Jason Voegele Murphy's Law, that brash proletarian restatement of Godel's Theorem. -- Thomas Pynchon, Gravity's Rainbow - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Compiling Eclipse plugins with ECJ (Eclipse Compiler for Java)
Hello, I'm trying to compile some Eclipse plugins (about 50). The problem is that I'd want to compile them with ECJ, but I need a relatively new version. Almost all the information available online is from 2004-2006, Eclipse 3.2. I could use Eclipse PDE, but PDE has its own dependency resolution mechanism, and the integration between PDE and Maven is rather tedious. For Eclipse 3.3/3.4, is there any Maven plugin which calls the ECJ? Thank, Costin. -- View this message in context: http://www.nabble.com/Compiling-Eclipse-plugins-with-ECJ-%28Eclipse-Compiler-for-Java%29-tp20065506p20065506.html 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: Local repository not downloading Eclipse plugins from the internal repository
Wendy Smoak-3 wrote: No pluginRespositories ? You'll need to repeat the repository as a pluginRepository if you want Maven to check it for plugins. Also check the repository metadata for the Eclipse plugin. Plugins won't work unless the metadata contains the 'release' and 'latest' elements. (Possibly only one of those is necessary, but if both are missing, it won't work.) Hi Wendy, thank you for helping me out again (last time on the Archiva users forum) :) Yes you were right again, it was the missing pluginRespositories tag. I guess it worked before because I had some old versions of Eclipse plugins on the machines where I have my local and internal repository which were created earlier, before the project was set up with the internal repo. Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Local-repository-not-downloading-Eclipse-plugins-from-the-internal-repository-tp15502970s177p15560496.html 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: Local repository not downloading Eclipse plugins from the internal repository
On Feb 18, 2008 10:31 AM, Papapara Tudu [EMAIL PROTECTED] wrote: I'm using Archiva 1.0.1 and Maven 2.0.8. My Maven settings.xml are the default ones, no changes (on both machines). My pom.xml has the following entry: ... repositories ... No pluginRespositories ? You'll need to repeat the repository as a pluginRepository if you want Maven to check it for plugins. Also check the repository metadata for the Eclipse plugin. Plugins won't work unless the metadata contains the 'release' and 'latest' elements. (Possibly only one of those is necessary, but if both are missing, it won't work.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Local repository not downloading Eclipse plugins from the internal repository
Wayne Fay wrote: What software are you using to run your internal repository? And how did you get the plugin there (mvn deploy; manual copy of files; something else)? Make sure the metadata is present for the Eclipse plugin in your repo. I'm using Archiva 1.0.1 and Maven 2.0.8. My Maven settings.xml are the default ones, no changes (on both machines). My pom.xml has the following entry: distributionManagement snapshotRepository idprojectrepo/id url dav:http://here.build.machine.ip/archiva/repository/projectrepo/ /url /snapshotRepository /distributionManagement repositories repository idprojectrepo/id nameprojectreponame/name urlhttp://here.build.machine.ip/archiva/repository/projectrepo//url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories The problem is, I have noticed that even when I run a build on the build machine, where the Archiva repository is located, it also doesn't download any Maven plugins. The only way for me to download and install the Maven plugins both on the build and my local machine is to set a proxy in my settings.xml and comment out the distributionManagement and repositories elements from pom.xml - so when I bypass the internal repository, it works fine. What could be wrong there? Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Local-repository-not-downloading-Eclipse-plugins-from-the-internal-repository-tp15502970s177p15547059.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Local repository not downloading Eclipse plugins from the internal repository
Hello, my project is using an internal repository for all dependencies. For some reason I cannot run any of the Eclipse Maven plugins, however all other dependencies get downloaded correctly from the internal repository. For example, when I run mvn eclipse:eclipse, I get the following error: [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no valid version could be found [INFO] I deleted the whole \org\apache\maven\plugins folder from my local repository but that didn't change. I also tested deleting that folder on the internal repository and then running eclipse:eclipse on that machine and it went fine, the plugin got installed correctly. But my local repository doesn't pick up that plugin from the internal repository. Also the Eclipse plugins like eclipse:eclipse and eclipse:clean were definitely working for me before, which I don't understand. I'm using maven 2.0.7. Any ideas why that might be happening? Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Local-repository-not-downloading-Eclipse-plugins-from-the-internal-repository-tp15502970s177p15502970.html 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: Local repository not downloading Eclipse plugins from the internal repository
What software are you using to run your internal repository? And how did you get the plugin there (mvn deploy; manual copy of files; something else)? Make sure the metadata is present for the Eclipse plugin in your repo. Wayne On 2/15/08, Papapara Tudu [EMAIL PROTECTED] wrote: Hello, my project is using an internal repository for all dependencies. For some reason I cannot run any of the Eclipse Maven plugins, however all other dependencies get downloaded correctly from the internal repository. For example, when I run mvn eclipse:eclipse, I get the following error: [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no valid version could be found [INFO] I deleted the whole \org\apache\maven\plugins folder from my local repository but that didn't change. I also tested deleting that folder on the internal repository and then running eclipse:eclipse on that machine and it went fine, the plugin got installed correctly. But my local repository doesn't pick up that plugin from the internal repository. Also the Eclipse plugins like eclipse:eclipse and eclipse:clean were definitely working for me before, which I don't understand. I'm using maven 2.0.7. Any ideas why that might be happening? Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Local-repository-not-downloading-Eclipse-plugins-from-the-internal-repository-tp15502970s177p15502970.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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
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. Here is my log:
C:\dev\myapp-maven\eclipsemvn install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Eclipse Plug-ins
[INFO] com.mycompany.framework.common
[INFO] org.springframework.spring
[INFO] com.mycompany.framework.eclipse.rcp
[INFO] org.eclipse.jface.databinding
[INFO] com.mycompany.security.crypto.smartcard
[INFO] org.apache.log4j
[INFO] org.eclipse.core.databinding
[INFO]
[INFO] Building Eclipse Plug-ins
[INFO]task-segment: [install]
[INFO]
[INFO] [psteclipse:update {execution: update}]
[INFO] [psteclipse:testPackage {execution: test-package}]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\dev\myapp-maven\eclipse\pom.xml to C:\Documents
and
Settings\e027723\.m2\repository\com\mycompany\eclipse\com.mycompany.eclipse.plugin\1.0.0\com.mycompany.eclipse.plugin-1.0.0.pom
[INFO]
[INFO] Building com.mycompany.framework.common
[INFO]task-segment: [install]
[INFO]
[INFO] [psteclipse:update {execution: update}]
[INFO] Defaulting prefixes to the single prefix 'com.mycompany.'.
[INFO] [psteclipse:testPackage {execution: test-package}]
[INFO] [site:attach-descriptor]
[INFO] [psteclipse:install]
[INFO] Installing
C:\dev\myapp-maven\eclipse\com.mycompany.framework.common\pom.xml to
C:\Documents and
Settings\e027723\.m2\repository\com\mycompany\com.mycompany.framework.common\1.0.0-SNAPSHOT\com.mycompany.framework.common-1.0.0-SNAPSHOT.pom
[INFO]
[INFO] Building org.springframework.spring
[INFO]task-segment: [install]
[INFO]
[INFO] [psteclipse:update {execution: update}]
[INFO] Defaulting prefixes to the single prefix 'org.springframework.'.
[INFO] [psteclipse:testPackage {execution: test-package}]
[INFO] [site:attach-descriptor]
[INFO] [psteclipse:install]
[INFO] Installing
C:\dev\myapp-maven\eclipse\org.springframework.spring\pom.xml to
C:\Documents and
Settings\e027723\.m2\repository\com\mycompany\org.springframework.spring\2.0.7\org.springframework.spring-2.0.7.pom
[INFO]
[INFO] Building com.mycompany.framework.eclipse.rcp
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [psteclipse:update {execution: update}]
[INFO] Defaulting prefixes to the single prefix 'com.mycompany.'.
Downloading:
http://repo1.maven.org/maven2/com/mycompany/org.springframework.spring/2.0.7/org.springframework.spring-2.0.7.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading: http://repo1.maven.org/maven2/com/ncipher/jutils/1.0/jutils-1.0.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/iaik/pkcs/pkcs11-wrapper/1.2.16/pkcs11-wrapper-1.2.16.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[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\com.mycompany.framework.eclipse.rcp\target\pde-test\com.mycompany.framework.eclipse.rcp-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 'com.mycompany.'.
[INFO] Validating target Eclipse environment in 'C:\Documents and
Settings\e027723\eclipse'...
[INFO] Cleaning target Eclipse environment in 'C:\Documents and
Settings\e027723\eclipse'...
[INFO] Building 'test.xml' for PDE testing in
'C:\dev\myapp-maven\eclipse\com.mycompany.framework.eclipse.rcp\target\pde-test\test.xml'...
[INFO] No test cases found - skipping
[INFO] [psteclipse:package]
[INFO] Building jar:
C:\dev\myapp-maven\eclipse
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
]: 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 groupId com.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
Re: Building Eclipse plugins with Maven 2
) 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 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; modelVersion 4.0.0/modelVersion groupId com.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
Re: Building Eclipse plugins with Maven 2
) 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 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; modelVersion 4.0.0/modelVersion groupId com.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
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
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 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
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
Re: Eclipse Plugins
Barrie Treloar a écrit : On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. Hi, The current maven-eclipse-plugin is definitively the more accurate plugin to begin with. The current SNAPSHOT could generate the MANIFEST.MF file needed by any eclipse plugin, but it would not generate plugin.xml. there is some work in progress by somebody here in the list to make an archetype for eclipse plugin. So for compiling eclipse plugin, the work is almost done ( for me, it is working ) . What is missing today is : - packaging eclipse plugin ( could be done with assembly ) - support for RCP packaging ( currently you cannot build eclipse RCP app like eclipse does with its own process ) - a plugin to test eclipse plugin the two last thing are done with eclipse's own stuff ( ant + headless eclipse). Stéphane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
I don't completely get the use the maven-eclipse-plugin to build eclipse plugins in maven. that raises a few questions. 1. you cannot develop the plugin in any other IDE, only in eclipse itself? 2. why even bother having it as maven project? do I miss something obvious? Milos On 8/4/06, Stéphane Bouchet [EMAIL PROTECTED] wrote: Barrie Treloar a écrit : On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. Hi, The current maven-eclipse-plugin is definitively the more accurate plugin to begin with. The current SNAPSHOT could generate the MANIFEST.MF file needed by any eclipse plugin, but it would not generate plugin.xml. there is some work in progress by somebody here in the list to make an archetype for eclipse plugin. So for compiling eclipse plugin, the work is almost done ( for me, it is working ) . What is missing today is : - packaging eclipse plugin ( could be done with assembly ) - support for RCP packaging ( currently you cannot build eclipse RCP app like eclipse does with its own process ) - a plugin to test eclipse plugin the two last thing are done with eclipse's own stuff ( ant + headless eclipse). Stéphane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
1. You can always develop with IDE other than Eclipse, notepad for example ! But for plugins, Eclipse provide some very useful editors and tools. With maven-eclipse-plugin, you can mix maven's concept of dependency managment and eclipse tools without effort. You could create an eclipse plugin without eclipse using maven assembly. 2. the main interrest to have it as maven project is continious integration and nightly builds. the eclipse'w way is complex and you can just build plugins, and tests them. you cannot generate site like maven does. Stéphane. Milos Kleint a écrit : I don't completely get the use the maven-eclipse-plugin to build eclipse plugins in maven. that raises a few questions. 1. you cannot develop the plugin in any other IDE, only in eclipse itself? 2. why even bother having it as maven project? do I miss something obvious? Milos On 8/4/06, Stéphane Bouchet [EMAIL PROTECTED] wrote: Barrie Treloar a écrit : On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. Hi, The current maven-eclipse-plugin is definitively the more accurate plugin to begin with. The current SNAPSHOT could generate the MANIFEST.MF file needed by any eclipse plugin, but it would not generate plugin.xml. there is some work in progress by somebody here in the list to make an archetype for eclipse plugin. So for compiling eclipse plugin, the work is almost done ( for me, it is working ) . What is missing today is : - packaging eclipse plugin ( could be done with assembly ) - support for RCP packaging ( currently you cannot build eclipse RCP app like eclipse does with its own process ) - a plugin to test eclipse plugin the two last thing are done with eclipse's own stuff ( ant + headless eclipse). Stéphane. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
Hi! I am about to start with my first Eclipse RCP/Plugin and I would like to be able to use Maven as well. Do you have an idea of when (full) support for PDE and RCP applications will be implemented and if so, would you like to share it? :) Regards, Jimisola -- View this message in context: http://www.nabble.com/Eclipse-Plugins-tf1958111.html#a5642162 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? As Fabrizio has indicated, PDE support is limited at best. Here are some other links I have found. http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) http://cwiki.apache.org/confluence/display/FELIX/OSGi+plugin+for+maven+2 An OSGi plugin which is not quite the same but probably close enough. http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html Some stuff in Geronimo for building their Eclipse plugin. http://vyzivus.host.sk/maven2-build-plugin-howto.html http://euromath2.sourceforge.net/eplugin/team-list.html http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00075.html http://mavenosgiplugin.berlios.de/ - A Maven 1.0 plugin http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/ Looks like a Maven 1.0 plugin http://jira.codehaus.org/browse/MECLIPSE-92 And maybe support for basic stuff in the eclipse plugin. I've seen a number of requests for this functionality fly past on the list. If effort is going to be spent addding these features then it would be good to pool the effort. The maven eclipse plugin feels like the correct spot. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
http://m2eclipse.codehaus.org/ The M2 Eclipse Plugin might have some stuff in it of use. I've yet to check. (The website is out of date and the source repository is not where the link indicates) SVN is here http://svn.codehaus.org/m2eclipse/trunk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
Not too much has happend with m2eclipse lately (last version 0.0.9 was released quite while ago). I don't know if is due to m2eclipse awaiting bug fixes/enhancements in the Maven Embedder (the Embedder seem to be a huge blocker) and/or if Eugene has too much to do. Either way, with all the open issues the project could definetly need some help. Sadly, I am not familiar with RCP nor plugin development (yet) so I wouldn't be much of a help. I've actually been meaning to help Eugene Kuleshov out with some documentation, but I got stuck with Jochen and the coming version of XML-RPC. I've noticed that links etc are incorrect as well. Regards, Jimisola -- View this message in context: http://www.nabble.com/Eclipse-Plugins-tf1958111.html#a5642896 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugins
On 7/18/06, Scott Goldstein [EMAIL PROTECTED] wrote: On the Maven 2 website, there's information about a Maven plugin which will build an eclipse project from a pom. My question is how this might work for an Eclipse project that is building an Eclipse RCP application. At the moment the maven eclipse plugins only creates an eclipse configuration for jar or j2ee (war, ejb, ear...) projects. Support for plugin projects is coming, and a few related features have just been committed (at this moment this is anyway limited to setting appropriate builders/natures and syncronizing the runtime classpath in the OSGI manifest). I am definitively interested in adding more support for pde and RCP applications. I will try to add new features for this to the maven eclipse plugin soon, if you have any specific requirement or proposal please submit a JIRA issue so that I can track and evaluate it. JIRA is at http://jira.codehaus.org/browse/MECLIPSE , related issues are organized under the PDE support component fabrizio I think this comes in two steps: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? I searched the archives for this list and saw a few posts about someone starting to work on this effort, but nothing since. Does anyone know if this is currently possible? Does anyone know if work is currently being done in this area? Thanks. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse Plugins
On the Maven 2 website, there's information about a Maven plugin which will build an eclipse project from a pom. My question is how this might work for an Eclipse project that is building an Eclipse RCP application. I think this comes in two steps: 1. How do you write a pom to build and release an Eclipse RCP application, including using an Eclipse Product Configuration to build the final package? 2. How do you then create the Eclipse project from the pom? I searched the archives for this list and saw a few posts about someone starting to work on this effort, but nothing since. Does anyone know if this is currently possible? Does anyone know if work is currently being done in this area? Thanks. Scott
Maven 2 and JUnit-Tests for Eclipse Plugins
Has anybody set up Maven 2 builds for Eclipse (PDE) plugin projects and has managed to integrate JUnit in-container tests for Eclipse-Plugins into the Maven build lifecycle? I would be very much interested in some best practices. Thank you! Arne -- View this message in context: http://www.nabble.com/Maven-2-and-JUnit-Tests-for-Eclipse-Plugins-tf1942500.html#a5324188 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Conflict using JBoss Eclipse plugins and Maven 2 plugin
Hello, I'm using Eclipse 3.1.2 and have been using the Maven 2 plugin. I installed the JBoss IDE plugin, specifically in the interest of using the jBPM plugin feature, and it appears to conflict with the Maven 2 plugin -- that's my best guess, as my Maven 2 functionality seems not to work or be available upon installing the JBoss plugins. I'm in a weird situation of needing to use the jBPM plugin on projects that are managed by Maven 2, and are dependent on other projects using Maven 2, which creates a real problem with dependency management. Has anyone else had this problem, and if so, have you found a way around it? Thanks, Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Developing eclipse plugins using maven
Hi, Any tips in developing eclipse plugins using maven? Tnx []s -- Nobody knows who i really am I never felt this empty before And if I never need someone to come along Who's gonna comfort me and keep me strong? -- Marcell Manfrin Barbacena [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] ICQ UIN: 63671762 Skype: callto://marcell84bruk +55 (83) 8808-8555 (Oi) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Developing eclipse plugins using maven
Hello, Create a new packaging as it was made for developing netbeans modules using maven. For more information, just check the netbeans plugin at mevenide.codehaus.org (in the source repository, you can find a mojos subdirectory where that plugin is located) Hope this helps. Raphaëk 2006/5/16, Marcell Manfrin Barbacena [EMAIL PROTECTED]: Hi, Any tips in developing eclipse plugins using maven? Tnx []s -- Nobody knows who i really am I never felt this empty before And if I never need someone to come along Who's gonna comfort me and keep me strong? -- Marcell Manfrin Barbacena [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] ICQ UIN: 63671762 Skype: callto://marcell84bruk +55 (83) 8808-8555 (Oi) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Developing eclipse plugins using maven
Hi, There was recently a post about a howto in development. Have a look at http://www.nabble.com/Eclipse-Plugin-Development-with-Maven-t942461.html#a4267979 -Tim Marcell Manfrin Barbacena schrieb: Hi, Any tips in developing eclipse plugins using maven? Tnx []s - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Need help with Building eclipse plugins
Hi Everyone, I need to build eclipse plugins, are there any existing plugins for it which simplies this task. Usually eclipse plugins has dependencies on many jars packaged in the eclipse plugins, so do I need to deploy these jars in my local/remote repository ? Is there simpler way to define the dependencies. -- -Gautham Pamu
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Well, I've finished a hacked-up set of maven projects and plugins that
build an update site. The reason I call it hacked-up is that it does
not use the repository for anything but the final update site JAR file
and the original plugin JARs - it uses an updateSite directory under
the HOME directory for the intermediate JARs.
There are several pieces to this:
1. A maven plugin that copies all plugin POM dependencies to a lib
directory under target.
2. A maven plugin that copies plugin.xml to the target directory, then
replaces the dependencies in it with the POM transitive dependencies,
and which updates the version qualifier with the build number (which we
have configured in AntHill to be in a property passed to maven) or the
timestamp if that is not present.
3. An ant task that copies the plugin.xml file to
target/work/plugins/${plugin.id}_${plugin.version}, the dependency JARs
into target/work/plugins/${plugin.id}_${plugin.version}/lib, and the
plugin JAR to target/work/plugins/${plugin.id}_${plugin.version} (and
removes the version number); then builds a JAR with all these contents
that is named ${plugin.id}_${plugin.version}.jar, where plugin.id and
plugin.version come from the plugin.xml file, and finally copies that
JAR to $HOME/updateSite/plugins.
4. A maven plugin that copies feature.xml to the target directory,
updates the version number of the feature as above, and updates the
plugin version numbers and JAR file names to match what it finds in the
$HOME/updateSite/plugins.
5. An ant task that copies the feature.xml to
target/work/features/${feature.id}_${feature.version}, builds a JAR from
that, and puts the jar in $HOME/updateSite/features. Note that
feature.id and feature.version come from the feature.xml file.
6. A maven plugin that copies site.xml to the target directory and
updates the feature version and name from the feature in
$HOME/updateSite/features.
7. An ant task that copies the site.xml file and the contents of
$HOME/updateSite to target/work/site, then creates a JAR with the name
${artifactId}-{version}, which is put into the repository.
The obvious limitation is that this can only build an update site with
one feature. Also, I don't like how much ant stuff there is - I'm sure
that many of these things can be done in maven directly, but I just ran
out of time.
When I can figure out an appropriate way to release these plugins, I'll
do it, but I will not likely have much more time to enhance it. If this
description inspires someone to work on this themselves, be my guest -
if you want, I can send you the code for these plugins after I make sure
that it all has the appropriate copyrights.
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Jim Babka
Sent: Wednesday, January 11, 2006 10:59 AM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update
sites
So, the questions then are, (a) where and how do I specify the
classifier, and (b) how do I write a custom plugin that creates a
second artifact? Regarding the second, the source code for the Javadoc
plugin was not terribly helpful because it uses a MavenProjectHelper
class for which I could find no documentation (so I don't know what the
parameters mean).
In any case, because I have to get something done quickly, I am
abandoning the effort of putting a second JAR in the repository. I'm
going to hack around this and use a temporary directory for all the
meta-JARs that I need, and then I'll have a feature build ANT goal
that pulls from that directory before it starts packaging things up.
This is certainly not even close to correct - it will only work because
we only need to build one feature - but I'm just stymied at every turn
by the lack of documentation right now. I know that the documentation
situation will improve, but I've got to get something working by the end
of the week. Hopefully, I'll have a chance to revisit this later after
more documentation is in place.
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 5:06 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update
sites
Hi Jim,
Sorry I hadn't answered your other Q's yet, but this is what I meant.
There is an assembly:attached goal in the next release of the assembly
plugin that will enable you to do what javadoc and sources do. In the
mean time, you need to use assembly:assembly install to generate and
install both, or use a custom plugin that just creates the one.
The name can be changed with finalName configuration to the assembly
plugin. Note it only impacts the target
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
We actually wrote a plugin to do the copy of all dependencies to the lib directory. It's pretty simple - it just: - gets the list of artifacts, - gets the list of files already in lib, - traverses the first list, and for each uses the copyFileToDirectory method of the org.codehaus.plexus.utils.FileUtils class to copy it to lib. - Compares the two lists, and for every file that is in lib but not in the dependencies, it deletes the file. This way we can include it as part of the process-resources phase, and thus it's part of every build. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Treloar, Barrie (SAPOL) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 4:07 PM To: 'Maven Users List' Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update sites In any case, because I have to get something done quickly, I am abandoning the effort of putting a second JAR in the repository. I'm going to hack around this and use a temporary directory for all the meta-JARs that I need, and then I'll have a feature build ANT goal that pulls from that directory before it starts packaging things up. This is certainly not even close to correct - it will only work because we only need to build one feature - but I'm just stymied at every turn by the lack of documentation right now. I know that the documentation situation will improve, but I've got to get something working by the end of the week. Hopefully, I'll have a chance to revisit this later after more documentation is in place. I'm doing something like this for my plugin: The non-eclipse dependencies are captured in the Maven pom.xml dependencies. To create a local copy of these libraries for inclusion in the project use the following command: +--- mvn dependency:copy-dependencies -DstripVersion=true -DoutputDirectory=lib +--- The libraries themselves should not be checked into CVS. Then in the MANIFEST.MF/plugin.xml editor I ensure that the Classpath entries on the Runtime tab include the libs just created. The .classpath and .project files are checked into CVS. So when the plugin is checked out it won't build since the libs are not there. After running the dependency:copy-dependencies command I can build the plugin. Of course I have not yet got to the point of automating all this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
I have tried the ANT-tasks that eclipse provides, and at least for
plugin-packaging they seem over-complicated. I have had success (just
recently based on the mini-guide for assembly) in packaging the
update-jar for an eclipse plugin as follows:
Pom.xml (note I'm specifying a MANIFEST.MF file)
===
!--
previously downloaded the eclipse jars into
local repo and put in for compile-time dependency
--
build
sourceDirectorysrc/sourceDirectory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestFilesrc/main/resources/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorsrc/main/assembly/dep.xml/descriptor
/configuration
/plugin
/plugins
/build
===end pom.xml===
Src/main/assembly/dep.xml
assembly
!-- TODO: a jarjar format would be better --
iddep/id
formats
formatjar/format
/formats
fileSets
fileSet
outputDirectory//outputDirectory
/fileSet
!-- I think this is everyting based on eclipse workspace --
fileset dir=${basedir}
includes=plugin.xml,META-INF/,null,icons/,pom.xml,toc.xml,html//
/fileSets
dependencySets
dependencySet
outputDirectory//outputDirectory
unpacktrue/unpack
scoperuntime/scope
excludes
excludejunit:junit/exclude
/excludes
/dependencySet
/dependencySets
/assembly
===end dep.xml===
I'm also interested in the features/update sites possibility,
particuarly where I want to accomplish these tasks through autobuild
instead of manually through Eclipse. I imagine something related to the
:release maven plugin would come into play.
P.s. I have also recently learned that the update-jar name does NOT seem
to matter for Eclipse to load, so you can use the
{artifactId}-{version}.jar for the eclipse-plugin-jar and deploy to
repo. Again, only so-far, if there is something later that this may
impact please let me know!
-D
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Found a reference on the mevenide-user mailing list with some good info: http://www.nabble.com/-mevenide-user-Re%3A-Project-status-t481604.html#a 1310842 I'm still stuck on including runtime-scope dependencies into the packaged jar (under /lib). Maven-dependency-plugin seems to be the right approach, but 1. it doesn't differentiate scopes 2. isn't visible to the package-phase during that maven instance -- i.e., the second time you run package-phase will see where you put the jars. Just trying both JAR-package approach and assembly-style approach, one of them should work (one of the intents is to deploy to repo to support eclipse-pde-plugin-dependencies to other eclipse-pde-plugins, so focusing on JAR-package approach). -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
So, the questions then are, (a) where and how do I specify the
classifier, and (b) how do I write a custom plugin that creates a
second artifact? Regarding the second, the source code for the Javadoc
plugin was not terribly helpful because it uses a MavenProjectHelper
class for which I could find no documentation (so I don't know what the
parameters mean).
In any case, because I have to get something done quickly, I am
abandoning the effort of putting a second JAR in the repository. I'm
going to hack around this and use a temporary directory for all the
meta-JARs that I need, and then I'll have a feature build ANT goal
that pulls from that directory before it starts packaging things up.
This is certainly not even close to correct - it will only work because
we only need to build one feature - but I'm just stymied at every turn
by the lack of documentation right now. I know that the documentation
situation will improve, but I've got to get something working by the end
of the week. Hopefully, I'll have a chance to revisit this later after
more documentation is in place.
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 5:06 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update
sites
Hi Jim,
Sorry I hadn't answered your other Q's yet, but this is what I meant.
There is an assembly:attached goal in the next release of the assembly
plugin that will enable you to do what javadoc and sources do. In the
mean time, you need to use assembly:assembly install to generate and
install both, or use a custom plugin that just creates the one.
The name can be changed with finalName configuration to the assembly
plugin. Note it only impacts the target/ generated file - it is still
installed in the repository with artifactId-version-classifier
as the name.
- Brett
On 1/11/06, Jim Babka [EMAIL PROTECTED] wrote:
So, I've been told separately that it is possible to have a project
generate multiple artifacts, because the sources and javadoc plugins
do
just that. The questions are (a) are they full artifacts that can be
depended upon by other projects, and (b) can someone point me at the
source code that does this? I see that there's an addAttachedArtifact
method on MavenProject - is that what I need to use?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Jim Babka
Sent: Monday, January 09, 2006 7:27 PM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features, and
update
sites
First of all, how do you tell the assembly plugin what name to give to
the JAR it creates? Second, how do you get that jar to be an artifact
that gets put into the repository?
I may be misunderstanding something here, so please bear with me. I
believe that the file names of any artifacts generated by a project
are
fixed to be {artifactId}-{version}, where artifactId and version
come
from the POM file - is this correct? If so, then the only thing you
can
do to create multiple artifacts is to have different file extensions
for
each - is that correct? If these are both correct, then you see my
dilemma - I need the same project (i.e. the same pom.xml) to generate
two artifacts: a JAR, and a JAR of JARs.
I would love to be mistaken here - am I?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 7:05 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and
update
sites
Those docs definitely look half-done. The latter parts are just pastes
of the defaults. Documentation is high on the list for the next
assembly plugin release.
The assembly produced would have to have a different name to the
original JAR which you are packaging up. The version would be the
same, the name would just be different.
However, you can create another plugin that does the custom behaviour
and only produces one jar. I think that's what the felix osgi plugin
does.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Thanks for getting back to me.
I looked at assemblies, but quickly got stuck there as well. What
does
the assembly plugin do about a version number? Does it use the
version
number for the project? Since that is the same as the version
number
for the JAR, I would have do come up with a different name, right?
But
I can't do that because the name
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Maven is building the JAR that contains the compiled plugin code (which goes into the repository), and a zip file that contains the 3 things discussed below (which just sits in the target directory). The latter can be directly unzipped into an Eclipse plugins directory, but is not suitable for an update site. I'm not comfortable sharing what we've done at this point yet because it is very specific to our environment, and until I can actually build an update site, I can't be sure that it is correct. Once I can do that, I'll look into releasing something to the world. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Treloar, Barrie (SAPOL) [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 10, 2006 7:34 PM To: 'Maven Users List' Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update sites Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). Are you saying that you have gotten Maven to compile the eclipse plugin as well. Or are you still using Ant Tasks? In the last few weeks I've seen a few requests for Maven/Eclipse plugin or RCP support. Any chance you are able to share the work you have started? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Looks interesting, but I think that this is causing the main plugin JAR
to be replaced in the repository by the assembly. I can't do that - I
must have the main plugin JAR in the repository because other projects
have a compile-time dependency upon the code there.
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Darren Hartford [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 11, 2006 9:05 AM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update
sites
I have tried the ANT-tasks that eclipse provides, and at least for
plugin-packaging they seem over-complicated. I have had success (just
recently based on the mini-guide for assembly) in packaging the
update-jar for an eclipse plugin as follows:
Pom.xml (note I'm specifying a MANIFEST.MF file)
===
!--
previously downloaded the eclipse jars into
local repo and put in for compile-time dependency
--
build
sourceDirectorysrc/sourceDirectory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestFilesrc/main/resources/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorsrc/main/assembly/dep.xml/descriptor
/configuration
/plugin
/plugins
/build
===end pom.xml===
Src/main/assembly/dep.xml
assembly
!-- TODO: a jarjar format would be better --
iddep/id
formats
formatjar/format
/formats
fileSets
fileSet
outputDirectory//outputDirectory
/fileSet
!-- I think this is everyting based on eclipse workspace --
fileset dir=${basedir}
includes=plugin.xml,META-INF/,null,icons/,pom.xml,toc.xml,html//
/fileSets
dependencySets
dependencySet
outputDirectory//outputDirectory
unpacktrue/unpack
scoperuntime/scope
excludes
excludejunit:junit/exclude
/excludes
/dependencySet
/dependencySets
/assembly
===end dep.xml===
I'm also interested in the features/update sites possibility,
particuarly where I want to accomplish these tasks through autobuild
instead of manually through Eclipse. I imagine something related to the
:release maven plugin would come into play.
P.s. I have also recently learned that the update-jar name does NOT seem
to matter for Eclipse to load, so you can use the
{artifactId}-{version}.jar for the eclipse-plugin-jar and deploy to
repo. Again, only so-far, if there is something later that this may
impact please let me know!
-D
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update si tes
In any case, because I have to get something done quickly, I am abandoning the effort of putting a second JAR in the repository. I'm going to hack around this and use a temporary directory for all the meta-JARs that I need, and then I'll have a feature build ANT goal that pulls from that directory before it starts packaging things up. This is certainly not even close to correct - it will only work because we only need to build one feature - but I'm just stymied at every turn by the lack of documentation right now. I know that the documentation situation will improve, but I've got to get something working by the end of the week. Hopefully, I'll have a chance to revisit this later after more documentation is in place. I'm doing something like this for my plugin: The non-eclipse dependencies are captured in the Maven pom.xml dependencies. To create a local copy of these libraries for inclusion in the project use the following command: +--- mvn dependency:copy-dependencies -DstripVersion=true -DoutputDirectory=lib +--- The libraries themselves should not be checked into CVS. Then in the MANIFEST.MF/plugin.xml editor I ensure that the Classpath entries on the Runtime tab include the libs just created. The .classpath and .project files are checked into CVS. So when the plugin is checked out it won't build since the libs are not there. After running the dependency:copy-dependencies command I can build the plugin. Of course I have not yet got to the point of automating all this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Hi Jim,
Actually putting the eclipse-pde-plugin-jar in my repo is also one of my
goals. The recommendation I offered using the assembly-mode was based
on a 'dirty' environment and once I figured out what was going on, this
will not work as expected.
What I have gone forward with is using a combination of marking
resources in the build-section of the pom.xml, utilizing
maven-dependency-plugin to download libs, an ant-call to do a 'pde-prep'
ANT target, and the maven-jar-plugin configuration to include the
MANIFEST. So far, this combination seems to be o.k. but I feel it is
shaky.
This approach I'm actually using the 'mvn deploy' task to put the
pde-plugin into the repo (using the ${artifactId}-${version}.jar
approach, note the dash instead of underscore). I have not solved the
two-places-to-keep-your-version-numbers-in-sync problem however
(plugin.xml and pom.xml).
-D
-Original Message-
From: Jim Babka [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 11, 2006 12:34 PM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features,
and update sites
Looks interesting, but I think that this is causing the main
plugin JAR to be replaced in the repository by the assembly.
I can't do that - I must have the main plugin JAR in the
repository because other projects have a compile-time
dependency upon the code there.
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Darren Hartford [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 11, 2006 9:05 AM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features,
and update sites
I have tried the ANT-tasks that eclipse provides, and at
least for plugin-packaging they seem over-complicated. I
have had success (just recently based on the mini-guide for
assembly) in packaging the update-jar for an eclipse plugin
as follows:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
So, I've been told separately that it is possible to have a project
generate multiple artifacts, because the sources and javadoc plugins do
just that. The questions are (a) are they full artifacts that can be
depended upon by other projects, and (b) can someone point me at the
source code that does this? I see that there's an addAttachedArtifact
method on MavenProject - is that what I need to use?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Jim Babka
Sent: Monday, January 09, 2006 7:27 PM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update
sites
First of all, how do you tell the assembly plugin what name to give to
the JAR it creates? Second, how do you get that jar to be an artifact
that gets put into the repository?
I may be misunderstanding something here, so please bear with me. I
believe that the file names of any artifacts generated by a project are
fixed to be {artifactId}-{version}, where artifactId and version come
from the POM file - is this correct? If so, then the only thing you can
do to create multiple artifacts is to have different file extensions for
each - is that correct? If these are both correct, then you see my
dilemma - I need the same project (i.e. the same pom.xml) to generate
two artifacts: a JAR, and a JAR of JARs.
I would love to be mistaken here - am I?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 7:05 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update
sites
Those docs definitely look half-done. The latter parts are just pastes
of the defaults. Documentation is high on the list for the next
assembly plugin release.
The assembly produced would have to have a different name to the
original JAR which you are packaging up. The version would be the
same, the name would just be different.
However, you can create another plugin that does the custom behaviour
and only produces one jar. I think that's what the felix osgi plugin
does.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Thanks for getting back to me.
I looked at assemblies, but quickly got stuck there as well. What
does
the assembly plugin do about a version number? Does it use the
version
number for the project? Since that is the same as the version number
for the JAR, I would have do come up with a different name, right?
But
I can't do that because the name is fixed by the project I'm in,
correct? So how can it possibly generate a second artifact with the
same name from within the same project?
Is there any better documentation on the assembly plugin than
http://maven.apache.org/guides/mini/guide-assemblies.html? The
examples
there (which is pretty much all there is right now) show formats and
outputDirectory tags, but I can't see how the former would have
anything to do with the file generated (since there are multiple), and
the latter makes it appear as though assemblies do not generate
artifacts (since there's only one place for an artifact to go - the
repository).
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 6:11 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and
update
sites
Hi Jim,
Sorry for not replying sooner. I've not done this, and I'm not sur eif
anyone else has, but we have certainly discussed it in the past.
Members of the pde-build-dev team were here at one point. We'd
appreciate any feedback you have on it.
Some pointers:
- the assembly plugin can create a jar that includes other jars, and
gets deployed alongside the original
- check out the Felix OSGi M2 plugin:
http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0
Hope these help for starters.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Eclipse does provide some ant tasks, but they require that Eclipse
is
running. They have a way to run in headless mode, but you need to
use
a
script that invokes Eclipse, and then tell Eclipse to run its
antRunner
process. As far as I can tell, there is no way to have ant run
these
Eclipse tasks without running ant from Eclipse (which we clearly
can't
do if we need to run ant from maven).
Since I got no other replies, I assume that somehow, no one has done
this before, so I need to dig into it. I have gotten to the
following
Re: [m2] Maven2 building Eclipse plugins, features, and update sites
Hi Jim,
Sorry I hadn't answered your other Q's yet, but this is what I meant.
There is an assembly:attached goal in the next release of the assembly
plugin that will enable you to do what javadoc and sources do. In the
mean time, you need to use assembly:assembly install to generate and
install both, or use a custom plugin that just creates the one.
The name can be changed with finalName configuration to the assembly
plugin. Note it only impacts the target/ generated file - it is still
installed in the repository with artifactId-version-classifier
as the name.
- Brett
On 1/11/06, Jim Babka [EMAIL PROTECTED] wrote:
So, I've been told separately that it is possible to have a project
generate multiple artifacts, because the sources and javadoc plugins do
just that. The questions are (a) are they full artifacts that can be
depended upon by other projects, and (b) can someone point me at the
source code that does this? I see that there's an addAttachedArtifact
method on MavenProject - is that what I need to use?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Jim Babka
Sent: Monday, January 09, 2006 7:27 PM
To: Maven Users List
Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update
sites
First of all, how do you tell the assembly plugin what name to give to
the JAR it creates? Second, how do you get that jar to be an artifact
that gets put into the repository?
I may be misunderstanding something here, so please bear with me. I
believe that the file names of any artifacts generated by a project are
fixed to be {artifactId}-{version}, where artifactId and version come
from the POM file - is this correct? If so, then the only thing you can
do to create multiple artifacts is to have different file extensions for
each - is that correct? If these are both correct, then you see my
dilemma - I need the same project (i.e. the same pom.xml) to generate
two artifacts: a JAR, and a JAR of JARs.
I would love to be mistaken here - am I?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 7:05 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update
sites
Those docs definitely look half-done. The latter parts are just pastes
of the defaults. Documentation is high on the list for the next
assembly plugin release.
The assembly produced would have to have a different name to the
original JAR which you are packaging up. The version would be the
same, the name would just be different.
However, you can create another plugin that does the custom behaviour
and only produces one jar. I think that's what the felix osgi plugin
does.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Thanks for getting back to me.
I looked at assemblies, but quickly got stuck there as well. What
does
the assembly plugin do about a version number? Does it use the
version
number for the project? Since that is the same as the version number
for the JAR, I would have do come up with a different name, right?
But
I can't do that because the name is fixed by the project I'm in,
correct? So how can it possibly generate a second artifact with the
same name from within the same project?
Is there any better documentation on the assembly plugin than
http://maven.apache.org/guides/mini/guide-assemblies.html? The
examples
there (which is pretty much all there is right now) show formats and
outputDirectory tags, but I can't see how the former would have
anything to do with the file generated (since there are multiple), and
the latter makes it appear as though assemblies do not generate
artifacts (since there's only one place for an artifact to go - the
repository).
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 6:11 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and
update
sites
Hi Jim,
Sorry for not replying sooner. I've not done this, and I'm not sur eif
anyone else has, but we have certainly discussed it in the past.
Members of the pde-build-dev team were here at one point. We'd
appreciate any feedback you have on it.
Some pointers:
- the assembly plugin can create a jar that includes other jars, and
gets deployed alongside the original
- check out the Felix
RE: [m2] Maven2 building Eclipse plugins, features, and update si tes
Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). Are you saying that you have gotten Maven to compile the eclipse plugin as well. Or are you still using Ant Tasks? In the last few weeks I've seen a few requests for Maven/Eclipse plugin or RCP support. Any chance you are able to share the work you have started? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). The question is, how do I add another artifact to the build when there is already an artifact that I must preserve, and when both artifacts are needed by different maven dependencies? Also, how can I say that I depend upon only one of those artifacts? Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 2:37 AM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites does eclipse provide ant tasks to do the plugin building? I've done exactly the same for netbeans modules, a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant tasks. At least the lifecycle definition might be of interest you, http://cvs.mevenide.codehaus.org/mojos/maven-nbm-plugin/ Regards Milos Kleint On 1/7/06, Jim Babka [EMAIL PROTECTED] wrote: I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature or for that matter deploying to an update site. Right now we have some hackery to at least get to the ZIP file, but unless there is something already existing, I see a bunch of long nights ahead while I write my own stuff. The requirement is that we can have an update site automatically built/updated by our build system. So, is there anything that I can use here? Even if there is an open source project that goes only part of the way, it would possibly give me a head start. Thanks in advance for any help that anyone can give me. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Maven2 building Eclipse plugins, features, and update sites
Hi Jim, Sorry for not replying sooner. I've not done this, and I'm not sur eif anyone else has, but we have certainly discussed it in the past. Members of the pde-build-dev team were here at one point. We'd appreciate any feedback you have on it. Some pointers: - the assembly plugin can create a jar that includes other jars, and gets deployed alongside the original - check out the Felix OSGi M2 plugin: http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0 Hope these help for starters. - Brett On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote: Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). The question is, how do I add another artifact to the build when there is already an artifact that I must preserve, and when both artifacts are needed by different maven dependencies? Also, how can I say that I depend upon only one of those artifacts? Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 2:37 AM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites does eclipse provide ant tasks to do the plugin building? I've done exactly the same for netbeans modules, a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant tasks. At least the lifecycle definition might be of interest you, http://cvs.mevenide.codehaus.org/mojos/maven-nbm-plugin/ Regards Milos Kleint On 1/7/06, Jim Babka [EMAIL PROTECTED] wrote: I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature or for that matter deploying to an update site. Right now we have some hackery to at least get to the ZIP file, but unless there is something already existing, I see a bunch of long nights ahead while I write my own stuff. The requirement is that we can have an update site automatically built/updated by our build system. So, is there anything that I can use here? Even if there is an open source project that goes only part of the way, it would possibly give me a head start. Thanks in advance for any help that anyone can give me. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
Thanks for getting back to me. I looked at assemblies, but quickly got stuck there as well. What does the assembly plugin do about a version number? Does it use the version number for the project? Since that is the same as the version number for the JAR, I would have do come up with a different name, right? But I can't do that because the name is fixed by the project I'm in, correct? So how can it possibly generate a second artifact with the same name from within the same project? Is there any better documentation on the assembly plugin than http://maven.apache.org/guides/mini/guide-assemblies.html? The examples there (which is pretty much all there is right now) show formats and outputDirectory tags, but I can't see how the former would have anything to do with the file generated (since there are multiple), and the latter makes it appear as though assemblies do not generate artifacts (since there's only one place for an artifact to go - the repository). Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 6:11 PM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites Hi Jim, Sorry for not replying sooner. I've not done this, and I'm not sur eif anyone else has, but we have certainly discussed it in the past. Members of the pde-build-dev team were here at one point. We'd appreciate any feedback you have on it. Some pointers: - the assembly plugin can create a jar that includes other jars, and gets deployed alongside the original - check out the Felix OSGi M2 plugin: http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0 Hope these help for starters. - Brett On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote: Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). The question is, how do I add another artifact to the build when there is already an artifact that I must preserve, and when both artifacts are needed by different maven dependencies? Also, how can I say that I depend upon only one of those artifacts? Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 2:37 AM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites does eclipse provide ant tasks to do the plugin building? I've done exactly the same for netbeans modules, a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant tasks. At least the lifecycle definition might be of interest you, http://cvs.mevenide.codehaus.org/mojos/maven-nbm-plugin/ Regards Milos Kleint On 1/7/06, Jim Babka [EMAIL PROTECTED] wrote: I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature
Re: [m2] Maven2 building Eclipse plugins, features, and update sites
Those docs definitely look half-done. The latter parts are just pastes of the defaults. Documentation is high on the list for the next assembly plugin release. The assembly produced would have to have a different name to the original JAR which you are packaging up. The version would be the same, the name would just be different. However, you can create another plugin that does the custom behaviour and only produces one jar. I think that's what the felix osgi plugin does. - Brett On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote: Thanks for getting back to me. I looked at assemblies, but quickly got stuck there as well. What does the assembly plugin do about a version number? Does it use the version number for the project? Since that is the same as the version number for the JAR, I would have do come up with a different name, right? But I can't do that because the name is fixed by the project I'm in, correct? So how can it possibly generate a second artifact with the same name from within the same project? Is there any better documentation on the assembly plugin than http://maven.apache.org/guides/mini/guide-assemblies.html? The examples there (which is pretty much all there is right now) show formats and outputDirectory tags, but I can't see how the former would have anything to do with the file generated (since there are multiple), and the latter makes it appear as though assemblies do not generate artifacts (since there's only one place for an artifact to go - the repository). Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 6:11 PM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites Hi Jim, Sorry for not replying sooner. I've not done this, and I'm not sur eif anyone else has, but we have certainly discussed it in the past. Members of the pde-build-dev team were here at one point. We'd appreciate any feedback you have on it. Some pointers: - the assembly plugin can create a jar that includes other jars, and gets deployed alongside the original - check out the Felix OSGi M2 plugin: http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0 Hope these help for starters. - Brett On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote: Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Since I got no other replies, I assume that somehow, no one has done this before, so I need to dig into it. I have gotten to the following stopping point, and I need help. An Eclipse plugin consists of a JAR that contains 3 classes of items: 1. Another jar with the actual code. 2. The plugin.xml file 3. 0 or more JAR dependencies for the plugin. Maven builds item 1 without a problem, and we've hacked up a Mojo to update item 2. Then we have a separate ant goal that runs from Maven to copy all 3 to the target directory, then zip it all up. The problem is that we need to add a second artifact to the build once this ant step is complete, because we need both the original jar (for other project build dependencies) and the new jar (for the later Eclipse feature build that I need to write). The question is, how do I add another artifact to the build when there is already an artifact that I must preserve, and when both artifacts are needed by different maven dependencies? Also, how can I say that I depend upon only one of those artifacts? Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Saturday, January 07, 2006 2:37 AM To: Maven Users List Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update sites does eclipse provide ant tasks to do the plugin building? I've done exactly the same for netbeans modules, a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant tasks. At least the lifecycle definition might be of interest you, http://cvs.mevenide.codehaus.org/mojos/maven-nbm-plugin/ Regards Milos Kleint On 1/7/06, Jim Babka [EMAIL PROTECTED] wrote: I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin
RE: [m2] Maven2 building Eclipse plugins, features, and update sites
First of all, how do you tell the assembly plugin what name to give to
the JAR it creates? Second, how do you get that jar to be an artifact
that gets put into the repository?
I may be misunderstanding something here, so please bear with me. I
believe that the file names of any artifacts generated by a project are
fixed to be {artifactId}-{version}, where artifactId and version come
from the POM file - is this correct? If so, then the only thing you can
do to create multiple artifacts is to have different file extensions for
each - is that correct? If these are both correct, then you see my
dilemma - I need the same project (i.e. the same pom.xml) to generate
two artifacts: a JAR, and a JAR of JARs.
I would love to be mistaken here - am I?
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 7:05 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and update
sites
Those docs definitely look half-done. The latter parts are just pastes
of the defaults. Documentation is high on the list for the next
assembly plugin release.
The assembly produced would have to have a different name to the
original JAR which you are packaging up. The version would be the
same, the name would just be different.
However, you can create another plugin that does the custom behaviour
and only produces one jar. I think that's what the felix osgi plugin
does.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Thanks for getting back to me.
I looked at assemblies, but quickly got stuck there as well. What
does
the assembly plugin do about a version number? Does it use the
version
number for the project? Since that is the same as the version number
for the JAR, I would have do come up with a different name, right?
But
I can't do that because the name is fixed by the project I'm in,
correct? So how can it possibly generate a second artifact with the
same name from within the same project?
Is there any better documentation on the assembly plugin than
http://maven.apache.org/guides/mini/guide-assemblies.html? The
examples
there (which is pretty much all there is right now) show formats and
outputDirectory tags, but I can't see how the former would have
anything to do with the file generated (since there are multiple), and
the latter makes it appear as though assemblies do not generate
artifacts (since there's only one place for an artifact to go - the
repository).
Jim Babka
Senior Software Engineer
Main: (512) 334 3200
Direct: (512) 334 3237
Email: [EMAIL PROTECTED]
Webify Solutions
Enabling the On Demand Enterprise(tm)
www.webifysolutions.com
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 6:11 PM
To: Maven Users List
Subject: Re: [m2] Maven2 building Eclipse plugins, features, and
update
sites
Hi Jim,
Sorry for not replying sooner. I've not done this, and I'm not sur eif
anyone else has, but we have certainly discussed it in the past.
Members of the pde-build-dev team were here at one point. We'd
appreciate any feedback you have on it.
Some pointers:
- the assembly plugin can create a jar that includes other jars, and
gets deployed alongside the original
- check out the Felix OSGi M2 plugin:
http://docs.safehaus.org/display/OSGI/OSGi+Plugin+for+Maven+2.0
Hope these help for starters.
- Brett
On 1/10/06, Jim Babka [EMAIL PROTECTED] wrote:
Eclipse does provide some ant tasks, but they require that Eclipse
is
running. They have a way to run in headless mode, but you need to
use
a
script that invokes Eclipse, and then tell Eclipse to run its
antRunner
process. As far as I can tell, there is no way to have ant run
these
Eclipse tasks without running ant from Eclipse (which we clearly
can't
do if we need to run ant from maven).
Since I got no other replies, I assume that somehow, no one has done
this before, so I need to dig into it. I have gotten to the
following
stopping point, and I need help. An Eclipse plugin consists of a
JAR
that contains 3 classes of items:
1. Another jar with the actual code.
2. The plugin.xml file
3. 0 or more JAR dependencies for the plugin.
Maven builds item 1 without a problem, and we've hacked up a Mojo to
update item 2. Then we have a separate ant goal that runs from
Maven
to
copy all 3 to the target directory, then zip it all up. The problem
is
that we need to add a second artifact to the build once this ant
step
is
complete, because we need both the original jar (for other project
build
dependencies) and the new jar (for the later Eclipse feature build
that
I need to write).
The question is, how do I add another artifact to the build when
Re: [m2] Maven2 building Eclipse plugins, features, and update sites
Jim Babka wrote: Eclipse does provide some ant tasks, but they require that Eclipse is running. They have a way to run in headless mode, but you need to use a script that invokes Eclipse, and then tell Eclipse to run its antRunner process. As far as I can tell, there is no way to have ant run these Eclipse tasks without running ant from Eclipse (which we clearly can't do if we need to run ant from maven). Did you look inside the plugins, sometimes the ant files are laying around there so we might extract them from the package where they are, if they rely on some variables passed on by the eclipse enviroment perhaps a EclipseMock object could inject the variables instead of the runtime? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Maven2 building Eclipse plugins, features, and update sites
does eclipse provide ant tasks to do the plugin building? I've done exactly the same for netbeans modules, a bunch of mojos and a custom lifecycle, internally reusing the netbeans ant tasks. At least the lifecycle definition might be of interest you, http://cvs.mevenide.codehaus.org/mojos/maven-nbm-plugin/ Regards Milos Kleint On 1/7/06, Jim Babka [EMAIL PROTECTED] wrote: I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature or for that matter deploying to an update site. Right now we have some hackery to at least get to the ZIP file, but unless there is something already existing, I see a bunch of long nights ahead while I write my own stuff. The requirement is that we can have an update site automatically built/updated by our build system. So, is there anything that I can use here? Even if there is an open source project that goes only part of the way, it would possibly give me a head start. Thanks in advance for any help that anyone can give me. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Maven2 building Eclipse plugins, features, and update sites
I have been searching for this now for several days and have found nothing, so I thought I would ask here. Is there a maven2 plugin that supports building of Eclipse plugins, features, and update sites? Right now we have several Eclipse plugins that are built into ZIP files that can be unzipped into an Eclipse plugins directory. However, there are several problems with this: 1. There's no support for updating the plugin.xml with the version information of the plugin's jar. 2. There's no support for putting the maven pom.xml dependencies (direct or transitive) into the plugin.xml. 3. There's no support for building an Eclipse feature that includes those plugins. 4. There's no support for building an Eclipse update site from the feature or for that matter deploying to an update site. Right now we have some hackery to at least get to the ZIP file, but unless there is something already existing, I see a bunch of long nights ahead while I write my own stuff. The requirement is that we can have an update site automatically built/updated by our build system. So, is there anything that I can use here? Even if there is an open source project that goes only part of the way, it would possibly give me a head start. Thanks in advance for any help that anyone can give me. Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin for Eclipse plugins
Thanks Dan, I don't understand how is the plugin connected with Eclipse. When I develop and debug my plugin, Eclipse needs the plugin.xml and MANIFEST.MF. But your plugin doesn't seem to create them. How I should keep those two files to be same? Jan dan tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] There is some working going on at http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/ -Dan On 10/4/05, jan_bar [EMAIL PROTECTED] wrote: Hi, is there maven plugin that helps developing Eclipse plugins and RCP? For instance META-INF/MANIFEST.MF contains list of dependant libraries. But I cannot specify library that is in maven repository. Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin for Eclipse plugins
It is best that you should directly ask the author at felix project. But from what i know and dont know ;-), this osgi plugin will generate MANIFEST.MF, but not the plugin.xml. It can generate MANIFEST.MF because the pom.xml has the manifest data. The plugin.xml has data specific to eclipse and pom.xml does not have it. again I can be totally wrong. -Dan On 10/13/05, jan_bar [EMAIL PROTECTED] wrote: Thanks Dan, I don't understand how is the plugin connected with Eclipse. When I develop and debug my plugin, Eclipse needs the plugin.xml and MANIFEST.MF. But your plugin doesn't seem to create them. How I should keep those two files to be same? Jan dan tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] There is some working going on at http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/ -Dan On 10/4/05, jan_bar [EMAIL PROTECTED] wrote: Hi, is there maven plugin that helps developing Eclipse plugins and RCP? For instance META-INF/MANIFEST.MF contains list of dependant libraries. But I cannot specify library that is in maven repository. Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin for Eclipse plugins
Hi, is there maven plugin that helps developing Eclipse plugins and RCP? For instance META-INF/MANIFEST.MF contains list of dependant libraries. But I cannot specify library that is in maven repository. Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin for Eclipse plugins
There is some working going on at http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/ -Dan On 10/4/05, jan_bar [EMAIL PROTECTED] wrote: Hi, is there maven plugin that helps developing Eclipse plugins and RCP? For instance META-INF/MANIFEST.MF contains list of dependant libraries. But I cannot specify library that is in maven repository. Thanks, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Building eclipse plugins with maven, where can I find the eclipse jars?
Hi, I want to build my eclipse plugins with maven (maven1) Where can I find the eclipse jars to compile against? Or has everybody put them in an internal repository? I also got the maven-eclise-plugin-plugin but is it so that I have to maintain two lists of dependent jars; one in project.xml and one in plugin.xml? Or is that some trick which can generate one of these lists? Many thanks! /Lucas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven projects and eclipse plugins
Hi, I posted a question on this two days ago but might have asked something too specific. Pretty much I'm trying to find a solution to using maven with my eclipse projects that are plugin projects. My specific issue is figuring out how to modify the plugin build process so that my eclipse plugin will be built with a lib directory that contains all of my project dependencies defined in project.xml. I think the easiest way to do that would be to have the maven eclipse plugin copy all of the depedendent artifacts to a lib folder off my project root. Then I could tag that fold for cvs ignore and modify my plugin.xml to include all jars in that folder on the runtime class path. Any quick ideas would be greatly appreciated.
RE: maven projects and eclipse plugins
You can use the tag deploy:copy-deps to copy your project dependencies but I don't find a documentation about it on the new site :-( Here is the old one : http://maven.apache.org/reference/user-guide.html#Copying_Dependency_JARs My 2 cents Arnaud -Message d'origine- De : Duncan Krebs [mailto:[EMAIL PROTECTED] Envoyé : mardi 13 septembre 2005 17:24 À : Maven Users List Objet : maven projects and eclipse plugins Hi, I posted a question on this two days ago but might have asked something too specific. Pretty much I'm trying to find a solution to using maven with my eclipse projects that are plugin projects. My specific issue is figuring out how to modify the plugin build process so that my eclipse plugin will be built with a lib directory that contains all of my project dependencies defined in project.xml. I think the easiest way to do that would be to have the maven eclipse plugin copy all of the depedendent artifacts to a lib folder off my project root. Then I could tag that fold for cvs ignore and modify my plugin.xml to include all jars in that folder on the runtime class path. Any quick ideas would be greatly appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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
Problems with Maven Repository and Eclipse Plugins
Hi there I have a question regarding Maven and RCP Plugin development: I have different subprojects, that produce libraries (jars) that I need in an eclipse plugin. Because the development speed is high, I want to use our internal maven repository to access the jars. In simple java projects I add the jars to the classpath with a variable (MAVEN_REPO/log4j/jars/log4j-1.2.8.jar). But in the PDE, I have to add the jar as a library to the runtime tag in the plugin.xml file. runtime library name=lib/log4j-1.2.8.jar/ /runtime I can't add my library in the maven repository here. How could I do this? Do I have to copy my jars to the pluginproject everytime I do a release on the Jars? Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Eclipse plugins and maven
Gilles thanks! -Original Message- From: Gilles Dodinet [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005 12:33 PM To: Maven Users List Subject: Re: Eclipse plugins and maven the mep plugin needs to be rewritten. ive started the rewriting but seriously lacked of time the past months. however in the yet to come new version theres some code [*] that you may find useful to avoid to declare your eclipse dependencies twice. [*] http://cvs.mevenide.codehaus.org/mojos/pde-plugin/m1/plugin.jelly?rev=1.4vi ew=auto : adding pde:classpath as a preGoal of build:start should do the trick. -- gd Christopher L Merrill wrote: Duncan Krebs wrote: I want to use Maven to build a plugin but am wondering how to setup my project.xml. For example, do I need to manually add each plugin dependency inside project.xml or does plugin.xml preserve this information? Also, as I do with my other maven projects can I generate the .classpath and .project file using the maven:eclipse for plugin projects or do these files need to be stored in CVS? Thanks - Duncan Have you looked at the MEP plugin? (Maven-Eclipse-Plugin plugin) It builds Eclipse plugins. http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/index.html -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14/02/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse plugins and maven
the mep plugin needs to be rewritten. ive started the rewriting but seriously lacked of time the past months. however in the yet to come new version theres some code [*] that you may find useful to avoid to declare your eclipse dependencies twice. [*] http://cvs.mevenide.codehaus.org/mojos/pde-plugin/m1/plugin.jelly?rev=1.4view=auto : adding pde:classpath as a preGoal of build:start should do the trick. -- gd Christopher L Merrill wrote: Duncan Krebs wrote: I want to use Maven to build a plugin but am wondering how to setup my project.xml. For example, do I need to manually add each plugin dependency inside project.xml or does plugin.xml preserve this information? Also, as I do with my other maven projects can I generate the .classpath and .project file using the maven:eclipse for plugin projects or do these files need to be stored in CVS? Thanks - Duncan Have you looked at the MEP plugin? (Maven-Eclipse-Plugin plugin) It builds Eclipse plugins. http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/index.html -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14/02/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse plugins and maven
Hi, I want to use Maven to build a plugin but am wondering how to setup my project.xml. For example, do I need to manually add each plugin dependency inside project.xml or does plugin.xml preserve this information? Also, as I do with my other maven projects can I generate the .classpath and .project file using the maven:eclipse for plugin projects or do these files need to be stored in CVS? Thanks - Duncan
Re: Eclipse plugins and maven
Duncan Krebs wrote: I want to use Maven to build a plugin but am wondering how to setup my project.xml. For example, do I need to manually add each plugin dependency inside project.xml or does plugin.xml preserve this information? Also, as I do with my other maven projects can I generate the .classpath and .project file using the maven:eclipse for plugin projects or do these files need to be stored in CVS? Thanks - Duncan Have you looked at the MEP plugin? (Maven-Eclipse-Plugin plugin) It builds Eclipse plugins. http://mevenide.codehaus.org/maven-eclipse-plugin-plugin/index.html -- - Chris Merrill | http://www.webperformanceinc.com Web Performance Inc. Website Load Testing and Stress Testing Software - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : maven and eclipse-plugins
Ok...I will take a look to this contribution but any idea or help is welcome. Thx, -emmanuel -Message d'origine- De : Vincent Massol [mailto:[EMAIL PROTECTED] Envoyé : dimanche 6 juillet 2003 11:24 À : 'Maven Users List' Objet : RE: maven and eclipse-plugins Hi Emmanuel, Not yet. I was planning to make one but haven't found the time. That would be a great contribution :-) Including the support for unit testing of Eclipse plug-in would also be great... Thanks -Vincent -Original Message- From: Emmanuel boudrant [mailto:[EMAIL PROTECTED] Sent: 06 July 2003 11:13 To: [EMAIL PROTECTED] Subject: maven and eclipse-plugins Hi, Is there any maven plug-in/goal in project to distribute Eclipse plug-in and features (build+upload on update site)? Thx -emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven and eclipse-plugins
Hi, Is there any maven plug-in/goal in project to distribute Eclipse plug-in and features (build+upload on update site)? Thx -emmanuel
RE: maven and eclipse-plugins
Hi Emmanuel, Not yet. I was planning to make one but haven't found the time. That would be a great contribution :-) Including the support for unit testing of Eclipse plug-in would also be great... Thanks -Vincent -Original Message- From: Emmanuel boudrant [mailto:[EMAIL PROTECTED] Sent: 06 July 2003 11:13 To: [EMAIL PROTECTED] Subject: maven and eclipse-plugins Hi, Is there any maven plug-in/goal in project to distribute Eclipse plug-in and features (build+upload on update site)? Thx -emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
