Robert Scholte
Robert Scholte
This proposal is too specific. What you're asking for is the ability to chain any transformers, it is not just about relocation. By limiting this we will have issues future...
Based on the example that is the problem you are trying to solve right now.
AFAICS your current integration test doesn't cover handle dynamic content, so I'm not not convinced that it should be part of this ticket. How would you handle a dynamic resource...
I still have issues with the argument of dynamic resources. The plugin should first collect all resources, both static and dynamic, followed by the transformations.
Sounds like a good proposal because it hacks into the current flow in the plugin: drop this PR and maintain the transformer yourself.
@melloware you've seen my comments. I hope somebody else can try to come with a different approach, I simply need all my spare time to move Maven core forward, otherwise...
If you only need the reactor, please never use `install` anymore, but just `verify`. And with this plugin you should only use `compile`, `test-compile` or `package` (in case you depend...
please resolve conflicts
In general I'd like prefer to keep the number of parameters to a minimum. So if we want to do this, why not set these as defaults. When there are...
The new version will be 3.n+1.0. The first 3 means that is requires at least Maven 3. We discovered that this pattern makes is very clear when certain plugins can...