Re: [autopatch-users] sql patches showing up twice, erroring

[Alex S. <ap...@gm...>]

It's been a while for me, but I've definitely been bit by it before.  As Mike says, your classpath probably has the same dir/war/jar twice.

On Sep 15, 2010, at 7:57 PM, Mike Hardy wrote:

> 
> Hello there -
> 
> This is a problem that others have reported before, and it is usually the case that the patches only exist in one spot, but they are somehow included in the classpath twice - usually the logging includes the classpath that was seen, and that can be used to determine that they are actually referenced a couple times for some reason.
> 
> That's a bit vague (I apologize), but perhaps if you posted the debugging log it'd be easy for me (or someone else) to see from the output if that is the case?
> 
> Sometimes when I'm having troubles like this it's helpful for me just to hear that it is working and possible, so I will say that I have definitely had this reported from others, and even seen it myself when I wasn't doing things right for whatever reason, but patch discovery *does* work, and there must be a reason and a solution for this. Likely small and easy even, once the real trouble source is found.
> 
> Hopefully the log'll be the thing that makes it clear
> 
> -Mike
> 
> On Sep 15, 2010, at 10:17 PM, Derrick Schneider wrote:
> 
>> Hi, I'm just getting started with autopatch, integrating it into an existing environment.
>> 
>> I've renamed my existing SQL scripts to fit the autopatch naming convention (patchNNNN_text.sql) and configured autopatch to find them in the classpath (I'm running the web application version). The problem is that it's finding each patch twice, and of course complaining that multiple patches have the same number. I have 18 existing SQL patches, and autopatch tells me it finds 36.
>> 
>> I've looked in the war that's being deployed with the patches, and there's only one copy of each file. I assume later patches will fail legitimately as things like create tables fail on the existing schema, but the first patch is just a no-op sql script.
>> 
>> My migration.properties lists this:
>> appdb.patch.path=patches.appdb
>> 
>> And my patches/appdb directory has files such as
>> patch0001_no_op.sql
>> ...
>> patch0018_user_table_last_login.sql
>> 
>> I cranked up autopatch's logging level, and sure enough, it says "found 36 patches" and then proceeds to log about each one from the same directory.
>> 
>> This is with autopatch 1.0.2, but it also failed on 1.2-b (I went to the earlier version thinking it might be a bug).
>> 
>> Thanks for your help
>> Derrick
>> 
>> -- 
>> Writer. Programmer. Puzzle Designer.
>> http://www.obsessionwithfood.com
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev_______________________________________________
>> autopatch-users mailing list
>> aut...@li...
>> https://lists.sourceforge.net/lists/listinfo/autopatch-users
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev_______________________________________________
> autopatch-users mailing list
> aut...@li...
> https://lists.sourceforge.net/lists/listinfo/autopatch-users