Release plan

Plan for release.

version 1.03

  • Start of iteration : 2005-01-10
  • End of iteration : 2005-01-20

statusstory
nok RSS Feed
nok Back Dependency
nok Artifact content
nok Transitive Dependency

version 1.02

  • Start of iteration : 2004-02-01
  • End of iteration : 2005-01-03

statusstory
done Default POM
done Remove JSTL
done Use Custom Tag

version 1.01

  • Start of iteration : 2003-11-05
  • End of iteration : 2003-12-27

statusstory
done Repoweb version
done POM display
done POM creation
done Artifact download

Stories

Before to start an unplanned story, a functional webtest must be built.

RSS Feed (since 1.03)
Add a RSS Feed channel for new Artifacts. If a POM is available add a link to the artifact web site (see http://today.java.net/pub/a/today/2003/08/08/rss.html).
Back Dependency (since 1.03)
One should be able to see artifact that depend on the current displayed artifact (like Wiki).
Attache Notes to artifact
One should be able to attach notes to an artifact (for team documentation (Maybe its redundant to POM)
POM with no artefact
One should be able to find all POM that do not have any attached artefact
Default POM (since 1.02)
Repoweb should be able to build automatically simple POM file for artefact that doesn’t have one. Repoweb should have a default set of POM for common artefact (such as junit)
Acceptance test : (pom-default) (pom-default-but-pom) (pom-no-default-no-pom)
Remove JSTL (since 1.02)
Reduce repoweb WebAPP size by removing JSTL dependencies (half size).
Use Custom Tag (since 1.02)
Reduce the use of scriptlet in the JSP page. Introduce custom JSP Tag.
Buffered remote repository
When it gets a request for a jar it doesn't have, it gets the jar from another server and stores it into it's cache before returning it to the requester)
Statistics
Statistics based upon repository contents (nb of snapshot, etc...)
Advanced class search
Add more search features such as fuzzy name search, inheritance search, etc…
Dependency graph
Build a graph representing jar dependencies using maven’s specific configuration file (project.xml).
Transitive Dependency (since 1.03)
Repoweb should offer a mechanism to handle transitive dependency stuff : i.e. using a repoweb-maven-plugin, it should be possible to ask repoweb to complete one (or a set of) Pom with transitive dependencies.
Dependency list with last version
For an artifact with a POM, add a link to build a dependency list with the last version found for each dependency found in the repository.
Try to guess dependency
Try to build a dependency list by inspecting the JAR file. Should be the default list proposed by RepoWeb during POM creation.
Persitance layer
Put statistics in a Database for performance purpose.
FTP repository
At this time, only local repository can be configured, add FTP support ( to select an FTP library)
Artifact content (since 1.03)
Display the content of an artefact directly into the descriptionowser. For the jar artefact, one would be able to display the content and download one specific jar entry.
Administrator role
User authenticated with admin role should be able to delete groups/types/artifacts. It should be able to clean-up the repository by removing SNAPSHOT versions.
Repoweb version (since 1.01)
Display repoweb version number in the footer of each page.
Acceptance test : (version-footer)
Artifact download (since 1.01)
Artifact should be downloadable from Repoweb, and Repoweb should be seen like a standard maven repository.
Acceptance test : (artifact-download) (unknown-artifact-download)
POM display (since 1.01)
The POM should be displayed near its artefact in the view list. In the artefact page, some information from the POM should be displayed (name, description, URL, dependency…).
Acceptance test : (pom-display-list) (pom-display-artifact)
POM creation (since 1.01)
One should be able to build (or edit) a POM for artifact.
Acceptance test : (pom-build) (pom-edit)