Nabble - Nexus Maven Repository Manager Dev List

Re: configuration for new plugin

2009-11-09T17:41:41Z

Yes, that's the only way I know of if you're using the wrapper.

On Mon, Nov 9, 2009 at 3:47 PM, Max Spring <m2spring@...> wrote:

> Just discovered the wrapper additional parameters in wrapper.conf.
> This should be as good as on the CLI.
> -Max
>
> On 11/9/2009 3:42 PM, Max Spring wrote:
>
> Related question: Is there a way to pass a Java property to Nexus (at Nexus
> startup CLI)?
> Thanks!
> -Max
>
>
> On 11/9/2009 6:12 AM, Brian Fox wrote:
>
> Nothing comes to mind, all the plugins we write are reconfigured with
> REST calls and the config file is only used for persistence between
> restarts.
>
> On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:
>
>
> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI. I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional
> commands, e-mail: nexus-dev-help@...
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional
> commands, e-mail: nexus-dev-help@...

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

Re: configuration for new plugin

2009-11-09T15:47:50Z

Just discovered the wrapper additional parameters in wrapper.conf.
This should be as good as on the CLI.
-Max

On 11/9/2009 3:42 PM, Max Spring wrote:

Related question: Is there a way to pass a Java property to Nexus (at Nexus startup CLI)?
Thanks!
-Max

On 11/9/2009 6:12 AM, Brian Fox wrote:

Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring m2spring@... wrote:

I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI.  I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max


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


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

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

Re: configuration for new plugin

2009-11-09T15:42:35Z

Related question: Is there a way to pass a Java property to Nexus (at Nexus startup CLI)?
Thanks!
-Max

On 11/9/2009 6:12 AM, Brian Fox wrote:

Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring m2spring@... wrote:

I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI.  I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max


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


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

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

Re: configuration for new plugin

2009-11-09T06:21:45Z

I would check out how this is done in log4j. Log4j has some feature that scans if the config file has been updated.

/Anders

On Mon, Nov 9, 2009 at 15:12, Brian Fox <brianf@...> wrote:

Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:
> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI. I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>

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

Re: configuration for new plugin

2009-11-09T06:12:44Z

Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:

> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI. I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>

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

configuration for new plugin

2009-11-08T19:43:13Z

I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI. I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max

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

Re: Adding more information to Nexus lucene indexer

2009-11-04T14:27:33Z

Hi there, you can read the blog posts i wrote a while back that explain how you can add your own custom data to the index (with a real sample project even)

http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-1/

http://www.sonatype.com/people/2009/06/nexus-indexer-api-part-2/

http://www.sonatype.com/people/2009/09/nexus-indexer-api-part-3/

Hope this helps

Damian

On Thu, Oct 29, 2009 at 11:58 AM, Tercio Oliveira de Almeida <tercio.coritiba@...> wrote:

Hi,

I need to add some extra info to the current Nexus indexer.

Should I implement a plugin extending the IndexerEngine or something like that?

What is the easiest approach to make this?

How can I say to the NexusIndexer that I need to add some other info
related to an artifact that is being uploaded?

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

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

Adding more information to Nexus lucene indexer

2009-10-29T09:58:13Z

Hi,

I need to add some extra info to the current Nexus indexer.

Should I implement a plugin extending the IndexerEngine or something like that?

What is the easiest approach to make this?

How can I say to the NexusIndexer that I need to add some other info
related to an artifact that is being uploaded?

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

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

Nexus 1.4.0 Released !!!

2009-10-28T06:41:59Z

Nexus 1.4.0 has been released.

This was a rather substantial release, and contains a lot of new functionality and bug fixes.

Including:

* You can now disable redeployment on a per repository basis, no longer need to define a confusing privilege scheme to achieve this. Can simply set repository to Read only, Deploy Once or Allow Redeploy.

* New security tools: the Role browser allows you to browse the tree of roles assigned to a user, and find the privileges each role is granting. Also, the new Privilege Trace alls you to find from where a user is getting privileges.

* Repository View Privilege: there is a new set of privileges (1 per repository) called a view privilege, if a user doesn't have the view privilege to a particular repository (or group) the privilege will not be seen in the UI (or over rest API calls)

* New Plugin Model: The new plugin model has been implemented and is ready for use !! The book updates will have information about the extension points available as well as information about the new Nexus Plugin Archetype to make it easy to get started with your own plugins. You can also read some more details in the blog posts that tamas put together a little while back http://www.sonatype.com/people/2009/07/writing-plugins-for-nexus-part-2/

For some of the more pertinent issues, see here http://nexus.sonatype.org/change-history.html (you will also find the FULL list of jira tickets resolved on the link at that page)

Nexus OSS can be downloaded here

http://nexus.sonatype.org/downloads/

Nexus Pro 1.4.0 ( as it is built off of OSS nexus ) contains same list of tasks implemented, along with some new plugins and enhancements to old plugins. Here are some highlights

* Site Plugin: This plugin gives the ability to deploy web sites to nexus professional, and have them served up to users

* User Account Plugin: Non registered users can now create new accounts in nexus on their own. Administrators can configure which role(s) will get assigned to these users upon signing up

* Atlassian Crowd Plugin: provides seamless integration between Nexus and Atlassian’s Crowd server, a versatile user and directory management system.

* Staging Plugin: a number of improvements here, including, staging rulesets (only allow artifacts that have signatures, or javadocs, etc.), staging bundle upload, and numerous user interface improvements

Nexus Pro can be evaluated/purchased here http://www.sonatype.com/products/nexus

Enjoy !!

Thanks,
Damian

Re: How can I add extra index information?

2009-10-25T15:58:04Z

Ok, but is there any documentation on how to do this?

On Sun, Oct 25, 2009 at 8:38 PM, Brian Fox <brianf@...> wrote:

This specific functionality is being introduced in a pro plugin with
the 1.4.1 release. You'll be able to provide an RDF file or the REST
api.

On Sun, Oct 25, 2009 at 6:17 PM, Tercio Oliveira de Almeida
<tercio.coritiba@...> wrote:
> Hi,
>
> I am creating a plugin the reads some extended information from a file that
> is in a specific format
> (RAS), and I would like to index this info to be able to search for it using
> Nexus Search.
>
> I'd like to do that when the file is being uploaded.
>
> Is it possible to do this using the current Nexus plugin api? If so, where
> can I find documentation
> regarding the classes responsible for this?
>
> thanks,
> --
> --
> Tércio Oliveira de Almeida
> Ciencia da Computação - UFRGS
> toalmeida@...
>
>

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

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

Re: How can I add extra index information?

2009-10-25T15:38:12Z

This specific functionality is being introduced in a pro plugin with
the 1.4.1 release. You'll be able to provide an RDF file or the REST
api.

On Sun, Oct 25, 2009 at 6:17 PM, Tercio Oliveira de Almeida
<tercio.coritiba@...> wrote:

> Hi,
>
> I am creating a plugin the reads some extended information from a file that
> is in a specific format
> (RAS), and I would like to index this info to be able to search for it using
> Nexus Search.
>
> I'd like to do that when the file is being uploaded.
>
> Is it possible to do this using the current Nexus plugin api? If so, where
> can I find documentation
> regarding the classes responsible for this?
>
> thanks,
> --
> --
> Tércio Oliveira de Almeida
> Ciencia da Computação - UFRGS
> toalmeida@...
>
>

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

How can I add extra index information?

2009-10-25T15:17:30Z

Hi,

I am creating a plugin the reads some extended information from a file that is in a specific format
(RAS), and I would like to index this info to be able to search for it using Nexus Search.

I'd like to do that when the file is being uploaded.

Is it possible to do this using the current Nexus plugin api? If so, where can I find documentation
regarding the classes responsible for this?

thanks,
--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

Re: Benefit of changing to the new Nexus 1.4 plugin API

2009-10-21T07:09:40Z

I haven't looked at the oss LDAP plugin. The realm itself should work
with no changes. The user management portion has been refactored. It
was a more radical shift to where we needed to be. From here on out
we plan to follow a more normal deprecation model.

However converting from the old API to the new is stright forward.
Which reminds me, its time to update the wiki!

-Brian

On Oct 21, 2009, at 9:26 AM, Brian Fox wrote:

> Yes, the old plugins will continue to work, and it's likely that we'll
> oss our ldap implementation soon as well. Instead, create some new
> cool plugins with the new api ;-)
>
> On Wed, Oct 21, 2009 at 3:15 AM, Anders Hammar <anders@...>
> wrote:
>> Hi,
>>
>> As Nexus 1.4 is approaching, I'm thinking about changing my oss
>> ldap realm
>> to use the new (realm) plugin api instead of the old Plexus
>> component style.
>> Would there be any actually benefit of doing that? Nexus 1.4 will be
>> backwards compatible so that old plugins will continue to work,
>> right?
>>
>> /Anders
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>

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

Re: Benefit of changing to the new Nexus 1.4 plugin API

2009-10-21T06:26:34Z

Yes, the old plugins will continue to work, and it's likely that we'll
oss our ldap implementation soon as well. Instead, create some new
cool plugins with the new api ;-)

On Wed, Oct 21, 2009 at 3:15 AM, Anders Hammar <anders@...> wrote:
> Hi,
>
> As Nexus 1.4 is approaching, I'm thinking about changing my oss ldap realm
> to use the new (realm) plugin api instead of the old Plexus component style.
> Would there be any actually benefit of doing that? Nexus 1.4 will be
> backwards compatible so that old plugins will continue to work, right?
>
> /Anders
>

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

Benefit of changing to the new Nexus 1.4 plugin API

2009-10-21T00:15:53Z

Hi,

As Nexus 1.4 is approaching, I'm thinking about changing my oss ldap realm to use the new (realm) plugin api instead of the old Plexus component style. Would there be any actually benefit of doing that? Nexus 1.4 will be backwards compatible so that old plugins will continue to work, right?

/Anders

Re: Deploying to a hosted repository

2009-10-06T09:07:15Z

I've never trusted hudson to do my deploys, instead I run a mvn
deploy. I'd be surprised if hudson really provided no way to set
credentials, perhaps it uses the maven settings, but I don't really
know for sure. I can see from the stack trace that it's using the http
wagon, so that looks ok and the urls appear correct, so somehow the
auth is wrong. Look in the rss feeds or the logs to see what user is
being sent, that might give you a starting point.

On Tue, Oct 6, 2009 at 11:40 AM, Andrew Chandler <andy@...> wrote:

> After upgrading hudson I'm able to get a more intelligent error out of it.
> I'm able to deploy to nexus using scp settings in the settings.xml/pom files
> using mvn deploy.   However if I want to let my build system deploy only if
> all modules successfully compile I am stuck.   This used to work with
> proxmity, we simply used a "dav" url.      Using http to do the upload
> though is failing.   I'm wondering if somehow security is set wrong etc?   I
> have no way to specify a username and password on this deployment url.    I
> tried adding the "deploy" capability to the anonymous user but I'm not sure
> that gets me everything I need.   Looking in the nexus admin console the
> mirror I'm having trouble with is of type "snapshot" - and logged in as
> admin I get the "browse", "configuration" "mirrors" tabs but no upload
> tab.   If I change the repository to release I get an upload tab but I have
> no idea why the difference or if its even relevant to the deployment
> issue.     Is there any way using a web browser or some simple test program
> that we can validate my snapshot repository is setup correctly to permit
> publishing updates via http?????
>
> Any help is appreciated.
>
>
> Deploying the main artifact vnd_project-1.1-SNAPSHOT.pom
>
> [INFO ] Retrieving previous build number from
> org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error
> deploying artifact: Failed to transfer file:
> http://ourmachine.visionael.com:8091/nexus/content/repositories/inhouse.snapshot/com/visionael/vnd_project/1.1-SNAPSHOT/vnd_project-1.1-SNAPSHOT.pom.
> Return code is: 401
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
> at
> hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
> at
> hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
> at
> hudson.maven.reporters.MavenAbstractArtifactRecord$1.perform(MavenAbstractArtifactRecord.java:213)
> at hudson.model.TaskThread.run(TaskThread.java:118)
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
> transfer file:
> http://ourmachine.visionael.com:8091/nexus/content/repositories/inhouse.snapshot/com/visionael/vnd_project/1.1-SNAPSHOT/vnd_project-1.1-SNAPSHOT.pom.
> Return code is: 401
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:172)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

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

Deploying to a hosted repository

2009-10-06T08:40:54Z

After upgrading hudson I'm able to get a more intelligent error out of it. I'm able to deploy to nexus using scp settings in the settings.xml/pom files using mvn deploy. However if I want to let my build system deploy only if all modules successfully compile I am stuck. This used to work with proxmity, we simply used a "dav" url. Using http to do the upload though is failing. I'm wondering if somehow security is set wrong etc? I have no way to specify a username and password on this deployment url. I tried adding the "deploy" capability to the anonymous user but I'm not sure that gets me everything I need. Looking in the nexus admin console the mirror I'm having trouble with is of type "snapshot" - and logged in as admin I get the "browse", "configuration" "mirrors" tabs but no upload tab. If I change the repository to release I get an upload tab but I have no idea why the difference or if its even relevant to the deployment issue. Is there any way using a web browser or some simple test program that we can validate my snapshot repository is setup correctly to permit publishing updates via http?????

Any help is appreciated.

Deploying the main artifact vnd_project-1.1-SNAPSHOT.pom

[INFO ] Retrieving previous build number from 
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Failed to transfer file: http://ourmachine.visionael.com:8091/nexus/content/repositories/inhouse.snapshot/com/visionael/vnd_project/1.1-SNAPSHOT/vnd_project-1.1-SNAPSHOT.pom. Return code is: 401
	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
	at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
	at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
	at hudson.maven.reporters.MavenAbstractArtifactRecord$1.perform(MavenAbstractArtifactRecord.java:213)
	at hudson.model.TaskThread.run(TaskThread.java:118)
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://ourmachine.visionael.com:8091/nexus/content/repositories/inhouse.snapshot/com/visionael/vnd_project/1.1-SNAPSHOT/vnd_project-1.1-SNAPSHOT.pom. Return code is: 401
	at org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:172)
	at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
	at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Poll: Which JVM are you using for nexus?

2009-10-05T06:44:23Z

Did you run into any issues with Open JDK? We do not test with it, it
should work, but _should_ and _do_ are not always the same.

Thanks

On Oct 4, 2009, at 5:05 PM, Ringo De Smet wrote:

> http://packages.ubuntu.com/intrepid/openjdk-6-jdk
>
> Ubuntu Intrepid because of reference deployment platform.
>
> Greetz,
>
> Ringo
>
> 2009/9/14 Brian Demers <bdemers@...>:
>>
>> I noticed sun's EOL time ends java 1.5 normal support for October
>> 30th.
>> http://java.sun.com/products/archive/eol.policy.html
>> Which prompted the question. which JVM (vender / version) are you
>> using in
>> production / development?
>>
>> Here at Sonatype we have CI builds running with sun JVM 1.6 on
>> windows and
>> ubuntu. We have developers using osx (1.5, 1.6) , windows (sun
>> 1.6), linux
>> (1.6)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>

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

Re: Repository Plugin Tests example

2009-10-05T04:28:45Z

Hi Tercio,

You can look at artifactory migration plugin.....

http://svn.sonatype.org/nexus-plugins/trunk/nexus-migration-plugin/

So far, it does has the integration tests on a isolated project. But we are working on having the IT and UT on the same project. So far it is a work in progress for nexus 1.4.1

VELO

On Sun, Oct 4, 2009 at 11:30 PM, Tercio Oliveira de Almeida <tercio.coritiba@...> wrote:

Hello,

Do you have some samples on how to test extra repository plugin in Nexus?

I would like to create a plugin to deal with RAS artifacts, and I would like to automated tests
and automated integration tests with Nexus, but I couldn't find any example on how to do that
with this kind of plugin.

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

Re: Repository Plugin Tests example

2009-10-05T01:53:50Z

Hi,

you are right here, the tools after PM support are not there yet.

You can track https://issues.sonatype.org/browse/NEXUS-2766

(or the JIRA in general)

~t~

On Mon, Oct 5, 2009 at 4:30 AM, Tercio Oliveira de Almeida <tercio.coritiba@...> wrote:

Hello,

Do you have some samples on how to test extra repository plugin in Nexus?

I would like to create a plugin to deal with RAS artifacts, and I would like to automated tests
and automated integration tests with Nexus, but I couldn't find any example on how to do that
with this kind of plugin.

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

Repository Plugin Tests example

2009-10-04T19:30:37Z

Hello,

Do you have some samples on how to test extra repository plugin in Nexus?

I would like to create a plugin to deal with RAS artifacts, and I would like to automated tests
and automated integration tests with Nexus, but I couldn't find any example on how to do that
with this kind of plugin.

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...

Re: Poll: Which JVM are you using for nexus?

2009-10-04T14:05:24Z

http://packages.ubuntu.com/intrepid/openjdk-6-jdk

Ubuntu Intrepid because of reference deployment platform.

Greetz,

Ringo

2009/9/14 Brian Demers <bdemers@...>:
>
> I noticed sun's EOL time ends java 1.5 normal support for October 30th.
> http://java.sun.com/products/archive/eol.policy.html
> Which prompted the question. which JVM (vender / version) are you using in
> production / development?
>
> Here at Sonatype we have CI builds running with sun JVM 1.6 on windows and
> ubuntu. We have developers using osx (1.5, 1.6) , windows (sun 1.6), linux
> (1.6)

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

Re: Strange artifact/pom setting in Maven Central...

2009-09-29T16:15:31Z

Hi Sam,

This was a bug on nexus 1.3.6 and it is already fixed on 1.4.0 (to be released in a few days).

If you wanna try

http://repository.sonatype.org/index.html#nexus-search;quick~json-lib

VELO

On Tue, Sep 29, 2009 at 8:05 PM, Sam Husson <shusson@...> wrote:

Folks,

I came across an unusual situation where a nexus search for json-lib
(GAV: net.sf.jason-lib:json-lib:2.3:jar) returned -- among other things
-- an entry with packaging jar where the pom does not have a classifier
or anything so that I could rationally expect to find both in our nexus
file system and in the remote Maven Central repo the following
artifact... net/sf/json-lib/json-lib/2.3/json-lib-2.3.jar. Well, on our
file system we see only the pom. In maven central we see
json-lib-2.3-jdk13-javadoc.jar 11-Jul-2009 22:40
245582
json-lib-2.3-jdk13-sources.jar 11-Jul-2009 22:40 102390
json-lib-2.3-jdk13.jar 11-Jul-2009 22:40 151390
json-lib-2.3-jdk15-javadoc.jar 11-Jul-2009 22:40 248751
json-lib-2.3-jdk15-sources.jar 11-Jul-2009 22:40 104049
json-lib-2.3-jdk15.jar

This suggests that a classifier should be specified. Sure enough, when I added <classifier>jdk15</classifier> to my dependency I got the correct jar.

My questions:

1 - How is it that the pom in does not specify a classifier yet json-lib-2.3.jar doesn't exist?
2 - How can nexus list the following in a search for json-lib:
version packaging classifier Download
2.3 jar artifact,pom

yet clicking the pom link shows this dependency...
<dependency>
<groupId>net.sf.json-lib</groupId>
<artifactId>json-lib</artifactId>
<version>2.3</version>
</dependency>

Instead of
<dependency>
<groupId>net.sf.json-lib</groupId>
<artifactId>json-lib</artifactId>
<version>2.3</version>
<classifier>whatever</classifier>
</dependency>

I hope this loaded question is not too confusing.

Sam

CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.

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

Strange artifact/pom setting in Maven Central...

2009-09-29T15:59:35Z

Folks,

I came across an unusual situation where a nexus search for json-lib
(GAV: net.sf.jason-lib:json-lib:2.3:jar) returned -- among other things
-- an entry with packaging jar where the pom does not have a classifier
or anything so that I could rationally expect to find both in our nexus
file system and in the remote Maven Central repo the following
artifact... net/sf/json-lib/json-lib/2.3/json-lib-2.3.jar. Well, on our
file system we see only the pom. In maven central we see
json-lib-2.3-jdk13-javadoc.jar 11-Jul-2009 22:40
245582
json-lib-2.3-jdk13-sources.jar 11-Jul-2009 22:40 102390
json-lib-2.3-jdk13.jar 11-Jul-2009 22:40 151390
json-lib-2.3-jdk15-javadoc.jar 11-Jul-2009 22:40 248751
json-lib-2.3-jdk15-sources.jar 11-Jul-2009 22:40 104049
json-lib-2.3-jdk15.jar

This suggests that a classifier should be specified. Sure enough, when I added <classifier>jdk15</classifier> to my dependency I got the correct jar.

My questions:

1 - How is it that the pom in does not specify a classifier yet json-lib-2.3.jar doesn't exist?
2 - How can nexus list the following in a search for json-lib:
version packaging classifier Download
2.3 jar artifact,pom

yet clicking the pom link shows this dependency...
<dependency>
<groupId>net.sf.json-lib</groupId>
<artifactId>json-lib</artifactId>
<version>2.3</version>
</dependency>

Instead of
<dependency>
<groupId>net.sf.json-lib</groupId>
<artifactId>json-lib</artifactId>
<version>2.3</version>
<classifier>whatever</classifier>
</dependency>

I hope this loaded question is not too confusing.

Sam

CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.

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

RE: Poll: Which JVM are you using for nexus?

2009-09-14T14:21:50Z

Jdk1.6.0_15

David Hudgins

Lead Technical Architect

Applied Systems Architecture | IT Architecture & Engineering

Mobile 972.207.3980

From: Brian Demers [mailto:bdemers@...]
Sent: Monday, September 14, 2009 10:52 AM
To: nexus-user@...; nexus-dev@...
Subject: [nexus-dev] Poll: Which JVM are you using for nexus?

I noticed sun's EOL time ends java 1.5 normal support for October 30th. http://java.sun.com/products/archive/eol.policy.html

Which prompted the question. which JVM (vender / version) are you using in production / development?

Here at Sonatype we have CI builds running with sun JVM 1.6 on windows and ubuntu. We have developers using osx (1.5, 1.6) , windows (sun 1.6), linux (1.6)

Re: Poll: Which JVM are you using for nexus?

2009-09-14T13:05:04Z

Server: Sun JDK 1.6.0_13 (64-bit) on SUSE Linux.
Locally I use both Sun JDK 1.5 and 1.6 on Windows (for Nexus test/development).

/Anders

On Mon, Sep 14, 2009 at 17:51, Brian Demers <bdemers@...> wrote:

I noticed sun's EOL time ends java 1.5 normal support for October 30th. http://java.sun.com/products/archive/eol.policy.html

Which prompted the question. which JVM (vender / version) are you using in production / development?

Here at Sonatype we have CI builds running with sun JVM 1.6 on windows and ubuntu. We have developers using osx (1.5, 1.6) , windows (sun 1.6), linux (1.6)

Re: [nexus-user] Poll: Which JVM are you using for nexus?

2009-09-14T09:00:38Z

Also, it would be great to know if anything is keeping you on 1.5 ( i
should have put that in the first email)

On Sep 14, 2009, at 11:56 AM, Carr, Brian M wrote:

> Java 1.5 64-bit on Solaris/sparc
>
> --b
> ______________________________
> Brian M. Carr
> Identity and Access Management
> ITS Applications
> University of Texas at Austin
> V: 512-232-6419
> F: 512-471-5746
> brianmcarr@...
>
> On Sep 14, 2009, at 10:51 AM, Brian Demers wrote:
>
>>
>> I noticed sun's EOL time ends java 1.5 normal support for October
>> 30th. http://java.sun.com/products/archive/eol.policy.html
>>
>> Which prompted the question. which JVM (vender / version) are you
>> using in production / development?
>>
>>
>> Here at Sonatype we have CI builds running with sun JVM 1.6 on
>> windows and ubuntu. We have developers using osx (1.5, 1.6) ,
>> windows (sun 1.6), linux (1.6)
>

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

Re: [nexus-user] Poll: Which JVM are you using for nexus?

2009-09-14T08:56:07Z

Java 1.5 64-bit on Solaris/sparc

--b
______________________________
Brian M. Carr
Identity and Access Management
ITS Applications
University of Texas at Austin
V: 512-232-6419
F: 512-471-5746
brianmcarr@...

On Sep 14, 2009, at 10:51 AM, Brian Demers wrote:

>
> I noticed sun's EOL time ends java 1.5 normal support for October
> 30th. http://java.sun.com/products/archive/eol.policy.html
>
> Which prompted the question. which JVM (vender / version) are you
> using in production / development?
>
>
> Here at Sonatype we have CI builds running with sun JVM 1.6 on
> windows and ubuntu. We have developers using osx (1.5, 1.6) ,
> windows (sun 1.6), linux (1.6)

smime.p7s (7K) Download Attachment

Poll: Which JVM are you using for nexus?

2009-09-14T08:51:56Z

I noticed sun's EOL time ends java 1.5 normal support for October 30th. http://java.sun.com/products/archive/eol.policy.html

Which prompted the question. which JVM (vender / version) are you using in production / development?

Here at Sonatype we have CI builds running with sun JVM 1.6 on windows and ubuntu. We have developers using osx (1.5, 1.6) , windows (sun 1.6), linux (1.6)

Re: Links plugin

2009-09-10T02:32:28Z

@Andres

No, we haven't published it yet anywhere.

On Tue, Sep 8, 2009 at 9:17 PM, Brian Fox <brianf@...> wrote:

Yes, I sent Igor the CLA.

2009/9/8 Tamás Cservenák <tamas@...>:

> That's cool! Thanks Igor.
> The details will follow soon, by Brian I believe ;)
> ~t~
>
> On Tue, Sep 8, 2009 at 6:00 PM, Czechowski, Igor
> <Igor.Czechowski@...> wrote:
>>
>> Hi Sonatype folks,
>>
>>
>>
>> We‘ve developed the plugin, that displays configurable links in a separate
>> navigation panel - its functionality is nothing more than what Help section
>> provides.
>>
>> The reason it was created is to provide internal help links for the
>> repository manager and replace existing help section as it’s not relevant
>> for repository end users in our usage scenario.
>>
>>
>>
>> The plugin to be more useful for the general Nexus community it would
>> require to have an administration side that we work on at this moment.
>>
>> Plugin was developed against version 1.3.6 , since we need something that
>> works with the latest stable version.
>>
>>
>>
>> We would like to donate the plugin with its source code to the Nexus
>> community (as long as community wants it :D)
>>
>>
>>
>> I be glad someone at Sonatype could tell me how we can achieve that.
>>
>>
>>
>> Cheers,
>>
>> Igor
>>
>>
>>
>> P.S. Once section would get renamed it could potentially replace static
>> Help section to provide configurable one.
>

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

Re: Links plugin

2009-09-08T12:17:37Z

Yes, I sent Igor the CLA.

2009/9/8 Tamás Cservenák <tamas@...>:

> That's cool! Thanks Igor.
> The details will follow soon, by Brian I believe ;)
> ~t~
>
> On Tue, Sep 8, 2009 at 6:00 PM, Czechowski, Igor
> <Igor.Czechowski@...> wrote:
>>
>> Hi Sonatype folks,
>>
>>
>>
>> We‘ve developed the plugin, that displays configurable links in a separate
>> navigation panel - its functionality is nothing more than what Help section
>> provides.
>>
>> The reason it was created is to provide internal help links for the
>> repository manager and replace existing help section as it’s not relevant
>> for repository end users in our usage scenario.
>>
>>
>>
>> The plugin to be more useful for the general Nexus community it would
>> require to have an administration side that we work on at this moment.
>>
>> Plugin was developed against version 1.3.6 , since we need something that
>> works with the latest stable version.
>>
>>
>>
>> We would like to donate the plugin with its source code to the Nexus
>> community (as long as community wants it :D)
>>
>>
>>
>> I be glad someone at Sonatype could tell me how we can achieve that.
>>
>>
>>
>> Cheers,
>>
>> Igor
>>
>>
>>
>> P.S. Once section would get renamed it could potentially replace static
>> Help section to provide configurable one.
>

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

Re: Links plugin

2009-09-08T11:38:10Z

Excellent! I believe there is a jira filed by me for something like this.
Until it gets hosted at Sonatype, is it available somewhere for me to try out?

/Anders

On Tue, Sep 8, 2009 at 18:00, Czechowski, Igor <Igor.Czechowski@...> wrote:

Hi Sonatype folks,

We‘ve developed the plugin, that displays configurable links in a separate navigation panel - its functionality is nothing more than what Help section provides.

The reason it was created is to provide internal help links for the repository manager and replace existing help section as it’s not relevant for repository end users in our usage scenario.

The plugin to be more useful for the general Nexus community it would require to have an administration side that we work on at this moment.

Plugin was developed against version 1.3.6 , since we need something that works with the latest stable version.

We would like to donate the plugin with its source code to the Nexus community (as long as community wants it :D)

I be glad someone at Sonatype could tell me how we can achieve that.

Cheers,

Igor

P.S. Once section would get renamed it could potentially replace static Help section to provide configurable one.

Re: Links plugin

2009-09-08T11:06:05Z

That's cool! Thanks Igor.

The details will follow soon, by Brian I believe ;)

~t~

On Tue, Sep 8, 2009 at 6:00 PM, Czechowski, Igor <Igor.Czechowski@...> wrote:

Hi Sonatype folks,

We‘ve developed the plugin, that displays configurable links in a separate navigation panel - its functionality is nothing more than what Help section provides.

The reason it was created is to provide internal help links for the repository manager and replace existing help section as it’s not relevant for repository end users in our usage scenario.

The plugin to be more useful for the general Nexus community it would require to have an administration side that we work on at this moment.

Plugin was developed against version 1.3.6 , since we need something that works with the latest stable version.

We would like to donate the plugin with its source code to the Nexus community (as long as community wants it :D)

I be glad someone at Sonatype could tell me how we can achieve that.

Cheers,

Igor

P.S. Once section would get renamed it could potentially replace static Help section to provide configurable one.

Links plugin

2009-09-08T09:00:59Z

Hi Sonatype folks,

We‘ve developed the plugin, that displays configurable links in a separate navigation panel - its functionality is nothing more than what Help section provides.

The reason it was created is to provide internal help links for the repository manager and replace existing help section as it’s not relevant for repository end users in our usage scenario.

The plugin to be more useful for the general Nexus community it would require to have an administration side that we work on at this moment.

Plugin was developed against version 1.3.6 , since we need something that works with the latest stable version.

We would like to donate the plugin with its source code to the Nexus community (as long as community wants it :D)

I be glad someone at Sonatype could tell me how we can achieve that.

Cheers,

Igor

P.S. Once section would get renamed it could potentially replace static Help section to provide configurable one.

Re: I want to create a plugin to provide OMG RAS support for Nexus

2009-09-02T09:58:25Z

Thanks Tamás,

I think I will choose the easy option. :-)

Do you mean _alternate_ screen as creating a new tab or something
to deal only with my custom repository?
Or to open my custom screen 'on demand', every time I would deal
with my custom repositoriess?
Would it work for either adding repository files, and getting its custom info?

2009/9/2 Tamás Cservenák <tamas@...>

Hi there,

as of plugins, yes:
http://svn.sonatype.org/nexus-plugins/trunk/nexus-sample-plugins/

But that example is hardly finished. That's due to the fact that UI is
lagging behind core capabilities currently. So, the current "core UI"
will be not able to manage your "new" repository type added by plugin.
Until this is not handled in core, there are two "workarounds"
mentioned in 2nd part of the blog that Brian referred to:

* bury yourself deeply into our current ExtJS (JavaScript) based UI
and add plugin JS resources that will modify the screen (hardly
possible, if it is at all) - HARD, not worth going this way
* simply, make your plugin provide and _alternate_ screen for managing
your kind of reposes - EASY

http://www.sonatype.com/people/2009/07/writing-plugins-for-nexus-part-2/

In "And finally, the bad news" section...

~t~

On Wed, Sep 2, 2009 at 4:12 PM, Tercio Oliveira de
Almeida<tercio.coritiba@...> wrote:
> Do you have an opensource project with extra repositories for nexus?
>
> Or any sample plugin that shows how to implement an extra repository for
> nexus?
>
> On Tue, Sep 1, 2009 at 7:49 PM, Brian Fox <brianf@...> wrote:
>>
>> The source is already available at http://svn.sonatype.org/nexus
>>
>> Tamas blogged about writing plugins:
>> http://www.sonatype.com/people/2009/06/writing-plugins-for-nexus-part-1/
>> but this doesn't show the new packaging type. Sometime this week we
>> should have an archetype created for a sample plugin. The blog and new
>> plugin model is dependent on 1.4 (trunk) so you should start there. We
>> are close to a release so it's fairly stable already.
>>
>> 2009/9/1 Tercio Oliveira de Almeida <tercio.coritiba@...>:
>> > Hello,
>> >
>> > I want to create a plugin for Nexus. The main objective, is to provide
>> > support for the
>> > OMG Reusable Asset Specification format. I'll do that by indexing the
>> > necessary values
>> > contained in the asset descriptor, and by providing additional output
>> > related to this asset,
>> > by querying the asset specification file.
>> >
>> > So, could someone please provide me access to your SVN and sources? And
>> > also, if
>> > you have specific documentation related to Nexus plugin development, it
>> > will help me a lot!
>> >
>> >
>> > thanks,
>> > --
>> > --
>> > Tércio Oliveira de Almeida
>> > Ciencia da Computação - UFRGS
>> > toalmeida@...
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
>> For additional commands, e-mail: nexus-dev-help@...
>>
>
>
>
> --
> --
> Tércio Oliveira de Almeida
> Ciencia da Computação - UFRGS
> toalmeida@...
>
>

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

--
--
Tércio Oliveira de Almeida
Ciencia da Computação - UFRGS
toalmeida@...