This only imports Spring Boot dependencyManagement, and it looks like the
thread starter would also like access to the plugins configured by
spring-boot-parent. He’d have to duplicate Spring Boot's plugin configuration
in his own project.
Nils.
> Op 5 dec 2023, om 15:11 heeft Franco
per pom instead of using
> > our own. For dependencies its pretty simple - you use the import scope,
> > but
> > what about plugins? I'm seeing some stackoverflow posts about the sameish
> > issue from 11 years ago that the suggestion was to use tiles plugin. Was
> &
Howdy,
For importing plugins there was even some PoC like this:
https://github.com/apache/maven/pull/1190
Also, planned for maven4 to (or already is, Guillaume?) support mixins.
HTH
T
On Tue, Dec 5, 2023 at 12:51 PM Bernd Eckenfels
wrote:
> Hello,
>
> I think that’s a long
trying to integrate the spring boot I
> come into an issue that I should inherit their super pom instead of using
> our own. For dependencies its pretty simple - you use the import scope,
> but
> what about plugins? I'm seeing some stackoverflow posts about the sameish
> issue f
what about plugins? I'm seeing some stackoverflow posts about the sameish
issue from 11 years ago that the suggestion was to use tiles plugin. Was
there any movement regarding this in the mean time?
As a workaround I currently have a dedicated springboot runtime module that
includes a si
Switch to AWS Corretto, they offer Java 21 already
Sylwester
wt., 12 wrz 2023, 10:26 użytkownik hantsy bai napisał:
> Oh, I think it is my fault, it seems Github actions does not support 21, I
> was using *zulu* distribution.
>
> ---
>
> Regards,
>
> *Hantsy Bai*
>
> Self-employed consultant, f
Oh, I think it is my fault, it seems Github actions does not support 21, I
was using *zulu* distribution.
---
Regards,
*Hantsy Bai*
Self-employed consultant, fullstack developer, agile coach,
freelancer/remote worker
GitHub: https://github.com/hantsy
Twitter: https://twitter.com/@hantsy
Mediu
Hi
Please run your build using option -e and have a look at the stack.
I use 21, and it works fine.
This might be some restrictions with spring boot parent.
Or, according to the error message "error: release version 21 not
supported" you might not using a jdk 21.
On Tue, 12 Sept 2023 at 17:16, han
I tried to update the compiler release to 21, and got a compiler error like
this.
Error: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile
(default-compile) on project spring6-sample-boot: Fatal error compiling:
error: release version 21 not supported -> [Help 1]
esources-p has a resources parameter
https://github.com/apache/maven-resources-plugin/blob/master/src/main/java/org/apache/maven/plugins/resources/ResourcesMojo.java#L77
but as it is marked read-only, you're right that it's not documented, as it's
not expected to be conf
a resources parameter
https://github.com/apache/maven-resources-plugin/blob/master/src/main/java/org/apache/maven/plugins/resources/ResourcesMojo.java#L77
but as it is marked read-only, you're right that it's not documented, as it's
not expected to be configured in a pom.xml
https
Hi
Please try a never version of Maven and m-resources-p
Maven 3.3.9 is EOL - https://maven.apache.org/docs/history.html
m-resources-p has no parameter "resources"
You should use resource configuration on project level not plugin
configuration, like in example:
https://maven.apache.o
#x27;s behavior regarding readonly
> parameters in plugins. It seems that, starting from version 3.3.9, maven
> no longer ignores configuration parameters for readonly arguments.
>
> In more detail:
>
> I have a project that follows the `war` packaging lifecycle and I'd like
> to par
Hi Nikos,
That goal is only intended to be configured from project.build.resources.
You can rather use
https://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html
https://issues.apache.org/jira/browse/MRESOURCES-293
Delany
On Sun, 16 Jul 2023, 17:19 Nikos Dragazis, wrote
Hi everyone,
I'd like to expose a deviation in maven's behavior regarding readonly
parameters in plugins. It seems that, starting from version 3.3.9, maven
no longer ignores configuration parameters for readonly arguments.
In more detail:
I have a project that follows the `war`
retty sure that whatever is "corrupted" is in the
`C:\Users\user\.m2\repository\com\akathist\maven\plugins\launch4j\launch4j-maven-plugin`
directory right? This is an honest question: is there any place else
that the Versions Maven Plugin stack could potentially be using to know
if it s
Eclipse Aether, today Maven Resolver), as
> > Maven2
> > > had "resolving" code scattered all over the place, duplicated, and
> > causing
> > > bugs and maintenance problems. One of the major goals of Maven3 was to
> > > promise "smooth sai
smooth sailing" for Maven2 users, so full backward compatibility
> > was the goal as well. This is one of the reasons why the maven-compat
> > module exists today, it contains Maven2 "compatibility layer" (alternate
> > implementations from Maven2 times), for plugins that sti
Users List
Cc: Garret Wilson
Subject: Re: Maven Artifact Resolver not seeing latest plugins on Maven Central
on my machine
Hi,
Short hint
org.apache.maven.repository.RepositorySystem is not used for resolving by
versions plugin
It used
for repositorySystem.createPluginArtifact
One of the major goals of Maven3 was to
> promise "smooth sailing" for Maven2 users, so full backward compatibility
> was the goal as well. This is one of the reasons why the maven-compat
> module exists today, it contains Maven2 "compatibility layer" (alternate
> imp
why the maven-compat
module exists today, it contains Maven2 "compatibility layer" (alternate
implementations from Maven2 times), for plugins that still use Maven2
codebase. On the other hand, this "smooth sailing" for users introduced
quite challenging (technical) issues belo
've tried the latest
`org.codehaus.mojo:versions-maven-plugin:2.15.0` as well, with the same
results. I'm using this POM because it's available online and does not contain
any version ignores to cause confusion.)
I wanted to see what plugins were out of date, so I ran:
```bash
gt;>> https://github.com/globalmentor/globalmentor-root/blob/bce5bdbac7797b5b9114a72e5da2f4d76f3e24a7/pom.xml),
>>>
>>> which uses `org.codehaus.mojo:versions-maven-plugin:2.12.0`, which in
>>> turn (I am told) uses Maven Artifact Resolver. (Note that I've tried the
&g
h in
turn (I am told) uses Maven Artifact Resolver. (Note that I've tried the
latest `org.codehaus.mojo:versions-maven-plugin:2.15.0` as well, with
the same results. I'm using this POM because it's available online and
does not contain any version ignores to cause confusion.)
I wan
in
> turn (I am told) uses Maven Artifact Resolver. (Note that I've tried the
> latest `org.codehaus.mojo:versions-maven-plugin:2.15.0` as well, with
> the same results. I'm using this POM because it's available online and
> does not contain any version ignores to cause c
ilable online and
does not contain any version ignores to cause confusion.)
I wanted to see what plugins were out of date, so I ran:
```bash
mvn versions:display-plugin-updates
```
It shows this:
```
[INFO] The following plugin updates are available:
[INFO] maven-failsafe-plugin ..
Hello,
I try to optimize my maven build structure. My goal is that I can manage the
build plugins and properties globally. I have got a multi maven project with
this structure
Pom.xml
|
| service
|parent/pom.xml => has got a section to external spring-boot
|apiservice/pom.
Hi all
I've been having some issues with plugins that run out of lifecycle, or
fork the lifecycle. For example
mvn org.openrewrite.maven:rewrite-maven-plugin:4.22.2:run
-Drewrite.activeRecipes=org.openrewrite.java.cleanup.NoPrimitiveWrappersForToStringOrCompareTo
This fails on one of my mo
ms on this would to enhance the current
prerequisites dist-tool report [1], to add prerequisites for older plugins
releases, to have more precise view of history.
But by lack of interest or help of the general community, this has stayed at
dream level
Regards,
Hervé
[1]
https://ci-builds.apac
;too bad"
> - man that'd be great!
>
> Cheers,
> Rick
>
> E-mail: hant...@gmail.com
> Twitter: rack88 <http://www.twitter.com/rack88>
>
>
> On Tue, Jun 8, 2021 at 12:31 PM Benjamin Marwell
> wrote:
>
> > Just FYI,
> >
> > IBM, Zulu, Orac
t...@gmail.com
> Twitter: rack88 <http://www.twitter.com/rack88>
>
>
> On Tue, Jun 8, 2021 at 12:31 PM Benjamin Marwell
> wrote:
>
> > Just FYI,
> >
> > IBM, Zulu, Oracle and Microsoft are giving extended support to paying
> > customers until the 2030
8, 2021 at 12:31 PM Benjamin Marwell
wrote:
> Just FYI,
>
> IBM, Zulu, Oracle and Microsoft are giving extended support to paying
> customers until the 2030s. I guess maven plugins will stay on 1.8 for quite
> a while, but that's just a guess.
> At least most libraries haven&#x
Just FYI,
IBM, Zulu, Oracle and Microsoft are giving extended support to paying
customers until the 2030s. I guess maven plugins will stay on 1.8 for quite
a while, but that's just a guess.
At least most libraries haven't moved to Java 11 yet (and afaik won't move
to Java 11 in
quot;general guideline" (aside that Maven CLI 3.x is Java
7, Maven 4.x CLI will be Java 8, etc), due to large ecosystem (plugins in
ASF and outside) and plugin version numbers being "unbounded" (are per
plugins, not really bounded to Maven CLI), we try our best when we switch
plugin
away from Java 7 as I poke through some
projects like Surefire and maven-javadoc-plugin's latest builds/releases.
This is creating some chaos for my company, where we typically use the
maven-release plugin via the command-line, but rarely specify versions of
the plugins it is dependent upon in o
did that with the jpackage plugin and might do this with
> others as well.
>
> - Ben
>
>
> On Tue, 30 Mar 2021, 18:39 Antoine Mottier,
> wrote:
>
> > Hello,
> >
> > While looking at https://maven.apache.org/plugins/index.html I
> > realized that many cor
k on this
list.
If you find a milestone version good enough, just post it here and ask for
a release. We did that with the jpackage plugin and might do this with
others as well.
- Ben
On Tue, 30 Mar 2021, 18:39 Antoine Mottier, wrote:
> Hello,
>
> While looking at https://maven.apache.org
Hello,
While looking at https://maven.apache.org/plugins/index.html I
realized that many core plugin versions are actually milestone version
(e.g. deploy: 3.0.0-M1).
It seems that some of them are release quite a long time ago (e.g.
deploy: 2018-09-23). I was wondering what is the
Hi,
Can someone explain the tag found in plugins?
https://maven.apache.org/guides/mini/guide-using-extensions.html
It seems like instead of being a plugin that provides lifecycle
enhancements using this tag, a lot of plugins should rather be extensions,
that can optionally accept configuration
Hello
$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:resolve-plugins
...
Downloading:
https://repo.maven.apache.org/maven2/com/puppycrawl/tools/checkstyle/8.29/checkstyle-8.29.pom
Downloaded:
https://repo.maven.apache.org/maven2/com/puppycrawl/tools/checkstyle/8.29
Hi,
the Maven Release Plugin 3.0.0-M1... supports of writing own rules #1 ..
etc.
Furthermore I would use simply things like versions-maven-plugin
otherwise (or tycho versions plugin to support OSGi with some script
steps in Jenkins for git magic (which I used a long time ago)...
What is the p
Hi Karl,
Unfortunately, the Maven-Release-Plugin doesn't cut it for us.
1. It doesn't support Tycho builds with regard to versions [1]
2. We do use release branches on our products (Eclipse RCP and docker
containers) to do some acceptance testing.
That's why we used to use the Atlassian Gitflow
Hi,
On 02.11.20 11:27, Nick Stolwijk wrote:
Hi folks,
We are struggling with our buildserver (Jenkins) and the Git-Flow Maven
Plugin[1] with regards to execute the Maven executable to run specific
goals and phases during release (i.e. run versions plugin to change version
or run `mvn verify` to
I'm not familiar with Maven Invoker, but the Maven Invoker Plugin does not
have such code.
It will call setMavenHome only if there's a configured value:
https://github.com/apache/maven-invoker-plugin/blob/dfd3c3680f31cb36ef1c14c18f4ea8b8d6115151/src/main/java/org/apache/maven/plugi
Thanks,
I looked at the Maven Release Plugin and I see that the logic of where
Maven is installed is not in the Maven-Invoker, but in the release plugin
[1]. There is some logic on how to 'find' Maven, using environment
variables like 'maven.home', 'MAVEN_HOME' and 'M2_HOME'. Does this mean
that t
Maybe have a look at Maven Invoker:
https://maven.apache.org/shared/maven-invoker/
(it's what the Maven Invoker Plugin and Maven Release Plugin use)
On Mon, Nov 2, 2020 at 11:28 AM Nick Stolwijk
wrote:
> Hi folks,
>
> We are struggling with our buildserver (Jenkins) and the Git-Flow Maven
> Plug
Hi folks,
We are struggling with our buildserver (Jenkins) and the Git-Flow Maven
Plugin[1] with regards to execute the Maven executable to run specific
goals and phases during release (i.e. run versions plugin to change version
or run `mvn verify` to check project).
The gitflow-m-p uses a flag t
There's a migration plan for moving plugin from Maven2 to Maven3[1]
As long as these steps haven't been finished, but people expect us to do
releases due to bugfixes or improvements, we must use some pre 3.0.0 as
version, hence the milestones.
For the plugins that are marked as M,
; > (
> > >
> >
> https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/
> > > )
> > > or the tests which are running on them:
> > >
> > >
> >
> https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-release/j
ob/master/
> > )
> > or the tests which are running on them:
> >
> >
> https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/lastCompletedBuild/testReport/
> >
> >
> > The question based on that is comming up:
> >
> >
ox/job/maven-release/job/master/
> )
> or the tests which are running on them:
>
> https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/lastCompletedBuild/testReport/
>
>
> The question based on that is comming up:
>
> What do you define as
n-release/job/master/lastCompletedBuild/testReport/
The question based on that is comming up:
What do you define as "unstable" ? All of those plugins are already
running very long (I mean very long) in production environments ... so
of course sometimes people find bugs ...
As Enric
gt; My name is Lukas, I'm a software engineer working at some very little
> > company located in Switzerland (called Quatico).
> >
> > I wanted to let you know that the versioning that is used in (as far as I
> > can see) all Maven Plugins (e.g. Apache Maven Install
kas, I'm a software engineer working at some very little
> company located in Switzerland (called Quatico).
>
> I wanted to let you know that the versioning that is used in (as far as I
> can see) all Maven Plugins (e.g. Apache Maven Install Plugin 3.0.0-M1) is
> very confusing .
>
Hi All & Maven Devs
My name is Lukas, I'm a software engineer working at some very little
company located in Switzerland (called Quatico).
I wanted to let you know that the versioning that is used in (as far as I
can see) all Maven Plugins (e.g. Apache Maven Install Plugin 3.0.0-M1
SHA512/256 support has been added to Nexus
in https://issues.sonatype.org/browse/NEXUS-21802 recently one cannot correctly
create/deploy those checksums with Maven standard plugins due to
https://issues.apache.org/jira/browse/MSHARED-704 and
https://issues.apache.org/jira/browse/MDEPLOY-271
lowing child pom:>
>
https://github.com/Serranya/de.serra.rocker-for-takes-maven-plugin/tree/wtf>
> (again wtf branch)>
>
> When I execute `mvn verify` on the parent pom the plugins>
> (spotbugs,checkstyle,failsafe,...) specified in the build section get>
>
the plugins
(spotbugs,checkstyle,failsafe,...) specified in the build section get
executed as expected.
But when I execute `mvn verify` in the child pom they don't get executed.
Somehow it seems like the plugins don't get inherited.
What confuses me additionally is the following:
I added
Excellent enhancement ; thank you Brian & Sonatype.
> Report issues or ideas here:
> https://github.com/sonatype/ossindex-maven/issues
As requested I submitted my feedback as an RFE (
https://github.com/sonatype/ossindex-maven/issues/10) to report possible
fixes on the vulnerabilities.
Regards,
--mobile
> On Jul 25, 2018, at 9:24 PM, Mark Derricutt wrote:
>
> On 26 Jul 2018, at 12:55, Brian Fox wrote:
>
> Find the Maven Plugin docs here:
> https://sonatype.github.io/ossindex-maven/maven-plugin/
>
> This looks awesome! One nit pick tho - the XML plugin definition has a bad
> on th
On 26 Jul 2018, at 12:55, Brian Fox wrote:
> Find the Maven Plugin docs here:
> https://sonatype.github.io/ossindex-maven/maven-plugin/
This looks awesome! One nit pick tho - the XML plugin definition has a bad
`` on the `` line.
Will be interesting to see how the results compare to the OWASP d
You probably know Sonatype for our work in the Maven community, Nexus
Repository Manager, and for hosting Central. You may not know that for
the last 7 years we've also been leading the way in solutions that
allow developers to innovate faster and be able to improve security,
license compliance and
From: Paul Benedict
Sent: Tuesday, February 6, 2018 7:00 PM
To: users@maven.apache.org
Subject: Metadata multiplicity of maven-script-ant plugins
I have a question based on these two references:
*)
https://maven.apache.org/plugin-tools-archives/plugin-tools
I have a question based on these two references:
*)
https://maven.apache.org/plugin-tools-archives/plugin-tools-3.2/maven-plugin-plugin/examples/ant-mojo.html
*) https://books.sonatype.com/mcookbook/reference/ch04s04.html
In each reference, the reader is directed to create one xxx.build.xml and
I'm sure this has been discussed before but I could only find this thread from
2011 with no replies.
https://www.mail-archive.com/users@maven.apache.org/msg118612.html
I had expected that build.plugins.plugin.dependencies would be resolved from
pluginRepositories, so I have some jars published
Hi Jochen,
Yes, I just wanted to show you some code how to get the POM/model, and at
that point, you can do _whatever you want_ to it (this is how for example
nexus staging plugin "installs" itself btw). Still, you need to be very
careful _what_ you do here... is VERY easy to screw things up.
For
Hi, Tamas,
thanks for the link to the configuration-maven-plugin. If I do get
this right, you are essentially introducing a way to reuse
configuration snippets within the POM.
Which would of course be an interesting idea. I still wonder, whether
it isn't possible to find another plugin within my
Jochen,
for how it could work, take this example (demo plugin doing similar thing
you want):
https://github.com/cstamas/configuration-maven-plugin
That above if clearly "hacking" :)
As Herve said, no "proper" way to do it, except adding "standard" property
(like those mentioned by Herve) and sub
On Fri, Feb 3, 2017 at 10:22 AM Stuart McCulloch wrote:
> Circling back to the original question: yes you can override components in
> recent versions of Maven but there are some caveats. First your component
> must be visible to the plugin (ie be in the same realm or a parent/imported
> realm li
On 3 Feb 2017 16:44, "Laird Nelson" wrote:
On Fri, Feb 3, 2017 at 1:15 AM Hervé BOUTEMY wrote:
> notice:@Component we're using in a Mojo is from Maven Plugin Tools
> org.apache.maven.plugins.annotations.Component [1]
>
Right; I (now :-)) understand this part and all of the things related to it
t; >>
>>> >> Best,
>>> >> Laird
>>> >>
>>> >> On Wed, Feb 1, 2017 at 11:59 AM Robert Scholte
>>> >>
>>> >> wrote:
>>> >> > No, plugin annotation are used to generate a plugin descript
On Fri, Feb 3, 2017 at 1:15 AM Hervé BOUTEMY wrote:
> notice:@Component we're using in a Mojo is from Maven Plugin Tools
> org.apache.maven.plugins.annotations.Component [1]
>
Right; I (now :-)) understand this part and all of the things related to it.
The part I didn't get was that there's onl
On Fri, Feb 3, 2017 at 10:27 AM, Hervé BOUTEMY wrote:
> b) is probably possible, but not recommended
A few words on how this would work, and *why* it is not recommended? I
am not interested in finding a solution for all Maven users, Just
something that works for me and my team.
Jochen
--
The
s:
>>
https://maven.apache.org/components/plugin-tools/maven-plugin-tools-annot
>> a
>>
>> > tions/index.html>
>> >
>> > >> Robert
>> > >>
>> > >> On Wed, 01 Feb 2017 19:21:09 +0100, Laird Nelson
>>
>>
>>
&
;> >
> >> > wrote:
> >> > > Thanks. But isn't _that_, in turn, replaced by JSR-330? This is
> >>
> >> what
> >>
> >> > > I'm
> >> > > confused about.
> >> > >
> >> >
t; >> >
> >> > I have this faint sense that Sisu and Guice are at the core of
Maven
> >> > these
> >> > days, with a Plexus layer on top.
> >> >
> >> > This makes me think that perhaps I should be using different
> &g
b) is probably possible, but not recommended
When we want to share some configuration between plugins, the usual solution is
to define a convention on a property name: see for example maven.test.skip that
is supported both by maven-compiler-plugin [1], Surefire [2], nar-maven-plugin
in
t; wrote:
> > >> > I apologize in advance for the inarticulate nature of this question.
> > >> >
> > >> > I have this faint sense that Sisu and Guice are at the core of Maven
> > >> > these
> > >> > days, with a Plexus laye
On Thu, Feb 2, 2017 at 1:51 AM Robert Scholte wrote:
> So basically it is still the same issue as a week or so ago: how to select
> a different implementation for an interface.
> Doing this within your code:
> AFAIK that's not possible, and I wonder if even JSR330 supports it.
>
Thanks. The add
So basically it is still the same issue as a week or so ago: how to select
a different implementation for an interface.
Doing this within your code:
AFAIK that's not possible, and I wonder if even JSR330 supports it.
If you don't specify a specific hint (or name), the default implementation
w
On Wed, Feb 1, 2017 at 1:27 PM Robert Scholte wrote:
> bq. If you want to use JSR-330, you must understand that your code won't
> be compatible with Maven 2 or 3.0.x but only with Maven 3.1.0+
>
> this is probably the reason why *I* haven't seen it used that much.
>
Sure. In my case, this won't
lexus.github.io/plexus-containers/plexus-component-metadata/plugin-info.html
On Wed, 01 Feb 2017 21:53:49 +0100, Laird Nelson
wrote:
So...sorry, I am still confused. :-( If I look at the Maven and JSR 330
guide, especially with regard to plugins (
http://maven.apache.org/maven-jsr330.html
So...sorry, I am still confused. :-( If I look at the Maven and JSR 330
guide, especially with regard to plugins (
http://maven.apache.org/maven-jsr330.html#How_to_use_JSR-330_in_plugins),
then @Component is not used (see line 17 in the code sample). Are you
saying this is a mistake?
I think
>> > I apologize in advance for the inarticulate nature of this
question.
>> >
>> > I have this faint sense that Sisu and Guice are at the core of
Maven
>> > these
>> > days, with a Plexus layer on top.
>> >
>> > This makes me think
> >>
> >> Robert
> >>
> >> On Wed, 01 Feb 2017 19:21:09 +0100, Laird Nelson
> >> wrote:
> >>
> >> > I apologize in advance for the inarticulate nature of this question.
> >> >
> >> > I have this faint sense th
e using different
annotations
> in
> my maven plugins than @Component etc.
>
> Is this (
>
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
> still the official guide for writing Maven plugins? If I wanted to
> inject
> some named Plexus
h a Plexus layer on top.
> >
> > This makes me think that perhaps I should be using different annotations
> > in
> > my maven plugins than @Component etc.
> >
> > Is this (
> >
> https://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
> &
and Guice are at the core of Maven
these
days, with a Plexus layer on top.
This makes me think that perhaps I should be using different annotations
in
my maven plugins than @Component etc.
Is this (
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
still the official
have this faint sense that Sisu and Guice are at the core of Maven these
> days, with a Plexus layer on top.
>
> This makes me think that perhaps I should be using different annotations in
> my maven plugins than @Component etc.
>
> Is this (
> https://maven.apache.org/g
I apologize in advance for the inarticulate nature of this question.
I have this faint sense that Sisu and Guice are at the core of Maven these
days, with a Plexus layer on top.
This makes me think that perhaps I should be using different annotations in
my maven plugins than @Component etc.
Is
Hi,
I'd like to create a plugin, which is intended to generate resources
for a web application.
In other words, the target directory would be the value, which is
typically configured as the webappDirectory property of the
maven-war-plugin.
To get that value, I see two options:
a) I create a pro
> includes a few platform specific plugins.
> In other words some of those plugins have o/s flag equal to “win32” and some
> others “linux”.
>
> Having this flag breaks my maven build because when building the feature on
> windows it cannot see the linux plugins and vice-vers
Hi
I am currently developing an eclipse RCP application and one of my features
includes a few platform specific plugins.
In other words some of those plugins have o/s flag equal to "win32" and some
others "linux".
Having this flag breaks my maven build because when bui
Any pointers please?
Thanks
Gaurav
On Mon, Sep 19, 2016 at 5:51 PM, Gaurav Gupta
wrote:
> Hi,
>
> I have a use case where I need to exclude transitive dependency of a
> plugin.
> I am using following plugin
>
> org.codehaus.mojo
> cobertura-maven-plugin
> 2.7
>
> This has transitive dependency
Hi,
I have a use case where I need to exclude transitive dependency of a plugin.
I am using following plugin
org.codehaus.mojo
cobertura-maven-plugin
2.7
This has transitive dependency on logback-classic. To exclude this
dependency, I tried following two options
1.
org.codehaus.
The Android Maven Plugin team is pleased to announce the releases of
Android Maven Plugin 4.4.1 -
http://www.simpligility.com/2016/01/android-maven-plugin-4-4-1-released/
Android NDK Maven Plugin 1.1.0 -
http://www.simpligility.com/2016/02/android-ndk-maven-plugin-1-1-0-released/
With help of
thanks, i doubt a new wagon option would subtract from the maven build
experience if broken deps are resolved back to thier source
https://jitpack.io/#l2x6/srcdeps-maven-plugin/0.0.11 does it as
transparent SAAS.
On Mon, Dec 7, 2015 at 11:58 AM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 12/7/15 8:
Hi,
On 12/7/15 8:15 PM, james northrup wrote:
I would like to intercepts maven repo requests and builds the ones
that fit a certain pattern of buildable SCM repos, specifically using
git[hub] repositories.
Maven is based on binary artifacts and NOT on source artifacts...
what pom options ex
I would like to intercepts maven repo requests and builds the ones
that fit a certain pattern of buildable SCM repos, specifically using
git[hub] repositories.
what pom options exist to control wagon so that a similar solution can
be added to a parent pom to utilize plugin to build or exec when bu
I had this list in mind: https://maven.apache.org/plugins/
I retrieved it by typing "maven plugins" in my favorite search engine.
Sander Verhagen
[ san...@sanderverhagen.net ]
NOTICE: my e-mail address has changed. Please remove verha...@sander.com now
and start
1 - 100 of 1956 matches
Mail list logo
