e
maven-ear-plugin
could not recognize "my-rar" artifact I also create my own "my-ear" package.
Thanks a lot for the help!
Jian
--
View this message in context:
http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1358571.html#a38258
g.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:531)
> ... 16 more
> [INFO]
> --------
>
p!
Jian
--
View this message in context:
http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1358571.html#a3657576
Sent from the Maven - Dev forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1358571.html#a3645848
Sent from the Maven - Dev forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
rar goal
at package phase.
Please see the detail at
http://www.nabble.com/-M2-Maven-Ear-Plugin-did-not-recognize-the-RAR-Sub-Project-t1327696.html#a3545087
Best regards,
Jian
--
View this message in context:
http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1
Jian.Wu wrote:
> Hi Brat,
>
> Thanks a lot for your quick reply!
>
>> I'm pretty sure that the rars generated can still have a dependency type
>> of rar - the type != packaging.
>
> Would you suggest that I can specify a packaging "my-rar" in my rar pom.xml,
> but in my ear pom.xml, I can specif
uot; phase.
Obviously, it would be very nice that there will be one Rar Plugin doing all
of these things.
Hope these information are helpful.
Best regards,
Jian
--
View this message in context:
http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefi
Jian.Wu wrote:
> Yes. This is what I want. But, my own packaging will also be
> "rar" since "my-rar" will be a "rar" specific for OC4J as an example.
>
> If I renamed as my-rar instead of "rar",
> I'll assume that "Ear Plugin" will not consume it since it is not a
> "RarModule".
I'm pretty sur
ackaging type with default plugin executed.
It is the same that you might want to use your own XML Parser instead
of the default xml parser from JAXP.
Maven should enforce a rigid build life cycle but not a list of maven
plugins should be executed.
My two cents:-)
Jian
--
View this messa
t; off these
> plugins in pom.xml and use the plugins internally built.
>
> Is this a good idea?
>
> Thanks,
>
> Jian
>
> --
> View this message in context:
> http://www.nabble.com/Should-all-
hese
plugins in pom.xml and use the plugins internally built.
Is this a good idea?
Thanks,
Jian
--
View this message in context:
http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1358571.html#a3639264
Sent from the Maven - Dev foru
11 matches
Mail list logo