Yang Gu wrote:
It is unclear how you got that not existed artifact in that pom, but
I see how quick-fix in the pom editor would make sense. Please submit
an enhancement request for such feature.
We will depend on some artifact which not exists in the repository
sometimes, such as one project depend on another no-mavenised project,
we have to install the artifact of no-mavenized project to local
repository or deploy to remote repository, especially when work on
legacy system its dependency management is very messy and lots of
dependent jar lost version, you have to install it if you decide to
depend on it. I have migrated some project to mavenised project these
days, this project haven't any dependency management, over fifty
artifact lost version information, I have to install those artifact to
my local repository by manual, of course, I give some special version
number for those nonversion artifact. Those artifact is same as the
notexisted-artifact I mentioned .
This is sort of scenario I had in mind for the wizard used for
installing artifacts into the local Maven repository. The only
difference is that you choose to create pom.xml before getting those
artifacts installed, hence have to duplicate the work and have to
specify artifact coordinates more then once. If you used wizard before
creating pom.xml and updated index for the local Maven repository, then
pom editor would allow you to use content assist or quite artifact
search when adding dependencies to the pom.xml.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
