[patch] Add a Wizard Export to manually add artifacts to a remote repository

This patch adds 2 new export wizards:

• InstallFile wizard, that resolve MNGECLIPSE-51
• DeployFile wizard, that resolves the current issue

Icons comes from the crysal icon set, I don't know if there is some licence incompatibilities ...

I did not had the opportunity to try the deploy file wizard :'(

Very nice.
Can you please attach "network_local.png" separately, patches can't include binary files.

Extracted from the crystal icon set (from everaldo) used in KDE.

I'm not completely sure that we can re-use them as part of an ASL2 project:

Icon set seems to be in LGPL
http://www.kde-look.org/content/show.php?content=25668

Somehow this patch slipped out of the horizon. Guillaume, would you be able to update it to the latest code? Let's not worry about icons now.

I'll try to find some time

Patch for org.maven.ide.eclipse includes:

• Updated code to suite current state of 0.9.6 trunk
• Merged "Deploy" Wizard into "Install/Deploy" Wizard. Both functionality can go well into the same Install/Deploy wizard.
• Added another page for selection of which (local/remote) repositories to be deployed to.
• Implemented install-file execution with PomExecutionManager
• Added wizard page for optional parameters (generatePom, createChecksum, reusing existing pom)

So, basically, it can be used and it works.

Todos/Problems/Possible Improvements:

• Not possible to execute multiple ILaunchConfigurations, e.g. for deploying the artifact, sources and javadoc at once if the user has all three. So, currently, he needs to do it low-level and specify a classifier and do the process three times.
• Implementation of deploy:deploy-file to remote repository. For this, I need to get a list of available remote repositories but I don't know where to get them. POM Model or MavenEmbedder Settings?
• Selection of artifact should not only be with a file system FileDialog, but Workspace-Browsing should also be allowed.
• If no file is selected and the File > Export > Maven > Install-File Wizard is called, the user should be able to select an external file.
• Missing NLS externalization
• Missing tests

Mike, it is fantastic to see such great progress on this!

Before we can apply this patch, we need all new files to have headers with the new license and Guillaume name should be in the @author tag. Assuming Guillaume don't mind the license change (but it would be good to confirm that), can you please update the patch for that?

I also wonder if you are interested to continue working on improving this feature to better fit into the m2eclipse code? For example, after very brief review of your code I have several suggestions and questions:

• first of all we really need basic tests to cover backend code (separate from the UI), see for example MavenBuilderTest and other tests in the org.maven.ide.eclipse.tests project
• I think it is better to use embedded maven runtime instead of spawning new JVM. It would allow to provide better error reporting, and will be faster. You can obtain embedder from MavenEmbedderManager and use MavenEmbedder.execute()
• what was the reason to create FileBrowser instead of directly using swt FileDialog? See for example, pom selection in the Maven launch configuration UI
• org.maven.ide.eclipse.internal.builder package is intended for the project builder and functionality you added there belong more to org.maven.ide.eclipse.internal.launch
• Util class is not intended for any UI code and similar functionality is available in the SelectionUtil class, which could be extended if needed
• deployment repositories can be retrieved from <distributionManagement>. Wizard should allow to select pom.xml where that section is declared (or pick it up from the selection wizard was started from), and also allow to specify repository manually.

Regarding wizard UI design:

• can you please elaborate on the reasons to allow to deploy to multiple repositories? Maven practice is that artifact should come from one repository
• I haven't looked at the implemented wizard UI, but from your description it sound like it only allow to deploy one artifact at a time. I think it worth to explore to have a list of artifacts (with add/remove buttons, similar to on from "materialize maven project" wizard). So, user can select multiple artifacts for import and also allow to edit their pom parameters. then list can be smart to identify that artifacts have classifier and simplify configuration.

Hi all
Amazing work Mike, thank you for updating my basic work.
Concerning the license, I'm OK with the ASL 2.0 -> EPL 1.0 change.

Guillaume, Mike, I used part of your code to implement wizard for deploying artifacts to the local Maven repository. I simplified code for launching Maven and made UI compatible with SWT designer that we are using for all UI work.

Currently wizard is not implementing deployment to remote repositories (doesn't seem like Mike's patch handle that scenario). Are you interested to work on this issue little more? I could use some help to implement deployment to remote repositories into the wizard.