>> Given a pom like the one for the upgrade tool:
>>
>> http://tinyurl.com/2alszs5
>>
>> ...how do I tell it to not export any packages? As far as I can
>> tell, this jar doesn't need to involve OSGi in any way. It's an
>> executable jar file that interacts with other jars only through the
>> manifest classpath.
> Why is it using
> <packaging>hk2-jar</packaging>
> instead of
> <packaging>jar</packaging>
> if it is supposed to be a plain jar?
I don't have any simple way of finding that out. But I'm guessing
someone said the jar should be in the modules dir, someone else said
"take a look at this example," etc, etc, and here we are.
If I make that change, the exported packages go away. But so does most
of the manifest, including the manifest classpath. Without that things
fall apart since I depend on some external jars. So someone who knows
maven want to suggest something?
>
> Make the above change and see.
>
> Secondly, I think we should stop using modules directory for such
> plain jar files. Can you raise it in next engg. meeting?
Sure thing. I think Jane mentioned to me that there's been some talk
about that already.
Cheers,
Bobby