I'm trying to clone a project from the Team Foundation Server, but I have only access to one repository from the server and I can't switch to another repository. I also tryed to refrech the plugin.
I'm using Intellij IDEA 2020.1.1 with Windows 10 Enterprise LTSB 2016 and the plugin:Azure DevOps.
I would appreciate when I get some tips to fix this problem.
In Intellij IDEA with the Azure DevOps extension installed, the repositories are not shown as a tree structure . They are shown in the same level in the Select repositorypage when trying to select a repository to clone. We can filter the repositories by specifying a key word.
For example, in below screenshot I have a project called LCgGit and it has three git repositories (LCGit, LCGit2, LCGit3). So, we can filter by Project name, then select the specific repository to clone.
It will automatically open the project once we cloned the repository. And we cannot switch repositories such as in the Team Explorer in VS. We have to clone another repository again and open the project which located in that repository. We can open it in a New Window or This Window.
To switch the repositories, we can navigate to File -> Open/Open recent -> Select a project to open.
Besides, there's a blog which talking about Working with IntelliJ for your reference. It's still available for the Intellij IDEA 2020.1.1. But the plugin name is changed to Azure DevOps. So you can search Azure DevOps in the Marketplace.
Related
I need to create a Hybrid Worklight project but it needs to be physically inside another project.
The reason is that we are using an API that generates a project using grunt and the guide I got (company standards, practices, etc) says: Once the project is in Eclipse, create a wl folder and create the Worklight project inside of it.
When I create a new Worklight project in Eclipse it always goes to Eclipse's Workspace folder. How can I change this?
Thanks
You cannot (at least, not in a standard/supported/known working way); a Worklight project contains Worklight applications but cannot contain other Worklight projects. Worklight projects are always contained directly within an Eclipse workspace (unless working with the CLI tools).
Based upon your clarifying comment, it seems that your containing "(general) project" is just another directory that contains a wl directory - not a real Eclipse project - that in turn contains your Worklight project. It seems you are creating the whole thing using the CLI tools.
In order to work with this project within Eclipse, you'll need to create a new Eclipse workspace elsewhere (the Eclipse workspace itself isn't particularly important and doesn't necessarily need to saved in source control). You can then use File->Import->Existing Projects into Workspace to import the Worklight project from the wl directory. You can either "Copy projects into workspace" (in which case you will end up with two copies), or leave that unticked, in which case your Eclipse workspace directory will just contain a reference to the original directory (I suspect you want the latter).
As a word of advice, generally you should try not to work with both Eclipse and the CLI tools at the same time. Although it may work, you will get conflicts with (for example) the embedded test server, and long term, you'll just cause confusion.
Edit: looks like Andrew says pretty much the same.
Using Eclipse, since what you see in the Project Explorer view is the workspace Eclipse uses, it makes sense to me that when you create a Worklight project in Eclipse, it will be located - in the filesystem - inside the workspace.
If you want to create your Worklight project elsewhere, you'll probably need to use the Worklight CLI tool. From a terminal, navigate to the location of the Grunt project and then, using the CLI commands, generate a Worklight project in that location.
currently I am having following version of clear case on my local machine.
I downloded plugin "com.rational.clearcase.win32-20081031A" from url: "http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/clearcase/ccplugin/com.rational.clearcase.win32-20081031A.zip" which include following files in feature and plugin folders.
3.then I installed this plugin from eclipse Help->Software update-> search and install->given here local path of plugin folder which looks like following screen shot 4. It got installed on eclipse;but when I am trying tu connect through it it's giveing me following error.
can you please suggest whats going wrong in it?
That plugin won't work with CCRC (ClearCase Remote Client), only with a full base ClearCase installation.
CCRC comes with its own Eclipse interface, in which you will find all the necessary ClearCase commands.
If you want a CCRC plugin (which is different from the SCM Adaptor you have downloaded), you need to download it from your CCRC server, as I detail in your last question.
What is a 'scoped' repository workspace ?
Does this mean only members in current team will be able to view the repository rather than 'public' where everyone in the prject area can view the repository.
Scoped is what I always recommend when creating a repo workspace:
It allows other member of the project area to access your repo workspace by adding it to their flow targets.
That allows them to accept changesets from your repo workspace even though you haven't delivered them on the Stream.
This is a nice change to the "reserved checkout" issue with ClearCase, when a collaborator is no longer there and the file is blocked.
Here, as long as you have checked in your changes, even if you are not there to deliver them, those changes aren't locked in your computer, but are available for the other members.
This is different from scoped flow target.
And RTC4.0 has introduced Scope read permissions on files and folders.
That being said, a "public" repo workspace has its use (see this thread):
The idea of using a public repository workspace, is to provide an up and running development environment for the team.
I do not want a developer to spend 2-3 hours with the support of somebody else to setup is workspaces, to run a web application with the J2EE artifacts. Currently we are using MAVEN to build are applications and setting up the development environment and we are struggling with it.
To much knowledge required by the developer and way to much money trying to automagically configure the RAD 7.5 workspace with MAVEN and are own scripts.
The idea is to setup pre-configured public repository workspace with all the necessary RAD 7.5 artifacts (server, EAR configuration, web configuration, link between projects and link to MAVEN repository for component that you dont want to load in your workspace.
For our team we may have around 8 public repository workspaces, some with only the front-end projects other with only the back end projects or a mix of both depending on our specific needs.
The developer come in the morning pick the proper public repository workspace for his task and is up and running in 10 minutes. He can see ongoing changes from other, accept changes from his team mate or not. Of Course, from the workspace the changes can be delivered in the stream used for continuous integration.
I think its cool.
I'm getting started with Titanium Studio to build mobile apps. I'm using Beanstalkapp (or any other remote git/svn repository) for version control.
I can't find a way to connect a new project to the remote repository from within titanium studio.
I can:
1 - create a new mobile project and start a new local git repository
2 - import an empty project from the remote git repository
When using 1 I don't know how to commit to a remote repository.
When using 2 I don't know how to add a mobile project, I always get "a project with the same name already exists within the workspace"
Any tips on how to set this up conveniently?
From the file menu in Ti Studio, choose Import, Then choose Git Repository as New Project, click next, enter your beanstalk URI and click finish.
I have not tried this with beanstalk, but it works flawlessly with Github.com
Once you have set up the project, access the context menu of the project in the project explorer (ctrl-click) and your git commands will be accessible from the Team menu
I would like to know weather there is a way/plugin to build a project with maven using a remote pom.xml(http://host:port/pom.xml) with out a pom.xml file in the directory where I run "mvn install".
I need this as I want to effect maven dependencies of multiple clients by making changes to one remote file hosted at (http://host:port/pom.xml).
I am not aware of a way to do this. Generally, if you are doing development with multiple developers, you should be using source control. For example, if you are using subversion, you would just make changes to the pom, commit, and the other developers can update.
Of course using a version control is absolutely necessary...It would quite helpfull to use a Maven Repository Manager to interchange the artifacts with each other simply by deploying the artifacts to a central Repository Manager in your company and furthermore it will increase the build time.
If you are on Windows, you can try mapping the remote location (possibly a network share or an FTP location) to a local drive, and then executing the maven command in your console for the mapped location. It should work.
Else, you can distribute the pom.xml file via an email and ask the users to use it as their project file.
The other option is to use a Version Control System (VCS) such as Mercurial and keeping your pom.xml stored in the repository and make it accessible for the users to checkout. So far, this is the best way to make sure everyone is using the same file.