On 19/06/2007, at 9:58 AM, Michael Busch wrote:
Paul Smith wrote:
Any chance of adding source jars as artifacts too? Makes the
Maven Eclipse plugin rather nice. I appreciate the effort in
organizing the artifacts (particularly the older versions).
cheers,
Paul
In German we have a
*sigh*, with attachment this time:
lucene_pom.2.patch
Description: Binary data
On 19/06/2007, at 11:42 AM, Paul Smith wrote:Enhanced version of previous patch. Now compiles and executes all unit tests (although some of them are failing for me)mvn -f lucene-core.pom.xml testyou can still do a pack
Enhanced version of previous patch. Now compiles and executes all
unit tests (although some of them are failing for me)
mvn -f lucene-core.pom.xml test
you can still do a package (including source distro) and skip the tests
mvn -f lucene-core-pom.xml -Dmaven.test.skip=true package
assem
Chris Hostetter wrote:
hmm... i thought i suggested before (but it may have just been in my head
and never made it into an email) that the template nature of those files
might confuse people, and we may want to rename them "*-pom.xml.template"
so people checking out of subversion don't get confus
lucene_pom.patch
Description: Binary data
Attached is a quick patch for the lucene-core pom so that it does compile and package successfully:mvn -f lucene-core.pom.xml packageEnds up with a binary jar in the target/ sub-foldermvn assembly:assemblyCreates a source distribution in the target folde
: We actually build with ant and use the maven-ant-tasks to deploy the m2
: artifacts. The pom.xml files in trunk are templates. The ant target
: "generate-maven-artifacts" takes those templates, replaces the @version@
: by the actual version number and creates a maven dist directory where it
: de
Paul Smith wrote:
quick check, I haven't tried the maven build system for lucene yet,
but getting a clean trunk, and doing this:
mvn -f lucene-parent-pom.xml -Dversion=2.2 install
It appears to be ignoring the version property:
Installing /workspace/lucene-svn/lucene-parent-pom.xml to
/User
quick check, I haven't tried the maven build system for lucene yet,
but getting a clean trunk, and doing this:
mvn -f lucene-parent-pom.xml -Dversion=2.2 install
It appears to be ignoring the version property:
Installing /workspace/lucene-svn/lucene-parent-pom.xml to /Users/
paulsmith/.m2/r
Paul Smith wrote:
I might try and grab the trunk and see if I can work out what's needed
to do that..
Paul
That'd be great! In particular we need to figure out which changes to
the pom.xml files are necessary.
- Michael
---
I'm just kidding, of course! I'll try to take a look at that.
However, making these artifacts was already a lot of work and I'm
not sure how soon I can work on the source artifacts.
I might try and grab the trunk and see if I can work out what's
needed to do that..
Paul
--
Paul Smith wrote:
Any chance of adding source jars as artifacts too? Makes the Maven
Eclipse plugin rather nice. I appreciate the effort in organizing the
artifacts (particularly the older versions).
cheers,
Paul
In German we have a saying, something like "Offer them your pinky, and
On 19/06/2007, at 6:14 AM, Michael Busch wrote:
Hello,
looking at JIRA and the email archives I find several people asking
us to upload Lucene to the Maven2 repository. Currently there are
only the artifacts from Lucene core 1.9.1 and 2.0.0 in the
repository. 1.9.1 is even incomplete, as
Hello,
looking at JIRA and the email archives I find several people asking us
to upload Lucene to the Maven2 repository. Currently there are only the
artifacts from Lucene core 1.9.1 and 2.0.0 in the repository. 1.9.1 is
even incomplete, as LUCENE-867 indicates. Therefore I ported the maven
p
13 matches
Mail list logo
