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 specify type as "rar" when I define my rar > project > as a dependency project?
Yes, I think so. > >> 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: Creating archetypes doesn't require a custom plugin, so its just whether 1 & 2 are possible now. > > 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 This should be possible with the current RAR 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. Seems like a bug in the rar plugin if it chokes when target/classes is empty. Not sure if you are including the jar itself, or an unpacked version of the jar, but both are possible today. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
