this might be the root cause:
MINSTALL-41 [1]:
I have a project wich I need to build only specifying a classifier (in
detail: a war project which I need to build with different profiles to
include different
configurations. So I set up different filters and the package produces
different classified wars).
So IMHO abuse of profiles, not a reason to support attachments without a
main artifact when packaging is 'war'.
Instead I would suggest extracting the configuration or if one *really*
wants to include configuration: use overlays per environment.
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MINSTALL-41
Op Sat, 09 Jan 2016 18:04:40 +0100 schreef Robert Scholte
<[email protected]>:
Hi,
I've created MDEPLOY-205: MavenProject with only attachments must have
packaging "pom"[1]
If I apply such a change, tests written for MDEPLOY-45 and MDEPLOY-78
fail.
[ERROR] The following builds failed:
[ERROR] * mdeploy-45-test\pom.xml
[ERROR] * no-main-artifact-1\pom.xml
[ERROR] * no-main-artifact-2\pom.xml
[ERROR] * no-main-artifact-snapshot\pom.xml
Original titles:
MDEPLOY-45: Classifier not supported by deploy:deploy [2]
MDEPLOY-78: Deploy with classifier does not deploy pom [3]
Both sound valid as long *as the packaging is pom*
For the hygiene of the repository if the packaging says jar there should
always an artifactId-version.jar
Anyone wants to convince me that I'm wrong?
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MDEPLOY-205
[2] https://issues.apache.org/jira/browse/MDEPLOY-45
[3] https://issues.apache.org/jira/browse/MDEPLOY-78
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
