Not sure its a bug that the source plugin doesn't produce the file
structure for me.
What I think the problem is, is that it's passed a bunch of compile
source roots that are normally just above the com directory. However
in this case because my pom is right down in with the source, all the
parent structure is missing by the time it gets to the source plugin.
Then it just does its job.
On 7 Sep 2005, at 12:37, Trygve Laugstøl wrote:
On Wed, Sep 07, 2005 at 12:15:54PM +0100, Ashley Williams wrote:
OK thanks. So are you saying that if I just delete the 'extends
AbstractMojo' then the plugin will still work (maybe by reflection or
codegen)?
No, you would still have to implement the interface.
Glad I've got your attention because I'm having a few problems with
the source:jar goal (saw your name on it!). I've placed my pom at the
same level as my java source and m2 install works fine:
com/acme/proj/ [MyMojo.java, pom.xml]
However when I run the source:jar goal and inspect the jar, the
MyMojo.java class is at the top level. Obviously if I hadn't made m2
install work then I would have expected this but I believe I've made
the necessary pom adjustments:
<build>
<sourceDirectory>.</sourceDirectory>
Actually I can sort of imagine why source:jar would have trouble with
this because I can't see in the pom anywhere where you can enter a
package name for the plugin to work out how many directories to go
'up' before doing the jar. Anything I can do locally on my machine?
From a quick look in the plugin's source code it seems correct, so
I'm not
sure what's going on. If you could make a test case to show the
errornous
behaviour that'd be great, if not file a bug so we won't forget.
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
