[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-mtj-dev] PackageBuilder ignoring generated classes

Hi Thiago,
The reason I went for the jar approach was that creating stubs seemed likey to result in the stubs being stored in the users scm system, which I thought was best avoided.

With the latest trunk, the weaver customised impl classes are being jar'd and copied. The problem is that the weaver persistable classes are not being copied from the floggy temp directory back into the project bin directory... Either that or the bin directory needs a refresh.. Whatever the cause, the woven data classes are not apppearing in the jar used by the emulator.

I'll continue to have a look over lunch today


----- Sent on the hoof from my phone ! -----

On 29 Oct 2009, at 01:54, "Thiago Moreira (timba)" <tmoreira2020@xxxxxxxxx> wrote:

  Hi all,

  I would like bring this thread back to live: http://dev.eclipse.org/mhonarc/lists/dsdp-mtj-dev/msg01298.html. We still didn't fix it so I'm here to ask more questions.

  David, how can I build stubs like you said in your last comment? I made a search and found the below reference of stubs and pde, it is related to what you meant ?


  Let me explain a little more how Floggy works, so maybe you guys can give us a better feedback

  1Â compiler finish its process
  2Â Floggy weaver start to analyze the bytecodes
  3Â Floggy weaver will for each class that implements Persistable add methods and fields in the class.
  4Â Floggy weaver will drop off predefined classes into bin folder to the package net.sourceforge.floggy.persistence.impl. These classes doesn't have a java file pair.

  Until the third step everything works fine since we have a correlated .java file for each .class file.

  The problem is MTJ does not embedded the classes from the fourth step!

  Any help is appreciated. Thanks in advance.

  Thiago Moreira


dsdp-mtj-dev mailing list