How to remove my jar from clojars? I don't want to mess up public group namespace. I want to move myproject/myproject to org.clojars.qertoip/myproject.
Open a ticket in Clojars' issue tracker on github. If you need it done privately (perhaps for security reasons) email the server caretakers.
If you would like to discuss the policy or help implement an alternative mechanism see this github issue.
There are more details in the Clojars About wiki page
I had the same trouble, when I asked on the irc channel ato told me that there is no option for removing jars cause someone may be already depending on them, what he told me was that he may remove it manually if i wanted to.
I don't think there's a mechanism for doing this yourself. Consider asking Clojars admin Alex Osborne (ato on github) to do it for you.
You might not be able to remove a jar, it however is possible to overwrite an existing jar by redeploying the same version
Related
My question is about using dynamics 365 JavaScript validator on a Managed solution?
will it work on a Managed solution?
I have used the JavaScript Validator and it only shows a log of all the API calls that will be deprecated along with their web resource name and line the code is on.
With this knowledge you can just run it on the managed solution and check
https://www.xrmtoolbox.com/plugins/XrmToolBox.Dynamics365V9JavascriptValidator/
I hate to say that it probably will not matter as you would not be able to update the Managed Solution if it failed anyway. Since Managed Solutions uninstall cleanly, I would:
1.) Create a test environment at trials.dynamics.com then install the Solution.
2.) Test the Solution to see if it performs appropriately.
3.) Attempt to uninstall the Solution cleanly.
You should have your answer there.
Additionally, check with the Publisher to see if there are any updates. Hope that helps.
I'm trying to deploy a spring-lemon app from github.
But the way the documentation advised to obtain and install the jar, isn't working.
While I keep on trying to sort this out, I wonder if it's possible to make spring-lemon available in maven public repo ?
That would be the perfect way to solve the problem.
I fully agree, and would like to see it in the central maven repository in fact. But, it needs some preparation to get approved. Sometime back I had tried it with some other project, but couldn't get approved.
So, it's low in my priority list now. Could you please create a ticket in GitHub, and it would be great if someone volunteers to take up this before I can.
Update 2021-08-21: 1.0.0.RC6 onward available on maven central
I provide a web service, but sometimes I need to update my web service. When i update the source code, i need to stop the service, then install the new service package.
Here is the problem:
1 I really don't want to stop the service when updating
2 I just need to update some specific features. But now I have to update the whole package. This makes the updating process long and heavy.
I think EJB would be a solution. But i need more advice.
Any advice is appreciated
You may want to think on lines of dynamic class loading tools. One of the tools i am aware is JRebel. You might want to have a look at it.
Other opensource alternative is springloaded. But its still naive and under constant development.
What is the great motivation behind integrating Redmine with a source control repository ? If it is only for monitoring reason, developers already have access to repository and they can do whatever they want diff, history with their IDE. For other people do they really need? I'm afraid, I can't see the real reason. Can you please help me to see ?
When you fix a bug that exists in Redmine's issue tracker, you can refer to the issue id in the commit message and Redmine will automatically associate the commit with the issue (or even close the issue).
This saves you the double work of referring the issue in the commit message and closing the issue in Redmine.
By the way, this is not Redmine-specific - you can do it with most bug trackers that offer source control integration.
I don't remember the exact syntax in Redmine right now, but most of the time, the syntax is something like:
fixes #123
...which would cause Redmine to automatically close issue #123, and create a link from the issue to the commit (and vice-versa).
Would it be possible/safe to run two instances of VisualSVNServer pointing to the same repo?
I've searched around and not had any luck finding anything related specifically to this question. The only reason I ask is because we have a need to enable Windows Authentication/Integration over http, and svn authentication over https. It does not seem to be an option to run both within a single instance of VisualSVNServer.
If not, do you know of alternative solution that would allow for this?
Edit: Received the following answer from VisualSVN Support
Thanks to Subversion design, repositories are ready to be accessed by several server instances simultaneously. We haven't experimented a lot with such configuration, but I think it's possible.
Am I understand properly, that you are going to store your repositories on a network storage and run two VisualSVN Server instances on different machines?
Please take care about the server.pid. file. In the current release, this file is stored in the repositories folder. So there will be a collision between two instances of VisualSVN Server. We are going to fix this problem in the upcoming release.
You can easily relocate the server.pid to another destination by adding the following command to the "C:\Program Files\VisualSVN Server\conf\httpd-custom.conf" file:
[[
PidFile "C:/Tmp/server.pid"
]]"
You can point two VisualSVN Server instances to the same repository if it stored on SMB share without any problems. It's typical configuration for active/active or active/passive cluster setups.
I wouldn't do this because as far as I know, VisualSVN brings its own web server (Apache) and SVN binaries. I would expect locking issues when running two of each on the same repo, if it's possible at all. VisualSVN probably won't install twice at all.
This sounds like a case for separate installation of SVN and Apache and custom configuration. I can't say whether what you want is possible but I would expect it is. It's probably to be fiddly, though - VisualSVN takes away a lot of configuration hassle that you have when doing the setup manually. Questions about that would be appropriate to ask on Serverfault.com.
Apart from VisualSVN, there also are other, also commercial wrappers. Maybe one of them is more flexible in this respect.
Update: Also, check this out: Supporting Multiple Repository Access Methods from the SVN book