Bug 172675 - [70cat][maven]UI to deploy artifact(s) in remote Maven repository
[70cat][maven]UI to deploy artifact(s) in remote Maven repository
Status: NEW
Product: projects
Classification: Unclassified
Component: Maven
6.x
All All
: P3 with 1 vote (vote)
: TBD
Assigned To: Milos Kleint
issues@platform
: PLAN
: 187229 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-21 12:13 UTC by jmborer
Modified: 2012-06-19 16:13 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jmborer 2009-09-21 12:13:51 UTC
It would be great to able to add an artifact into a remote repository as it is currently available for the local 
repository (install missing dependency). One solution would be to provide the action in the repositories browser view when 
you pop up a menu for the given node. A dialog should then ask you for groupid, artifactid, etc as well as connection 
crendentials or use those of your settings file.
Comment 1 Antonin Nebuzelsky 2010-07-30 15:17:31 UTC
Reassigning to default owner.
Comment 2 Jesse Glick 2011-03-11 15:29:08 UTC
Probably WONTFIX; a repository manager like Nexus provides its own UI for uploading ad-hoc artifacts. Only useful to provide such a UI in the IDE if there is some direct connection to the development workflow, so that reentering information is unnecessary.

(Should consider removing the UI for installing an artifact in the local repository, too, since this is generally a bad idea; should either upload to a repository manager, or create a wizard to use something like http://jira.codehaus.org/secure/attachment/53864/MNG-1867.zip to keep the binary in the source tree.)
Comment 3 Jesse Glick 2011-04-27 17:55:26 UTC
*** Bug 187229 has been marked as a duplicate of this bug. ***
Comment 4 Jesse Glick 2012-02-14 19:22:10 UTC
https://jira.codehaus.org/browse/MNG-3989 has more discussion. com.googlecode.addjars-maven-plugin:addjars-maven-plugin seems like a good option, though currently it works in NB only if you separate the libs into their own project.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo