Re: Can I release the Install Plugin?

Dennis Lundberg wrote: I had a look at the Install Plugin which hasn't had a release in a long time, almost two years now. So I thought that I'd do a release of it. Thanks Dennis! Does anyone have something that you want added before a release? I was just looking through some issues in the

Re: [PLEASE TEST] Maven 2.1.0-RC2

John Casey wrote: http://tinyurl.com/maven-2-1-0-RC2 Again, let me know if you have any problems. Just to make sure you're aware of this: I discovered one more regression in the RC (MNG-4086) that was caused by my work on merging MNG-3284 to 2.1.x. The issue is fixed by now and an IT in-pla

Re: Redeployment of plugin sites (was Re: [maven-shade-plugin] Typo in examples)

On Sun, Mar 15, 2009 at 4:30 AM, Benjamin Bentmann wrote: > Do we have some guideline for the deployed plugin site and its > state/contents? For instance, the site is now saying "Version: > 1.3-SNAPSHOT", its "Source Repository" report points to trunk instead of >  maven-shade-plugin-1.2 and the

Re: Redeployment of plugin sites (was Re: [maven-shade-plugin] Typo in examples)

until somebody puts it in the parent pom's URL and your project does not override but has a different version On 15/03/2009, lukewpatterson wrote: > > > Benjamin Bentmann wrote: >> >> >> Do we have some guideline for the deployed plugin site and its >> state/contents? >> > > I really wish using $

Can I release the Install Plugin?

Hi I had a look at the Install Plugin which hasn't had a release in a long time, almost two years now. So I thought that I'd do a release of it. JIRA has a list of 9 issues solved: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136&styleName=Html&version=13495 Nothing major seems t

Re: install:install-file & Repository MetaData files maven-metadata-local.xml

Yes it is definately dirty. Using a repo is the cleanest way --Brian (mobile) On Mar 15, 2009, at 7:54 AM, Kaveh Goudarzi wrote: Hi Brian, So is the idea would be to use the assembly plugin to create a bundle which the user can "unpack" over their repository and end up with the correc

Re: Redeployment of plugin sites (was Re: [maven-shade-plugin] Typo in examples)

Benjamin Bentmann wrote: > > > Do we have some guideline for the deployed plugin site and its > state/contents? > I really wish using ${project.version} in the site url pattern was a more common practice. -- View this message in context: http://www.nabble.com/-maven-shade-plugin--Typo-in-

Re: install:install-file & Repository MetaData files maven-metadata-local.xml

Hi Brian, So is the idea would be to use the assembly plugin to create a bundle which the user can "unpack" over their repository and end up with the correct files? (sounds a bit dirty no?) or is there a specific repo goal/descriptor function for this that I've missed? In the mean

Re: Redeployment of plugin sites (was Re: [maven-shade-plugin] Typo in examples)

I once got pretty upset as a user when I struggled with a non-functional plugin feature documented on a plugin site just to find that the site described unreleased stuff. While this particular problem doesn't apply Hehe, I tried using the "prepare-package" phase a few days ago; it didn't work

Redeployment of plugin sites (was Re: [maven-shade-plugin] Typo in examples)

Hervé BOUTEMY wrote: [...] site deployed. Do we have some guideline for the deployed plugin site and its state/contents? For instance, the site is now saying "Version: 1.3-SNAPSHOT", its "Source Repository" report points to trunk instead of maven-shade-plugin-1.2 and the source XRef report

Re: [maven-shade-plugin] Typo in examples

fixed in svn and site deployed. Don't hesitate to open a Jira issue and attach a patch if you find other fixes. Thank you Hervé Le dimanche 15 mars 2009, Paul a écrit : > I was shading multiple jars needing services declarations and have been > facing a typo issue, more precisely a "missing s"