<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Why not make a package org.jdom with artifactId jdom version 2.0.0 containing both packages (org.jdom and org.jdom2) with every class in org.jdom deprecated?</div><div><br></div><div>It's a bit more work but it might offer a good incentive for the move.</div><div><br></div><div>paul</div><div><br></div><div>PS: no big issue about the other decisions.</div><div><br></div><br><div><div>Le 17 mars 2012 à 16:45, Jason Hunter a écrit :</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">In Maven I'm OK either way. If it's under the artifact name jdom2 we avoid accidental breakage, but we will have people for years initiating new projects against jdom instead of jdom2 just by accident.<br></span></blockquote></div><br></body></html>