maven solr-core pom should depend on servlet api
Key: SOLR-1789
URL: https://issues.apache.org/jira/browse/SOLR-1789
Project: Solr
Issue Type: Bug
Components: Build
Affects
2009
New Revision: 830013
URL: http://svn.apache.org/viewvc?rev=830013view=rev
Log:
specversion, Lucene maven version
Modified:
lucene/solr/branches/branch-1.4/common-build.xml
lucene/solr/branches/branch-1.4/src/maven/solr-core-pom.xml.template
Modified: lucene/solr/branches/branch-1.4
On Oct 26, 2009, at 8:40 PM, Yonik Seeley wrote:
On Mon, Oct 26, 2009 at 8:14 PM, Grant Ingersoll
gsing...@apache.org wrote:
Not following...
I just updated the default version to 1.4.1-dev on the branch.
I really don't know what maven_version should be set to... I guess we
can leave it at
-Yonik
http://www.lucidimagination.com
On Mon, Oct 26, 2009 at 8:46 PM, Grant Ingersoll gsing...@apache.org wrote:
On Oct 26, 2009, at 8:40 PM, Yonik Seeley wrote:
On Mon, Oct 26, 2009 at 8:14 PM, Grant Ingersoll gsing...@apache.org
wrote:
Not following...
I just updated the default
artifacts will be published at that time.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components
thing that remains is publishing the artifacts to the official
Maven repo on the release. I will update the release instructions to do this,
per the Lucene Java instructions.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL
!
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib - DataImportHandler
the issue.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
:runtime
BUILD FAILED
.../solr-clean/build.xml:695: The following error occurred while executing this
line:
solr-clean/common-build.xml:252: artifact:deploy doesn't support the
uniqueVersion attribute
Upgrading them to 2.0.9 and it works.
Maven - Solr Artifact Publishing
[
https://issues.apache.org/jira/browse/SOLR-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12623778#action_12623778
]
Grant Ingersoll commented on SOLR-586:
--
Can we close this?
Maven - Solr Artifact
released artifact when 1.3 goes out. Some
one with enough karma should take a look at lucene's way of doing this and make
the changes on hudson.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira
on hudson.
I'll take a look.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
to take care of the publishing aspects.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients
Maven's recommendation at
http://maven.apache.org/pom.html#Maven_Coordinates
Committed revision 687158.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project
Ryan!
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
...
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib - DataImportHandler
-artifacts target. Run ant package twice and
the same thing happens. Simply deleting the tar/zip before package runs will
fix this. I shall make the change in the package target.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL
!-- Stax --
dependency
{noformat}
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients
, my bad. Thanks Ryan!
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
earlier (patch doesn't apply,
build.xml changes reflect lib/xxx paths for the templates), so it still fails
for me. However, I still recommend that we go ahead and apply the actual
commits, and clean up any problems later.
Maven - Solr Artifact Publishing
problem if I don't use -p0 in the patch command.
{{patch -p0 SOLR-586.patch}}
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New
but not if you only use CommonsHttpSolrServer.
This is ready to be committed now.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New
Spencer and Craig!
I'll keep this issue open for a day or two in case any problems show up with
the builds or until we can make the necessary changes on hudson.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https
to be committed now.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
not found.
Please make sure the maven-ant-tasks jar is in ANT_HOME/lib, or made
available to Ant using other mechanisms like -lib or CLASSPATH.
##
{noformat}
Maven - Solr Artifact Publishing
maven project.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
with Apache's release policies.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java
with this if the vote passes. If that wasn't the
case, the normal license compatibility rules would apply.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
solr donated to Apache)
2. removed Embedded from the core description.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
integrating it with the existing builds so that there would be no need for
a maven folder.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue
are using a dev-snapshot of stax. Any
particular reason for this? Should we move to a stable version? 1.2.0 is the
latest stable version I can find on the central maven repository.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL
a dev-snapshot of stax. Any
particular reason for this? Should we move to a stable version? 1.2.0 is the
latest stable version I can find on the central maven repository.
yes, if possible, we should try to avoid dev builds. However, we should switch
the .jar in an independent issue
Maven - Solr
a dependency on solr-server for SolrJ because it is only needed
for EmbeddedSolrServer but not if you only use CommonsHttpSolrServer.
This is ready to be committed now.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https
use CommonsHttpSolrServer.
+1.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java
and try again?
It applies cleanly on the trunk.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components
shouldn't disrupt anything if the nightly build script hasn't
been changed yet. I can commit to check any newly committed change first thing
tomorrow (Pacific time).
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https
the latest SOLR-586.patch ? I just tried it on a
clean checkout and it works well.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New
should stop using IDEs to create/apply patches.
I'll post a new one shortly.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New
caused.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
quite nicely (Maven based app that
needed Solrj in embedded mode).
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
that the previous comment refers to
the attachment named SOLR-586-20080811-craigmcc.zip even though they were
uploaded together ... so this should clarify things.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https
to start making the changes. Hope to post a patch soon.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components
[
https://issues.apache.org/jira/browse/SOLR-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SOLR-586 started by Shalin Shekhar Mangar.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL
the Ant Maven Tasks jar into your Ant environment.
Does SolrJ also require a Lucene dependency if you use it in the embedded
server style?
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse
for extending DIH API.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib
.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib - DataImportHandler
artifacts a _load_ more useful.
Ah, I see the POM isn't actually being used in and of itself. It's just there
to list the dependencies. I'd need to amend {{build.xml}} to produce source
jars as well. Oh well. I'll try and see how much effort that will be.
Maven - Solr Artifact Publishing
the Solr build process produces sources and javadoc jars
in addition to the current binary jars.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig McClanahan updated SOLR-586:
--
Attachment: solr-server.pom.xml
Additional POM for the server part of Apache Solr.
Maven
.
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org/jira/browse/SOLR-586
Project: Solr
Issue Type: New Feature
Components: clients - java, contrib - DataImportHandler
Version/s: 1.3
Assignee: Shalin Shekhar Mangar
Summary: Maven - Solr Artifact Publishing (was: Maven - Solrj
Artifact Publishing)
Maven - Solr Artifact Publishing
Key: SOLR-586
URL: https://issues.apache.org
I'm a big fan of the lucene-java way of integration maven ... not because
i understand it, but because as a non-maven user i didn't even notice when
the change happened, but all the maven users i know say it's so great
that we have maven support now. ... that sounds like a win/win to me.
I'm
* I wouldn't be in favor of changing the build to rely on Maven2. We
use Maven internally at Krugle, and sometimes it works well, and other
times it's a royal pain in the butt. So having it as an option would
be nice, and handy for me personally, but I'd hate to foist Maven on
everybody
Hello! Hope you all are having nice holidays. let me lob another
idea out there and see if you think I'm crazy...
How do you all feel about changing the directory layout so it plays
nicely with maven? While we are at it, how do you feel about
switching to maven for the primary build
On Dec 28, 2007, at 5:50 PM, Ken Krugler wrote:
Hello! Hope you all are having nice holidays. let me lob another
idea out there and see if you think I'm crazy...
How do you all feel about changing the directory layout so it plays
nicely with maven? While we are at it, how do you feel
Hello! Hope you all are having nice holidays. let me lob another idea
out there and see if you think I'm crazy...
How do you all feel about changing the directory layout so it plays
nicely with maven? While we are at it, how do you feel about switching
to maven for the primary build
56 matches
Mail list logo
