This is what I did in the ksoap2-android multi module build. Releasing it as a
standalone project is even better and cleaner. For a company wide usage..
https://github.com/mosabua/ksoap2-android
This project also shows the config via pluginMgt and then activation via simple
config in plugins w
Le lundi 20 octobre 2014 16:34:35 Stephen Connolly a écrit :
> build-tools can depend on an older (already released) version of parent
+1
that's the easiest way IMHO
so easy that this simple one line reply didn't get much traction :)
but it's the way to go
Regards,
Hervé
>
> On 20 October 201
Hello,
no I have'nt tried it personally, and I am not sure if the person who
used the binary approach considerd maven plugin. I dont think so
because the maven job was replacing an existing DOS batch file with
the same command :)
Gruss
Bernd
Am Mon, 20 Oct 2014 19:03:18 -0600 schrieb David
Hof
Hi Bernd,
Thanks I'll take a look at the Windows approach. Just curious, did you try
using Stephen's maven plugin? Just wondering if that might work for your
use case.
A little background on my use case might be in order. I just got handed
this task today. For years this has been building wit
Hello David,
you can replace the ISO in local builds with a a ZIP file for most
cases - but there is also a Windows/cygwin binary available.
Or you use the original mkisofs which offers a win32 executable.
(http://www.student.tugraz.at/thomas.plank/index_en.html)
BTW: for unpacking the ISO in in
Hi Bernd,
Tanks for the suggestion, that's an interesting approach. However I
suspect that's Linux only and that might be deal breaker. We have some CI
build agents that are Linux but most developers use Windows and I suspect
they will want to run this too.
Thanks,
-Dave
On Mon, Oct 20, 2014 a
Am Mon, 20 Oct 2014 11:47:05 -0400
schrieb Jason van Zyl :
> The best mechanism I have seen to date for sharing configuration
> amongst many projects is the Airbase POM in the Airlift project that
> was developed by Henning (I've cc'd him).
It seems that the project is well documented in the read
Hello David,
we are using an external executable to do this.
It is genisoimage from crdkit.org (debian fork of cdrtools). It can
produce for example Joilet extensions (which are used for long
filenames AFAIK). There are still filename limitations for ISO names
(but the joilet names seen on linux/
On 21 October 2014 09:20, David Hoffer wrote:
> Hum, why isn't the Maven user list the right place to ask about how to use
> Maven to create an iso? I'm not saying I have to use that plugin to do the
> job, just looking for input on how to do this regardless of the plugin.
If you want to ask g
If anyone wants to take over the development of that plugin just let me
know. I have no need for it any more and too busy with other things to work
on it
On 20 October 2014 23:33, Barrie Treloar wrote:
> On 21 October 2014 08:12, David Hoffer wrote:
>
> > I'm trying to use iso9660-maven-plugin
Hum, why isn't the Maven user list the right place to ask about how to use
Maven to create an iso? I'm not saying I have to use that plugin to do the
job, just looking for input on how to do this regardless of the plugin.
Thanks for the -X tip, I'll try that too.
-Dave
On Mon, Oct 20, 2014 at 4
On 21 October 2014 08:12, David Hoffer wrote:
> I'm trying to use iso9660-maven-plugin to generate an iso image and I'm
> getting string index out of range errors. My input has long file names,
> e.g.
>
> 7b0a8ad702ee0be0b971a082023550bd71bd33d3cbb4fa17f1de6af66f1871d4-comps-Server.x86_64.xml.gz
I'm trying to use iso9660-maven-plugin to generate an iso image and I'm
getting string index out of range errors. My input has long file names,
e.g.
7b0a8ad702ee0be0b971a082023550bd71bd33d3cbb4fa17f1de6af66f1871d4-comps-Server.x86_64.xml.gz
and I suspect this is causing the problem.
How can I res
There actually is a slightly better way (which is to generate a policy jar,
which contains the config files for PMD, checkstyle etc) and reference that
from the POMs.
See https://github.com/kitei/kitei-policy for an example. (kitei-root is
the base pom and kitei-rules builds the rules jar).
-h
O
The best mechanism I have seen to date for sharing configuration amongst many
projects is the Airbase POM in the Airlift project that was developed by
Henning (I've cc'd him).
Airbase uses PMD but you can probably use a similar technique for Checkstyle. I
always point people at the Airbase POM
build-tools can depend on an older (already released) version of parent
On 20 October 2014 15:56, James Green wrote:
> Is there a good practice to achieve this?
>
> I have a company-parent POM which has config to deal with site generation
> and distributionMangement. Everything has this as it's
Is there a good practice to achieve this?
I have a company-parent POM which has config to deal with site generation
and distributionMangement. Everything has this as it's parent.
I also have a build-tools JAR that supplies checkstyle.xml. The problem is
company-parent depends-on build-tools withi
Link to this weeks Maven Developer Hangout:
https://plus.google.com/u/0/events/cuqgqo7nloc2toagctvvl0d9lok
Thursday, October 23rd @ 4PM ET
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com
18 matches
Mail list logo
