I always appreciate a good starwars reference. Actually there are 12 maven
modules overall in this particular project, so I don't think I fear multiple
modules. Could we have split the actual Jersey application classes into a
separate project outside of the war project - yes, agreed.
What I do ob
But you shouldn't be having java code in module 3 (as it is a war module)
so that should be split in two to follow best practice... It sounds like
you have multiple-module-phobia... That way is the way of fear. Fear leads
to anger... Anger leads to the dark side. Embrace the many modules on the
lig
I thought about it, but its very complicated to obfuscate in stages because
some of the classes to be obfuscated in projects 3 and 4 rely on the
obfuscated entrypoints in project 2.
Basically obfuscation has to be the last thing done before final testing and
assembly.
-Original Message-
Sounds like you should be obfuscating *in* module 2 and then adding the
dependency with classifier to module 3 and 4 (or do two obfuscations in
module 2 if you need different flavours)
On Wednesday, 28 August 2013, Richard Sand wrote:
> Hi all,
>
> Wayne, thanks for the feedback. I understand whe
Hi all,
Wayne, thanks for the feedback. I understand where you're coming from. I've
written out here a concrete example of what I want to do with these plugins,
and with maven in general wrt passing generated artifacts between plugins.
Hopefully others will weigh in on whether this approach is
See also https://jira.codehaus.org/browse/MRELEASE-594
Some background info: the maven-release-plugin ensures that the *used*
dependencies of the project are final.
If a dependency is *defined* as SNAPSHOT in dependencyManagement but it
isn't used, the release is considered stable.
However, i
