This would need a change to the accurev scm provider. The concept doesn't
map to maven's concept of an SCM but could be implemented with a system
property, or the provider could look for the existence of a an issues xml
file and provide that to the promote command as part of maven's "checkin"
process.
Also need to remember that the release plugin checks in the poms twice
during the prepare step, and it would use the same issue(s) for both.
I don't have an AccuWork setup to test this with at the moment but if you
email me direct I can point you at what needs to be changed.
Cheers,
Grant.
On Wed, 31 Mar 2010 15:43:19 -0400, "Miszczak, Christian"
<[email protected]> wrote:
> Hi,
>
>
> We are using the maven build framework for our java development with
> AccuRev as our source controler, and we want to force all developers
across
> the stream hierarchy to use AccuWork's issue specification for publishing
> their changes through promote action.
>
> The process works fine for developers since they select issue from a list
> returned by the query associated with the change package trigger, but how
> can I let the maven release plugin do something similar, of using an
> existing issue, for identyfing his changes to source code.
>
> Any idea ?
>
>
> Thank you,
>
> Chris.
>
>
>
>
>
> TD Assurance réfère collectivement à toutes les entités et
> activités Canadiennes d'assurance des particuliers au sein de
> TDBFG.
> TD Insurance refers collectively to all of the Canadian personal
> lines insurance entities and activities within TDBFG.
> -------------------------------------------------
> AVIS DE CONFIDENTIALITE.
>
> Ce courriel, ainsi que tout renseignement ci-inclus, destiné
> uniquement au(x) destinataire(s) susmentionné(s), est confidentiel.
> Si vous n'êtes pas le destinataire prévu ou un agent responsable de
> la livraison de ce courriel, tout examen, divulgation, copie,
> impression, reproduction, distribution ou autre utilisation de
> toute partie de ce courriel est strictement interdit de même que
> toute action ou manquement à l'égard de celui-ci. Si vous avez reçu
> ce message par erreur ou sans autorisation, veuillez en aviser
> immédiatement l'expéditeur par retour de courriel ou par un autre
> moyen et supprimez immédiatement et entièrement cette communication
> de tout système électronique.
>
> NOTICE OF CONFIDENTIALITY.
>
> This communication, including any information transmitted with it,
> is intended only for the use of the addressee(s) and is
> confidential. If you are not an intended recipient or responsible
> for delivering the message to an intended recipient, any review,
> disclosure, conversion to hard copy, dissemination, reproduction or
> other use of any part of this communication is strictly prohibited,
> as is the taking or omitting of any action in reliance upon this
> communication. If you received this communication in error or
> without authorization please notify us immediately by return e-mail
> or otherwise and permanently delete the entire communication from
> any computer, disk drive, or other storage medium.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
