Hi,
Can you please explain how do you think the artifact
installation/deployment workflow should look like? For example, simple a
description of the initial situation and simple step by step
instructions after that would be very helpful to understand what you
have in mind.
The current wizard been contributed by other m2eclipse users and it is
crafted to be extended to support deployment to remote repositories, but
it haven't been implemented yet. See
http://jira.codehaus.org/browse/MNGECLIPSE-335
From the team perspective it is not enough to deploy only to the local
Maven repository, because anyone who need to work with that dependency
would have to perform this manual step.
As for the groupId and other fields on the artifact wizard, they
history is supposed to be recorded in the drop down on each field, is
that functionality working for you?
regards,
Eugene
Yang Gu wrote:
This feature is available under the Import menu.
For example, right click on a jar file in your workspace, select
Import >
Maven > Install or Deploy an artifact (archive) into a Maven repository
Some notes of mine:
- the reference to "install or deploy to a Maven repository" looks
misleading to me, as it just installs the jar into the local repository,
maybe the text should be something more like "install into the local
Maven
repository" and "deploy to a Maven repository" should be a separate
action
under "Export..."
+1, It's seems this action only install the artifact into local
repository, it's equals to command 'mvn install:install-file'. IMHO,
this menu should reside in more visible location, maybe all related
menu of maven should be organized into one place such as one main menu
like 'Project','Run' ，'Windows' etc. Of course the related menu of
create new project should keep as before.
- the install artifact action didn't trigger a maven project update
configuration, so I had to manually do it before having the missing
artifact
error go away
- as it is, it would be much more useful if the install artifact
action was
also a quick fix provided for the missing artifact error, which already
populates the groupId-artifactId-version fields in the form
+1, I think this quick fix feature is very useful to help us to reduce
our effort when install artifact, especially there is lots of missing
artifact, after all, input the groupId-artifactId-version is
duplicated work every time, it's should be done by the systenm
automatically.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
