Am 15.04.2010 16:51, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 15:40, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare
a dependen
Hi Henrik,
Henrik Niehaus wrote:
> Am 15.04.2010 15:40, schrieb Jörg Schaible:
>> Hi Henrik,
>>
>> Henrik Niehaus wrote:
>>
>>> Am 15.04.2010 14:54, schrieb Jörg Schaible:
>>
>> [snip]
>>
Please look into the POMs of the plugins and tell whether they declare
a dependency to another plug
Am 15.04.2010 15:40, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
Please look into the POMs of the plugins and tell whether they declare a
dependency to another plugin themselves. If yes, which ones?
- Jörg
Hi Jörg,
thanks f
Hi Henrik,
Henrik Niehaus wrote:
> Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
>> Please look into the POMs of the plugins and tell whether they declare a
>> dependency to another plugin themselves. If yes, which ones?
>>
>> - Jörg
>
> Hi Jörg,
>
> thanks for your answer. A colleague o
Am 15.04.2010 14:54, schrieb Jörg Schaible:
Hi Henrik,
Henrik Niehaus wrote:
Hi Maven users,
I'm having problems with two plugins, which both define a custom
packaging type. The packaging types are source-plugin and binary-plugin,
which are defined in a private maven plugin and warpath, which
Hi Henrik,
Henrik Niehaus wrote:
> Hi Maven users,
>
> I'm having problems with two plugins, which both define a custom
> packaging type. The packaging types are source-plugin and binary-plugin,
> which are defined in a private maven plugin and warpath, which is
> defined in the warpath plugin.
Hi Maven users,
I'm having problems with two plugins, which both define a custom
packaging type. The packaging types are source-plugin and binary-plugin,
which are defined in a private maven plugin and warpath, which is
defined in the warpath plugin.
If I run the project with both plugins de
on the second thought, if you can whip you installer easily thru a small ant
script, you can use maven-antrun-plugin
to create the installer, then use build-helper-maven-plugin to attach your
output to be installed/deploy
-D
On 4/25/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
>
> On 4/25/06, da
On 4/25/06, dan tran <[EMAIL PROTECTED]> wrote:
>
> take a look at http://mojo.codehause.org/maven-native/native-maven-plugin
That would be:
http://mojo.codehaus.org/maven-native/native-maven-plugin/
(No 'e' on the end of codehaus ;)
--
Martin Cooper
it uses build lifecyle extension to provi
take a look at http://mojo.codehause.org/maven-native/native-maven-plugin
it uses build lifecyle extension to provide its own packaging type.
-Dan
On 4/25/06, Marteijn Nouwens <[EMAIL PROTECTED]> wrote:
>
> Hello everybody maybe are repost but my subscribing went wrong,
>
> I am new to maven 2.
Hello everybody maybe are repost but my subscribing went wrong,
I am new to maven 2.0. but experienced 1.0 user.
Do i understand correctly that packaging defines the type of product that is
being build. If so, can you define more than one and define your own custom
types. like installer and appli
11 matches
Mail list logo