[platform-dev] Re: How to have two project in one

[Monezz]

[MalevolentCat]

Thank you. I'll try Javier's suggestion first. This just might exactly be what I need.

[MalevolentCat]

Ok, I've tried to apply the instructions of the second method described in the link Javier sent (http://wiki.netbeans.org/DevFaqWrapperModules) to my situation. I have two project, the original application is a free-form java project and the plugin is a module project which is situated inside the original application's project directory. I arranged for the module a forced build of the original application and copying of the jar to the module's build\cluster\modules\ext whenever I build the module. I know that these instructions are for module library wrappers, but I was hoping they could be applicable to regular modules as well. The problem is that I don't have access from the module to the packages/classes within the imported jar. The forced build of the original application project works just fine. Here's what I actually did:

[Ernie Rael]

IIUC, you want a single NBM project that includes a jar (rather than
needing two NBM). What you're describing is the right idea; note that
there should be no library wrapper involved.

In a project I've got that does this, in project.xml there is

[MalevolentCat]

Hello,
there isn't a wrapper. I think this is not the problem. If I understand it, this piece of code:


<public-packages> <package>com.raelity.logman</package>
<package>com.raelity.logman.ui</package>
</public-packages>



makes the packages between <package> and </package> available for use by other modules, but this is not the case. The module itself doesn't have access to packages stored in the imported jar. But I tried it anyway, just to be sure. Here's my module's project.xml:

[Ernie Rael]

The binary-origin refers to where it is built so code completion works. So I think it should be something like
<binary-origin>../../StanseNetbeans/dist/stanse.jar</binary-origin>
to refer to the original project instead of looking in the NBMs area.

On 4/19/2012 7:52 AM, Martin Velek wrote:

[MalevolentCat]

Ah, yes. Now it works, how could I not see that? I wonder how it copied the jar before (even with the wrong path), because when i checked, the jar was there, copied to the module's ext. Unfortunately, every time I try to clean and build the module, the included jar gets erased and then it won't build because of it. Any ideas how to fix that? I suppose I could copy some stable version of the original application's jar somewhere where it doesn't get deleted during the cleanup and then copy it to the module before the building starts. Finally the release target execution would replace it with the freshly built jar. Anyway thank you very much for your help!



2012/4/19 Ernie Rael <address-removed ([email]address-removed[/email])>

[MalevolentCat]

Now I see, the build script copied the jar before, but the module had no way of knowing where the original jar was so the completion didn't work.


2012/4/19 Martin Velek <address-removed ([email]address-removed[/email])>

[MalevolentCat]

What do you mean? I did it the same way, following the instructions there. But now I was dealing with the fact the original jar gets deleted with the clean target and the module can no longer see it so the module can't build if it uses some classes from the jar, but I fixed it already. The jar target of the original project copies the jar to some other place, where it doesn't get deleted, only rewritten with the next execution of the jar target. Everything seems to work. Thank you all very much for helping me

2012/4/19 Javier Ortiz <address-removed ([email]address-removed[/email])>

[Ernie Rael]

[MalevolentCat]

Hmmm, that's more elegant solution than mine. Thank you, I will follow by your example.


Martin

2012/4/19 Ernie Rael <address-removed ([email]address-removed[/email])>