Hi,
2.10 is rather old. Could you try it with a more recent version such as
2.17?
Am Donnerstag, 11. September 2014 schrieb David Hoffer :
I have a module where maven-surefire-plugin (2.10) is configured to use
TestNG and JUnit47. The former has several tests that all succeed and the
later
Hi,
I'm currently releasing a new version of Flexmojos. While I sort of found a
procedure for releasing that maven plugin, it's still sort of a PITA.
The main problem is that the project contains the plugin as well as some
modules that use the plugin. Now in order to build, I have a minimal
HI,
I'm currently releasing a new version of Flexmojos. While I sort of found a
procedure for releasing
that maven plugin, it's still sort of a PITA.
The main problem is that the project contains the plugin as
well as some modules that use the plugin.
This is the basic mistake in this
But if I create a plugin using the official maven-plugin archetype the setup is
almost the same so it can't be that off-track.
Chris
Von: Karl Heinz Marbaise khmarba...@gmx.de
Gesendet: Freitag, 12. September 2014 14:46
An: Maven Users List
Betreff: Re:
The main problem is that the project contains the plugin as
well as some modules that use the plugin.
This is the basic mistake in this scenario. If you build a maven-plugin
make a separate project from it and do the release etc. only from the
maven-plugin and afterwards you have the
I did try 2.17 to see if it would fix the problem but got an additional
error (I forget what it was) so I reverted it back to 2.10. I ended up
just converting the TestNG tests to use JUnit and all works fine now.
-Dave
On Fri, Sep 12, 2014 at 12:38 AM, Andreas Gudian andreas.gud...@gmail.com
Yeah I did try dependency:resolve-plugins but that just shows the first
level dependencies not what I needed. Seems like this would be a very
useful goal to add to dependency plugin.
-Dave
On Wed, Sep 10, 2014 at 1:13 PM, Baptiste Mathus m...@batmat.net wrote:
Found that, seems to match your
Unfortunately not. To me it seems as if the reactor checks if everything is
available and if it's missing the build fails. The strange thing is that it
only checks if something is there ... during the build the freshly built
version of the plugin is used ... it's just that maven gives up before
No I can't build with an empty local repo. I have to build the plugin first
using the minimal profile.
As i said in the other post, Maven gives up before starting to build.
You can have a look ... the project is publicly available. Unfortunately I
didn't create it ... I took over development 2
Are you sure it's not pulled from the local repository?
To check, remove that SNAPSHOT and run 'mvn verify' and NEVER 'mvn
install'.
Robert
Op Fri, 12 Sep 2014 16:56:05 +0200 schreef Christofer Dutz
christofer.d...@c-ware.de:
Unfortunately not. To me it seems as if the reactor checks if
Unfortunately I've tried that :-( I can't start the build at all if the plugin
is not already in the repo as soon as a module intending on using the plugin is
in reactor.
Chris
Von: Robert Scholte rfscho...@apache.org
Gesendet: Freitag, 12. September
The problem I have here is that this would definitely fix my problem.
Breaking it out into another OSS project would be sweet…
BUT… it would introduce its own set of problems.
Now I have two projects to maintain. And the number is increasing… From an
IDE perspective, I have to have N windows
I think you can use an dummy aggregation project to host both of your
internal and OSS and make IDE like eclipse happy
root
aggregate-proj
pom.xml
your-oss
pom.xml
your-internal
-D
pom.xml
On Fri, Sep 12, 2014 at 8:58 AM, Kevin Burton bur...@spinn3r.com wrote:
Hi Kevin,
I want to post this to a public repo… it’s open source.
The problem is that the parent module is not OSS.
Child modules of a multi-module build do not need to use the toplevel
module as parent.
In other words, you can keep using your toplevel pom.xml as an _aggregator_
without it
In other words, you can keep using your toplevel pom.xml as an
_aggregator_
without it being the _parent_ of your OSS module.
Ha. That works. But the versions plugin now won’t update the version of
the sub-module…
This is super fun! :)
On Fri, Sep 12, 2014 at 9:33 AM, Curtis Rueden
OK… so this definitely works and the aggregation model compiles my module.
But I need a way to bump the version number because I have complex
dependencies and updating 10 places every time I change the project version
isn’t going to be fun.
On Fri, Sep 12, 2014 at 10:03 AM, Kevin Burton
You mentioned you were using the versions plugin and it wasn¹t working-
did you use it before? Can you describe your use case in terms of the
command line you are using, and what versions you want to upgrade?
On 9/12/14, 10:16 AM, Kevin Burton bur...@spinn3r.com wrote:
OKŠ so this definitely
Thanks…
I just want to bump the version number on the release.
I was using the auto increment fork of the versions number to make it
easier… but I can use the versions plugin manually.
I mean the general use case is I have about 20 modules and mildly complex
inheritance and I don’t want to have
mvn package” on my code , without tests, is actually pretty fast. Takes
about one minute. (I don’t need the tests btw as I’m using continuous
integration and the code is already tested).
One minute is pretty darn good…
The problem is that ‘deploy’ takes about 7 minutes.
That’s kind of not
Is it possible to fork plugin execution so that it executes in a separate
process?
I think doxia+markdown has a threading bug with peg down.
I get the attached exception.
Works fine with default options but -T 8 breaks it.
I assume if I just have the site plugin in a separate proc that it will
On Sep 12, 2014, at 2:22 PM, Kevin Burton bur...@spinn3r.com wrote:
Is it possible to fork plugin execution so that it executes in a separate
process?
No. Not unless the plugin supports forked execution. I'm not sure we'd ever
want to support this anyway. Looks like it's loading two copies
Hi Kevin,
I think the issue is that I”m using scpexe for my
distributionManagement repository.
Is there some reason you can't just use wagon-ssh?
http://stackoverflow.com/a/14404990
Regards,
Curtis
On Fri, Sep 12, 2014 at 1:11 PM, Kevin Burton bur...@spinn3r.com wrote:
mvn package” on my
What about using https .. does that compare in speed or is it faster? If
faster.. why not use it?
manfred
Curtis Rueden wrote on 12.09.2014 11:31:
Hi Kevin,
I think the issue is that I”m using scpexe for my
distributionManagement repository.
Is there some reason you can't just use
Worth a shot.. I’m using scpexe which forks OpenSSH as it’s easier to use
when I forward SSH auth… this way I’m not constantly entering passwords for
machines I’ve already authenticated to...
On Fri, Sep 12, 2014 at 11:31 AM, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Kevin,
I think the
I have a case where I to modify the version used by a transitive plugin
dependency and I'm not sure the best way to do this.
In my use case I have maven-antrun-plugin which has a dependency on
fmpp-maven-plugin which has a dependency on fmpp which uses version ranges
to specify its 4 dependencies
On 13 September 2014 02:46, Kevin Burton bur...@spinn3r.com wrote:
OK… so this definitely works and the aggregation model compiles my module.
But I need a way to bump the version number because I have complex
dependencies and updating 10 places every time I change the project version
isn’t
26 matches
Mail list logo
