Hi,
I have a new challenge for your maven-indexer expertise :)
What about adding additional information to the local index? I see the
default indexers (min, etc..) produce really minimal information. The
problem is that everybody is using these default indexers and all the
available indexes
I configured the WAR plugin to overlay a zip file. Nothing fancy. Here's
the config:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.5/version
configuration
overlays
groupIdorg.company/groupId
artifactIdui/artifactId
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron,
I'm not sure if it's a better or worse solution. It does minimize the
configuration effort. This is always a good thing when moving people
from Ant to Maven.
What it does illustrate (at least to me) is that the code base I'm
working with has
On Monday, 8 December 2014 at 16:24, Paul Benedict wrote:
I configured the WAR plugin to overlay a zip file. Nothing fancy. Here's
the config:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.5/version
configuration
overlays
Yup. I copied/pasted and didn't even see the error I made. Thanks for
pointing that out, Stuart!
PS: Still sounds like a bug :-) It should not have seen any overlays -- but
it was coerced to a String unexpectedly.
Cheers,
Paul
On Mon, Dec 8, 2014 at 12:07 PM, Stuart McCulloch mccu...@gmail.com
I'm contemplating an upgrade of a large Maven 3.0.4 build to 3.2.3, just
wondering if anyone knows of either any key gotchas in the upgrade and/or
key benefits?
One feature I'm wondering at the outset is...with 3.2.3 can I specify the
reporting plugin versions in pluginManagement or does this
Hi,
I've been looking around for a way force usage of the http lightweight
client for Wagon using maven 3.2.3
I've tried a few options like this:
mvn -Dmaven.wagon.provider.http=lightweight
or the servers block:
servers
server
idgeomesa/id
configuration
Hi Eduard,
for additional information see:
http://jira.codehaus.org/browse/MINDEXER-81
Currently, the ArtifactInfo is hardwired, is not extensible.
Re available index for Central, it’s not the “minimal usable”
the decision driver, but the SIZE of the index download instead.
We were
The Mojo team is pleased to announce the release of the License Maven Plugin,
version 1.8.
This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).
Description
---
This License Plugin
Hi,
The Mojo team is pleased to announce the release of Animal Sniffer version 1.13.
Animal Sniffer provides tools to assist verifying that classes
compiled with a newer JDK/API are compatible with an older JDK/API.
The following tools are provided by animal sniffer:
* A command line tool to
Le lundi 8 décembre 2014 13:01:10 David Hoffer a écrit :
I'm contemplating an upgrade of a large Maven 3.0.4 build to 3.2.3, just
wondering if anyone knows of either any key gotchas in the upgrade and/or
key benefits?
you should check compatibility issues known with some plugins:
One other issue came up in this upgrade. We still have branches that have
to stay at 3.0.x. How can I make the trunk build use 3.2.3 w/o changing
everyone's M2_HOME? Is there a way to bootstrap the build so the build
picks the specified version of Maven? E.g. I want the build to specify the
12 matches
Mail list logo