Hi,
It should be worked out of the box.
configuration for plugin wich add new packaging, in parent / super pom
should be defined in section:
build -> *pluginManagement*
and only in module when you can use custom packaging you add
plugin in build -> plugin
śr., 7 paź 2020 o
z-Mariscal <
alvaro.sanchezmaris...@gmail.com> wrote:
> Hi,
>
> I'm writing a plugin that intends to support custom packaging types.
>
> The plugin's components.xml looks like:
>
>
>
>
>
> org.apache.maven.life
Hi,
I'm writing a plugin that intends to support custom packaging types.
The plugin's components.xml looks like:
org.apache.maven.lifecycle.mapping.LifecycleMapping
my-c
Github user atanasenko closed the pull request at:
https://github.com/apache/maven/pull/43
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Github user atanasenko closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/11
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user atanasenko closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/12
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
GitHub user atanasenko opened a pull request:
https://github.com/apache/maven-integration-testing/pull/12
MNG-5805: Custom packaging types: configuring DefaultLifecycleMapping
mojo executions
You can merge this pull request into a Git repository by running:
$ git pull https
Github user atanasenko commented on the pull request:
https://github.com/apache/maven/pull/43#issuecomment-96817019
It looks like you applied only the pom file change of sisu version.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/43#issuecomment-96789423
Applied on d8ae13fd7b6be8a238a2b74f2b494668cd967c30. If it looks good then
close out this issue along with the IT PR.
---
If your project is set up for it, you can reply t
GitHub user atanasenko opened a pull request:
https://github.com/apache/maven/pull/43
MNG-5805: Custom packaging types: configuring DefaultLifecycleMapping
mojo executions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user atanasenko opened a pull request:
https://github.com/apache/maven-integration-testing/pull/11
MNG-5805: Custom packaging types: configuring DefaultLifecycleMapping
mojo executions
You can merge this pull request into a Git repository by running:
$ git pull https
y has 'goals' parameter in components.xml, and
> DefaultLifecyclePluginAnalyzer does not take those into account.
>
> I propose an enhancement, which adds support for setting configuration and
> dependencies as part of custom packaging type mojo executions.
>
> A usecase
ccount.
I propose an enhancement, which adds support for setting configuration and
dependencies as part of custom packaging type mojo executions.
A usecase is an ability to create a packaging type which mostly consists of
standard maven plugins but with a custom configuration.
Example: package phase
Hi
Did you find anything, any progress?
I would like to know if I can workaround this problem on my side.
Thanks
Grzegorz
On 2013-11-04 16:55, Jason van Zyl wrote:
> Danke.
>
> On Nov 4, 2013, at 10:51 AM, Grzegorz Słowikowski
> mailto:gslowikow...@gmail.com>> wrote:
>
>> Simplified version co
Danke.
On Nov 4, 2013, at 10:51 AM, Grzegorz Słowikowski
wrote:
> Simplified version commited here:
>
> http://maven-play-plugin.googlecode.com/svn/tmp/test-projects/reactor-problem/
>
> Grzegorz
>
> On 4 listopad 2013 15:12:45, Jason van Zyl wrote:
>> If I checkout your test project it does
Simplified version commited here:
http://maven-play-plugin.googlecode.com/svn/tmp/test-projects/reactor-problem/
Grzegorz
On 4 listopad 2013 15:12:45, Jason van Zyl wrote:
> If I checkout your test project it doesn't build. If you make a self
> contained example that builds I'll take a look. It
If I checkout your test project it doesn't build. If you make a self contained
example that builds I'll take a look. It is most definitely a problem with the
WorkspaceReader which should be relatively easy to fix.
On Nov 4, 2013, at 3:08 AM, Grzegorz Słowikowski wrote:
> Hi
>
> Maybe I'm doi
On 2013-11-04 10:03, Mikolaj Izdebski wrote:
> On 11/04/2013 09:08 AM, Grzegorz Słowikowski wrote:
>> Maybe I'm doing something wrong and maybe it's Maven bug.
>> Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
>>
>> I have multi-module test project for my plugin:
>> https://maven-play-plugi
On 11/04/2013 09:08 AM, Grzegorz Słowikowski wrote:
> Maybe I'm doing something wrong and maybe it's Maven bug.
> Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
>
> I have multi-module test project for my plugin:
> https://maven-play-plugin.googlecode.com/svn/tags/test-projects-1.0.0-beta6/
Hi
Maybe I'm doing something wrong and maybe it's Maven bug.
Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
I have multi-module test project for my plugin:
https://maven-play-plugin.googlecode.com/svn/tags/test-projects-1.0.0-beta6/packagings/default/inter-app-dependency
There are two sub
Hi to all,
I'm writing a custom packager to help my IT create ZIP archives from a
sum of jars/wars.
I could get the jars/wars but can't figure how to get the jars
required by wars (we didn't put them in WEB-INF/lib since we should
share them).
here is my actual code, how could I get jar dependen
Thanks Arik that seems to be what I want. Now to the task of converting the
plugins I created for packaging applications, and installers with izpack,
waba and others types like swing plugins. The izpack is one i saw in the
list as not yet converted.
Marteijn Nouwens
2006/4/25, Arik Kfir <[EMAIL
hi Marteijn,
Yes, packaging determines the project type - and you can definitly define
you own packaging types (provided you create the appropriate plugin). See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.htmlfor
information on creating your own packaging and matching
Hello everybody,
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 application. With matching plugins.
Thanks
Marteij
[ http://jira.codehaus.org/browse/MNG-1760?page=all ]
Brett Porter closed MNG-1760:
-
Assign To: Brett Porter
Resolution: Won't Fix
> Custom packaging type ignored when POM contains modul
[ http://jira.codehaus.org/browse/MNG-1760?page=all ]
Brett Porter reopened MNG-1760:
---
> Custom packaging type ignored when POM contains modules entry
> --
>
> K
is a programmed
limitation and not a bug
> Custom packaging type ignored when POM contains modules entry
> --
>
> Key: MNG-1760
> URL: http://jira.codehaus.org/browse/MNG-1760
> Project: Mave
Custom packaging type ignored when POM contains modules entry
--
Key: MNG-1760
URL: http://jira.codehaus.org/browse/MNG-1760
Project: Maven 2
Type: Bug
Reporter: Aaron Anderson
First I have not come
28 matches
Mail list logo
