Brett Porter wrote:
That bug is fixed in SVN - however, I'm not sure that the exceution
should be needed, but I don't quite understand what you are attempting
- hopefully someone with more RAR experience than me (that's anyone :)
will know the answers.
- Brett
There are two problems I encountered using M2 version 2.0. The first is
that when I set <packaging>rar</packaging> in my pom, M2 compiles my
sources and creates a RAR file but my compiled sources which should be
in a JAR file that should be included in the packaged RAR file is not
created. I solved that problem by using the JAR plugin. The next problem
is that when I try to install the RAR file, M2 copies the JAR file into
my local repository and renames it into a RAR file. What should happen
is that the RAR file (which contains the JAR file) is that one that
should be copied. It seems that the artifact installer looks for a JAR
file and copies it into the repository and just renames it into the
required packaging.
Hope this clears things up. Anyway, I'm going to try using the fixed
version in SVN. This may solve my problems. Thanks!
Regards,
Henry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
