You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Brett Porter <br...@apache.org> on 2009/12/17 05:30:04 UTC
how should snapshots look on the project page?
Hi,
In the branch, I've added two versions for artifacts: the project version and the artifact version. So you might have:
project version: 1.0-SNAPSHOT; artifact versions: 1.0-20091123.112233-1, 1.0-20091123.223344-2
or
project version: 7.0.1, artifact version: 7.0.1.v20091125
... that is, it's not specific to snapshots - but it's the main use case considering here.
So, currently the project page is a bit funny:
- it only appears under /browse/.../1.0-SNAPSHOT/ (since it's looking for the project version, not the artifact version)
- it lists the artifact versions under "other versions"
- all the artifact versions are listed in the download box
I think there's some alternatives:
1) list the versions by artifact instead of by project (making the page an "artifact" page instead of a project page)
2) keep the current, but allow clicking through to the per-artifact versions (again making it an artifact page instead of a project page, but the higher pages in browse still reflect project versions)
3) continue as is, list only the latest version of an artifact, click through to the bare repository if you need older artifacts
4) adjust the page to list all, categorised by version, in the download box (perhaps folding the old ones by default). This makes it a project-centric page
None of the above affects the raw webdav repository, it is just the "browse" aspects.
I have a preference, but thought I'd check if others had one first? Are the descriptions clear enough?
Thanks,
Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how should snapshots look on the project page?
Posted by Brett Porter <br...@apache.org>.
On 22/12/2009, at 3:06 PM, Wendy Smoak wrote:
> On Mon, Dec 21, 2009 at 9:00 PM, Brett Porter <br...@apache.org> wrote:
>
>> Good point, I only got to testing 5 or so. How bad does it look? The rest of the page needs some refinement and I'd rather just fiddle the CSS once :)
>
> It doesn't look bad at all, it just overlaps:
> http://www.pbase.com/wendysmoak/image/120483390
This is the best patch I can come up with, but I don't really think it's better. The page structure probably needs revisiting (eg, using JQuery UI for the tabs :D)
- Brett
Re: how should snapshots look on the project page?
Posted by Wendy Smoak <ws...@gmail.com>.
On Mon, Dec 21, 2009 at 9:00 PM, Brett Porter <br...@apache.org> wrote:
> Good point, I only got to testing 5 or so. How bad does it look? The rest of the page needs some refinement and I'd rather just fiddle the CSS once :)
It doesn't look bad at all, it just overlaps:
http://www.pbase.com/wendysmoak/image/120483390
--
Wendy
Re: how should snapshots look on the project page?
Posted by Brett Porter <br...@apache.org>.
On 22/12/2009, at 2:41 PM, Wendy Smoak wrote:
> On Wed, Dec 16, 2009 at 9:30 PM, Brett Porter <br...@apache.org> wrote:
>
>> In the branch, I've added two versions for artifacts: the project version and the artifact version. So you might have:
>>
>> project version: 1.0-SNAPSHOT; artifact versions: 1.0-20091123.112233-1, 1.0-20091123.223344-2
>
> I had trouble visualizing what you were describing so I couldn't
> comment, but I'm testing the branch at r892806 and I like the display
> of the timestamped snapshot versions out to the right. I deployed 30
> or so to see what the page would look like,and it continues down the
> page. It might be cleaner to make the pom snippet a smaller box so it
> doesn't overlap.
Good point, I only got to testing 5 or so. How bad does it look? The rest of the page needs some refinement and I'd rather just fiddle the CSS once :)
>
>> project version: 7.0.1, artifact version: 7.0.1.v20091125
>>
>> ... that is, it's not specific to snapshots - but it's the main use case considering here.
>
> I don't understand how this would work with non-snapshots though. As
> far as I know, Maven would consider 7.0.1 and 7.0.1.v20091125 to be
> two separate unrelated releases.
Yeah, it'd never be applicable to Maven unless we had some other way to map them. I just wanted to generalise the concept.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how should snapshots look on the project page?
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Dec 16, 2009 at 9:30 PM, Brett Porter <br...@apache.org> wrote:
> In the branch, I've added two versions for artifacts: the project version and the artifact version. So you might have:
>
> project version: 1.0-SNAPSHOT; artifact versions: 1.0-20091123.112233-1, 1.0-20091123.223344-2
I had trouble visualizing what you were describing so I couldn't
comment, but I'm testing the branch at r892806 and I like the display
of the timestamped snapshot versions out to the right. I deployed 30
or so to see what the page would look like,and it continues down the
page. It might be cleaner to make the pom snippet a smaller box so it
doesn't overlap.
> project version: 7.0.1, artifact version: 7.0.1.v20091125
>
> ... that is, it's not specific to snapshots - but it's the main use case considering here.
I don't understand how this would work with non-snapshots though. As
far as I know, Maven would consider 7.0.1 and 7.0.1.v20091125 to be
two separate unrelated releases.
--
Wendy
Re: how should snapshots look on the project page?
Posted by Brett Porter <br...@apache.org>.
On 17/12/2009, at 6:04 PM, Deng Ching wrote:
> On Thu, Dec 17, 2009 at 12:30 PM, Brett Porter <br...@apache.org> wrote:
>
>> So, currently the project page is a bit funny:
>> - it only appears under /browse/.../1.0-SNAPSHOT/ (since it's looking for
>> the project version, not the artifact version)
>> - it lists the artifact versions under "other versions"
>> - all the artifact versions are listed in the download box
>>
>>
> Just a clarification.. when browsing at the artifactId level, you'll only
> see 1.0-SNAPSHOT or 7.0.1 in the list of versions right?
yep
>
> I'm fine with this implementation, but maybe change "Other Versions" to
> "Artifact Versions" and make the difference between the "project version"
> and "artifact version(s)" clear in the docs :)
agreed
>
>
>> I think there's some alternatives:
>> 1) list the versions by artifact instead of by project (making the page an
>> "artifact" page instead of a project page)
>> 2) keep the current, but allow clicking through to the per-artifact
>> versions (again making it an artifact page instead of a project page, but
>> the higher pages in browse still reflect project versions)
>>
>
> In the current implementation, I thought you can also click through to the
> per-artifact versions?
Yes, in v1.2.x. I meant current as in, what's on the branch now. The change to the query infrastructure has impacted how it appears.
>
>
>> 3) continue as is, list only the latest version of an artifact, click
>> through to the bare repository if you need older artifacts
>> 4) adjust the page to list all, categorised by version, in the download box
>> (perhaps folding the old ones by default). This makes it a project-centric
>> page
>>
>
> I'm also fine with #4 as an alternative :)
If there's no other objections, I'll go ahead with this one then. It allows the browse actions to be doing less "smarts" and provides a more natural view and less congested search results, IMO.
Thanks,
Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: how should snapshots look on the project page?
Posted by Deng Ching <od...@gmail.com>.
On Thu, Dec 17, 2009 at 12:30 PM, Brett Porter <br...@apache.org> wrote:
> Hi,
>
> In the branch, I've added two versions for artifacts: the project version
> and the artifact version. So you might have:
>
> project version: 1.0-SNAPSHOT; artifact versions: 1.0-20091123.112233-1,
> 1.0-20091123.223344-2
>
> or
>
> project version: 7.0.1, artifact version: 7.0.1.v20091125
>
> ... that is, it's not specific to snapshots - but it's the main use case
> considering here.
>
> So, currently the project page is a bit funny:
> - it only appears under /browse/.../1.0-SNAPSHOT/ (since it's looking for
> the project version, not the artifact version)
> - it lists the artifact versions under "other versions"
> - all the artifact versions are listed in the download box
>
>
Just a clarification.. when browsing at the artifactId level, you'll only
see 1.0-SNAPSHOT or 7.0.1 in the list of versions right?
I'm fine with this implementation, but maybe change "Other Versions" to
"Artifact Versions" and make the difference between the "project version"
and "artifact version(s)" clear in the docs :)
> I think there's some alternatives:
> 1) list the versions by artifact instead of by project (making the page an
> "artifact" page instead of a project page)
> 2) keep the current, but allow clicking through to the per-artifact
> versions (again making it an artifact page instead of a project page, but
> the higher pages in browse still reflect project versions)
>
In the current implementation, I thought you can also click through to the
per-artifact versions?
> 3) continue as is, list only the latest version of an artifact, click
> through to the bare repository if you need older artifacts
> 4) adjust the page to list all, categorised by version, in the download box
> (perhaps folding the old ones by default). This makes it a project-centric
> page
>
I'm also fine with #4 as an alternative :)
>
> None of the above affects the raw webdav repository, it is just the
> "browse" aspects.
>
> I have a preference, but thought I'd check if others had one first? Are the
> descriptions clear enough?
>
> Thanks,
> Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
Thanks,
Deng