Hi,
Having the following situation:
* a maven project with modules.
* a module with dependencies in the set of modules.
* developers intention is to make sure everything is freshly compiled.
* marks the 'clean' action with 'Build with dependencies' on the module.
* the clean action first builds the dependencies and then cleans the module.
'Build with dependencies' is clearly not 'Clean with dependencies' but i
would expect some kind of dependency action, because the build process
has something similar, and the intention is this case is to extend the
behaviour over the dependencies.
Also 'Clean and Build' with 'Build with dependencies' does truly what is
says. First build dependencies and then cleans the module, which seems odd.
In an netbeans ant project, if i remember correctly, the actions did
more resemble the recursive behaviour than the maven projects. I used to
structure my makefiles to taken dependencies recursion into account, and
i'm sure i copied that behaviour from examples before me.
Is this odd behaviour? by design? bug? very complex to improve?
stupidity on my side?
Greetings,
Simon
--
create firmware without programming https://www.bendyroad.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
