Nabble - Archiva - Issues

[jira] Updated: (MRM-1285) The content of the Downloads box is sometimes too large for the box

2009-11-25T01:15:55Z

[ http://jira.codehaus.org/browse/MRM-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1285:
----------------------------------

Fix Version/s: 1.2.3

> The content of the Downloads box is sometimes too large for the box
> -------------------------------------------------------------------
>
> Key: MRM-1285
> URL: http://jira.codehaus.org/browse/MRM-1285
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Affects Versions: 1.2
> Reporter: Dennis Lundberg
> Priority: Minor
> Fix For: 1.2.3
>
> Attachments: downloads-too-large.png
>
>
> When you browse an artifact, the contents of orange Downloads box in the top right corner of the screen sometimes overflows the borders of the box. There is no functional problem with this, but it doesn't look very nice. See attached screenshot.

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

[jira] Updated: (MRM-1284) Support for archetype-catalog.xml

2009-11-25T01:15:55Z

[ http://jira.codehaus.org/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1284:
----------------------------------

Fix Version/s: 1.3

> Support for archetype-catalog.xml
> ---------------------------------
>
> Key: MRM-1284
> URL: http://jira.codehaus.org/browse/MRM-1284
> Project: Archiva
> Issue Type: New Feature
> Components: indexing
> Reporter: Mike R. Haller
> Fix For: 1.3
>
>
> When creating new archetypes for custom type of projects, the archetypes need to be published (deployed) to a repository. However, to use the archetypes (e.g. in M2Eclipse), you need to set an URL for a remote archetype-catalog.xml
> Archiva should be able to (dynamically) produce the contents of an archetype-catalog.xml based on (all) of the archetypes deployed in the given repository. This would enable teams to use their own archetypes more efficiently.

[jira] Created: (MRM-1285) The content of the Downloads box is sometimes too large for the box

2009-11-24T23:59:55Z

The content of the Downloads box is sometimes too large for the box
-------------------------------------------------------------------

Key: MRM-1285
URL: http://jira.codehaus.org/browse/MRM-1285
Project: Archiva
Issue Type: Bug
Components: browser
Affects Versions: 1.2
Reporter: Dennis Lundberg
Priority: Minor
Attachments: downloads-too-large.png

When you browse an artifact, the contents of orange Downloads box in the top right corner of the screen sometimes overflows the borders of the box. There is no functional problem with this, but it doesn't look very nice. See attached screenshot.

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

[jira] Commented: (MRM-1284) Support for archetype-catalog.xml

2009-11-24T05:24:55Z

[ http://jira.codehaus.org/browse/MRM-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199203#action_199203 ]

Mike R. Haller commented on MRM-1284:
-------------------------------------

See also MNGECLIPSE-1152

> Support for archetype-catalog.xml
> ---------------------------------
>
> Key: MRM-1284
> URL: http://jira.codehaus.org/browse/MRM-1284
> Project: Archiva
> Issue Type: New Feature
> Components: indexing
> Reporter: Mike R. Haller
>
> When creating new archetypes for custom type of projects, the archetypes need to be published (deployed) to a repository. However, to use the archetypes (e.g. in M2Eclipse), you need to set an URL for a remote archetype-catalog.xml
> Archiva should be able to (dynamically) produce the contents of an archetype-catalog.xml based on (all) of the archetypes deployed in the given repository. This would enable teams to use their own archetypes more efficiently.

[jira] Created: (MRM-1284) Support for archetype-catalog.xml

2009-11-24T05:22:55Z

Support for archetype-catalog.xml
---------------------------------

Key: MRM-1284
URL: http://jira.codehaus.org/browse/MRM-1284
Project: Archiva
Issue Type: New Feature
Components: indexing
Reporter: Mike R. Haller

When creating new archetypes for custom type of projects, the archetypes need to be published (deployed) to a repository. However, to use the archetypes (e.g. in M2Eclipse), you need to set an URL for a remote archetype-catalog.xml

Archiva should be able to (dynamically) produce the contents of an archetype-catalog.xml based on (all) of the archetypes deployed in the given repository. This would enable teams to use their own archetypes more efficiently.

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

[jira] Commented: (MRM-1228) Ping service in not working

2009-11-22T04:26:55Z

[ http://jira.codehaus.org/browse/MRM-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198971#action_198971 ]

Maria Odea Ching commented on MRM-1228:
---------------------------------------

Added ping invocation from sample client in trunk [-r883067|http://svn.apache.org/viewvc?revision=883067&view=revision]

> Ping service in not working
> ---------------------------
>
> Key: MRM-1228
> URL: http://jira.codehaus.org/browse/MRM-1228
> Project: Archiva
> Issue Type: Bug
> Components: xmlrpc
> Affects Versions: 1.2.1
> Environment: - xmlrpc client developed in PHP
> Reporter: Fabien
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> I can't use ping service with xmlrpc client
> The reponse is "No handler for the method"
> I have tried several methods :
> - TestService.ping
> - PingServiceImpl.ping
> - PingService.ping
> I suppose that it's a bug because SearchService and AdministrationService are working in xmlrpc

[jira] Closed: (MRM-1228) Ping service in not working

2009-11-22T04:24:55Z

[ http://jira.codehaus.org/browse/MRM-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1228.
---------------------------------

Resolution: Fixed

Fixed in trunk [-r883066|http://svn.apache.org/viewvc?revision=883066&view=revision] with the following changes:
* changed from TestService to PingService
* fixed bean config in applicationContext in webapp
* added service object annotation for xmlrpc binder

[jira] Closed: (MRM-747) Archiva should prevent re-deployment of released or non-snapshot versioned artifacts

2009-11-22T03:44:55Z

[ http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-747.
--------------------------------

Resolution: Fixed

Documentation of this feature committed to trunk [-r883060|http://svn.apache.org/viewvc?revision=883060&view=revision].

> Archiva should prevent re-deployment of released or non-snapshot versioned artifacts
> ------------------------------------------------------------------------------------
>
> Key: MRM-747
> URL: http://jira.codehaus.org/browse/MRM-747
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.0.1
> Reporter: Alexandre Navarro
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: ArchivaDavResourceFactory.java, MRM-747.diff, MRM-747.svndiff, MRM-747_trunk.diff, ReleaseArtifactAlreadyExistsException.java
>
>
> It is possible de redeploy a versionned jar with webdav eventhough it must be impossible.
> It is possible de redeploy a versionned jar eventhough the file is readonly.
> It is very problematic.

[jira] Commented: (MRM-747) Archiva should prevent re-deployment of released or non-snapshot versioned artifacts

2009-11-22T03:27:55Z

[ http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198963#action_198963 ]

Maria Odea Ching commented on MRM-747:
--------------------------------------

Added selenium test in trunk [-r883059|http://svn.apache.org/viewvc?revision=883059&view=revision]

[jira] Commented: (MRM-747) Archiva should prevent re-deployment of released or non-snapshot versioned artifacts

2009-11-22T02:53:55Z

[ http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198955#action_198955 ]

Maria Odea Ching commented on MRM-747:
--------------------------------------

Functionality applied to web upload form in trunk [-r883057|http://svn.apache.org/viewvc?revision=883057&view=revision]

[jira] Commented: (MRM-747) Archiva should prevent re-deployment of released or non-snapshot versioned artifacts

2009-11-22T01:32:55Z

[ http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198938#action_198938 ]

Maria Odea Ching commented on MRM-747:
--------------------------------------

This feature is now configurable per repository based on the changes committed to trunk [-r883051|http://svn.apache.org/viewvc?revision=883051&view=revision]:
* added new field 'blockRedeployments' in repository configuration in archiva config file
* added test

[jira] Closed: (MRM-1274) SearchService.quickSearch returns artifacts with null as repositoryId

2009-11-22T00:39:55Z

[ http://jira.codehaus.org/browse/MRM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1274.
---------------------------------

Resolution: Fixed

Fixed in trunk [-r883046|http://svn.apache.org/viewvc?revision=883046&view=revision] with the following changes:
* get repo id from db since it's not set in search result
* set repositoryId as bean field in Artifact obj so it's included when bean is converted
* updated unit tests

> SearchService.quickSearch returns artifacts with null as repositoryId
> ---------------------------------------------------------------------
>
> Key: MRM-1274
> URL: http://jira.codehaus.org/browse/MRM-1274
> Project: Archiva
> Issue Type: Bug
> Components: xmlrpc
> Affects Versions: 1.2.2
> Environment: Tomcat 6.0.20
> Reporter: Kamil Mętrak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Executing following code results getting null's
> List<Artifact> list = searchService.quickSearch("test");
> for(Artifact a:list){
> System.out.println(a.getRepositoryId());
> }

[jira] Assigned: (MRM-1033) Changing the location of a scanned repository results to the contents of the new location not getting indexed

2009-11-20T00:44:55Z

[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching reassigned MRM-1033:
-------------------------------------

Assignee: Maria Odea Ching

> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.

[jira] Closed: (MRM-1033) Changing the location of a scanned repository results to the contents of the new location not getting indexed

2009-11-20T00:44:55Z

[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1033.
---------------------------------

Resolution: Fixed

Patch applied to trunk [-r882448|http://svn.apache.org/viewvc?revision=882448&view=revision]. Thanks Marica!

[jira] Closed: (MRM-1278) Wrong repository displayed in Archiva browse

2009-11-19T19:33:56Z

[ http://jira.codehaus.org/browse/MRM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1278.
---------------------------------

Resolution: Fixed

> Wrong repository displayed in Archiva browse
> --------------------------------------------
>
> Key: MRM-1278
> URL: http://jira.codehaus.org/browse/MRM-1278
> Project: Archiva
> Issue Type: Bug
> Components: browser, web application
> Affects Versions: 1.2.2
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1278-browse.png, MRM-1278-commandline.png
>
>
> Artifact was deployed to 'snapshots' repository, but it shows 'internal' in the Artifact Information page from browse. See attached screen shots for details.

[jira] Commented: (MRM-1278) Wrong repository displayed in Archiva browse

2009-11-19T19:33:56Z

[ http://jira.codehaus.org/browse/MRM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198790#action_198790 ]

Maria Odea Ching commented on MRM-1278:
---------------------------------------

Selenium test committed to trunk [-r882399|http://svn.apache.org/viewvc?revision=882399&view=revision] with the following changes:
* added selenium test that uploads SNAPSHOT artifacts in releases and snapshots repositories and checks artifact info page for correct artifact information
* refactored upload artifact methods in AbstractManagementTest, moved them over to AbstractArchivaTest to avoid repetition in other tests that use it

[jira] Created: (MRM-1283) migrate Archiva's "browse" functionality to use the metadata content repository API

2009-11-19T18:26:55Z

migrate Archiva's "browse" functionality to use the metadata content repository API
-----------------------------------------------------------------------------------

Key: MRM-1283
URL: http://jira.codehaus.org/browse/MRM-1283
Project: Archiva
Issue Type: Improvement
Components: browser, web application
Reporter: Brett Porter

the first steps to removing direct interaction with the database - see MRM-1025 for more information.

A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.

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

[jira] Updated: (MRM-1283) migrate Archiva's "browse" functionality to use the metadata content repository API

2009-11-19T18:26:55Z

[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1283:
------------------------------

Fix Version/s: 1.3
Assignee: Brett Porter

> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.

[jira] Updated: (MRM-1282) introduce a metadata content repository API

2009-11-19T18:19:55Z

[ http://jira.codehaus.org/browse/MRM-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1282:
------------------------------

Fix Version/s: 1.3

> introduce a metadata content repository API
> -------------------------------------------
>
> Key: MRM-1282
> URL: http://jira.codehaus.org/browse/MRM-1282
> Project: Archiva
> Issue Type: Improvement
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> see MRM-1025 for justification

[jira] Created: (MRM-1282) introduce a metadata content repository API

2009-11-19T18:19:55Z

introduce a metadata content repository API
-------------------------------------------

Key: MRM-1282
URL: http://jira.codehaus.org/browse/MRM-1282
Project: Archiva
Issue Type: Improvement
Reporter: Brett Porter

see MRM-1025 for justification

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

[jira] Assigned: (MRM-1282) introduce a metadata content repository API

2009-11-19T18:19:55Z

[ http://jira.codehaus.org/browse/MRM-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter reassigned MRM-1282:
---------------------------------

Assignee: Brett Porter

[jira] Commented: (MRM-1025) make the archiva database an optional part of the installation

2009-11-19T17:34:55Z

[ http://jira.codehaus.org/browse/MRM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198788#action_198788 ]

Brett Porter commented on MRM-1025:
-----------------------------------

the next step is to remove the ProjectModelToDatabaseConsumer as this is the only remaining requirement for the second database scan.

The following relies on the project model directly:
- the dependency-graph module (in turn, used only by the DependencyTree tag in the webapp, as it was not implemented for XMLRPC)
- DefaultRepositoryBrowsing (see below)
- DatabaseProjectModelResolver. This is primarily used in populating the model itself, and the dependency graph. If the above usages are removed, this can be removed.

The following utilise DefaultRepositoryBrowsing:
- "used by" in the webapp
- all tabs of the artifact page (ShowArtifactAction)
- the "shared model" on the artifact parent page
- to determine the artifact packaging in XMLRPC search (falls back to JAR - this code should be improved)
- getDependencies in XMLRPC

The key step is to introduce a metadata content repository API that can be a single touchpoint for the application, rather than the current situation of spreading between the repository-layer and direct access to the database which makes the availability of the model unreliable, is not easily extensible by plugins, and causes the main need for slow pre-scanning.

I believe the next steps are to flesh out the new metadata content repository api to support querying the above information. While it could be made to continue to interface to the existing database using the same resolvers, I believe it is valuable to simplify it using existing APIs and then revisit functionality that might need to catch up. Therefore, it can have a dumb implementation to start with (perhaps going back to reading the POM and dependency tree on demand for most uses, and not implementing get used by initially), and be improved later.

The API can be tested by migrating browse and xmlrpc to it, then removing the dependency graph module and unprocessed database consumers, model code, database scheduler and corresponding UI. If this is successful, other uses of the database can be moved over (RSS, other browse and xmlrpc functionality, and reporting) and the tree / used by made to work again. Following that, uses of repository-layer and model can be moved over as well and deletion scanning revisited.

> make the archiva database an optional part of the installation
> --------------------------------------------------------------
>
> Key: MRM-1025
> URL: http://jira.codehaus.org/browse/MRM-1025
> Project: Archiva
> Issue Type: Task
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>

[jira] Updated: (MRM-1025) make the archiva database an optional part of the installation

2009-11-19T16:58:55Z

[ http://jira.codehaus.org/browse/MRM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1025:
------------------------------

Fix Version/s: (was: Backlog)
1.3

the first steps of this have been done

- started a trivial metadata content repository implementation and consumer to generate metadata. This needs much more work to be useful, but gives the right API hooks (see r721955)
- split scanning from the repository layer (see r722004) - this means some code that needed scanning need not depend on the repository-layer (and therefore archiva-model)
- removed database cleanup consumers, relying on "events" from when Archiva notices a deletion (See note below)
- removed some unused database consumers (see MRM-1281)
- split the scheduler into modules to isolate database and indexer dependent code, so that the nexus index consumer need not have a dependency on the database (see r882207)

Note that currently:
- detecting deleted files on the filesystem and updating the index / database is non-functional (see r723334)

[jira] Updated: (MRM-1281) remove unused consumers

2009-11-19T15:39:55Z

[ http://jira.codehaus.org/browse/MRM-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1281:
------------------------------

Fix Version/s: (was: 1.3)
1.2.3

> remove unused consumers
> -----------------------
>
> Key: MRM-1281
> URL: http://jira.codehaus.org/browse/MRM-1281
> Project: Archiva
> Issue Type: Task
> Components: repository scanning
> Affects Versions: 1.2.2
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.2.3
>
>
> The following are not used and contain no implementation:
> * BytecodeStatsToDatabaseConsumer.java
> * VerifyMetadataAgainstDatabaseConsumer.java

[jira] Issue Comment Edited: (MRM-1281) remove unused consumers

2009-11-19T15:39:55Z

[ http://jira.codehaus.org/browse/MRM-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198768#action_198768 ]

Brett Porter edited comment on MRM-1281 at 11/19/09 5:39 PM:
-------------------------------------------------------------

merged to trunk - since these didn't do anything I don't think it's a problem to remove them in a point release

was (Author: brettporter):
marking fixed for 1.3 - if the MRM-1025 branch is not merged, this change will need to be merged to the new trunk

[jira] Closed: (MRM-1281) remove unused consumers

2009-11-19T15:26:55Z

[ http://jira.codehaus.org/browse/MRM-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-1281.
-----------------------------

Resolution: Fixed
Fix Version/s: 1.3
Assignee: Brett Porter

marking fixed for 1.3 - if the MRM-1025 branch is not merged, this change will need to be merged to the new trunk

> remove unused consumers
> -----------------------
>
> Key: MRM-1281
> URL: http://jira.codehaus.org/browse/MRM-1281
> Project: Archiva
> Issue Type: Task
> Components: repository scanning
> Affects Versions: 1.2.2
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> The following are not used and contain no implementation:
> * BytecodeStatsToDatabaseConsumer.java
> * VerifyMetadataAgainstDatabaseConsumer.java

[jira] Created: (MRM-1281) remove unused consumers

2009-11-19T15:24:55Z

remove unused consumers
-----------------------

Key: MRM-1281
URL: http://jira.codehaus.org/browse/MRM-1281
Project: Archiva
Issue Type: Task
Components: repository scanning
Affects Versions: 1.2.2
Reporter: Brett Porter

The following are not used and contain no implementation:

* BytecodeStatsToDatabaseConsumer.java
* VerifyMetadataAgainstDatabaseConsumer.java

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

[jira] Commented: (MRM-1276) Selenium tests need a clean up

2009-11-19T03:14:55Z

[ http://jira.codehaus.org/browse/MRM-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198705#action_198705 ]

Maria Odea Ching commented on MRM-1276:
---------------------------------------

The code itself needs clean up as well. Tests are very dependent on each other, making it hard to add new tests without breaking the other tests because of these dependencies. There are also a lot of commented out parts in the source that can already be removed.

> Selenium tests need a clean up
> ------------------------------
>
> Key: MRM-1276
> URL: http://jira.codehaus.org/browse/MRM-1276
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.2.2
> Reporter: Brett Porter
> Fix For: Backlog
>
>
> the current selenium tests are quite hard to navigate:
> - multiple different folders (it-resources vs resources)
> - unnecessary configuration (a lot of Tomcat config instead of just the files that need changing)
> - complicated POM and no documentation of the profiles
> - poor formatting in the source code (tabs, etc)
> - poor hierarchy (required to call open() then open( ... ) in sequence - should have all the init in one class and use TestNG to order)
> I think this could use some cleaning up

[jira] Commented: (MRM-1278) Wrong repository displayed in Archiva browse

2009-11-19T01:59:55Z

[ http://jira.codehaus.org/browse/MRM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198697#action_198697 ]

Maria Odea Ching commented on MRM-1278:
---------------------------------------

Fix committed to trunk [-r882090|http://svn.apache.org/viewvc?revision=882090&view=revision] with the following changes:
* retrieve artifact by using ArtifactsRelatedConstraint instead of using getArtifact(..) with an incorrect type
* updated existing and added new unit test for repo browse

[jira] Updated: (MRM-1278) Wrong repository displayed in Archiva browse

2009-11-19T01:04:55Z

[ http://jira.codehaus.org/browse/MRM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1278:
----------------------------------

Fix Version/s: 1.2.3

[jira] Commented: (MRM-1280) SNAPSHOT artifacts are not processed with timestamped versions when added via web upload form while their poms are processed with timestamped versions resulting to being treated as separate versions in browse

2009-11-18T22:29:55Z

[ http://jira.codehaus.org/browse/MRM-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198686#action_198686 ]

Maria Odea Ching commented on MRM-1280:
---------------------------------------

The download link for the jars are also incorrect as it points to the generic snapshot (e.g. 1.0-SNAPSHOT) instead of the timestamped one that is actually in the repository.

> SNAPSHOT artifacts are not processed with timestamped versions when added via web upload form while their poms are processed with timestamped versions resulting to being treated as separate versions in browse
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1280
> URL: http://jira.codehaus.org/browse/MRM-1280
> Project: Archiva
> Issue Type: Bug
> Components: browser, web application
> Reporter: Maria Odea Ching
>

[jira] Closed: (MRM-1180) use of Lucene 2.4 creates incompatible Nexus indexes for consumers with older versions of Lucene

2009-11-18T21:37:55Z

[ http://jira.codehaus.org/browse/MRM-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-1180.
---------------------------------

Resolution: Won't Fix
Fix Version/s: (was: 1.2.3)

> use of Lucene 2.4 creates incompatible Nexus indexes for consumers with older versions of Lucene
> ------------------------------------------------------------------------------------------------
>
> Key: MRM-1180
> URL: http://jira.codehaus.org/browse/MRM-1180
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Brett Porter
>
> Brian says more recent Nexus component has a separate binary format that might help with this.
> The different version might also cause the NPEs

[jira] Commented: (MRM-1280) SNAPSHOT artifacts are not processed with timestamped versions while their poms are processed with timestamped versions resulting to being treated as separate versions in browse

2009-11-18T21:12:55Z

[ http://jira.codehaus.org/browse/MRM-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198680#action_198680 ]

Maria Odea Ching commented on MRM-1280:
---------------------------------------

To reproduce this:
# Go to Upload Artifact page and upload a new artifact with the following coordinates:
#* groupId: org.apache.archiva
#* artifactId: archiva-indexer
#* version: 1.0-SNAPSHOT
#* packaging: jar
# Tick Generate Maven 2 POM checkbox
# Select snapshots for the repository
# Add a SNAPSHOT artifact and click Submit
# After uploading the artifact, browse it from the webapp browse

Notice that in the download box, only the Jar file is shown. The Other Versions field in the artifact info page shows the timestamp version and when you click it, you'll be redirected to the artifact info page that shows only the Pom file in the download box.

Running the database scanning solves this problem though.

> SNAPSHOT artifacts are not processed with timestamped versions while their poms are processed with timestamped versions resulting to being treated as separate versions in browse
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1280
> URL: http://jira.codehaus.org/browse/MRM-1280
> Project: Archiva
> Issue Type: Bug
> Components: browser, web application
> Reporter: Maria Odea Ching
>

[jira] Updated: (MRM-1280) SNAPSHOT artifacts are not processed with timestamped versions when added via web upload form while their poms are processed with timestamped versions resulting to being treated as separate versions in browse

2009-11-18T21:12:55Z

[ http://jira.codehaus.org/browse/MRM-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1280:
----------------------------------

Summary: SNAPSHOT artifacts are not processed with timestamped versions when added via web upload form while their poms are processed with timestamped versions resulting to being treated as separate versions in browse (was: SNAPSHOT artifacts are not processed with timestamped versions while their poms are processed with timestamped versions resulting to being treated as separate versions in browse)

[jira] Created: (MRM-1280) SNAPSHOT artifacts are not processed with timestamped versions while their poms are processed with timestamped versions resulting to being treated as separate versions in browse

2009-11-18T19:48:55Z

SNAPSHOT artifacts are not processed with timestamped versions while their poms are processed with timestamped versions resulting to being treated as separate versions in browse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Key: MRM-1280
URL: http://jira.codehaus.org/browse/MRM-1280
Project: Archiva
Issue Type: Bug
Components: browser, web application
Reporter: Maria Odea Ching

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