The documentation for publishing to Central is very comprehensive. I
suggest you take a closer look. Specifically
https://central.sonatype.org/register/central-portal/
https://central.sonatype.org/publish/producer-terms/
https://repo1.maven.org/terms.html
And maybe contact a lawyer and Sonaty
Fri, 1 Mar 2024, /Olivier Lamy/:
users will not be able to rebuild from sources.
is it a requirement? No real idea as already said in this thread, you
need to ask Sonatype.
But it breaks the concept of opensource as you cannot build from the sources :)
The sources uploaded to Maven Central a
e <
> > > florent.bivi...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I'm working on an open-source project that we want to release to
> > Maven
> &g
024 at 1:31 PM Florent Biville <
> > florent.bivi...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm working on an open-source project that we want to release to
> Maven
> > > > Central
Maven
> > > Central in the coming weeks.
> > >
> > > The project currently includes a plugin dependency that is NOT
> > open-source
> > > (nor in a public GitHub repository). Is that a blocker for releases to
> > > Maven Central? I kno
t that we want to release to Maven
> > > Central in the coming weeks.
> > >
> > > The project currently includes a plugin dependency that is NOT
> > open-source
> > > (nor in a public GitHub repository). Is that a blocker for releases to
> > > Maven
plugin dependency that is NOT
> open-source
> > (nor in a public GitHub repository). Is that a blocker for releases to
> > Maven Central? I know it would be for regular dependencies and plugins,
> but
> > I'm not 100% sure about plugin dependencies in particular (although I
> would
> > guess it's the same).
> >
> > Any input would be appreciated,
> >
> > Best regards,
> > Florent
> >
>
Hub repository). Is that a blocker for releases to
> Maven Central? I know it would be for regular dependencies and plugins, but
> I'm not 100% sure about plugin dependencies in particular (although I would
> guess it's the same).
>
> Any input would be appreciated,
>
> Best regards,
> Florent
>
e for regular dependencies and plugins, but
I'm not 100% sure about plugin dependencies in particular (although I would
guess it's the same).
Any input would be appreciated,
Best regards,
Florent
Hi Alexander,
this is an old thread, but no one has replied yet.
While I think this is possible – what are you trying to achieve?
Or in other words: WHY do you need the dependencies unpacked? What do
you do with them?
Regards,
Ben
On 2020/08/19 18:23:06, Alexander Broekhuis wrote:
> Hi all,
>
Hi all,
I currently have a setup in which I have some custom artifacts that I use
as dependencies and unpack using unpack-dependencies.
This all works great, but now I also have a custom plugin which needs one
of the custom artifacts as dependency. I don't see those dependencies being
unpacked. I
Karl Heinz Marbaise-3 wrote
>>I thought I could just enter it once as a plugin dependency in
>> the user project pom - assuming it would be the only one.
>
> You can give this via the plugin configuration and which means your
> plugin must resolve it's dependencies and make a required download fo
The users of my plugin define a dependency which the mojo unpacks and
extracts certain files from.
You know that such a plugin already exists? maven-dependency-plugin:unpack /
unpack-dependencies ?
https://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
Hi,
On 13/09/17 23:29, Adam Hardy wrote:
On 12/09/17 18:05, Adam Hardy wrote:
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I
can only get artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to
On 12/09/17 18:05, Adam Hardy wrote:
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only
get artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to my mind: Why do you need the dependencies o
Hi Adam,
On 12/09/17 18:05, Adam Hardy wrote:
Hi,
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only get
artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to my mind: Why do you need the
Hi,
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only get
artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
Presumably I call something like project.getPlugin(key).getDependencies()?
If the 'key' required for proje
refore I
declared dependency on it inside the section. The plugin (and
compiler) are only needed to build the artifact, not to use it.
The problem is that it seems the *dependency:unpack-dependencies* Maven
plugin only looks for project dependencies, not plugin dependencies.
*dependency:unpack*
Von: Christofer Dutz
Gesendet: Dienstag, 29. März 2016 19:14
An: users@maven.apache.org
Betreff: AW: Plugin dependencies to artifacts of the same build?
Sorry ... that email went off unintentionally ... well to continue ... if the
plugin is part of the
oogle-closure-library-third-party-0.0-20150902-b129bb9e.jar
Can anyone here explain why?
Chris
Von: Christofer Dutz
Gesendet: Dienstag, 29. März 2016 19:13
An: users@maven.apache.org
Betreff: AW: Plugin dependencies to artifacts of the same build?
So I added
: Christofer Dutz
Gesendet: Dienstag, 29. März 2016 16:14
An: users@maven.apache.org
Betreff: Plugin dependencies to artifacts of the same build?
Hi,
I am currently trying to sort out some glitches in my Maven build.
I am working on a new flexjs-maven-plugin as part of my efforts to migrate more
Hi,
I am currently trying to sort out some glitches in my Maven build.
I am working on a new flexjs-maven-plugin as part of my efforts to migrate more
and more of the Apache Flex project to Maven.
In the reactor I have a a compiler, a maven-plugin providing a custom lifecycle
mapping for Fle
ion:
> http://stackoverflow.com/a/7079876/345845.
>
> Karl-Heinz is everywhere :-).
>
> 2014-09-10 16:50 GMT+02:00 David Hoffer :
>
> > Similar to dependency:tree for project dependencies how can I get a
> similar
> > list of plugin dependencies used in the build?
&
Found that, seems to match your question:
http://stackoverflow.com/a/7079876/345845.
Karl-Heinz is everywhere :-).
2014-09-10 16:50 GMT+02:00 David Hoffer :
> Similar to dependency:tree for project dependencies how can I get a similar
> list of plugin dependencies used in the build?
>
Similar to dependency:tree for project dependencies how can I get a similar
list of plugin dependencies used in the build?
-Dave
In fact 1.1 is only on my machine. I installed it from source.
Anyway, I went back to 1.0 and the same results.
However, it's working now, as I just had to add ant.
On Sun, Jul 27, 2014 at 8:33 AM, Thomas Sundberg wrote:
> On 27 July 2014 12:02, Mansour Al Akeel wrote:
>> Thomas,
>> Thank you f
Issue resolve.
My bad. I had to explicitly include ant dependency.
On Sun, Jul 27, 2014 at 6:02 AM, Mansour Al Akeel
wrote:
> Thomas,
> Thank you for the fast response. Unfortunately this is not the case.
> I have generate a maven plugin project from the archetype, and add:
>
>
>
On 27 July 2014 12:02, Mansour Al Akeel wrote:
> Thomas,
> Thank you for the fast response. Unfortunately this is not the case.
> I have generate a maven plugin project from the archetype, and add:
>
>
> org.apache.ddlutils
> ddlutils
> 1.1
>
>
Thomas,
Thank you for the fast response. Unfortunately this is not the case.
I have generate a maven plugin project from the archetype, and add:
org.apache.ddlutils
ddlutils
1.1
I added the import statement to my Mojo:
import org.apache.ddlut
On 27 July 2014 10:05, Mansour Al Akeel wrote:
> I am writing a custom plug in. This plugin has other dependencies. How
> can I make these dependencies available when running the plugin
> without having to add them manually ??
I assume that your dependencies are declared in your plugin project.
I
I am writing a custom plug in. This plugin has other dependencies. How
can I make these dependencies available when running the plugin
without having to add them manually ??
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache
>
> Also, do i need to redefine 'central' it looks redundant to me
It's best-practice IMO. It ensures that the central definition declared in
the super-POM is overwritten with a dummy (not working) URL. It will/should
then be handled by the mirror so that it is redirected to the internal
mirror.
Hi Ander
that makes sense
now i only have
product-repo
*,!plugin-central
Internal Maven Repository Manager
http://repos.xxx.com:8081/nexus/content/groups/public
Also, do i need to redefine 'central' it looks redundant to me
Thanks
-D
On Mon, May 26,
For my solution on this topic I didn't declare a mirror for
'plugin-central', i.e. I didn't have the 'plugin-repo' mirror declaration.
I does not add anything as it is only a mirror for one repo.
/Anders
On Sun, May 25, 2014 at 3:00 AM, Dan Tran wrote:
> I got some thing working
>
> 1. at my r
I got some thing working
1. at my repo manager, create a proxy, called plugin-central, to host
another central.maven.org/maven2
2. reconfigure my global settings.xml with the following contents. Please
help to review this content
product-repo
*,!plugin-central
Internal M
It will if you use the same id, ie 'central'.
/Anders (mobile)
Den 24 maj 2014 09:36 skrev "Dan Tran" :
> Anders' suggestion sounds very logical
>
> however, i found this at super pom
>
>
>
> central
> Central Repository
> http://repo.maven.apache.org/maven2
> defa
Anders' suggestion sounds very logical
however, i found this at super pom
central
Central Repository
http://repo.maven.apache.org/maven2
default
false
central
Central Repository
http://repo.maven.apache.org/m
On 6 May 2014 20:23, Anders Hammar wrote:
> >
> > Presumably you are trying to separate artifacts used by plugins during
> > your build (where you might use e.g. GPL licensed modules) from artifacts
> > used as dependencies in your project proper (where using that same GPL
> > licensed modules wo
>
> Presumably you are trying to separate artifacts used by plugins during
> your build (where you might use e.g. GPL licensed modules) from artifacts
> used as dependencies in your project proper (where using that same GPL
> licensed modules would make your legal department scream) by separating t
On 06.05.2014 09:07, Dan Tran wrote:
Ofcourse, I do have Maven repo manager ̣ nexus at this time), however still
struggle on how to get only plugin's artifact goto one proxy and others
goto to another proxy using mirror settings.
Are you able to do so?
-Dan
I'm none to sure that this would eve
Hello,
It would be good if Proxy requests would actually carry the repository URLs or
names the request is actually proxied for. I havent seen a proxy which allows
configuration in this regard (and therefore I think the protocol does not
provide this extra information)
Bernd
> Am 06.05.2014 u
Ofcourse, I do have Maven repo manager ̣ nexus at this time), however still
struggle on how to get only plugin's artifact goto one proxy and others
goto to another proxy using mirror settings.
Are you able to do so?
-Dan
On Mon, May 5, 2014 at 11:59 PM, Christian Domsch wrote:
> Hi Dan,
>
>
Hi Dan,
Did you consider using nexus? There you can setup any kind of strange
repo setup your mind can come up with ;-) For your case, create one repo
for your project stuff and one repo for your plugin stuff. Create a
group for both for easy access and control access by authorization...
Chr
Thanks Barrie,
Will see what I can can do.
On Mon, May 5, 2014 at 5:04 PM, Barrie Treloar wrote:
> On 6 May 2014 09:21, Dan Tran wrote:
>
> > for legal purpose ( btw, please dont drill me here), I would like to use
> > one mirror as a gate way for all of of my project dependencies,and
> anoth
On 6 May 2014 09:21, Dan Tran wrote:
> for legal purpose ( btw, please dont drill me here), I would like to use
> one mirror as a gate way for all of of my project dependencies,and another
> mirror as a gate way for all of my plugins and their dependencies
>
>
> is it possible? Posting a settings
for legal purpose ( btw, please dont drill me here), I would like to use
one mirror as a gate way for all of of my project dependencies,and another
mirror as a gate way for all of my plugins and their dependencies
is it possible? Posting a settings.xml config here is very much appreciated
Thank
Hi,
Thanks for your answer.
I'll try to explain better what I am trying to do.
I have an artifact, say, com.mycompany.ant-build-utils containing ant
scripts that do some interaction with SCM an CI, that we need to use during
the build. Now, as you say, it is untarred manually on a shared drive a
Hi,
Not sure I understand what your issue is.
Are you depending on some filesystem path?
What's the displayed error?
-- Baptiste
Le 16 mai 2013 18:42, "arnaud dufranne" a écrit :
> Hi,
>
> I am currently looking into writing an ant based maven plugin. My main
> issue is that this plugin depends
Hi,
I am currently looking into writing an ant based maven plugin. My main
issue is that this plugin depends on an artifact (tar.gz in a company
repository) containing a few ant scripts, whose tasks should be run when
using the plugin.
I declared the dependency in my plugin's pom.xml, and the plu
Hi,
I am currently looking into writing an ant based maven plugin. My main
issue is that this plugin depends on an artifact (tar.gz in a company
repository) containing a few ant scripts, whose tasks should be run when
using the plugin.
I declared the dependency in my plugin's pom.xml, and the plu
und entfaltet
> >>> keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit
> >>> von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> >>> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas
> >>
aire prévu, nous te demandons avec bonté que pour satisfaire
>>> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
>>> de ceci est interdite. Ce message sert à l'information seulement et n'aura
>>> pas n'importe quel
estinataire prévu, nous te demandons avec bonté que pour satisfaire
>> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
>> de ceci est interdite. Ce message sert à l'information seulement et n'aura
>> pas n'importe quel effet léga
e ceci
> est interdite. Ce message sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: Override plugin dependencies?
> From: newman...@gmail.com
> Date: Mon, 20 Aug 2012 18:50:16 -0600
> To: users@maven.apache.org
>
> I have a couple of quick questions ab
I have a couple of quick questions about plugins and their dependencies. I am
on a private network so it is sometimes difficult to get a plugin and all it's
dependencies.
1. I am trying to use the maven-release-plugin and during the deploy phase it
is looking for the maven-javadoc-plugin ver
Hello,
I wonder if you try to declare checktyle plugin too in build/plugins
section with your dependency.
That should works for maven3
2011/11/15 Nate Stoddard :
> I'm resending this because the formatting got butchered the first type.
> Sorry for the duplicate.
>
> Nate Stoddard
>
> =
>
> I'
I'm resending this because the formatting got butchered the first type.
Sorry for the duplicate.
Nate Stoddard
=
I'm trying to use the new Maven 3 style of generating reports, but I'm
having problems with one in particular. I have some custom Checkstyle
checks, but I'm not able to add t
I'm trying to use the new Maven 3 style of generating reports, but
I'm having problems with one in particular. I have some custom
Checkstyle checks, but I'm not able to add the dependency in the right
spot to make everything work. Here's part of my POM:
org.apache.maven.plugins
maven-site-p
It is a bit hard to know what you want to do but it seems that you are
using module (a) to build something that needs to be deployed to
someplace prior to module (b) trying to use it.
I guess that the trick it give Maven a property that tells Module A
where to deploy the Antrun file and tells
I'd like to have a multi-module project in which module (a) builds the
code of an ant task, and module (b) lists module (a) as a dependency
of the antrun plugin to use it. I have a vague memory that this isn't
going to work in the reactor. Can anyone tell me if I'm inventing a
problem?
---
Hi all,
I have a parent pom that declares the antrun plugin in pluginManagement
section. It supplies a version, and a set of dependencies to fix the version
of Ant used.
I then have a child project that uses the antrun plugin and adds a reactor
library to the list of dependencies.
When the parent
Hi,
You can use artifact exclusions for plugin dependencies as well.
For example
Hello,
Is there any way how to exclude plugin dependency?
I have parent pom with plugin
...
org.apache.maven.plugins
maven-checkstyle-plugin
Hello Maven users,
Maven dependecy:resolve-plugins resolved plugin dependency from
repository and not from pluginRepository. Isn't that a bug?
Plugin used is http://code.google.com/p/maven-annotation-plugin/ ,
version 2.0.2. It's available at central but not all of it's
dependencies are there (an
Adding pluginRepositories to my settings fixed it nicely. Thanks for the
link, as well.
On Thu, Mar 17, 2011 at 6:35 AM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Jason Nerothin wrote:
>
> The drools libs are out on the jboss snapshots repository and the
>> connector
>> lib is bein
Jason Nerothin wrote:
The drools libs are out on the jboss snapshots repository and the connector
lib is being staged in archiva. In both cases, they're sitting right where I
expect them to be in my local repository.
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xComp
I'm in the process of building out my first plugin. The simple example
worked fine, and I get it to build to my local repo with clean install.
However, at runtime, it can't locate a handful of jars:
[ERROR] Failed to execute goal com.xxx.xxx:xxx-maven-plugin:1.0:alive
(default-cli) on project xxx
Hi Stephen,
The organizational pom can prescribe the use of the most recently
released ruleset.
The next version of the ruleset would "technically" be checked against
the previous version, but as rulesets are not java code the check will
not be applied on that artifact.
True.
But its a littl
The organizational pom can prescribe the use of the most recently
released ruleset.
The next version of the ruleset would "technically" be checked against
the previous version, but as rulesets are not java code the check will
not be applied on that artifact.
-Stephen
On 17 December 2010 11:55, A
Hi Wayne,
thanks for the advice.
What's the best way to resolve this kind of chicken-and-egg problem
without introducing too many extra projects just to break the cycle? Any
This is exactly what you have to do. The rulesets should be packaged
and versioned independent of the project. Ideally
> What's the best way to resolve this kind of chicken-and-egg problem
> without introducing too many extra projects just to break the cycle? Any
This is exactly what you have to do. The rulesets should be packaged
and versioned independent of the project. Ideally you'd have one
corporate ruleset a
Hi all,
I am experiencing a kind of chicken-and-egg problem in my usage of the
m-pmd-p, the m-checkstyle-p, and the m-license-p. All these plugins are
capable of loading their respective configurations (rulesets or license
headers) from the plugin's classpath. As such it seems sensible to
create d
On 16 August 2010 15:16, janne postilista wrote:
> Heh. Not the first headache I have with this plugin...
>
> I'm curious, care to briefly explain what's the fundamental problem
> with maven-glassfish-pluginwhy is having a plugin that depends on
> another plugin a problem?
>
In Maven 2.x the
Heh. Not the first headache I have with this plugin...
I'm curious, care to briefly explain what's the fundamental problem
with maven-glassfish-pluginwhy is having a plugin that depends on
another plugin a problem?
Does this somehow explain the mystery why the version range gets resolved in
m
Ohhh!!!
You're using maven-glassfish-plugin well that explains it.
Here is the golden rule.
Friends don't let friends use the java.net maven repositories...
Here is another bad example, they have a plugin that depends on another
plugin... which will mess up big big big time unless you a
Thanks for the suggestion. This cured my build:
org.glassfish.maven.plugin
maven-glassfish-plugin
2.1
...
you define the exclusions on your dependencies and that will purge them from
your entire dependency tree
On 16 August 2010 14:49, janne postilista wrote:
> I'm not sure what that means exactly?
>
> The problem is nested a few levels down in my dependencies:
>
> my webapp -> maven-glassfish-plugin
I'm not sure what that means exactly?
The problem is nested a few levels down in my dependencies:
my webapp -> maven-glassfish-plugin -> maven-plugin -> maven-plugin-api
maven-plugin's pom.xml has the problematic reference to maven-plugin-api
version [2.0,)
Is your suggestion still usable in th
have you considered using exclusions to knock out the problematic transitive
dep and then add in a corrected version for your own project
On 16 August 2010 14:41, janne postilista wrote:
> It's not the solution I want, but can I somehow tell in my pom.xml
> that if a dependency has defined it's o
It's not the solution I want, but can I somehow tell in my pom.xml
that if a dependency has defined it's own dependency as:
org.apache.maven
maven-plugin-api
[2.0,)
compile
FORCE it to use 2.0 exactly?
Tried adding to my pom.xml:
And when I change my direct dependency in pom.xml
from
org.apache.maven
maven-plugin-api
[2.0,)
compile
to
org.apache.maven
maven-plugin-api
2.0
compile
linux build finds the
Thanks, but it doesn't seem to be a Hudson issue.
Installed maven 2.2.1 (same as my local windows version) to the linux
machine and trying the same build from there, I get:
[INFO]
[ERROR] BUILD ERROR
[INFO] -
1. This is a hudson issue so report on the hudson list.
On 16 August 2010 12:54, janne postilista wrote:
> My build craps out because
>
> [HUDSON] Archiving
> /home/zzz/.hudson/jobs/ci-build/workspace/trunk/webapp/pom.xml to
>
> /home/zzz/.hudson/jobs/ci-build/modules/zzz$webapp/builds/2010-08-16
When I add this dependency directly to my pom.xml, build still works locally:
org.apache.maven
maven-plugin-api
[2.0,)
compile
So it seems dependency version range resolving works after all. If I
clear my repository before doing th
My build craps out because
[HUDSON] Archiving
/home/zzz/.hudson/jobs/ci-build/workspace/trunk/webapp/pom.xml to
/home/zzz/.hudson/jobs/ci-build/modules/zzz$webapp/builds/2010-08-16_14-27-53/archive/zzz/webapp/1.0-SNAPSHOT/pom.xml
[INFO] -
We are all mortals...:-)
However, it looks like it has been fixed in 3.0-alpha-1. Mike, try
3.0-alpha-5! When you've tried it, there is no going back...:-)
http://www.sonatype.com/people/2009/11/maven-30-new-and-improved-formula/
/Anders
On Tue, Dec 8, 2009 at 06:55, Wayne Fay wrote:
> > Child
> Child project 2 has the exact same setup "however" it changes the dependency
> defined in the plugin to be dependent on a different project.
>
> configurations. It always seems that the first time a plugin is loaded that
> is the classpath used for that plugin whenever it is executed.
This is a
I haven't run into this use case, but I would think it should work. Have you
tried other Maven versions like 2.0.x? Also, I would strongly suggest you
try out 3.0-alpha-5. My experience is that errors that I've run into with
the 2.x code is fixed in 3.0.
/Anders
On Mon, Dec 7, 2009 at 23:29, Mike
Hello,
This is with Maven 2.2.1.
I have an aggregate POM file that contains 2 child projects, say
project A and project B.
Each of these child projects uses a custom build plugin. Project A
calls it like
myGrupId
myArtifactId
> parent pom in one process the plugin seems to get stuck on the plugin
> dependencies defined in the first module executed. Subsequent plugin
> dependency configurations are ignored. It feels like this is an issue with
> the underlying Maven dependency mechanism and not with th
known issue. I don't recall the JIRA
2009/11/12 Tim Fulmer :
> Hi All,
>
> We've run into a slight issue with plugin dependencies. We're using plugin
> dependencies to configure the version of Flex to use in several Flex modules
> with the Flex-Mojos plugin. The
Hi All,
We've run into a slight issue with plugin dependencies. We're using plugin
dependencies to configure the version of Flex to use in several Flex modules
with the Flex-Mojos plugin. The idea is we need to support two different
versions of Flex, v3.4 and v4.0. This works fine
afaik, no
you can use a previous version of the plugin, but not the same version
as is built in your reactor.
the reason is that maven needs do determine the build plan before it
starts, and your (as yet uncompiled) plugin in the reactor therefore
has an unknown effect on the build, resul
Hi all,
I am trying to set up a multi-project build in which one module depends
on the Maven plugin created by other module.
So far, the only way I could build the project is by building the Maven
plugin module and then activate the multi-project build.
Is there any possibility to define th
Hello,
I'm trying to create a plugin that can either run in process or run in
a separate process. To run in a separate process I need to examine
the plugins dependencies and resolve them in case they have been
overridden in the pom. For instance, I want to be able to do
com.3levers.maven.plu
ow have people gotten around
> this issue when enforcing custom rules?
>
--
View this message in context:
http://www.nabble.com/Adding-plugin-dependencies-via-a-profile-tp19094340p19096205.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
this message in context:
http://www.nabble.com/Adding-plugin-dependencies-via-a-profile-tp19094340p19094340.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
when I execute maven, it will download all project dependencies to the
local repository, including the required plugins:
e.g. the
org.codehouse..mojo:findbugs-maven-plugin:maven-plugin:2.0-SNAPSHOT will
be copied to my local repository.
but this plugin itself depends on junit 3.8.2
when I execute
Hi,
I have a project that has two child modules and a parent module.
The child modules both use the same plugin, but have different plugin
dependencies.
If I run each child module separately, everything buids fine. If I build
the child modules as part of the parent modules build, it fails due to
1 - 100 of 214 matches
Mail list logo
