On Wed, Jul 23, 2008 at 1:39 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> > On 23/07/2008, at 1:34 AM, Jason van Zyl wrote: > > Ok, >> >> I have a package for the new 140 version as that's what I'm using but what >> they have in central currently doesn't use classifiers which is probably not >> so good. >> >> http://repo1.maven.org/maven2/org/bouncycastle/ >> >> So we can either: >> >> 1) Follow what they have their which is incorrect technically >> 2) Deploy using classifiers as it probably should. Leave the old version >> 130 there as it but also redeploy it using classifiers >> >> If we can decide I'll push version 140 into central. >> >> > I think part of the problem is that there will be only one POM, but you > need to express dependencies, and all those have classifiers. This is > probably why I put them in in the form I did some time back. I'd prefer > classifiers myself if there's some way we can think to work around that? > > - Brett Is there any plans to fix this general problem? I.e. where the classifiers have different dependencies than the main artifact. It would seem to be the use case that classifiers suggest using. i.e. a jdk1.4 classifier is not only compiled with 1.4 source, but has additional dependencies because the 1.4 jre does not have all the apis that 1.5 has... so the jdk1.4 build should pull in those dependencies. I know one solution would be the schema-changing solution... but what about having poms with classifiers too? OK, so that would not get picked up by Maven <= 2.0.11... but still > > > > On 22-Jul-08, at 10:23 AM, Daniel Kulp wrote: >> >> >>> Brett, >>> >>> What are you doing about the fact that we cannot ship any versions of >>> bouncycastle that is currently in the central repository due to the IDEA >>> patent encumbered algorithm in it? >>> >>> (FYI: they did create a new "140" version with it removed, but it's not >>> at central yet) >>> >>> Dan >>> >>> >>> >>> On Jul 22, 2008, at 9:07 AM, Brett Porter wrote: >>> >>> >>>> On 22/07/2008, at 7:30 PM, Chad La Joie wrote: >>>> >>>> So, I had a look at the code wagon manager code and it looks pretty >>>>> much as I'd have expected. I was not able to find the >>>>> WagonOpenPgpSignatureVerifierObserver class. Could you point me to that? >>>>> >>>>> Thanks. >>>>> >>>> >>>> http://svn.apache.org/viewvc/maven/sandbox/trunk/wagon/wagon-openpgp/ >>>> >>>> You'll also be looking for: >>>> http://svn.apache.org/viewvc/commons/sandbox/openpgp/trunk/ >>>> >>>> Both of these should have snapshots deployed already. >>>> >>>> There's certainly too many levels of indirection in here - it started >>>> out with a different intent and I'll likely be cutting it down a bit once >>>> it >>>> is working. >>>> >>>> Cheers, >>>> Brett >>>> >>>> -- >>>> Brett Porter >>>> [EMAIL PROTECTED] >>>> http://blogs.exist.com/bporter/ >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> --- >>> Daniel Kulp >>> [EMAIL PROTECTED] >>> http://www.dankulp.com/blog >>> >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Apache Maven >> jason at sonatype dot com >> ---------------------------------------------------------- >> >> We know what we are, but know not what we may be. >> >> -- Shakespeare >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
