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 8 years ago.
Improve this question
OSGi allows to add/change dependencies aka bundle, when Maven allows to add/change dependencies aka jars.
Then what the difference? It's like hitting the one goal by different ways
Maven is more of a build system you use to create OSGi bundles. The maven creators call it (I might be wrong on this) life cycle management tool. It helps you build, test, integrate and release (also deploy) your software. This includes dependency management on the library or component base.
OSGi on the other hand is more of a runtime thing where a bundle can add services or consume others. (I'm obviously no OSGi expert)
So you can use maven to create OSGi bundles but both technologies do not live in the same context. I think you cannot compare them. They serve a very different purpose.
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 1 year ago.
Improve this question
I have created a library to use some utilities I need in multiple projects. So lets say I'm building a new version of the library and overwrite the old one, do my other project automatically update the library to the newer version when I reload my project? (Or when I build it)
You should not be referencing external libraries by relative path unless you have a good reason for it, exactly for reasons like these. Ideally you want to use a build automation tool which will handle this, for example Maven, Gradle or Ant, so that the dependencies are included on compile and are a part of your JAR or whatever you are building your project into.
https://www.baeldung.com/ant-maven-gradle
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 2 years ago.
Improve this question
I am new to spring boot and for build tool i am using Maven .
I wanted to know that how does spring boot application runs after maven build process finishes like
What is the output of the build ?
How build is executed ?
Although much of the detail about the build and run process is abstracted away by IDE (like IntelliJ) but i am curious to know about what happens internally ?
The spring-boot-maven-plugin Maven Plugin can generate an executable JAR which includes all dependency JARs and start-up, classloader code in addition to you application code.
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 3 years ago.
Improve this question
I'm trying to get a maven plugin (specifically Jacoco) to run on every maven project, but I can't find much info on this. I don't think settings.xml would work and the lifecycle extension documentation isn't very helpful either.
Any ideas?
Usually, you declare such plugins in a company parent POM and use it as parent in all your projects.
according to maven doc
https://maven.apache.org/settings.html
I think that you can't enforce a plugin on every maven project of a given host. there's no settings directive to do that.
Anyway you can facilitate the command line plugin dedicated goal through pluginGroups settings section.
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 am programming a YouTube-Downloader, and I'd like to use the 2 libraries VGet and WGet, since no other library worked. How do I embed those into my project? I'm using IntelliJ 14.
As noted at the bottom on the pages of those two libraries, the libraries are available on Maven Central.
You could search on Maven for "com.github.axet", e.g. http://search.maven.org/#search%7Cga%7C1%7Ccom.github.axet
Then you'll see the vget and wget libraries. By clicking on the latest version, you come to a page where there is also a jar-file to be downloaded.
But please be aware: Both libraries require additional libraries (e.g. some of the Apache commons libs), which you'll need as well. It is thus highly recommended, to use a dependency management tool like Maven, Ivy or Gradle for your project. I don't know IntelliJ that good, but at least Maven should be supported out of the box. Then all you have to do is specify that you want to use wget and vget, and libraries used by wget or vget will be automatically added to your classpath as well.
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 am relatively new to Play Framework 2 and I was wondering What are the advantages/differences of creating/using a plugin in play framework 2 over modules?
I mean why would you add something to your project through developing a plugin and why through creating a module? am I mixing things up?
A module is just a play app that is meant to be used in another app rather than stand alone, so basically a play project which results in a jar that you can depend on/include in a play app. It could contain utility classes, prewritten controllers, templates etc. that you would explicitly include or use in your app. Here is a good tutorial about writing modules: http://www.objectify.be/wordpress/?p=363
A plugin will be bound to the play app lifecycle, so that you can setup and initialize resources on app startup and clean them out on stop. Examples are database connection pools, stuff that gets cached because initialization is expensive, could also be stuff that should not live across application restarts that you would normally put in a singleton, which will break the tests since the same singleton will be reused across multiple App instances when running the tests.
A lot of the play parts are actually implemented as plugins if take a look under the hood.
Plugins are often distributed as modules but they can also be a part of the application code base.