Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
currently, there is an attachArtifact call inside the plugin building the attachment. It imposes a m-a and m-p dependency, as well as an artifactFactory requirement to be able to construct the artifact to attach.
sort out
- if there is an easier way to achieve this
- how to retain the default source binding, but also how to turn it off
- how to make the source binding happen only on "release" (bear in mind people may not be using the release plugin... a profile was the original idea)
- how to bind assembly similarly
Attachments
Attachments
Issue Links
- is related to
-
MNG-5940 Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
- Closed
-
MNG-7029 Remove super POM "release-profile" release profile
- Closed
- relates to
-
MNG-709 lifecycle can end up in an infinite loop
- Closed
- supercedes
-
MNG-427 Assembly plugin : upload to remote repository
- Closed