In my team, we want to create our own Nexus plugin (for Nexus 3) to prevent or allow some packages to be downloaded based on our own custom rules.
I know about such a solution as Nexus Firewall, but we can not use it, since it is not free.
I have tried to find documentation or a guide on how to make your own plugin but was not able to find any decent resources.
Links I found:
Nexus development guide (To be honest not that good guide)
The same question to sonotype team (but about nexus2)
Snyk plugin - great example but no way a strict documentation
It would be really helpful if anyone can give any advice on where to start first or provide any helpful links to use.
I need to search for all artifacts among my projects that require a particular dependency. Mvnrepository.com has such a feature, so I checked whether Nexus Repository Manager supported it as well.
I did not find any such feature, so I decided to come ask here, seeing as I usually don't do well with Nexus documentation or interface.
Does it support it?
I'll ask whether there are other tools that might do so in a separate question.
I'm starting to work to a new project and I'm evaluating the use of Nexus to manage the artifacts. What I need is a private repository that allow me to store on a private server my artifacts and at the same time to store, let's say on the same server, the artifact that are dependencies for my project.
I saw that there are 3 different type of repository available in nexus, and two of them (Hoisted and Proxy) has properties that I need, as I can evaluate from this documentation.
Can someone give me more detailed informations about the correct configuration of my repository to achieve the goals I described before?
Thanks in advance
If you have home grown artifacts as well as pull open source dependancies from the internet, a common configuration suggested is a "hosted" repository for your own stuff, a "hosted" repository for 3rd party stuff (not written by you but not internet accessible) and at least one proxy repository to where you get your internet artifacts from, then put them all in a repository group for one URL to access all of them from.
This is shown for example here.
What Format type will depend on what your artifacts are. If Java then Maven, if nupkgs then NuGet etc. If you explore the Sonatype documentation more, you'll note that Nexus Repository 3 has support for types that Nexus Repository 2 doesn't. This is noteworthy because you just linked the Nexus Repository 2 docs, but it might not even be the right choice for you.
You can't mix and match groups with formats, so if you use (for example) both Maven and NuGet you'd need two groups.
Not all formats are supported by NXRM either, so if you have ones we don't support, you can look for a ticket suggesting implementation and watch and guide any acceptance in the Sonatype NEXUS project of JIRA (https://issues.sonatype.org/projects/NEXUS/).
The Sonatype user group or community website are likely better places for general questions of this nature and also good for specific questions about problems you are having before filing a bug ticket in the JIRA.
The configuration I used is those described in this link: it's similar to those described by joedragons in the answer above.
While I'm working in java, I used three pre-defined repository provided with the nexus installation: the one pointing to maven central and two others for my snapshots and releases. I grouped them under a group.
Quite simple, but I think it will be sufficient to cover my needs.
Chrome is on the verge of definitly break compatability with NPAPI, and IE breaking with ActiveX the future of Java Applets is dark. Currenty we actively use a secure applet for out client organizations that enables their users to upload a bunch of files from their file system to our servers with the click of a button. The applet has full access to any configured drive, including network drives.
With the imminent death of the applet this functionality is going to be lost if we don't find an alternative. I have already tried to explore different solutions, including the chrome FileSystem API but that is currently only available for Chrome (http://caniuse.com/#feat=filesystem) and has limited access.
Does anybody know about an alternative to keep supporting the much appreciated functionality? Unfortunately we are obligated to support all browser down to IE8.
I've written a post about this here.
Once Google Chrome was the first to announce that they won’t be supporting NPAPI anymore, they were also the first to provide a new architecture in order to rewrite your code to work on their browser. You can take a look on Native Messaging, which “can exchange messages with native applications using an API that is similar to the other message passing APIs”. The problem is that this approach only works on Chrome, is not something that you can adapt to other browsers.
A more useful approach is FireBreath, a browser plugin in a post NPAPI world. Check the words below from one buddy of the project:
“FireBreath 2 will allow you to write a plugin that works in NPAPI, ActiveX, or through Native Messaging; it’s getting close to ready to go into beta. It doesn’t have any kind of real drawing support, but would work for what you describe. The install process is a bit of a pain, but it works. The FireWyrm protocol that the native messaging component uses could be used with any connection that allows passing text data; it should be possible to make it work with js-ctypes on firefox or plausibly WEB-RTC or even CORS AJAX in some way. For now the only thing we needed to solve was Chrome, but we did it in a way that should be pretty portable to other technologies.”
In light of the answer provided by Uly Marins I have researched the options suggested. Unfortunately these options weren't viable for our application, because the mayority of our users do not have sufficient rights to install third party plugins. Additionally the API is still in Beta which won't do any good in a stable production environment.
The main problem we wanted to solve was the abbility to delete files from the accessed folders. It seemed like one of the mayor goals of the removal of the NPAPI support was exactly to prevent this kind of possibility. Therefore we needed to reduce our goals to a simple solution that was still acceptable for our users, with the additional training on how to clear the selected folder manually (because most of our users are almost computer illiterate and needed to access network folders).
Long answer short. The requested solution is just not possible anymore and had to be replaced by a simpler solution and additional training.
I'm a newbie developers and building an application with 3 other remote developers. I've only worked alone until now, and now I need a way to share my source code with the other developers on the project. All of the project sites out there (SourceForge, Codeplex, Google, etc) seem to be aimed at Open Source development I'm not interested in making our code available to the world, I'm just looking for a method of sharing the code among the four of us. What is the best known method...or how is this usually accomplished?
Set up a Subversion repository (can be accessed across http).
There is an excellent online free book detailing pretty much everything you need to know about Version Control with Subversion
Yep, you need a version control repository which is remotely accessible. Subversion is excellent and very widely used; Git is another good option.
You could set up your own repository - you'll need a server which all devs can access via ssh, or via Apache/WebDAV - or use a hosted service, like Beanstalk, Project Locker, Unfuddle, SVNsite, etc.
http://beanstalkapp.com/
Set up a Subvserion repository (http://subversion.tigris.org/). You can control who may view your data through accounts, plus it gives you document versioning. When paired with a Http server, you can even view the source directly in a browser.
Subversion has all sorts of plugins for Eclipse and even Visual Studio, I believe. Tortise SVN is a stand-alone SVN client you may like, although I recommend an IDE-integrated plugin.
Subversion also goes well with a continuous integration server, such as Continuum.
Hosted: http://wush.net is another Subversion hosting platform.
Or, if you can host your own server, check out the VERY easy to use and VERY free VisualSVN Server: http://www.visualsvn.com/server/
You don't say what computing resources you have available, but the easy choice is to use a central server with say SVN to which you all have ssh access using a public key. You can probably rent such a service for around $10 per month.
If you don't like central servers, you can try Mercurial or git and ssh back and forth between your personal development machines.
If ssh is problematic, git actually enables you to send patches to each other by email (probably Mercurial does too). Ben Lynn's Git Magic tutorial explains.
You can use an online source control (like SVN or Git), and share it only with your team members. You should look into Unfuddle, it's a free source control/project hosting, complete with bug tracking system. I use it for my personal projects and it's awesome.
I think the best solution is Subversion. Subversion is a free source control system that is ideal for your requirement.
You can use many other support tools like Tortoise SVN to make the things more easier.
Here is one of the cheat sheets that describes commands of SVN.
Most of the Web hosting providers support easy one click installation of SVN on their servers. ex : Dreamhost So you can get a setup done very easily.
CVS is another Source control system that are used widely but I haven't seen any providers that support easy installation of CVS but there should be. You can have support tools for CVS such as Tortoise CVS as well.
I don't think you are interested in visual source safe (Microsoft Proprietary and not over Web) so I am not going to add information about it here. :)
You need to set up a source control repository. It's a pretty big topic, I'm really not sure where the best place to start reading about it would be. I'm sure the Wikipedia article on Revision Control will at least give you a bit of an overview.
This seems like a decent introductory series as well: Source Control HOWTO
Subversion works just fine over http/https. It is an open source project, but you can use it for whatever purposes you want.
http://subversion.tigris.org/
Most modern source control systems work well. Subversion is a common one. Which operating system will the developers be running?
If you just want to get up and running quickly with something, check out a hosted subversion system like www.beanstalk.com or www.unfuddle.com.
Subversion is open source, and I know you don't need it, but there are a lot of options here. If on Windows, check out Tortoise SVN. If on a Mac and you don't want a command line client, check out Versions.
You can actually setup google code to only allow viewing/editing by registered members. And I don't think they force any licenses either.
We currently use VSS but are in the process of migrating everything over to Source Gear Vault because VSS makes jumping out of our third story windows a common thought...
Here is a free solution with premium options available... https://freepository.com I have not tried this one.
Try github. It will cost you $12/month though.
Just use devunity.com. upload your code via zip or import it from svn and thats it. lets you collaborate around code instantly.