Beta-4 Released

[Brian Fox]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services
• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services
• Group Browsing
• Left Nav menu optimization and cleanup
• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added
• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it’s not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.

 

 

[craigb]

Great news. Thanks for all the hard work.

The upgrade went fine except for one temporary problem...

Until I entered a value in the Base Url setting in Administration->Server, which is stated as being optional, almost nothing in the UI worked (e.g. couldn't browse repos, could list repos but couldn't see any of their settings, couldn't load the logs, etc), and the log did not show any errors. As soon as I entered the base url, everything started to work again. I'm guessing it has something to do with our server setup, going through apache, etc, but it was a little worrying at first.

thanks again,
Craig

On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services
• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services
• Group Browsing
• Left Nav menu optimization and cleanup
• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added
• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it's not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.

 

 

[Brian E Fox]

Ok thanks for letting us know, we'll double check and rerelease if needed

--Brian (mobile)

On Jul 7, 2008, at 8:34 PM, Craig <supkichen@...> wrote:

Great news. Thanks for all the hard work.

The upgrade went fine except for one temporary problem...

Until I entered a value in the Base Url setting in Administration->Server, which is stated as being optional, almost nothing in the UI worked (e.g. couldn't browse repos, could list repos but couldn't see any of their settings, couldn't load the logs, etc), and the log did not show any errors. As soon as I entered the base url, everything started to work again. I'm guessing it has something to do with our server setup, going through apache, etc, but it was a little worrying at first.

thanks again,
Craig

On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services
• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services
• Group Browsing
• Left Nav menu optimization and cleanup
• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added
• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it's not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.

 

 

[Golly]

Awesome!! Thanks for the hard work!!

Great to hear about increasing the code coverage too. Keep up the great work guys!!!

Brian Fox wrote:

Beta 4 is released:

[Brian Fox]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Craig,

Can you give us some more info on your setup? Did anything about the proxy change between beta-3 and beta-4? Ie it really just stopped working until you put in the base url and there were no other changes?

 

Thanks,

Brian

 

From: Craig [mailto:supkichen@...]
Sent: Monday, July 07, 2008 8:35 PM
To: nexus-user@...
Subject: Re: [nexus-user] Beta-4 Released

 

Great news. Thanks for all the hard work.

The upgrade went fine except for one temporary problem...

Until I entered a value in the Base Url setting in Administration->Server, which is stated as being optional, almost nothing in the UI worked (e.g. couldn't browse repos, could list repos but couldn't see any of their settings, couldn't load the logs, etc), and the log did not show any errors. As soon as I entered the base url, everything started to work again. I'm guessing it has something to do with our server setup, going through apache, etc, but it was a little worrying at first.

thanks again,
Craig

On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services

• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services

• Group Browsing
• Left Nav menu optimization and cleanup

• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added

• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it's not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.

 

 

 

[Aaron Metzger]

Brian Fox wrote:

>
> Next up is Beta-5 with a complete rework of the Authorization /
> Authentication to support Role based access.
>
>  

The last public discussion of the role based access that I saw indicated
that you guys were heading in the direction of role based access to
*repositories* as compared to role based access to *artifacts*.  Is this
still the case?

My use case is that an artifact represents the smallest addressable unit
of intellectual property that we need to manage and would hate to have
to create one repository per artifact to control access to each artifact.

Maybe I'm thinking more in terms of "artifact access control lists" than
authorization/authentication.

Anyway, this is an area of great interest and I would appreciate any
high-level insight regarding the direction you plan to go with this feature.

--
Thanks,
Aaron




---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

Hi Aaron,
You would probably be interested in checking out the user stories scheduled
for Beta-5[1] in particular, Nexus-98[2]. In short, you should be able to do
what you are looking for, but we are definitely interested in feedback on
the intended approach.

[1]
http://issues.sonatype.org/secure/IssueNavigator.jspa?reset=true&&type=6&pid
=10001&resolution=-1&fixfor=10021&fixfor=10022&fixfor=10020&sorter/field=pri
ority&sorter/order=DESC

[2] http://issues.sonatype.org/browse/NEXUS-98

--Brian


-----Original Message-----
From: Aaron Metzger [mailto:ametzger@...]
Sent: Tuesday, July 08, 2008 10:09 AM
To: nexus-user@...
Subject: [nexus-user] Role Based Access

Brian Fox wrote:

>
> Next up is Beta-5 with a complete rework of the Authorization /
> Authentication to support Role based access.
>
>  

The last public discussion of the role based access that I saw indicated
that you guys were heading in the direction of role based access to
*repositories* as compared to role based access to *artifacts*.  Is this
still the case?

My use case is that an artifact represents the smallest addressable unit
of intellectual property that we need to manage and would hate to have
to create one repository per artifact to control access to each artifact.

Maybe I'm thinking more in terms of "artifact access control lists" than
authorization/authentication.

Anyway, this is an area of great interest and I would appreciate any
high-level insight regarding the direction you plan to go with this feature.

--
Thanks,
Aaron




---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[hgomez]

What about maven 1 repositories support ?

2008/7/8 Brian Fox <brianf@...>:

> Craig,
>
> Can you give us some more info on your setup? Did anything about the proxy
> change between beta-3 and beta-4? Ie it really just stopped working until
> you put in the base url and there were no other changes?
>
>
>
> Thanks,
>
> Brian
>
>
>
> From: Craig [mailto:supkichen@...]
> Sent: Monday, July 07, 2008 8:35 PM
> To: nexus-user@...
> Subject: Re: [nexus-user] Beta-4 Released
>
>
>
> Great news. Thanks for all the hard work.
>
> The upgrade went fine except for one temporary problem...
>
> Until I entered a value in the Base Url setting in Administration->Server,
> which is stated as being optional, almost nothing in the UI worked (e.g.
> couldn't browse repos, could list repos but couldn't see any of their
> settings, couldn't load the logs, etc), and the log did not show any errors.
> As soon as I entered the base url, everything started to work again. I'm
> guessing it has something to do with our server setup, going through apache,
> etc, but it was a little worrying at first.
>
> thanks again,
> Craig
>
> On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:
>
> Beta 4 is released:
>
> Enhancements / New Features:
>
> Ability to Define Base URL for hosting behind Apache/Proxy
> Artifact Upload via the UI
> Scheduled Services
>
> Service to Evict unused artifact from Proxy Repositories
> Snapshot Removal Services
> Reindex / Clear Caches / Publish Group Index services
>
> Group Browsing
> Left Nav menu optimization and cleanup
>
> Search Box added to Left Nav
> Logs and Config screens combined
> Maintenance and Configuration Sections collapsed
> Online help section added
> RSS Feeds combined into a new UI, new Feeds added
>
> Search Result Paging
> Updated Documentation (Tim is pushing the updates today if it's not out
> there yet)
>
> In addition to the user visible features named above, we have started
> parallel efforts to increase our automated testing coverage. The first is to
> fully automate regression testing at the Maven and REST level and the second
> is with UI testing via Selenium. We feel that this will enable us to
> continue to roll out the high quality releases that everyone is used to as
> the feature set continues to grow.
>
> You can read more about the changes and download the bundle from here.
>
> Next up is Beta-5 with a complete rework of the Authorization /
> Authentication to support Role based access.
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[hgomez]

> What about maven 1 repositories support ?

I defined the maven 1 repository (http://download.java.net/maven/1/)
and tried to group it with central but got as error :

Repository referenced by Repository Group does not share same content type!

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian E Fox]

This has been supported since Beta-3. You can't mix repos of different
types in the same group. If you want to add this repo with the rest,
define an M2 Virtual repository and link it to the M1 repo you already
created. You can then put the virtual repo in the group.

-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@...]
Sent: Tuesday, July 08, 2008 12:00 PM
To: nexus-user@...
Subject: Re: [nexus-user] Beta-4 Released

> What about maven 1 repositories support ?

I defined the maven 1 repository (http://download.java.net/maven/1/)
and tried to group it with central but got as error :

Repository referenced by Repository Group does not share same content
type!

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[hgomez]

Great Thanks

2008/7/8 Brian E. Fox <brianf@...>:

> This has been supported since Beta-3. You can't mix repos of different
> types in the same group. If you want to add this repo with the rest,
> define an M2 Virtual repository and link it to the M1 repo you already
> created. You can then put the virtual repo in the group.
>
> -----Original Message-----
> From: Henri Gomez [mailto:henri.gomez@...]
> Sent: Tuesday, July 08, 2008 12:00 PM
> To: nexus-user@...
> Subject: Re: [nexus-user] Beta-4 Released
>
>> What about maven 1 repositories support ?
>
> I defined the maven 1 repository (http://download.java.net/maven/1/)
> and tried to group it with central but got as error :
>
> Repository referenced by Repository Group does not share same content
> type!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[craigb]

Hi Brian,

The two non-standard things I did to the install was set the following:

wrapper.port=32501 in wrapper.conf - for some reason, without this we kept getting a port conflict and the wrapper wouldn't start
<host>myhost</host> in plexus.xml

Apart from those, nexus is just sitting behind apache. The config was/is exactly the same for beta-3 and beta-4

hth,
Craig

On Tue, Jul 8, 2008 at 10:59 PM, Brian Fox <brianf@...> wrote:

Craig,

Can you give us some more info on your setup? Did anything about the proxy change between beta-3 and beta-4? Ie it really just stopped working until you put in the base url and there were no other changes?

 

Thanks,

Brian

 

From: Craig [mailto:supkichen@...]
Sent: Monday, July 07, 2008 8:35 PM
To: nexus-user@...
Subject: Re: [nexus-user] Beta-4 Released

 

Great news. Thanks for all the hard work.

The upgrade went fine except for one temporary problem...

Until I entered a value in the Base Url setting in Administration->Server, which is stated as being optional, almost nothing in the UI worked (e.g. couldn't browse repos, could list repos but couldn't see any of their settings, couldn't load the logs, etc), and the log did not show any errors. As soon as I entered the base url, everything started to work again. I'm guessing it has something to do with our server setup, going through apache, etc, but it was a little worrying at first.

thanks again,
Craig

On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services

• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services

• Group Browsing
• Left Nav menu optimization and cleanup

• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added

• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it's not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.

 

 

 

[Brian E Fox]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Craig,

We aren’t able to reproduce this locally and in most cases the default of having that field be empty is correct. I’m a little baffled at this point.

 

From: Craig [mailto:supkichen@...]
Sent: Thursday, July 10, 2008 12:26 AM
To: nexus-user@...
Subject: Re: [nexus-user] Beta-4 Released

 

Hi Brian,

The two non-standard things I did to the install was set the following:

wrapper.port=32501 in wrapper.conf - for some reason, without this we kept getting a port conflict and the wrapper wouldn't start
<host>myhost</host> in plexus.xml

Apart from those, nexus is just sitting behind apache. The config was/is exactly the same for beta-3 and beta-4

hth,
Craig

On Tue, Jul 8, 2008 at 10:59 PM, Brian Fox <brianf@...> wrote:

Craig,

Can you give us some more info on your setup? Did anything about the proxy change between beta-3 and beta-4? Ie it really just stopped working until you put in the base url and there were no other changes?

 

Thanks,

Brian

 

From: Craig [mailto:supkichen@...]
Sent: Monday, July 07, 2008 8:35 PM
To: nexus-user@...
Subject: Re: [nexus-user] Beta-4 Released

 

Great news. Thanks for all the hard work.

The upgrade went fine except for one temporary problem...

Until I entered a value in the Base Url setting in Administration->Server, which is stated as being optional, almost nothing in the UI worked (e.g. couldn't browse repos, could list repos but couldn't see any of their settings, couldn't load the logs, etc), and the log did not show any errors. As soon as I entered the base url, everything started to work again. I'm guessing it has something to do with our server setup, going through apache, etc, but it was a little worrying at first.

thanks again,
Craig

On Tue, Jul 8, 2008 at 6:34 AM, Brian Fox <brianf@...> wrote:

Beta 4 is released:

Enhancements / New Features:

• Ability to Define Base URL for hosting behind Apache/Proxy
• Artifact Upload via the UI
• Scheduled Services

• Service to Evict unused artifact from Proxy Repositories
• Snapshot Removal Services
• Reindex / Clear Caches / Publish Group Index services

• Group Browsing
• Left Nav menu optimization and cleanup

• Search Box added to Left Nav
• Logs and Config screens combined
• Maintenance and Configuration Sections collapsed
• Online help section added
• RSS Feeds combined into a new UI, new Feeds added

• Search Result Paging
• Updated Documentation (Tim is pushing the updates today if it's not out there yet)

In addition to the user visible features named above, we have started parallel efforts to increase our automated testing coverage. The first is to fully automate regression testing at the Maven and REST level and the second is with UI testing via Selenium. We feel that this will enable us to continue to roll out the high quality releases that everyone is used to as the feature set continues to grow.

You can read more about the changes and download the bundle from here.

Next up is Beta-5 with a complete rework of the Authorization / Authentication to support Role based access.