I create a Liferay Workspace Project in eClipse. After that, I delete the workspace project in the eClipse.
The problem is that I can't create another new Liferay Workspace Project after deleted it.
It just showed "A Liferay Workspace project already exists in this Eclipse instance."
How can I completely delete the "Liferay Workspace Project"?
Eric
I can only tell you an alternative: just create a new eclipse workspace. It's a lot quicker than figuring out where the tool set saves this information
Related
My new Tortoise SVN repository project should be mix of some files on my local disk and some files already part of another existing project in SVN. Regarding those (existing) files, can I simply copy them using repo browser into new project and then do check out to bring them into local working copy ? Or should I check out existing files to working folder of new project, then add new local files to it and after that add all of them to mentioned new repo project ? Or ... ?
Here are some solutions depending on your application:
if you do not want to duplicate the existing files in the repository: you should use svn:externals property (see Subversion doc and TortoiseSVN doc). This allows you retrieving in the working copy of your new project some folders coming from another location in repository (e.g. from another project). The constraint is that you can do that with entire folders, not separate files.
if you don't matter duplicating the files in the repository: in your local working copy (not in the repo browser), you should select the files you want to copy, right click and choose Context Menu → Copy from the explorer context menu. Then browse to the target folder, right click and choose TortoiseSVN → Paste. Then commit all in once. This is described here.
I moved a git-repository to another namespace in gitlab through the 'transfer project' option in the Admin Area. I am owner/master of both namespaces.
The first time I did the transfer it took ages for the page to automatically refresh after the move; but I figured I just let it run it's course; when I clicked away to another page and then got back, nothing seemed to have happened: Project was still in the old namespace, project is not visible in the new namespace.
However in the old namespace, it now says: " repository: does not exist" in the Project info and if I go look on disk, the nameofrepository.git & nameofrepository.wiki.git are actually moved into the directory of the new namespace and are not in the old directory anymore.
Is there any way of updating/fixing this information in gitlab easily? I did restart gitlab already, but that didn't seem to help out at all.
We're running gitlab 7.5.1
We had a similar problem in GitLab 7.1.1. The move made the original repo empty but the project did not appear in the destination group. We fixed it as follows (for this purpose let's say the original project x was in group a, and it was being moved to group b):
Browse to the repositories folder on the GitLab server.
Locate the target group b and folder x (which is what we found). This meant GitLab had moved the folder but not created the project correctly.
In GitLab create a new project in group b called temp.
Rename the project folder x in group b to temp.
Check in GitLab that the project contents is now available in group b, project temp.
If all is well, in GitLab rename project temp to whatever you want it to be (probably project x).
If those instructions are a bit convoluted, the main point is getting GitLab to create a project and then overwrite the projects folder with the moved folder. Why the project does not appear I don't know, but presume it's a bug with GitLab.
I am trying to migrate an GitLab setup from 7.8.2 to 7.12.2. I am not really sure how to go about this. I have installed a new box, on Ubuntu 14.04.2.
Now I would really like to just export the old user/group database and import it on the new server, then copy all the repositories from the old server to the new one. And tell the users to start using the new one.
I do not know which database my new gitlab installation uses, neither the old one.
I have been up and down the gitlab documentation, but cannot find sufficient information on how to migrate from one server to another.
I followed the instructions on https://about.gitlab.com/downloads/ for ubuntu, and all seems to work fine. I am looking for a way to export the users/groups from the old gitlab box and import it on the new gitlab box. and then just copy all the repositories from the old box to the new one.
Any assistance? I know next to nothing about gitlab :(
I would take the following steps
Find out if gitlab is installed by hand or with gitlab-omnibus. This you need to know for the exact backup and update steps.
Do a backup of the old version just to be safe
Update the current 7.8.2 instance to 7.12.2 instance by following the update guideline
Back up the newly updated gitlab system
Restore the backup on the new system
Backup & restore documentation can be found here
I have deleted the workspace from accurev. Now when I am again creating the workspace. It's giving error that workspace already exists. How can I resolve this?
update: Is there any accurev plugin through which i can directly promote the code to accurev strean using IBM RSA.
Workspaces and streams are never really removed due to the time-safe architecture; they are deactivated and can later be reactivated. This also means that a workspace or stream owns every name it's ever had. You will need to create the new workspace with a new, unique name.
Via the command line, "accurev reactivate wspace workspaceName"
I have been working with a TFS project that supports copying build output to source control. If I open the build definition, this is under "Build Defaults". There is an option to copy build output to a source control folder.
I have just installed TFS Server 2013 (with update 2) and I want to use this feature with a new Team Project. However, if I create new build in VS 2012 or VS 2013 on the new server, I am not given the option to copy build output to source control. What gives?
I am not looking for a workaround, I want to know what to change so that my server acts like the first one I described. Thanks!
Screenshots of what I'm talking about: http://imgur.com/a/mhDNQ
This was a feature that was temporarily present in TFS, but I believe has since been removed. If I recall it was put in there specifically to support the cloud-hosted elastic build servers which didn't have access to network shares to drop the builds in.
Most people recommend against putting your build outputs into TFS. The best approach is to publish them to a NuGet feed.
In any case if you want to put your build outputs into TFS (or a NuGet feed) you'll have to modify the build workflow to do that yourself.
Open a new build definition > process.
Under template select new and you should be able to choose project and folder. Find your original template and link it. Your option should appear.
In TFS 2013 this has changed to be "store drops in TFS". When you select this option the drop I'd stored in a new inversioned store that you can access.
While you can easily get the files out as indecision or zips the built in tools like release management do not support it yet. I would recommend that you use this option but publish your assets to a nugget repository.
If your TFS is available online (VSO or https) then you can use MyGet to dynamically load the nugget packages that you are publish and make them available on a feed.
http://docs.myget.org/docs/how-to/use-tfs-online-git-with-myget-build-services