Hi Eric,
Seriously, though, it looks like you're only repacking existing dependencies.
So you might want to look into the Assembly plugin (after reading the chapters
in the Sonatype book).
I'll have a look at the m-assembly-p. That being said, here's what I try
to do:
- Grab a couple of dependency JARs so they end up in the final JAR/ZIP.
(That's the easy part.)
- Download a *-sources JAR and compile *some* .java sources; the
resulting .class files have to end up in the final JAR/ZIP.
(Alternatively, extract the correspodning .class files from the
primary artifact.)
- Copy some other sources (.scala files) verbatim into the final
JAR/ZIP.
The reason I currently compile the .java sources myself rather than
simply extracting the resulting classes from the primary artifact is
that after compilation I can no longer easily distinguish .java and
.scala files. But only the latter of which have to be copied verbatim
into the final JAR/ZIP.
That being said, there is one thing that makes me wonder whether the
m-assembly-p is the right tool for the job: it attaches an additional
artifact. But in my understanding this project produces only on artifact
(containing the stuff described above). Simply producing a dummy
artifact somehow feels wrong to me, like I am abusing the plugin for
something it wasn't meant to do.
Best wishes,
Andreas Sewe
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
