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 specify type as "rar" when I define my rar
project
as a dependency project?
> What exactly is it that you need to do that it can't?
Generally, we want to create a list of ArcheTypes defining a list of
standard project structures.
For rar, we need two types of rar projects:
1). A rar project which contains the source code and will generate both jar
and rar file at the
end. This actually can be done by a RAR+Jar Plugin
2). A rar project for packaging which depends on a separate jar project,
assuming one jar would
be packaged into multiple rars with different configurations. this will
run into problem with
"mvn compile" or " mvn test" since this rar project does not create
"target/classes". This
can be worked out by introducing a rar-helper plugin to create an empty
target/classes
directory at "process-resources" 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-surefire-plugin--t1358571.html#a3642125
Sent from the Maven - Dev forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
