Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I've been working on an Android app for a company and now I have to pass it off to another software engineer. How do I pass on everything via email? is there something I can do to export everything in eclipse so someone can continue where I left off?
I'm assuming that you're not using a version control system.
Go get one now. Run - Don't walk.
Get the company to invest a couple of bucks in a private Github account or something similar. Get your code into the version control system, and then send your replacement the credentials to log into the version control system.
To perform a one-time move of your project, right-click the project, select Export and select Archive file under the General node. You can attach that archive file to an email and pass it on; the other developer can simply import this Eclipse project archive.
For continuous code-sharing use version control, such as git, on a shared repository. Bitbucket offers free service, even for closed-source projects, and there are other providers out there. Version control has the added benefit of allowing you tagging, branching, etc... it's really the only practical way to develop and deploy well-used apps.
go to you workspace folder. find your application folder.
attach it to .RAR and send this RAR to the other guy. the other guy will have to import the application via eclipse just by "Importing an existence application"
P.S: email clients such as GMAIL has some security issues with some extensions, that's why i mentioned to use .RAR extension. i'm trying to be simple as such.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I created an Java application under the use of Eclipse. Now the application will be running in production. However, if there should be a change in near future, another user of my department should be able to grab the code and improve it.
How would we achieve this, without any versioning software / repository (like SVN ors so)?
Is it a good practice for such a small bit of code, to just export the project as ZIP File and others just import them into their workspace?
It is not a best practice to not use any version control software.
However, if you really want to do it there are many ways. One way I would say is by using a shared folder (assuming that you all are on the same network).
Right click on your Project on Eclipse, then export to your localhost, zip the code and copy it to the shared folder. If your folder is shared on network, others can get the updated code anytime they need it once you update the shared folder. But whoever gets the code will have to make sure that their localhost workspace is updated properly.
I would suggest, you create folders inside the shared folder like dev/tst/stg/prod and copy the code accordingly. And also make sure that you are not replacing any previous stable code in case if you want to revert the changes.
For instance, if it is dev then create a folder with today's date and copy the code changes done today so that it will be easy for any new person to get the latest code and work on.
If you are not on the same network but both got access to internet then you may use Dropbox to share the code. Hope my response help you.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I'm trying to import an Eclipse project from GitHub into IntelliJ. I'm however having problems figuring out the correct way of doing that.
I'm following this question to do the importing(I'm leaving everything on default and simply click "Next", since the answer doesn't mention anything else and I have no idea what the other stuff does), but it still doesn't work. The configuration/project structure appears to be seriously broken and I have no idea why.
More exactly, I'm currently stuck at the following screen: The "Problems" tag explains in more detail that both the things in red are "invalid". I tried searching for that error, but it seems that people encounter it on all different project models and build tools like Maven, Spring, or Android. None of them concern Eclipse projects and the solutions vary from issuing a bunch of commands that I don't understand somewhere to deleting this project file or another.
Since there are so many unknowns in play here, I decided to ask, rather than waste days crapshooting only to break something in my IDE or Java installation. How do I get this project to work? It's a simple local machine visual app, it shouldn't be this complicated to import it in an IDE.
Basically the issue is how those two libraries are defined. If you select one and then click on the edit button to the right, a dialog will open and show the path to where those libraries are defined. They are likely configured to find the necessary JARs at a specific path on the (original developers) system. For example, for the jfxrt.jar library, maybe it is configured that the classes/binary JAR is at C:\Program Files\Java\JavaFx\jfxrt.jar or C:\Users\Bob\libs\fx\jfxrt.jar. Wherever they are defined, you either need to put the necessary JARs in that directory, or modify the config to point to the location on your system where you have the JARs. This of course may require you to download the necessary JARs.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I know this is not strictly related to programming, if you think this should be moved please let me know.
I have a medium-sized Java server written by me where I use various libraries.
I'm interested in knowing if it is possible to package the library jars inside my software Jar file without having to redistribute my source code (e.g. without having to make my software open sourced).
With packaging I mean just putting the jars inside my own jar, not their contents, and use Eclipse jarinjar loader to use them.
This is an example file structure inside the final Jar:
/mysource/*
/org/eclipse/jarinjarloader/*
/library1.jar
/library2.jar
In particular, these are the libraries I'm using:
MySQL connector/J (license: GPL)
A few libraries licensed with Apache Software License version 2.0
I want to avoid making the libraries downloadable separately because I'd like to avoid having to force each of my users to setup the classpath before running my program.
So, can I package the libraries this way?
If the license is GPL and you are running it on your server only then you are ok to use the GPL'd code in your server. If you distribute the software in any form to a user, including through the browser, then you will have to release your source code as well. If the software just sits on the backend and is never distributed then you are ok to do whatever.
If the code is AGPL then you have to release your source code even if it's behind a server if the software is interacted with in any way over the internet or otherwise by a third party.
If it's Apache licensed then you can likely use it however you wish generally.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I started a job in a company where they use Maven in combination with Git. I haven't worked with Maven before and I hope my question isn't too stupid. Why should one use Maven in combination with Git? From what I read Maven has a local, a central and can have a remote repository where it can find it's dependencies. This should enable a team of programmers to work together on the same code. What is the purpose of Git here? Would it be possible to program in a Team just with Maven and without the help of Git?
Well maven and git are for different purposes:
GIT holds the sourcecode of your application
MAVEN is used for dependency management. It holds the binary dependecies of your application. It also creates a abstraction of the used IDE. One developer can use eclipse and another intellij. The project can also be built with the commandline.
I guess it would be possible to work with just Maven. It might even not be totally horrible. However, Maven is system for distributing releases (even if they are snapshots or whatever). It is a totally different tool, than what a version control software is. I guess you could say Maven is the just the "distributed" part without the "version control" part of DVCS systems such as git.
A real version control can do a lot of stuff Maven does not support directly, such as merging, diffs, commit logs. I'm sure it would be possible to build an actual, fully featured version control system on top of Maven, with suitable plugins, but it would be very klunky and awkward to use. The likes of git already do all this, and they have been designed to do it from the start, so they do it better than some hack on top of Maven could ever do, so I doubt nobody has actually tried.
I mean, you could do version control with just shared folder, naming conventions, manual log files, an IM group chat (irc channel) for synchronizing between developers, stock diff tools etc for comparing stuff, etc. It would just be horrible to use and very easy to "break" (in this case, easy to corrupt entire project and all its history). There has been a long evolution of version control systems, you can start reading about it for example here, and starting do it on top of Maven would be like jumping 30 years back in time.
When using Maven, your project's dependencies are well defined in pom.xml which is good for collaborative development as addition of dependencies doesn't require other developers to be informed as Maven automatically handles dependencies itself by downloading dependencies.
Git is used for distributed version control which is very good to keep track code changes in your project.
Basically, these two tools make collaborative development easy. However, this is just a crash course description, there are many of advantages.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I need to create a very simple DMS (Document Management System) / File Repository / file manager or whatever we might call it under Java EE.
It should permit the user to create folders and upload files into it and the folder/files information should be stored inside the database for checking which user created what (in this sense a simple file-manager which only lets one browse directories on the server's disk is not enough).
To be more explicit here's what it should be more or less:
So far I searched for canned solutions which I could use however I only found TinyDMS (http://sourceforge.net/projects/tinydms/) which is very good (picture above is a screenshot of it in action), it uses jackrabbit for file search however needs a lot of Spring framework dependencies and is a hell to be compiled (didn't succeed yet).
Then there's OpenKM and LogicalDoc but those are really complex programs which don't fit well to be included into a third party application.
Isn't there anything I can start with?
use jackrabbit DMS java base.
http://jackrabbit.apache.org/
If you don´t want to use Alfresco, Nuxeo, or other DMS, maybe you should develop your own "Light (DMS)". For that you can start with the repository; for this you could try Apache Jackrabbit or Modeshape as the lower level to manage data, files, versionong, deletion, etc. Personally, I´m using Modeshape for my graduate project beacuse of it´s documentation and ease of implementation. Then I use JAAS to manage users and its permissions for each file or folder.