Peter Monks

@boneill would you mind answering Roy's questions? That will help nail down what's happening.

FWIW I just noticed that the stack trace above is incomplete (the code was losing important exception information), so I've just fixed that (in rev 1e5ee077f982248ee84d87a70add87b79c0de746). I'll try to cut...

I just pushed [RC2](https://github.com/pmonks/alfresco-bulk-import/releases/tag/2.0-RC2) - if you could give that a whirl and paste in the full exception stack we might get a bit more information about what's going on.

@roywetherall any insights based on the information @boneill provided above?

Any updates? I'd like to dig a bit deeper into this before pushing the v2.0 GA, but don't have access to an RM environment to test against.

@taradic the `setType` call is required for imports where replacement is enabled. The precise scenario is where an existing node (i.e. one that was _not_ created by the tool) needs...

That's correct. You should watch this ticket in order to be notified of any work here. In the meantime you can post-process the imported content to set ACLs. This is...

I don't have any immediate plan to fix it, for two reasons: 1. I consider post-processing to be a better approach, in part because... 2. Richard McKnight implemented this for...

Testing is blocked on [Alfresco issue SHA-312](https://issues.alfresco.com/jira/browse/SHA-312), so dropping from Version 2.0 (code remains, but is "use at your own risk" due to lack of testing).

Yes, but in doing so you would lose the ability to control the created and modified dates.