Hi,
Is there a way to treat the maven warnings as errors?
The Apache Maven team would like to announce the release of Maven
3.5.0-alpha-1.
http://maven.apache.org/
NOTE: This is an ALPHA release. There is the potential that features may be
added/removed between this release and the first GA release in the 3.5.x
release line.
Please consult the Known Iss
m regarding the scope and definitions
of properties.
I have a parent pom:
https://github.com/io7m/maven-parent-properties-20170301/blob/develop/pom.xml
... which contains a definition like this:
...
...
com.github.siom79.japicmp
just a specific
> example of a more general problem regarding the scope and definitions
> of properties.
>
> I have a parent pom:
>
> https://github.com/io7m/maven-parent-properties-20170301/blo
> b/develop/pom.xml
>
> ... which contains a definition like this:
>
On 2017-03-01T12:46:45 -0600
Curtis Rueden wrote:
>
> In this way, I ensure that all projects which extend our parent add all the
> useful metadata and properties needed for successful builditude.
>
> We released scijava-maven-plugin 1.0.0 on Maven Central; feel free to use
> it if it helps you.
On 2017-03-01T12:46:45 -0600
Curtis Rueden wrote:
>
> In this way, I ensure that all projects which extend our parent add all the
> useful metadata and properties needed for successful builditude.
>
Hm, slight issue with this.
If you take a look at how my projects are usually designed:
http
Hi,
> Note how this is a module of the root project and therefore it'd be
> redundant to have to re-specify all of the information such as the
> contributors, SCM location [0], etc. I only provide the information
> that's specific to that module such as the OSGi manifest,
> dependencies, etc.
If
Thanks for all the hard work that goes into maintaining and improving the tool!
Any chance the Aether work would somehow enable declaring server credentials
only once in settings.xml and then reusing them for multiple
build.repositories.repository nodes in pom.xml (such as when you have multiple
