Hello everyone, :-)
is it somehow possible not to "install" an artifact which already exists
in the local repository?
What about artifacts in a remote repository? Is it possible to prevent
deployment of such artifacts?
I don't want to have our build server to accidentally install an
artifa
It works!!! Thanks Stuard
So my change should be good for commit for 3.4?
-Dan
On Sun, Nov 13, 2016 at 3:01 PM, Stuart McCulloch wrote:
> Hi Dan,
>
> There are two places in MavenCli which create a container.
>
> You’ve enabled JSR250 for the temporary container that resolves the core
> extens
The Apache Maven team is pleased to announce the release of the Apache Maven
Site Plugin, version 3.6
The Site Plugin is used to generate a site for the project. The generated site
also includes the project's reports that were configured in the POM.
https://maven.apache.org/plugins/maven-s
On 17 Nov 2016, Clemens von Musil wrote:
> We pushed a very minimal example project to a public github repo located
> here:
>
> https://github.com/kr1schan/mavenToy
>
> The project consists of an ear, two war modules, one ejb module and one
> plain jar artifact.
> Both war modules depend on the
We pushed a very minimal example project to a public github repo located
here:
https://github.com/kr1schan/mavenToy
The project consists of an ear, two war modules, one ejb module and one
plain jar artifact.
Both war modules depend on the ejbmodule as well as on the jar artifact.
SkinnyWar is ena
