You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2011/03/01 22:32:36 UTC

[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities

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

Marshall Schor commented on UIMA-1717:
--------------------------------------

I tried going to https://hudson.apache.org/hudson as an anonymous user, and had no trouble seeing the list of projects, UIMA and UIMA-AS among them.

They are now both set up and deploy snapshots to the Apache Nexus.

Richard - are you still having issues getting to that URL?

> Use Apache Hudson and Nexus repository facilities
> -------------------------------------------------
>
>                 Key: UIMA-1717
>                 URL: https://issues.apache.org/jira/browse/UIMA-1717
>             Project: UIMA
>          Issue Type: Wish
>          Components: Build, Packaging and Test
>            Reporter: Richard Eckart de Castilho
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities

Posted by Marshall Schor <ms...@schor.com>.

On 3/1/2011 5:50 PM, Jörn Kottmann wrote:
> On 3/1/11 10:32 PM, Marshall Schor (JIRA) wrote:
>>      [
>> https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001125#comment-13001125
>> ]
>>
>> Marshall Schor commented on UIMA-1717:
>> --------------------------------------
>>
>> I tried going to https://hudson.apache.org/hudson as an anonymous user, and
>> had no trouble seeing the list of projects, UIMA and UIMA-AS among them.
>>
>> They are now both set up and deploy snapshots to the Apache Nexus.
>>
>> Richard - are you still having issues getting to that URL?
> No, we are not publishing snapshots for UIMA-AS. I did not wanted to do
> anything which might
> interfere with the release work Jerry is doing. If we enable it while doing a
> release we should
> ensure that we never have a pom in the trunk which does not have the SNAPSHOT
> tag in the
> version. Otherwise that might be published to the snapshot repo
> and that might be a problem for some users, because they then maybe have an
> old RC in their
> local repo and not the actually released version.

Well, OK.  I had changed this in the job configuration to publish snapshots, but
now I've unchecked the box...  to revert that change.

I guess I don't fully understand how something bad happens.

It sounds like you're saying that if, by chance the build svn extract happens
right at the point where the release plugin has temporarily changed the pom to
the release pom naming (without the -SNAPSHOT), that the Hudson build could end
up deploying that build (with poms that do not say -SNAPSHOT) to the maven
snapshot repository.  Did I understand correctly?

Have you ever heard of that happening?  My hope is that the Maven plugin for
Hudson would "refuse" to publish non-snapshot builds to the snapshot repository. 

-Marshall

>
> In our case it would be unlikely that a non-snapshot version is pushed to the
> snapshot
> repo, because we are using the release plugin which checks in the non-snapshot
> version poms,
> tags this version and then checks in a new poms with snapshot versions again.
>
> In my opinion we should disable the publishing of snapshots when we are
> preparing a release
> to avoid the problem above and to motivate users to instead use the published
> RC version.
>
> Jörn
>
>

Re: [jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities

Posted by Jörn Kottmann <ko...@gmail.com>.
On 3/1/11 10:32 PM, Marshall Schor (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001125#comment-13001125 ]
>
> Marshall Schor commented on UIMA-1717:
> --------------------------------------
>
> I tried going to https://hudson.apache.org/hudson as an anonymous user, and had no trouble seeing the list of projects, UIMA and UIMA-AS among them.
>
> They are now both set up and deploy snapshots to the Apache Nexus.
>
> Richard - are you still having issues getting to that URL?
No, we are not publishing snapshots for UIMA-AS. I did not wanted to do 
anything which might
interfere with the release work Jerry is doing. If we enable it while 
doing a release we should
ensure that we never have a pom in the trunk which does not have the 
SNAPSHOT tag in the
version. Otherwise that might be published to the snapshot repo
and that might be a problem for some users, because they then maybe have 
an old RC in their
local repo and not the actually released version.

In our case it would be unlikely that a non-snapshot version is pushed 
to the snapshot
repo, because we are using the release plugin which checks in the 
non-snapshot version poms,
tags this version and then checks in a new poms with snapshot versions 
again.

In my opinion we should disable the publishing of snapshots when we are 
preparing a release
to avoid the problem above and to motivate users to instead use the 
published RC version.

Jörn