Re: Failed to deploy artifacts

[Wayne Fay]

> We are running Nexus 1.8. I am considering upgrading to the latest version.
> Would our artifacts be migrated safely?

This mailing list supports Apache Maven. Sonatype Nexus has its own
mailing lists. Please use them for such questions.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Failed to deploy artifacts

[AnasMughal]

Oh, thanks for the pointer... I figured it out... The permissions were wrong.
Thank you very much for your help.

We are running Nexus 1.8. I am considering upgrading to the latest version.
Would our artifacts be migrated safely?

--
View this message in context: 
http://maven.40175.n5.nabble.com/Failed-to-deploy-artifacts-tp5710875p5710923.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: How does one mirror a maven repository?

[Gandhi, Pawan]

This may be helpful
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html


-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu] 
Sent: Wednesday, June 06, 2012 1:02 PM
To: Maven Users List
Subject: Re: How does one mirror a maven repository?

Nexus Pro has functionality that would allow you to do mirroring, we have a 
bunch of customers doing exactly what you ask.

On Fri, Jun 1, 2012 at 12:53 PM, Phillip Hellewell  wrote:

> Hi,
>
> Our company would like to mirror our Maven repository at a remote 
> location.  Currently we've been using Nexus with a proxy repository, 
> which works as advertised, but we really need a full mirror not just 
> an on-demand cache.
>
> The reason we need it to be a full mirror is because we want it to 
> also serve as a remote backup, should our central repository have a 
> catastrophic disk failure.
>
> Is there any way to accomplish this with Nexus, or do I just need to 
> set up rsync or something?
>
> Thanks,
> Phillip
>

This message, including any attachments, is intended only for the recipient(s) 
named above. It may contain confidential and privileged information. If you 
have received this communication in error, please notify the sender immediately 
and destroy or delete the original message. Also, please be aware that if you 
are not the intended recipient, any review, disclosure, copying, distribution 
or any action or reliance based on this message is prohibited by law.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: why is commons-math3 jar missing from sonatype mirror of central?

[Brian Fox]

Found the email Russ ;-)

Anyway, repository.s.o isn't intended to be a mirror, it's just a
proxy used primarily by us for internal use and for oss users building
our stuff. http://search.maven.org has replaced the need to use rso's
search as well.

Regarding why the files aren't in the repository, it's no longer synced as
a mirror since we now have 4 other machines for that purpose, so only
things that have been requested are in there. It does appear to be in the
index though:
https://repository.sonatype.org/index.html#nexus-search;quick~commons-math



On Mon, Jun 4, 2012 at 8:54 PM, Russ Tremain  wrote:

> it is here:
>
>http://repo.maven.apache.org/**maven2/org/apache/commons/**
> commons-math3/3.0
>
> but not getting sync'd to the sonatype mirror:
>
>https://repository.sonatype.**org/index.html#nexus-search;**
> quick~commons-math3
>
> in fact I only see 7 of the 32 files mirrored.
>
> anyone know why?
>
> It makes me wonder if other files are missing as well...
>
> /r
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@maven.**apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: How does one mirror a maven repository?

[Brian Fox]

Nexus Pro has functionality that would allow you to do mirroring, we have a
bunch of customers doing exactly what you ask.

On Fri, Jun 1, 2012 at 12:53 PM, Phillip Hellewell  wrote:

> Hi,
>
> Our company would like to mirror our Maven repository at a remote
> location.  Currently we've been using Nexus with a proxy repository, which
> works as advertised, but we really need a full mirror not just an on-demand
> cache.
>
> The reason we need it to be a full mirror is because we want it to also
> serve as a remote backup, should our central repository have a catastrophic
> disk failure.
>
> Is there any way to accomplish this with Nexus, or do I just need to set up
> rsync or something?
>
> Thanks,
> Phillip
>

RE: Editing a plugin announcement doesn't work

[Martin Gainty]

possibly version mismatch on one of your dependent jars..i would try 
contacting1)atlassian
2)maven users group

Martin-
___
...extensive disclaimer goes here...

 > Date: Wed, 6 Jun 2012 10:20:58 -0400
> Subject: Re: Editing a plugin announcement doesn't work
> From: davelnew...@gmail.com
> To: d...@struts.apache.org
> 
> Hmm, my off-the-top-of-my-head guess is this is due to a Confluence
> upgrade, but I neither know anything about that, nor could I do anything
> about it if I did.
> 
> Anyone?
> 
> d.
> 
> For reference:
> 
> java.lang.ClassCastException: com.atlassian.confluence.pages.BlogPost
> cannot be cast to com.atlassian.confluence.pages.Page
>   at 
> com.atlassian.confluence.pages.actions.EditPageAction.doDefault(EditPageAction.java:134)
>   at sun.reflect.GeneratedMethodAccessor1837.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:302)
>   at 
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:170)
>   at 
> com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:35)
>   at 
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
>   at 
> com.atlassian.confluence.util.LoggingContextInterceptor.intercept(LoggingContextInterceptor.java:49)
>   at 
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
>   at 
> com.atlassian.confluence.core.CancellingInterceptor.intercept(CancellingInterceptor.java:23)
>   at 
> com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
> 
> 
> 
> On Wed, Jun 6, 2012 at 10:10 AM, Rees Byars  wrote:
> 
> > Sure Dave, sorry I didn't include better information before.  I've
> > attached a screenshot of the page that is generated.
> > As far as my permissions go, I don't know what they are exactly, but I
> > know that I can edit most other pages, and I created the announcement.
> >
> > The steps to recreate the error are:
> >
> > 1) Go to https://cwiki.apache.org/S2PLUGINS/home.html
> > 2) Click on one of the Announcement Blog Posts listed on the page
> > 3) From the blog post page, click "Edit Page" in the top right-hand corner
> >
> > Thanks,
> > Rees
> >
> >
> > On Wed, Jun 6, 2012 at 8:03 AM, Dave Newton  wrote:
> >
> >> Generates "an error"? What error? Do you have edit rights? Please provide
> >> actionable information.
> >>
> >> Dave
> >>
> >> On Wed, Jun 6, 2012 at 7:59 AM, Rees Byars  wrote:
> >>
> >> > From the plugin page (https://cwiki.apache.org/S2PLUGINS/home.html),
> >> if I
> >> > click on an announcement blog post and then click edit, it generates an
> >> > error.  I wanted to edit an announcement, but it doesn't seem possible
> >> for
> >> > me.
> >> >
> >> > Not a major issue to me, so no worries if it doesn't get addressed.
> >> >
> >> > Regards,
> >> > Rees
> >> >
> >>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> > For additional commands, e-mail: dev-h...@struts.apache.org
> >
  

Re: maven release plugin and subversion externals

[Michael Holopainen]

That method will work fine with projects external repos. Just as long as
there are no svn:external links inside the folders itself come from
svn:externals link. 

Other important thing to note is that if you are using separeate aggregation
and root pom's in the project. then you must have  definition
in you modules'  -tags. 



--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-release-plugin-and-subversion-externals-tp109483p5710914.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven release plugin and subversion externals

[Michael Holopainen]

Start with reading the Maven release plugin description, specially prepare
and perform action's documentation. 

This problem with svn:externals is that IF you are using svn:externals that
link to the project itself the release branch will point to the trunk.

release:prepare phase will 
1. crawls the project's pom.xml and change the  number to the given
release version  
2. commits the changed code to SVN repo using each module's  
 - value
3. makes an svn copy of the revision it jsut committed to svn to the
 (defaulting to "../tags" relative to scm-developerConnection value 
4. it then again crawls the project's pom.xml and change the 
number to the next SNAPSHOT version

NOW, here is the problem ! 
Let's assume that you have the externals properties defined to the projects
root folder. Now when the release:prepare makes a copy of that folder in SVN
it is a copy and that copy contains identical properties. So both the folder
in trunk and the copy of the folder in release - branch contain IDENTICAL
dynamic links to the trunk of the modules sub folders which now have the
next -SNAPSHOT version in them. So when you run the release:perform it
"releases" the the next SNAPSHOT, not the release. 

This is easy to fix, but only as long as you are using svn:externals _ONLY_
at the root level of the project !  
You must do little magic between running release:prepare and relese:perform.
So you ABSOLUTELY MUST NOT run in same mvn command (mvn relese:prepare
release:perform) ! Instead you must:
1. First run the release prepare. 
2. The look at the Maven ouput (or run: mvn log . ) to find revision number
of the relase branch version (svn copy). 
3. Now armed with the revision number of the release you must checkout the
new release branch to some temp folder (The HEAD not the revision!). Go the
the folder where you just checked out the release branch and edit that
folder's svn properties, "svn propedit svn:externals ." and add the revision
we talked about to each modules link definition "-r123". Then remember to
commit it back to svn !  
4. That's it ! Now Go back to the folder you ran the release:prepare at. And
delete this temp folder to where you checked out the release to. Now run
"mvn release:perform" which checks out the release branch to a temp folder
where it build, tests and deploys artifacts to the maven repo. Now that the
links in SVN release branch point to correct revision of the source code
everything works ok. 

You do need to do this for every time you make a relase. You can script all
this.  

P.S. When I talk about "branch" I mean svn release "tag", I just feel in
this context word "branch" better describes what we are doing (and in svn
there is no tag or branch, just copy).

--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-release-plugin-and-subversion-externals-tp109483p5710913.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org