Yes, I've created a new packaging. In my test project pom.xml, I now have:
apple
com.test.phases
AppleLifecycle
true
The AppleLifecycle project defines the "apple" lifecycle. However,
contrary to how custom lifecycles are usually defined, my components.xml
looks like this:
org.apa
Not sure what you aiming for, but you could introduce new packaging, and
that new packaging might introduce completely new lifecycle also.
If you build some "custom" packaging, this would be the best, since it gives
you freedom to do all what you need in your custom build, but also freedom
to map
2010/12/1 Gajo Csaba :
> I didn't try it yet, but I'll try it now.
>
> I think this will not solve the problem. If you write mvn deploy, you will
> probably have the compile, test etc. phases executed. What I need is, to not
> run any of these phases, but immediately print out "this is not supporte
I didn't try it yet, but I'll try it now.
I think this will not solve the problem. If you write mvn deploy, you
will probably have the compile, test etc. phases executed. What I need
is, to not run any of these phases, but immediately print out "this is
not supported" and end the execution. Th
take a look at the maven deploy plugin configuration[1] and set
true
hope this helps
Simo
[1] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Dec 1, 2010 at 12:18 PM, Gajo Csaba wrote:
> I want to del
I want to delete the deploy goal. Make it exist as much as "mvn apple" does
On 1.12.2010 12:14, Antonio Petrelli wrote:
It's best to tell us what you want to accomplish.
Fighting Maven is always a bad thing.
Antonio
2010/12/1 Gajo Csaba:
Hello,
I'm trying to create a custom lifecycle. In thi
It's best to tell us what you want to accomplish.
Fighting Maven is always a bad thing.
Antonio
2010/12/1 Gajo Csaba :
> Hello,
>
> I'm trying to create a custom lifecycle. In this case, I don't mean
> providing custom classes for one of the defined phases, but redefining the
> phases themselves.
Hello,
I'm trying to create a custom lifecycle. In this case, I don't mean
providing custom classes for one of the defined phases, but redefining
the phases themselves. For example, the DefaultLifecycleMapping seems to
support clean, compile, test etc...
How can I, for example, make it so th
nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045597.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mai
4.2.2.GA (nor does the
packaged EAR). There are several NPEs in the server.log and I'm not sure
why...
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045577.html
Sent from
Am Freitag, 9. Juli 2010 08:04:20 schrieb Martin Höller:
> Am Freitag, 9. Juli 2010 00:38:37 schrieb asookazian:
> > Thanks! Now I just need to write a simple Mojo/plugin that will copy the
> > exploded EAR directory to the server/default/deploy directory in JBoss.
> > cool.
>
> Or you use the mav
Am Freitag, 9. Juli 2010 00:38:37 schrieb asookazian:
> Thanks! Now I just need to write a simple Mojo/plugin that will copy the
> exploded EAR directory to the server/default/deploy directory in JBoss.
> cool.
Or you use the maven-antrun-plugin and save yourself some work :)
hth,
- martin
sig
exploded EAR directory to the server/default/deploy directory in JBoss.
cool.
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045261.html
Sent from the Maven - Users mailing list archive a
have you had a look at the unpackTypes configuration option of m-ear-p?
On 8 July 2010 16:28, asookazian wrote:
>
>
> Martin Höller wrote:
> >
> > Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian:
> >> There is some limited coverage of creating a cust
On 7/8/10 11:28 AM, asookazian wrote:
> I just realized something very basic after reading first chapter of Maven 2:
> Effective Implementation. "The web application archive is produced in the
> target directory, which is Maven's default working directory. There you
> will find both the target/si
Martin Höller wrote:
>
> Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian:
>> There is some limited coverage of creating a custom lifecycle here:
>> http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-cu
>>stom-lifecycle.html
>>
>
Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian:
> There is some limited coverage of creating a custom lifecycle here:
> http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-cu
>stom-lifecycle.html
>
> but it also covers forking and parallel lifecycles, I
e.maven.plugins:maven-war-plugin:exploded
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1044822.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
phases in the lifecycle are missing in the components.xml descriptor.
I tried to add validate which is not valid:
org.apache.maven.plugins:maven-validate-plugin:validate
b/c that plugin does not exist.
How do you know which plugin a lifecycle phase is associated with? mvn
help:d
ell. Any ideas how to fix this so the override
actually works? thx.
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1044808.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
20 matches
Mail list logo
