Hi Martijn,

Not sure what your build script is going to do, but I suspect the ASF
repository can only contain packages which were released by the project's
PMC, in other words the jars that are already being distributed for 2.10.0
and 2.11.0. I recall Nathan Beyer (not sure if he's still subscribed to
this list) did this for Xerces a few years back. Though I haven't searched
I would expect that there would be something in the mailing list archives
on what he deployed.

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [email protected]
E-mail: [email protected]

Martijn Verburg <[email protected]> wrote on 12/13/2010 11:33:05 AM:

> Hi all,
>
> Really impressed that I was able to just check out the code and
> build it in about 10 minutes.  The Ant build script is really nicely
> laid out as well - kudos!
>
> I'm slowly starting to put a build script together (based partly off
> Benson's work) and I have a few initial questions:
>
> 1.)  Do any of the committers here have an account on the ASF Nexus?
>  It looks like a committer will need an account in order to deploy.
>
> 2.)  What artifacts should go to Maven Central?  I have yet to
> analyse the existing build fully, but my very quick understanding is
> that it produces 2 JARs (xercesImpl & xercesSamples) is that
> correct?  xercesImpl obviously needs to go, but I wasn't so sure
> about xercesSamples.
>
> I'll have more questions as I go but hopefully I can keep plugging
> away until I have a decent patch to add to the JIRA.
>
> PS:  Benson let me know if you *don't* want me to use any part of
> your work or how I should reference/acknowledge your ideas/
> copyright/whatever :).
>
> Cheers,
> Martijn
>
> On Mon, Dec 13, 2010 at 10:40 AM, Martijn Verburg
<[email protected]
> > wrote:
> Hi Benson,

> Why are you bothering to aim at the sonatype bundle system? Aren't we
> just aiming at the ASF Nexus? The requirements are not precisely
> identical.
>
> Ah, I learn something new every day!  I wasn't even aware of the ASF
> Nexus (my open source projects aren't ASF, so I go through the
> general Sonatype Nexus).  It certainly sounds like the ASF Nexus
> would be the route to use.
>
> If the builds here already produce all the jars (core, sources,
> javadoc) and sign them, then all you need to do is operate the deploy
> plugin, which you can do from the ant tools. If they don't produce the
> right tools, then the annoying problem is to get the jars made and
> signed, the later of which is not easy for ant. When I did this for
> GATE, I did a bit of hybridization.
>
> See https://gate.svn.sourceforge.net/svnroot/gate/gate/trunk/build/
> deploy/maven/
> for a complete example.
>
> Ironically, this *is* something aimed at the sonatype system.
>
> Cool, thanks for the example!  I need to get the source code and get
> myself familiar with the build for Xerces.  Hopefully I can start to
> investigate all of this week, I'm not as familiar with Ant and its
> tools (I've been a Maven user for the last 2-3 years now) but I'm
> sure it'll come back to me :).
>
> Thanks again for the tips/help!
>
> Cheers,
> Martijn
>
> On Fri, Dec 10, 2010 at 3:12 AM, Martijn Verburg
> <[email protected]> wrote:
> > Hi Benson,
> > I've never tried using the Maven ANT tools to perform a release that
the
> > Sonatype Nexus repo will accept (it is a fairly new process they have
in
> > place).  I'm not sure if Ivy has that type of 'release' support either.
> > I'm happy to look into either of those if they can perform the right
tasks!
> >  Again I'm not here to upset the apple cart.
> > Benson, have you given either of those tools a go on another project?
Are
> > there any particular pointers I should watch out for?
> > Cheers,
> > Martijn
> >
> > On Fri, Dec 10, 2010 at 12:52 AM, Benson Margulies
<[email protected]>
> > wrote:
> >>
> >> There is no earthly reason for a 'parallel maven build'. The maven ant
> >> tools can just be dropped into the ant build to handle this, or, I
> >> suspect, Ivy.
> >>
> >> On Thu, Dec 9, 2010 at 3:18 PM, Martijn Verburg
> >> <[email protected]> wrote:
> >> > Hi Michael,
> >> > I _completely_ understand and I have no desire to break what already
> >> > works.
> >> >  I'll definitely try to go with the manual upload process to begin
with
> >> > and
> >> > might then add a patch for a Maven build that can run side by side
with
> >> > your
> >> > ANT build in order to make future releases easier.
> >> > I'm hopefully also doing this for the Jsch project, so it's all good
> >> > practice :)
> >> > Cheers,
> >> > Martijn
> >> >
> >> > On Thu, Dec 9, 2010 at 6:50 PM, Michael Glavassevich
> >> > <[email protected]>
> >> > wrote:
> >> >>
> >> >> Hi Martijn,
> >> >>
> >> >> Xerces existed long before Maven. It has a build process which
works
> >> >> well
> >> >> for it based on Ant. It's never needed anything more complex, so
> >> >> there's
> >> >> been no motivation to ever look at Maven or for any of the
developers
> >> >> to
> >> >> learn it. If it ain't broke don't fix it, in my opinion.
> >> >>
> >> >> That's why these sorts of upload requests sit around for months /
> >> >> years.
> >> >> It's out of scope of our release process.
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Michael Glavassevich
> >> >> XML Parser Development
> >> >> IBM Toronto Lab
> >> >> E-mail: [email protected]
> >> >> E-mail: [email protected]
> >> >>
> >> >> Martijn Verburg <[email protected]> wrote on 12/09/2010
12:13:42
> >> >> PM:
> >> >>
> >> >> > Hi Michael,
> >> >> >
> >> >> > OK, obviously I'm not familiar with the Xerces dev environment
> >> >> > whatsoever :).  I'll take a look around the website/wiki/docs/
> >> >> > whatever and get back to you with some questions no doubt.
> >> >> >
> >> >> > Initially it might be a manual upload of the signed JAR files
etc,
> >> >> > but hopefully it'll become a process that can be driven by a
maven
> >> >> > build (and yes a Maven build should be able to sit alongside
another
> >> >> > build tool/process in case Xerces developers despise Maven for
> >> >> > whatever reason ;p).
> >> >> >
> >> >> > Cheers,
> >> >> > Martijn
> >> >>
> >> >> > On Thu, Dec 9, 2010 at 4:33 PM, Michael Glavassevich
> >> >> > <[email protected]
> >> >> > > wrote:
> >> >> > Hi Martijn,
> >> >> >
> >> >> > You're very much welcome to do that if you're interested.
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > Michael Glavassevich
> >> >> > XML Parser Development
> >> >> > IBM Toronto Lab
> >> >> > E-mail: [email protected]
> >> >> > E-mail: [email protected]
> >> >> >
> >> >> > Martijn Verburg <[email protected]> wrote on 12/09/2010
> >> >> > 11:06:30
> >> >> > AM:
> >> >> >
> >> >> > > Hi all,
> >> >> >
> >> >> > >
> >> >> > > As mentioned
in https://issues.apache.org/jira/browse/XERCESJ-1454
> >> >> > > I'm happy to try and help you guys out with the Sonatype
process to
> >> >> > > get these versions into Maven central.  Our team is quite keen
to
> >> >> > > use the latest and greatest in our automated builds.
> >> >> > >
> >> >> > > Cheers,
> >> >> > > Martijn
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

Reply via email to