link-nv/Handier-Maven-Deploy — Issue #16: better handle unknown packaging types
Author: dhouthoo
Created: 2011-12-06 13:56:33+00:00
State: open

when we filter a pom file with a non-standard packaging type we actually prevent that filtered pom to ever be filtered again because we throw away the build section.

Either we must (partially) keep the build section alive on strange packaging types, but this is not required if you're not going to filter that pom again. Or we if we get the packaging type exception we can just stop trying to filter that specific pom since it has been filtered before (or was broken anyway).

Third option: we do a soft filtering in case of an unknown packaging type: don't edit the dependency section (we don't have it since the project didn't parse)

Fourth option, not sure f this will work: set the packaging type aside and pretend this is a pom or jar project. Right before writing the filtered pom, we swap the saved packaging type in again ... hehehe