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 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
+1
This will be a nice feature addition.
On Apr 19, 2015, at 6:22 PM, Anton Tanasenko wrote:
> Hi,
> There is no possibility right now to map goals to phases with a custom
> configuration and/or dependencies when dealing with custom packagin types.
> DefaultLifecycleMapping only has 'goals' pa
Hi,
There is no possibility right now to map goals to phases with a custom
configuration and/or dependencies when dealing with custom packagin types.
DefaultLifecycleMapping only has 'goals' parameter in components.xml, and
DefaultLifecyclePluginAnalyzer does not take those into account.
I propose
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
