Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Lucene: Java-Dev

[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging

 

 

First page Previous page 1 2 3 4 Next page Last page  View All Lucene java-dev RSS feed   Index | Next | Previous | View Threaded


jira at apache

Apr 24, 2012, 7:17 AM

Post #1 of 88 (343 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260595#comment-13260595 ]

Benson Margulies commented on SOLR-3405:
----------------------------------------

What you did is perfect in every way if you *want* to publish the JAR so that API-style users get the benefit, but it's a lot of work if all you want it to put a patch into a war or an assembly.

How does the following alternative strike you?

WAR FILES:

Some script (probably in ant):

1. Grab and patch patch the source (not changing the package) and builds a jar for each patched item.
2. The results are assembled into a 'sparse war file' (just containing WEB-INF/lib/all-them-jars).
3. mvn install:install-file (or the maven ant tools) push the results to the local repository.
4. the pom for the war file lists the results as an 'overlay'.

It seems to me that the WAR file is the whole show here, since all the patched binaries go inside the war? If that's no so, let me know.



> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:19 AM

Post #2 of 88 (333 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260598#comment-13260598 ]

Uwe Schindler commented on SOLR-3405:
-------------------------------------

I dont understand this issue and I don't want to get the whole thing again by scinnging through the whole issue. Can we conclide in the issue description, what we should do here? I think the 3.6 artifacts in Lucene and Solr are exectly the way we want it? It works out of the box and starts a working Solr? What should be changed?

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:21 AM

Post #3 of 88 (333 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260600#comment-13260600 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

I don't think we have to attack the patched binaries scenario right now on this issue?

I just want the current maven artifacts to be consistent with whats in apache-solr-xx.tar.gz :)

If maven is consistent with the binary release, I think there will be a lot less concern
about maven, because then we know what we are 'publishing'.

But currently we don't! Maven is different here, and that should be fixed so its release
artifacts are consistent with the binary package.


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:23 AM

Post #4 of 88 (333 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260603#comment-13260603 ]

Benson Margulies commented on SOLR-3405:
----------------------------------------

Oh, drat. I thought I was cleverly reducing noise on the list by parking this idea here. Sorry.


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:25 AM

Post #5 of 88 (332 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260606#comment-13260606 ]

Uwe Schindler commented on SOLR-3405:
-------------------------------------

How does it differ? I dont understand it, sorry! Do you mean the JAR files are different? Please give an example.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:27 AM

Post #6 of 88 (334 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260609#comment-13260609 ]

Robert Muir commented on SOLR-3405:
-----------------------------------


{noformat}
$ unzip -l apache-solr-3.5.0.zip | grep commons-csv
$
{noformat}

But,

http://search.maven.org/#artifactdetails|org.apache.solr|solr-commons-csv|3.5.0|jar

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 7:37 AM

Post #7 of 88 (329 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260616#comment-13260616 ]

Uwe Schindler commented on SOLR-3405:
-------------------------------------

OK, that explains :-)

In my opinion, Solr should not deploy any maven artifact except SOLRJ and the WAR file.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 8:41 AM

Post #8 of 88 (321 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260669#comment-13260669 ]

Michael McCandless commented on SOLR-3405:
------------------------------------------

+1

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 9:37 AM

Post #9 of 88 (322 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260689#comment-13260689 ]

Ryan McKinley commented on SOLR-3405:
-------------------------------------

wasn't this solved in 3.6?

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 9:43 AM

Post #10 of 88 (325 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260694#comment-13260694 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

Not at all!

Look at the issue title: apache-solr-3.6.0.zip does *not* contain
the third party jars used in the war file (such as guava.jar), go look inside the zip.

But the maven artifacts expose these inner details: http://search.maven.org/remotecontent?filepath=org/apache/solr/solr-core/3.6.0/solr-core-3.6.0.pom

This is why the commons-csv issue emerged.


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 10:11 AM

Post #11 of 88 (322 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260713#comment-13260713 ]

Ryan McKinley commented on SOLR-3405:
-------------------------------------

why would we distribute guava.jar? Seems like we are doing the right thing here.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 10:19 AM

Post #12 of 88 (325 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260717#comment-13260717 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

OK i'll go change it to use a patched guava jar. Now what?

Now its a serious problem for maven (and we have to make either a "solr-guava" fake release, or suck in all of their code).

But its no problem for any of our other packaging:
* source build can download + patch
* binary dist doesn't include guava jar anyway

This needs to be fixed (maven should be equivalent to binary packaging), or we shouldn't publish any maven at all.

So maven just needs the .war, and the solrj in its artifacts. it doesnt need all this other stuff.
this makes like 50 or so third party dependencies so much simpler.

The reduced exposure prevents things like commons-csv problems (totally 100% a maven problem, as I've always said, look at my comment above)

it also makes it so that PMC members who don't understand maven, can simply look at the binary release
and understand what we are ALSO releasing into maven.


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 10:53 AM

Post #13 of 88 (327 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260754#comment-13260754 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

So under this proposal, which of these would NOT be published on maven central?:

* solr-core-X.Y.Z.jar
* solr-test-framework-X.Y.Z.jar
* solr-<contrib-name>-X.Y.Z.jar

If I understand properly, under this proposal, the Solr war would be published on maven central, but several maven proponents have said that that is not useful. By contrast, I believe there are people who currently depend on solr-core and solr-test-framework via Maven.

For solrj, to make maven artifacts consistent with the binary distribution, I think the POM should mark as optional those dependencies that don't ship with the binary distribution (that may already be the case, I haven't checked).

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 10:59 AM

Post #14 of 88 (321 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260762#comment-13260762 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

I think the contribs are actually in our package (along with their third party dependencies!)

So in my opinion, they should also be in maven: it should match.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 11:27 AM

Post #15 of 88 (320 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260789#comment-13260789 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

bq. But the maven artifacts expose these inner details: http://search.maven.org/remotecontent?filepath=org/apache/solr/solr-core/3.6.0/solr-core-3.6.0.pom
bq. I think the contribs are actually in our package (along with their third party dependencies!) So in my opinion, they should also be in maven: it should match.

Ok, so if I understand correctly, the problem as you see it is not the binary jars/war that are published on Maven Central (AFAICT, the set of jars/war in Maven Central are the same as in Solr's binary distribution), but rather the POMs associated with them that refer to third-party artifacts, like commons-csv. Right?

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 11:49 AM

Post #16 of 88 (323 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260814#comment-13260814 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

yeah: i mean we can look at this two ways:
1) that the solr binary package is broken by just shipping solr-core.jar without its dependnecies
2) that the maven package is over-reaching by needing to specify them.

I think, more importantly than anything else (as mentioned on this issue title), that they should match.

if its so important to use solr-core.jar (but not the war), we could add these dependencies
to the binary release too.

However we should think seriously about this: because we are talking about a lot of third party dependencies,
a lot more to be responsible for, and trickier handling of patched dependencies. And i've never heard
anyone complain about e.g. guava.jar not being in the binary package, ever. but maybe i'm missing something.

I hope this makes sense: the fact that they are different I think is the worst.


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 11:53 AM

Post #17 of 88 (320 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260819#comment-13260819 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

Or just said another way, we are currently releasing solr two different ways as binary:

1. as an "app" (war file) in the .zip
2. with its "guts exposed" on maven

we should be able to come to an agreement about what needs to be in the binary release,
and how it will be packaged, whether solr is an application or not, etc. we have to.

its absurd to be releasing it two completely different ways.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 11:57 AM

Post #18 of 88 (321 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260825#comment-13260825 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

bq. the fact that they are different I think is the worst.

Stated another way: POMs for Solr jars/war published on Maven Central should never require (i.e., have a non-optional dependency on) a third party artifact if that third party dependency is not directly included in the binary package; the contents of the war don't count as "inclusion in the binary package".



> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:01 PM

Post #19 of 88 (319 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260831#comment-13260831 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

bq. 2. with its "guts exposed" on maven

hmm, by "guts exposed" you mean: the Solr Maven artifacts' POMs document their dependencies. Right?

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:01 PM

Post #20 of 88 (322 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260832#comment-13260832 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

Well i think so, I mean the way maven publishes solr, it publishes it as if it were an _api_, not an application.
But the binary release treats solr as an application. This is a big difference!

Because of this we previously also published some war dependencies (commons-csv) also as _api_ in maven too.
This is what got people all upset, but if you look at our binary package we don't ever package their stuff up this way.

Releasing an application is easier. we don't care about dependencies (except that they are legal): just that our .war works.
and if the .war also wants to be in maven, then it should declare no dependencies (it works by itself).


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:09 PM

Post #21 of 88 (333 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260841#comment-13260841 ]

Benson Margulies commented on SOLR-3405:
----------------------------------------

It might be helpful to note the following: with 3.5.0, 3.6.0, and 4.0-SNAPSHOT, I can create a Maven project with a dependency on solr-core, and have all the necessaries show up to sucessfully use EmbeddedSolrServer. The result is:

{noformat}
[INFO] | +- org.apache.solr:solr-solrj:jar:3.5.0:provided
[INFO] | | \- org.codehaus.woodstox:wstx-asl:jar:3.2.7:provided
[INFO] | +- org.apache.solr:solr-noggit:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-core:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-analyzers:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-highlighter:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-memory:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-misc:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-queries:jar:3.5.0:provided
[INFO] | | \- jakarta-regexp:jakarta-regexp:jar:1.4:provided
[INFO] | +- org.apache.lucene:lucene-spatial:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-spellchecker:jar:3.5.0:provided
[INFO] | +- org.apache.lucene:lucene-grouping:jar:3.5.0:provided
[INFO] | +- org.apache.solr:solr-commons-csv:jar:3.5.0:provided
[INFO] | +- commons-codec:commons-codec:jar:1.5:provided
[INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:provided
[INFO] | +- commons-httpclient:commons-httpclient:jar:3.1:provided
[INFO] | +- org.slf4j:jcl-over-slf4j:jar:1.6.3:provided
[INFO] | +- commons-io:commons-io:jar:1.4:provided
[INFO] | +- commons-lang:commons-lang:jar:2.4:provided
[INFO] | +- com.google.guava:guava:jar:r05:provided
[INFO] | \- javax.servlet:servlet-api:jar:2.4:provided
{noformat}


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:09 PM

Post #22 of 88 (321 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260840#comment-13260840 ]

Ryan McKinley commented on SOLR-3405:
-------------------------------------

bq. it publishes it as if it were an _api_, not an application.

solr-core.jar is an API (how would anyone write RequestHandlers,Components,etc,etc w/o it!)

solr.war is an application




> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:11 PM

Post #23 of 88 (322 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260844#comment-13260844 ]

Robert Muir commented on SOLR-3405:
-----------------------------------

Benson, but you cannot do this with the binary release right? surely not? there is no guava.jar in the binary package, nor any lucene jars.

Like i said, the release should be the same.

It can't be: we release solr as an application on lucene.apache.org, but separately/differently as an API over on sonatype.com


> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:21 PM

Post #24 of 88 (320 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260856#comment-13260856 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

bq. It can't be: we release solr as an application on lucene.apache.org, but separately/differently as an API over on sonatype.com

I disagree. The official Solr binary distribution includes the API jars outside of the .war.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 24, 2012, 12:27 PM

Post #25 of 88 (323 views)
Permalink
[jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging [In reply to]

[ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260865#comment-13260865 ]

Steven Rowe commented on SOLR-3405:
-----------------------------------

bq. there is no guava.jar in the binary package, nor any lucene jars.

In the 3.6.0 binary dist, there are lucene jars under {{contrib/analysis-extras/lucene-libs/}}. Assuming the uima contrib follows the same pattern, it too will have a {{lucene-libs/}} directory containing the Lucene uima module's jar.

> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
> Key: SOLR-3405
> URL: https://issues.apache.org/jira/browse/SOLR-3405
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Fix For: 4.0
>
>
> Lets take the commons-csv scenario:
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
> in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*, and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party jars
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less surface area.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene

First page Previous page 1 2 3 4 Next page Last page  View All Lucene java-dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.