On Fri, Apr 12, 2013 at 3:27 PM, Reto Bachmann-Gmür <[email protected]> wrote:

>
>
> On Fri, Apr 12, 2013 at 12:22 PM, Rupert Westenthaler <
> [email protected]> wrote:
>
>> On Fri, Apr 12, 2013 at 10:35 AM, Reto Bachmann-Gmür <[email protected]>
>> wrote:
>> > Hi Rupert
>> >
>> > I'm sorry that I missed that thread. I retract my request to revert the
>> > code.
>> >
>> > According to
>> >
>> http://maven.apache.org/guides/mini/guide-central-repository-upload.html:
>> >
>> > "Only releases can be uploaded to the central repository, that means
>> files
>> > that won't change and that only depend on other files already released
>> and
>> > available in the repository."
>> >
>> > But
>> https://docs.sonatype.org/display/Repository/Central+Sync+Requirementsis
>> > a bit less strict:
>> >
>> > "Besides, we *discourage* putting release repository/pluginRepository in
>> > your POM. In ideal conditions, all your dependencies should be already
>> in
>> > central and central repository is self-contained. Otherwise people's
>> build
>> > might break because of missing dependencies. If some of your
>> dependencies
>> > are not in central, please upload them using our 3rd-party artifacts
>> bundle
>> > upload service<
>> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
>> >
>> > ."
>> >
>> > Maybe we can avoid the need for the repository by excluding those
>> > transitive dependencies?
>> >
>>
>> As stated in the other thread it is not possible to avoid this
>> dependency as it is directly used by the solr-core module
>>
>
> I understand that solr core has this dependency. My assumption is that not
> all features provided by solr-core depend on this so that even if we
> exclude this dependency  as with
>
> <dependency>
>             <groupId>...</groupId>
>             <artifactId>...</artifactId>
>             <exclusions>
>                 <exclusion>
>                     <artifactId>....
>                     <groupId>...
>                 </exclusion>
>             </exclusions>
>
> and suppress the respective import-package we would still have the
> functionality we actually need.
>
>
Ok, I know saw the other thread. So if we need the solr rest-service we
also need this dependency.



> Cheers,
> Reto
>
>
>> best
>> Rupert
>>
>> > Cheers,
>> > Reto
>> >
>> > On Fri, Apr 12, 2013 at 6:21 AM, Rupert Westenthaler <
>> > [email protected]> wrote:
>> >
>> >> Hi
>> >>
>> >> On Thu, Apr 11, 2013 at 7:57 PM, Reto Bachmann-Gmür <[email protected]>
>> >> wrote:
>> >> > Hi Rupert,
>> >> >
>> >> > Could you revert this change so that we can do a release of it
>> first? The
>> >> > experience is that it takes a while till dependencies go into maven
>> >> central
>> >> > so that after this update it might not be possible to release the
>> module
>> >> > for quite a while.
>> >> >
>> >>
>> >> I do not see that this is a problem for a release as the Solr project
>> >> was also able to release 4.2.0 and 4.2.1. Also deployment on Maven
>> >> Central should not be a problem, as also
>> >> org.apache.solr:solr-core:4.2.0 as well as version 4.2.1 are on maven
>> >> central and clearly show the dependency. Also deploying artifacts with
>> >> other maven repositories than maven central is no longer a problem,
>> >> because the the solr-parent does exactly that.
>> >>
>> >> Your fear was exactly the reason why I started this thread [1] and if
>> >> the outcome would be that is is indeed a problem, that I fully agree
>> >> with you that we should revert those changes until this is fixed by
>> >> Solr (meaning that Restlet is available on Maven Central).
>> >>
>> >> If there are additional questions, opinions about dependencies that
>> >> are not available on Maven Central, please use [1]. Having this
>> >> discussion in two threads will make it much harder for others to
>> >> follow.
>> >>
>> >> best
>> >> Rupert
>> >>
>> >> [1] http://stanbol.markmail.org/thread/awla77qdzlirqqrx
>> >>
>> >>
>> >> > Cheers,
>> >> > Reto
>> >> >
>> >> > On Thu, Apr 11, 2013 at 7:53 PM, Reto Bachmann-Gmür (JIRA)
>> >> > <[email protected]>wrote:
>> >> >
>> >> >>
>> >> >>     [
>> >> >>
>> >>
>> https://issues.apache.org/jira/browse/STANBOL-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629169#comment-13629169
>> >> ]
>> >> >>
>> >> >> Reto Bachmann-Gmür commented on STANBOL-1026:
>> >> >> ---------------------------------------------
>> >> >>
>> >> >> Please release the previous version before changing this. Because of
>> >> this
>> >> >> external maven repository it might last a long while till the
>> updated
>> >> >> version can be released.
>> >> >>
>> >> >> > Update commons.solr to Solr 4.2.1
>> >> >> > ---------------------------------
>> >> >> >
>> >> >> >                 Key: STANBOL-1026
>> >> >> >                 URL:
>> >> https://issues.apache.org/jira/browse/STANBOL-1026
>> >> >> >             Project: Stanbol
>> >> >> >          Issue Type: Improvement
>> >> >> >          Components: Commons
>> >> >> >            Reporter: Rupert Westenthaler
>> >> >> >            Assignee: Rupert Westenthaler
>> >> >> >            Priority: Minor
>> >> >> >
>> >> >> > This will update the Lucene/Solr version used by Stanbol form 4.1
>> to
>> >> >> 4.2.1
>> >> >>
>> >> >> --
>> >> >> This message is automatically generated by JIRA.
>> >> >> If you think it was sent incorrectly, please contact your JIRA
>> >> >> administrators
>> >> >> For more information on JIRA, see:
>> >> http://www.atlassian.com/software/jira
>> >> >>
>> >>
>> >>
>> >>
>> >> --
>> >> | Rupert Westenthaler             [email protected]
>> >> | Bodenlehenstraße 11                             ++43-699-11108907
>> >> | A-5500 Bischofshofen
>> >>
>>
>>
>>
>> --
>> | Rupert Westenthaler             [email protected]
>> | Bodenlehenstraße 11                             ++43-699-11108907
>> | A-5500 Bischofshofen
>>
>
>

Reply via email to