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.
Related
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 2 years ago.
Improve this question
I hope that someone can help me with my problem. I am quite new to stuff like Git, Spring Boot and in general Java (Maven Projects). But i want to try to modernize our archiving system for our PL/SQL scripts. Right now, we archive them by hand and zip a version with the old date to then reserv it, that no other developer can make changes at the same time. After finishing working on the script, the developer releases the script in a specific folder (release) where it gets tested. After a successful test, other developer can now finally work on the script again.
Now, i wanna try and modernize this whole procedure:
I wanna import all our PL/SQL scripts into GitLab
If some developer is working on a script and commits/pushes it, i want that a action happens, where the script gets also copied into our release-directory, where it can be tested from our consultant (in context of the specific ticket the script gets released to)
I dont excactly know if my thought fits in here but i think it would fit the modernizing concept, if a new branch would be used for this (developer/testing branch). So that after a period of 2 weeks (our scrum sprint) all changes could get merged into the master branch
I would like to know, what is the best way to realize this and how would i go forward. Because i dont know if my idea with GitLab + Spring Boot Application is the best in this scenario and even if it is, how do i manage to monitor that. Its the starting point that i am missing. Once its there i think i can handle everything but the beginning is my problem (and missing examples).
I am sorry in advance for my bad english and hope you can help me getting started with my idea :)
Thx
Steven
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 2 years ago.
Improve this question
I have written a java application, which is used by many people in our organization. I often have to make changes to the application, so i deploy the new .jar file overwriting the existing one, while other people may have it open (i don't know why windows is permitting me this, when it doesn't permit me to rename or delete the jar...). This creates anomalies in the application, and if someone tries to close and reopen it while someone else has it open, the application doesn't start at all.
I know that the most clean solution would be to close all the instances of my appilcation before deploying the new version, but this is near impossible since the application is run by many people (even by customers outside our organization).
What could i do? Is there any other valid solution?
One way is to use a .bat file (assuming you're running on Windows) and let that file point to the most recent version of the application.
When you need to deliver a new version you create a new directory, copy the updated application into it, and then you modify the .bat file.
Another way is to use Getdown
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 5 years ago.
Improve this question
When do we need to attach source to a jar?
Can we debug without attaching the source code?
Can we see the stacktrace line numbers without the source (AFIAK we can't)?
What is the best practice for local builds? Do we need the source code?
What about CI?
Can we leave the source code only for production release?
Thanks,
Omer
It's good practice to also publish the sources jar along with your binary jar in your internal (or external) Maven repository. It makes life of the developer that is working with your code much easier since they can see your comments / browse the codebase and be able to have all that at debug time. Now as you are saying even if the sources jar is not published, developers have ways around it primarily relying on their IDE. In Eclipse for instance you can install the Java Decompile plugin that would give you access to the code during debug time or on IntelliJ there is something similar without the need of installing a plugin.
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 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 8 years ago.
Improve this question
Just note that I am looking for possible solutions for more then couple of hours. I saw similar problems on Stack Overflow but this just not work.
Ok so I have created a Dynamic Web Project in Eclipse Kepler. Later I shared everything with my team mate. Problem arises when he is trying to change one of the classes. He changed private field to something else. But when he restart tomcat server republish code he got an exception that path to the file is invalid. But he changed that!!!
Eclipse still thinks that variable has an old value.
Any idea how to fix it? We restarted eclipse multiple times, restarted tomcat server.
Make sure Eclipse actually builds the class file. JSP files are compiled by the web server at runtime, so changes there might work.
Look at the file system, make sure that the time stamps of all the .class files change when you save a change in Eclipse.
What do you mean by shared? If you are using some sort of source control application, the problem is most likely there. Quick fix if you are pressed for time would be just copying the entire project directory, and creating a project from said directory. Also, tomcat has a tendency to not 'update' your deployed project for some reason. If, however, you kill the work/catalina folder and re deploy your project it should work.
Remove the project from your container, clean the container and redeploy the project