Release maven-javadoc-plugin 2.5 ?

Hello, Roadmap for maven-javadoc-plugin 2.5 seems to be ok. http://jira.codehaus.org/browse/MJAVADOC?report=com.atlassian.jira.plugin.system.project:roadmap-panel Is it possible to release it ? Thanks Damien - To unsubscribe,

Re: [vote] Release Continuum 1.1 Final

> Everyone is encouraged to vote and give their feedback. Everything is working fine (embedding in Tomcat, mysql database upgrade with proxy), so +1 Damien Lecan

Re: How to discuss about misspelling ?

> Can you provide a patch for you translations fixes? Patch is ready, against continuum-1.1-beta-4 tag. How can I submit it : - here ? - in http://jira.codehaus.org/browse/CONTINUUM-546 ? - in a new jira ? Damien

Re: [vote] Release Continuum 1.1-beta-4

> It's duplicate with CONTINUUM-1492. > Can you detailled what kind of proxy you use ? (NTLM authentification ?). Squid, without authentication > Because as I have explained in CONTINUUM-1492, I have tested this > successfully with adding -Dhttp.proxyHost=proxyhost.com, > -Dhttp.proxyPort=80 (but

Re: [vote] Release Continuum 1.1-beta-4

2007/10/25, Emmanuel Venisse <[EMAIL PROTECTED]>: > Hmm, file an issue and I'll try to fix it (but I don't have a proxy to do a > real test) http://jira.codehaus.org/browse/CONTINUUM-1536 Damien

Re: [vote] Release Continuum 1.1-beta-4

> [x] -1 Don't release it, because... I can't upgrade my MySql database. I exported Continuum 1.1-beta-3 database with a patched DMC beta-3, I created a new db for 1.1-beta-4, and DMC beta-4 doesn't seem to be able to load data in this new database : ... 20101 [main] INFO JPOX.RDBMS - Creatin

Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3

> > The export tool itself fails to read old database schema. Something > > else to configure ? > > to export 1.1-beta-2 db, you must use dmc 1.1-beta-2 and to import in > 1.1-beta-3 db, dmc 1.1-beta-3 Ok, I patched dmc 1.1-beta-2 too in order to export data. Than I used a patched dmc 1.1-beta-3

Re: [vote] Release Continuum 1.1-beta-3

> Everyone is encouraged to vote and give their feedback. Page group summary is now very fast, database upgrade for Mysql works (almost), so +1 (non binding) Damien Lecan -- View this message in context: http://www.nabble.com/-vote--Release-Continuum-1.1-beta-3-tf4482966.html#a12823925 S

Re: [m2-javadoc] MJAVADOC-116 fix?

Hello, Will something be done for this bug ? It's a serious regression, very, very annoying ... Thanks Damien 2007/7/25, Paul Gier <[EMAIL PROTECTED]>: > I spent a little time looking into a similar issue a while ago. The > issue seems to be with the inter-module dependency resolution when a >

Re: [VOTE] Release maven-one-plugin 1.1

+1 (Non-binding) M1 to M2 pom converter is an amazing feature, very useful. It's work well. There's no reason now not to migrate M1 projects to M2 (Jakarta commons projects ? ;o) Thanks for your work Damien Lecan 2007/5/31, Dennis Lundberg <[EMAIL PROTECTED]>: Hi, I'd

Re: Tool to clean snapshots from the repo

ponent. If you are interested in this method, I can point you to the script that does the cleaning. Evan On 5/11/07, Damien Lecan <[EMAIL PROTECTED]> wrote: > > Any idea of how to remove old artifact snapshot ? > > Can repositorytools be useful for that ? > > Than

Re: Tool to clean snapshots from the repo

Any idea of how to remove old artifact snapshot ? Can repositorytools be useful for that ? Thanks Damien Which goal specifically? I can only see: repositorytools:add-artifact repositorytools:add-plugin-group repositorytools:add-repository repositorytools:copy-artifact repositorytools:copy-r

Re: "Corrupted" maven-metadata-central.xml when going offline => online mode ?

2007/4/20, Jason van Zyl <[EMAIL PROTECTED]>: It's in JIRA, same thing happens if there is a connection problem. The metadata will get written out and then not work on subsequent runs. This one ? http://jira.codehaus.org/browse/MNG-2377 Opened since Maven 2.0-alpha-1 (but only since june 2006)

"Corrupted" maven-metadata-central.xml when going offline => online mode ?

en-source-plugin' does not exist or no valid version could be found" To recovered your project, you have to remove org/apache/maven/plugins/maven- or to call mvn with -U option. Is it a usual behavior ? Can it be linked with the fact that sometimes my local repository d

Re: dependency on system library (java.library.path)

Hello, For system libraries however the name cares when it is loaded from something that I can not control (foo-1.0.jar loads foo.dll and it can not be named foo-1.0.dll). Is there a way to put various artifacts with different versions but the same file-name into a maven repository? In other wor

Re: Adding default OSGi information to JARs

2007/3/28, Carlos Sanchez <[EMAIL PROTECTED]>: > It would be great if that could be available in 2.0.x version of > Maven. We are too far from 2.1 version. you will always have the option to add a plugin to your pom that will generate the OSGi manifest (the maven-bundle-plugin from Apache Felix).

Re: Adding default OSGi information to JARs

> Ok I understand, but you didn't answer my (not clear) question : if > OSGi packaging is fast enough, will OSGi manifest entries be > transparently added to every maven-build jars ? > > Or will it be an OSGi developer option, that will never be known and > used by other common people ? IMHO this

Re: Adding default OSGi information to JARs

> How this will be done ? At first by putting an innocuous plugin in the lifecycle, or in 2.1 with extensions in Plexus it will be an extension to the JAR plugin that populates manifest information. It would be great if that could be available in 2.0.x version of Maven. We are too far from 2.1 v

Re: Adding default OSGi information to JARs

Hello, [...] it is entirely non-invasive then I think it would be fine to add to the default lifecycle. How this will be done ? Does "bundle" packaging will become official, or will it supercede default jar packaging ? Will it be active by default ? Thank you for this great job