On 01/07/2015 12:29 PM, František Řezáč wrote:
Your reasoning about the relationship between independent modules is right and
made me think again really hard to formulate my intuitive disagreement.
The important thing to notice is why a submodule is released. If it's because
of some new,
I have found that the shade plugin is not completing the job. I manually
updated one class, com.amazonaws.services.s3.model.S3ObjectInputStream,
updating the imports to use the shaded versions of the org.apache.http.*
imports:
import org.shaded.http.client.HttpClient;
import
Hi,
I have asked a question on stackoverflow about what I thought should be a
relatively common scenario but I didn't get an answer even though I put a
bounty on it and published it through my social networks to wide audience.
Since it's still unanswered after a long time, I'm sending it here as a
What is the relationship between the independent modules?
If a child module gets a new version, should that trigger a change for
other modules that depend on it?
It seems to me from your description, that you do care when a child
module releases a new version.
If this should trigger a change in
On 1 July 2015 at 11:35, František Řezáč frantisek.re...@calavera.info
wrote:
Hi,
I have asked a question on stackoverflow about what I thought should be a
relatively common scenario but I didn't get an answer even though I put a
bounty on it and published it through my social networks to
Your reasoning about the relationship between independent modules is right and
made me think again really hard to formulate my intuitive disagreement.
The important thing to notice is why a submodule is released. If it's because
of some new, comprehensive feature set to be used in dependent
Hello, no (IMHO) you are on the right track. Consider that one of the
benefits deploying on a javaee app server, is that you already have a set of
libraries bundled on your runtime. You dont have to 'increase' the size of
your app, by bundling more or less the same libs or slightly different.
It
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin Version 2.10.1.
Sorry the link to the plugin was wrong. The link correctly looks like
this:
http://maven.apache.org/plugins/maven-ear-plugin/
Enjoy,
-The Apache Maven team
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin Version 2.10.1.
This plugin generates Java EE Enterprise Archive (EAR) file. It can also
generate the deployment descriptor file (e.g. application.xml).
http://maven.apache.org/maven-ear-plugin/
Release
The Apache Maven team is pleased to announce the release of the
Apache Maven Invoker Plugin Version 2.0.0
The Invoker Plugin is used to run a set of Maven projects. The plugin can
determine whether each project execution is successful, and optionally can
verify the output generated from a given
10 matches
Mail list logo
