You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <de...@geronimo.apache.org> on 2006/07/07 15:54:29 UTC

[jira] Created: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
---------------------------------------------------------------------------------------------------------------

         Key: GERONIMO-2170
         URL: http://issues.apache.org/jira/browse/GERONIMO-2170
     Project: Geronimo
        Type: Bug
    Security: public (Regular issues) 
  Components: buildsystem  
    Versions: 1.1.1    
    Reporter: Kevan Miller
     Fix For: 1.1.1


Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.

1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Created: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by Kevan Miller <ke...@gmail.com>.
On Jul 7, 2006, at 12:47 PM, Matt Hogstrom wrote:

> I have the repo I released 1.1 on.  Should we make this available  
> as an optional download?

I like the idea, but not without some review. The repo would contain  
some binaries which we don't ship in Geronimo. I think we need to do  
some due diligence first....

We still need to fix the reference to people.apache.org...

--kevan

>
> Kevan Miller (JIRA) wrote:
>> Tagged versions of Geronimo should not include people.apache.org/ 
>> repository in their list of maven repositories
>> --------------------------------------------------------------------- 
>> ------------------------------------------
>>          Key: GERONIMO-2170
>>          URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>>      Project: Geronimo
>>         Type: Bug
>>     Security: public (Regular issues)   Components:  
>> buildsystem      Versions: 1.1.1        Reporter: Kevan Miller
>>      Fix For: 1.1.1
>> Geronimo 1.1.0 includes people.apache.org/repository in its list  
>> of maven repo's. This repository is liable to be relocated in the  
>> future and is not used to hold "released" version of packages. A  
>> tagged version of geronimo should not be dependent on any  
>> resources in this repository.
>> 1.1.1 should not use this repository (and therefore will not be  
>> dependent on any resources in the repository). The release  
>> checklist should be updated to insure that this mistake is not  
>> repeated in the future.


Re: [jira] Created: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by Matt Hogstrom <ma...@hogstrom.org>.
I have the repo I released 1.1 on.  Should we make this available as an optional download?

Kevan Miller (JIRA) wrote:
> Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
> ---------------------------------------------------------------------------------------------------------------
> 
>          Key: GERONIMO-2170
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>      Project: Geronimo
>         Type: Bug
>     Security: public (Regular issues) 
>   Components: buildsystem  
>     Versions: 1.1.1    
>     Reporter: Kevan Miller
>      Fix For: 1.1.1
> 
> 
> Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.
> 
> 1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.
> 

[jira] Updated: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2170?page=all ]

Alan Cabrera updated GERONIMO-2170:
-----------------------------------

    Fix Version/s: 1.1.x
                       (was: 1.1.1)

Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch.

> Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2170
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.1
>            Reporter: Kevan Miller
>             Fix For: 1.1.x
>
>
> Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.
> 1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by "Dain Sundstrom (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2170?page=all ]

Dain Sundstrom closed GERONIMO-2170.
------------------------------------

    Resolution: Fixed

This should no longer be a problem.  If you find a bad repo, please open a jira with a specific problem.

> Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2170
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.2
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.1.x, 1.2
>
>
> Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.
> 1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2170?page=all ]

Kevan Miller updated GERONIMO-2170:
-----------------------------------

    Fix Version/s: 1.1.1
                       (was: 1.1.x)
         Assignee: Kevan Miller

This is something that needs to be part of the process for generating a "release". I'll take the responsibility of insuring the proper steps occur.

> Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2170
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.1
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.1.1
>
>
> Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.
> 1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (GERONIMO-2170) Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories

Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2170?page=all ]

Kevan Miller updated GERONIMO-2170:
-----------------------------------

        Fix Version/s: 1.1.x
                       1.2
                           (was: 1.1.1)
    Affects Version/s: 1.1.2
                           (was: 1.1.1)

I thought this was a simple edit. However, there are a number of artifacts which we're dependent upon, which are only in Apache or Codehaus repo's. Will need to generate upload requests. Probably the long-term solution to this is setting up a Geronimo specific repo... 

> Tagged versions of Geronimo should not include people.apache.org/repository in their list of maven repositories
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2170
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2170
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.2
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.2, 1.1.x
>
>
> Geronimo 1.1.0 includes people.apache.org/repository in its list of maven repo's. This repository is liable to be relocated in the future and is not used to hold "released" version of packages. A tagged version of geronimo should not be dependent on any resources in this repository.
> 1.1.1 should not use this repository (and therefore will not be dependent on any resources in the repository). The release checklist should be updated to insure that this mistake is not repeated in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira