It's not against ASF's licenses or policy to have non-Apache licensed dependencies in optional code packages but the simplest path is to just delete the classes from the tag directly. You don't have to roll back anything.
For releases with Maven, you do: mvn release:prepare release:perform Kalle On Thu, Oct 28, 2010 at 4:19 PM, Les Hazlewood <[email protected]> wrote: > Actually, I think we must re-release without the crowd source code. > The CrowdRealm.java file imports and uses atlassian-specific > packages/classes, so until we *guarantee* that we can import and > depend on Crowd APIs while being ASF 2.0 compliant, we need to leave > this out of a release. I'm all for putting it in the 1.2 release > though - we just need to spend a bit of time to guarantee > compatibility. > > It would look very bad as our first TLP release to not have done this > homework. > > I'll roll-back the POMs to reflect the previous 1.1.0-SNAPSHOT version > so we can go through the re-release process. Note that this is just > an SVN change - we can revert it if there is any objection to this. > And the crowd code still exists in the 1.0.x branch, so we haven't > lost anything. > > Les >
