I came across these files in one of the git repository
package-lock.json.swn
package-lock.json.swp
package-lock.json.swo
Related
I'm using a .gitignore file that was recommended for use with CodenameOne projects (See the blog post) and have committed my project to GitHub. Now I want to retrieve that project to a new PC and continue working on it but I'm having endless troubles doing it.
Shai shared a "quick trick" workaround which involves creating a new project then copying the relevant files from a clone of the Git into it, but then it's not a proper clone of the github repo that can be worked on and then synced back up to the remote.
So what I'm asking is: what steps (and troubleshooting resouces) would I use to ensure that:
I am storing the right files to the GitHub Repo to enable success
The IntelliJ Project will work with the retrieved files
I can commit changes back to the Repo going forwards.
Sorry, I'm a bit new to juggling GitHub repos and CN1's plugin structure for Idea has me mystified (I tried merging a new project with a directory which has a clone of the GitHub repo and the CN1 plugin is disabled - can't click on it)
I resorted to using the following .gitignore (using Codepoint One with IntelliJ IDEA):
# macOS
.DS_Store
# build artifacts
/build/
/dist/
/lib/impl/
/native/internal_tmp/
/out/
# idea
/.idea/**/workspace.xml
/.idea/**/tasks.xml
*.iws
With this setting, most of the IntelliJ configs are committed, as well as some binaries: CodeNameOneBuildClient.jar, JavaSE.jar, lib/CLDC11.jar, lib/CodenameOne.jar, lib/CodenameOne_SRC.zip.
This is not optimal (the binaries don't really belong in Git and take about 40 MB combined). But this way I can clone the project on a different machine and start working right away. It also doesn't produce Git diffs on every build — but only if the libs are updated.
IntelliJ/IDEA Codename One projects are nearly identical to NetBeans Codename One project with the one major difference being the additional idea directory. Just copy that directory from a working intelliJ project and add it to the gitignore. The project should work.
I tried downloading the bazar repository from launchpad with revision history using:
bzr branch lp:<repo-name>
This repository includes the .bzr directory which contains the revision history.
However launchpad.net also shows an option of downloading the zip file for some repositories.
The zip file does not contain the .bzr directory. It just contains the source snapshot of the latest version.
In github it is possible to download zip files with complete git revision history (ie. the .git directory is present)
I was wondering if this is possible in Launchpad?
No, I don't think Launchpad has such feature. The zip files you see are packaged by the project owners, not something generated or automatic. They could package zip files including the full history but the purpose is usually the opposite: a release version of the project with no history, only the files.
If you want a zipped version of the full history, you have to do it in two steps: branch and then zip up.
The --no-tree flag might be useful for you. Using that flag with the branch command will create only the .bzr directory without the working tree (the project files).
I've got a large svn repository which I'm splitting and migrating to several git repositories.
So this single svn repository,
software/project_1/
/project_2/
/project_X/
will become these git repositories:
repositories/project_1.git
/project_2.git
/project_X.git
I'm having trouble preserving the history for files that cross multiple git repositories due to an svn mv sometime in their history.
For example, consider the following repository:
software/project_1/<core_stuff>
/project_X/
Development happened under software/project_1/project_X/ for a while before it was svn mv'ed into a standalone software/project_X/
Now, for all of my project_X history, project_1.git has the pre-svn mv stuff, and project_X.git has the post-svn mv stuff.
Is this situation common? Is it possible to meaningfully track the history of files in such a situation?
I want to create a bazaar repository and have the .bzr directory not alongside the versioned files.
I'm searching for an option like "--git-dir" in git, or a way to achieve the same thing. Evenctually I'd accept an hack too.
A solution using bzrlib is feasible
Example current structure
project/.bzr
project/foo_versioned_file
project/bar_versioned_file
Wannabe structure
project/foo_versioned_file
project/bar_versioned_file
/unrelated_path/.bzr
There is nothing like --git-dir in bzr, but if you only need avoid having the full history along your working tree, then it's worth to consider using lightweight checkouts. Lightweight checkouts allow you to use only small number of files in .bzr/ directory (but you have to have it anyway) and the real branch with its repository and its history can be kept outside the working tree. So:
bzr branch bzr+ssh://HOST/REPO/BRANCH /unrelated_path
bzr checkout --lightweight /unrelated_path project
I wanted to know if we can have mass upload of artifacts to the repository in Nexus.
You can do it in a variety of ways:
Use the Nexus artifact upload page (note this only works for multiple artifacts with the same groupId and artifactId).
Set up a script, with multiple invocations of the maven-deploy-plugin's deploy-file goal, one for each artifact.
If you have access to the file system, you can copy the files directly into [sonatype-work]/storage/[repository-name]. If you do this, set up scheduled tasks to rebuild the metadata and reindex the repository.
Use the Nexus Repository Conversion Tool to create Release and Snapshot folders based on your local .m2 folder and then move the contents of those folders into [sonatype-work]/storage/[repository-name].