> > Whatever files also need to be included along with the jars in order to
> > make the maven distribution complete that can't be built completley
> > dynamicly (ie: the md5 files) can certainly be commited into the
> > repository ... but if making a release requires a lot of manual
upating to
>
Chris Hostetter wrote:
> Whatever files also need to be included along with the jars in order to
> make the maven distribution complete that can't be built completley
> dynamicly (ie: the md5 files) can certainly be commited into the
> repository ... but if making a release requires a lot of manual
: Where and how would you store for example the dependency information
: that you would be using to generate the poms? For lucene java it is easy
: for most modules as there is only dependency to lucene-core but for
: example in solr, nutch and hadoop it starts to go beyond trivial.
Whatever file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Grant.
> Initial thoughts and then more inline below, and keep in mind I long ago
> drank the Maven kool-aid and am a big fan. :-)
>
> I know it is a pain to a few, but realistically speaking there has not
> been all that much noise about Maven ar
Chris Hostetter wrote:
> : Couldn't we just add various ANT targets that package the jars per
> : the Maven way, and even copy them to the appropriate places? I
> : wonder how hard it would be
> : to have ANT output the POM and create Maven Jars. I know it is
>
> This is what i would view as the
: Couldn't we just add various ANT targets that package the jars per
: the Maven way, and even copy them to the appropriate places? I
: wonder how hard it would be
: to have ANT output the POM and create Maven Jars. I know it is
This is what i would view as the ideal situation ... a patch to th
On Apr 11, 2007, at 11:02 AM, Sami Siren wrote:
We wouldn't touch the existing single maven artifact in the
repository,
just would deploy the new artifacts under different gId, nothing
existing is broken on the way. We could of cource continue publishing
under gId 'org.apache.lucene' if so dec
Grant Ingersoll wrote:
> Initial thoughts and then more inline below, and keep in mind I long ago
> drank the Maven kool-aid and am a big fan. :-)
>
> I know it is a pain to a few, but realistically speaking there has not
> been all that much noise about Maven artifacts not being available. We
>
Initial thoughts and then more inline below, and keep in mind I long
ago drank the Maven kool-aid and am a big fan. :-)
I know it is a pain to a few, but realistically speaking there has
not been all that much noise about Maven artifacts not being
available. We use Maven for everything we
I have been hoping to put up mechanism for (easier) deployment of m2
artifacts to maven repositories (both Apache snapshot repository and the
main maven repository at ibiblio).
The most convenient way would be to use maven2 to build the various lucene
projects but as the mailing list conversation
10 matches
Mail list logo