Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Hello We only need to be ready to answer to the same question *a lot* :-) -- Olivier Le 25 juil. 2011 00:26, Hervé BOUTEMY herve.bout...@free.fr a écrit : ok, I added a doc to add a protocol and improved the error message [1] I think we can safely do the change proposed in MSITE-598: users won't be lost (of course, they'll need to read the error message...) Regards, Hervé [1] http://jira.codehaus.org/browse/MSITE-599 Le dimanche 24 juillet 2011, Benson Margulies a écrit : A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. On Sun, Jul 24, 2011 at 4:33 PM, Robert Scholte rfscho...@codehaus.org wrote: I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay consistent: specify wagons with extensions.We just need to document this very well, both on the site and the failure-message, including the required xml to add to the pom. -Robert [1] http://jira.codehaus.org/browse/MSITE-598 From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: Is Maven Site Plugin 3.0-beta-4 ready for release? Date: Sun, 24 Jul 2011 21:56:22 +0200 one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed
Maven eclipse plugin
Hey Maven developers, I would ask about maven-eclipse plugin. Seems that source code activity is going down. Latest commit in github mirror of maven plugins (and svn repository) which changes anything in plugins goals is dated to November 01, 2010. It means that during last 9 moths there was no fixes in trunk. I am already ASF commiter and I would like help you with this plugin in part time to minimize number of pending issues. For example I've reported an issue in 2009 and provided patch. Issue wasn't commented and it wasn't revieved. Any ideas how to bring eclipse plugin to life again? Best regards, Lukasz Dywicki - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven eclipse plugin
2011/7/26 Łukasz Dywicki l...@code-house.org: Hey Maven developers, I would ask about maven-eclipse plugin. Seems that source code activity is going down. Latest commit in github mirror of maven plugins (and svn repository) which changes anything in plugins goals is dated to November 01, 2010. It means that during last 9 moths there was no fixes in trunk. I am already ASF commiter and I would like help you with this plugin in part time to minimize number of pending issues. For example I've reported an issue in 2009 and provided patch. Issue wasn't commented and it wasn't revieved. Any ideas how to bring eclipse plugin to life again? There's maybe two of us scratching that itch at the moment and neither of us very often. I'm not sure of the procedure for getting karma for commits, you'd get access to the whole of maven not just that little bit. As you are already an ASF committer this should be possible. I'll ask... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven eclipse plugin
OK, 1. I do not use eclipse... my fingers have learned IntelliJ IDEA, and I am not switching if I can help it, so these are just general recommendations. 2. Did you patch include tests. Ideally the tests should fail until the rest of your patch is applied and pass thereafter. 3. Once your patch has tests, then try pinging the dev list with a subject like [MECLIPSE-___] I have submitted a patch WITH test cases... any takers??? Give a good 2 weeks before replying on that mail as some of the plugins can be a bit laggard in having their maintainers chime in. 4. If step 3 still gave you no joy, do a svn log of the plugin an see who the 80-90% of commits was, or the last committer to make a release of the plugin... DO NOT mail them directly, instead, reply to the mail in step 3, asking them specifically if they feel like commenting. Do not add them as a CC, they are on the mailing list already, you are just trying to _gently_ ping them into a response... You could also try pinging them on the #maven-dev channel on IRC if you spot them. PING them in public. something like @mrdeveloper I've attached a patch with test cases to MECLIPSE-___ what are the chances of you reviewing and applying the patch and when might there be a release cut? 5. Wait... reviving the mail thread from #3 each about once a month. DO NOT start a new mail thread, just reply to your old one. Usually getting to step 3 will get your fix committed. 2011/7/26 Łukasz Dywicki l...@code-house.org Hey Maven developers, I would ask about maven-eclipse plugin. Seems that source code activity is going down. Latest commit in github mirror of maven plugins (and svn repository) which changes anything in plugins goals is dated to November 01, 2010. It means that during last 9 moths there was no fixes in trunk. I am already ASF commiter and I would like help you with this plugin in part time to minimize number of pending issues. For example I've reported an issue in 2009 and provided patch. Issue wasn't commented and it wasn't revieved. Any ideas how to bring eclipse plugin to life again? Best regards, Lukasz Dywicki - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven eclipse plugin
He could just fork it into the sandbox, and apply the changes there and get you to merge them back. All ASF committers have write access to our sandbox. On 26 July 2011 14:19, Barrie Treloar baerr...@gmail.com wrote: 2011/7/26 Łukasz Dywicki l...@code-house.org: Hey Maven developers, I would ask about maven-eclipse plugin. Seems that source code activity is going down. Latest commit in github mirror of maven plugins (and svn repository) which changes anything in plugins goals is dated to November 01, 2010. It means that during last 9 moths there was no fixes in trunk. I am already ASF commiter and I would like help you with this plugin in part time to minimize number of pending issues. For example I've reported an issue in 2009 and provided patch. Issue wasn't commented and it wasn't revieved. Any ideas how to bring eclipse plugin to life again? There's maybe two of us scratching that itch at the moment and neither of us very often. I'm not sure of the procedure for getting karma for commits, you'd get access to the whole of maven not just that little bit. As you are already an ASF committer this should be possible. I'll ask... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
Am 26.07.2011 01:27, schrieb Kasun Gajasinghe: Manually, editing the pom with the available plugin versions is much complicated, http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html Automate this using a CI server and you're probably mostly done. Best Ansgar - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
Am 26.07.2011 00:56, schrieb Kasun Gajasinghe: So, doesn't having an intermediary layer that will point to newer set of plugins is justified? Sure. Simplest solution that will work: use your own parent pom with an updated pluginManagement section. Ansgar - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
Am 26.07.2011 21:14, schrieb Ansgar Konermann: Am 26.07.2011 01:27, schrieb Kasun Gajasinghe: I'm sorry, wrong list. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1150994 - /maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/AbstractDeployMojo.java
did you try what an end-user can see when he tries to use an unavailable
protocol?
I'm ok with more detailed error message.
But the stacktrace, which is the only message which is displayed at the end of
Maven reactor run, stating that protocol could not be found, is not helpful:
the detailed error message is more expressive IMHO, telling the user where to
find information on how to fix.
Regards,
Hervé
Le mardi 26 juillet 2011, ltheu...@apache.org a écrit :
Author: ltheussl
Date: Tue Jul 26 06:42:00 2011
New Revision: 1150994
URL: http://svn.apache.org/viewvc?rev=1150994view=rev
Log:
move detailed error message to logger and preserve stacktrace
Modified:
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugi
ns/site/AbstractDeployMojo.java
Modified:
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugi
ns/site/AbstractDeployMojo.java URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/mai
n/java/org/apache/maven/plugins/site/AbstractDeployMojo.java?rev=1150994r1
=1150993r2=1150994view=diff
==
---
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugi
ns/site/AbstractDeployMojo.java (original) +++
maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugi
ns/site/AbstractDeployMojo.java Tue Jul 26 06:42:00 2011 @@ -343,7 +343,7
@@ public abstract class AbstractDeployMojo
return buildDirectory;
}
-private Wagon getWagon( final Repository repository, final
WagonManager manager, final Log log ) +private static Wagon getWagon(
final Repository repository, final WagonManager manager, final Log log )
throws MojoExecutionException
{
final Wagon wagon;
@@ -354,13 +354,12 @@ public abstract class AbstractDeployMojo
}
catch ( UnsupportedProtocolException e )
{
-log.error( Unavailable protocol for site deployment: ' +
repository.getProtocol() + ' ); +log.error( Unsupported
protocol for site deployment: ' + repository.getProtocol() +
+ '. For adding new protocols to the site plugin, see +
+
http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-
protocol.html );
-throw new MojoExecutionException(
- this,
- Unavailable protocol for
site deployment: ' + repository.getProtocol() + ', -
To add a new protocol to site plugin, see -
+
http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-
protocol.html ); +throw new MojoExecutionException(
Unsupported protocol for site deployment: ' ++
repository.getProtocol() + '., e );
}
catch ( TransferFailedException e )
{
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1150948 - in /maven/plugins/trunk/maven-site-plugin: pom.xml src/it/full-reporting/pom.xml src/it/full-reporting/verify.groovy src/main/java/org/apache/maven/plugins/site/AbstractSite
Hervé, Do you have an idea how to fix this for Maven 2? If you don't, then I'd like to postpone this change to a time when we have a solution for Maven 2. I feel that it is better (and easier) if this version of the plugin behaves the same (as much as possible) when it is run with Maven 2 and Maven 3. On 2011-07-26 00:57, hbout...@apache.org wrote: Author: hboutemy Date: Mon Jul 25 22:57:29 2011 New Revision: 1150948 URL: http://svn.apache.org/viewvc?rev=1150948view=rev Log: [MSITE-402] ensure order of reports like defined in POM (works with Maven 3 but not with Maven 2.2 for the moment) Modified: maven/plugins/trunk/maven-site-plugin/pom.xml maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groovy maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven/plugins/site/AbstractSiteRenderingMojo.java Modified: maven/plugins/trunk/maven-site-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/pom.xml?rev=1150948r1=1150947r2=1150948view=diff == --- maven/plugins/trunk/maven-site-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/pom.xml Mon Jul 25 22:57:29 2011 @@ -205,7 +205,7 @@ under the License. dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-exec/artifactId - version1.0/version + version1.0.1-SNAPSHOT/version /dependency !-- Maven -- Modified: maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml?rev=1150948r1=1150947r2=1150948view=diff == --- maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml Mon Jul 25 22:57:29 2011 @@ -65,6 +65,23 @@ dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration +reportSets + reportSet +reports + reportindex/report + reportsummary/report + reportlicense/report + reportproject-team/report + reportscm/report + reportissue-tracking/report + reportmailing-list/report + reportdependencies/report + reportcim/report + reportplugin-management/report + reportplugins/report +/reports + /reportSet +/reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId Modified: maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groovy URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groovy?rev=1150948r1=1150947r2=1150948view=diff == --- maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groovy (original) +++ maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groovy Mon Jul 25 22:57:29 2011 @@ -25,21 +25,71 @@ assert content.contains( 'Test set: org. assert content.contains( 'Tests run: 1, Failures: 0, Errors: 0, Skipped: 0' ); -assert new File( basedir, 'target/site/surefire-report.html' ).exists(); -assert new File( basedir, 'target/site/index.html' ).exists(); -assert new File( basedir, 'target/site/checkstyle.html' ).exists(); -assert new File( basedir, 'target/site/cpd.html' ).exists(); -assert new File( basedir, 'target/site/apidocs/index.html' ).exists(); -assert new File( basedir, 'target/site/apidocs/org/apache/maven/plugins/site/its/App.html' ).exists(); -assert new File( basedir, 'target/site/cobertura/index.html' ).exists(); -assert new File( basedir, 'target/site/xref/index.html' ).exists(); -assert new File( basedir, 'target/site/xref-test/index.html' ).exists(); +sitedir = new File( basedir, 'target/site' ); -assert new File( basedir, 'target/site/taglist.html' ).exists(); -assert new File( basedir, 'target/site/team-list.html' ).exists(); +assert new File( sitedir, 'surefire-report.html' ).exists(); +assert new File( sitedir, 'index.html' ).exists(); +assert new File( sitedir, 'checkstyle.html' ).exists(); +assert new File( sitedir, 'cpd.html' ).exists(); +assert new File( sitedir, 'apidocs/index.html' ).exists(); +assert new File( sitedir, 'apidocs/org/apache/maven/plugins/site/its/App.html' ).exists(); +assert new File( sitedir, 'cobertura/index.html' ).exists(); +assert new File( sitedir, 'xref/index.html' ).exists(); +assert new File( sitedir,
Re: svn commit: r1150948 - in /maven/plugins/trunk/maven-site-plugin: pom.xml src/it/full-reporting/pom.xml src/it/full-reporting/verify.groovy src/main/java/org/apache/maven/plugins/site/AbstractSite
I still need to investigate what's happenning with m-site-p 2.3 and Maven 2.2 yes, it's better to have same behaviour with every Maven version I'll work on it tomorrow Regards, Hervé Le mercredi 27 juillet 2011, Dennis Lundberg a écrit : Hervé, Do you have an idea how to fix this for Maven 2? If you don't, then I'd like to postpone this change to a time when we have a solution for Maven 2. I feel that it is better (and easier) if this version of the plugin behaves the same (as much as possible) when it is run with Maven 2 and Maven 3. On 2011-07-26 00:57, hbout...@apache.org wrote: Author: hboutemy Date: Mon Jul 25 22:57:29 2011 New Revision: 1150948 URL: http://svn.apache.org/viewvc?rev=1150948view=rev Log: [MSITE-402] ensure order of reports like defined in POM (works with Maven 3 but not with Maven 2.2 for the moment) Modified: maven/plugins/trunk/maven-site-plugin/pom.xml maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.gr oovy maven/plugins/trunk/maven-site-plugin/src/main/java/org/apache/maven /plugins/site/AbstractSiteRenderingMojo.java Modified: maven/plugins/trunk/maven-site-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/pom.x ml?rev=1150948r1=1150947r2=1150948view=diff == --- maven/plugins/trunk/maven-site-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/pom.xml Mon Jul 25 22:57:29 2011 @@ -205,7 +205,7 @@ under the License. dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-exec/artifactId - version1.0/version + version1.0.1-SNAPSHOT/version /dependency !-- Maven -- Modified: maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/i t/full-reporting/pom.xml?rev=1150948r1=1150947r2=1150948view=diff == --- maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/pom.xml Mon Jul 25 22:57:29 2011 @@ -65,6 +65,23 @@ dependencyDetailsEnabledfalse/dependencyDetailsEnabled dependencyLocationsEnabledfalse/dependencyLocationsEnabled /configuration +reportSets + reportSet +reports + reportindex/report + reportsummary/report + reportlicense/report + reportproject-team/report + reportscm/report + reportissue-tracking/report + reportmailing-list/report + reportdependencies/report + reportcim/report + reportplugin-management/report + reportplugins/report +/reports + /reportSet +/reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId Modified: maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groov y URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/i t/full-reporting/verify.groovy?rev=1150948r1=1150947r2=1150948view=dif f == --- maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groov y (original) +++ maven/plugins/trunk/maven-site-plugin/src/it/full-reporting/verify.groov y Mon Jul 25 22:57:29 2011 @@ -25,21 +25,71 @@ assert content.contains( 'Test set: org. assert content.contains( 'Tests run: 1, Failures: 0, Errors: 0, Skipped: 0' ); -assert new File( basedir, 'target/site/surefire-report.html' ).exists(); -assert new File( basedir, 'target/site/index.html' ).exists(); -assert new File( basedir, 'target/site/checkstyle.html' ).exists(); -assert new File( basedir, 'target/site/cpd.html' ).exists(); -assert new File( basedir, 'target/site/apidocs/index.html' ).exists(); -assert new File( basedir, 'target/site/apidocs/org/apache/maven/plugins/site/its/App.html' ).exists(); -assert new File( basedir, 'target/site/cobertura/index.html' ).exists(); -assert new File( basedir, 'target/site/xref/index.html' ).exists(); -assert new File( basedir, 'target/site/xref-test/index.html' ).exists(); +sitedir = new File( basedir, 'target/site' ); -assert new File( basedir, 'target/site/taglist.html' ).exists(); -assert new File( basedir, 'target/site/team-list.html' ).exists(); +assert new File( sitedir, 'surefire-report.html' ).exists(); +assert new File( sitedir, 'index.html' ).exists();
Re: POM5 proposal
Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
No. I can't paste anything into our wiki at ASF. I don't have edit access, and John asked infra for help in giving me edit access, and I don't think that any help has been forthcoming so far. On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg strub...@yahoo.de wrote: sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
Are you sure? https://issues.apache.org/jira/browse/INFRA-3792 I hadn't read it either, assuming you were about to shortly move it once I saw that resolved… I guess the loop wasn't closed. - Brett On 27/07/2011, at 10:14 AM, Benson Margulies wrote: No. I can't paste anything into our wiki at ASF. I don't have edit access, and John asked infra for help in giving me edit access, and I don't think that any help has been forthcoming so far. On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg strub...@yahoo.de wrote: sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
Duh. I someone didn't end up watching that issue. Off I go to paste. On Tue, Jul 26, 2011 at 8:20 PM, Brett Porter br...@apache.org wrote: Are you sure? https://issues.apache.org/jira/browse/INFRA-3792 I hadn't read it either, assuming you were about to shortly move it once I saw that resolved… I guess the loop wasn't closed. - Brett On 27/07/2011, at 10:14 AM, Benson Margulies wrote: No. I can't paste anything into our wiki at ASF. I don't have edit access, and John asked infra for help in giving me edit access, and I don't think that any help has been forthcoming so far. On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg strub...@yahoo.de wrote: sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
It's not a work of art, but it gives us something to elaborate that isn't just a thread in the email archive. https://cwiki.apache.org/confluence/display/MAVEN/POM-5+compatibility+design On Tue, Jul 26, 2011 at 8:23 PM, Benson Margulies bimargul...@gmail.com wrote: Duh. I someone didn't end up watching that issue. Off I go to paste. On Tue, Jul 26, 2011 at 8:20 PM, Brett Porter br...@apache.org wrote: Are you sure? https://issues.apache.org/jira/browse/INFRA-3792 I hadn't read it either, assuming you were about to shortly move it once I saw that resolved… I guess the loop wasn't closed. - Brett On 27/07/2011, at 10:14 AM, Benson Margulies wrote: No. I can't paste anything into our wiki at ASF. I don't have edit access, and John asked infra for help in giving me edit access, and I don't think that any help has been forthcoming so far. On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg strub...@yahoo.de wrote: sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: POM5 proposal (a long-winded response)
maven.mdo** model idmaven/id nameMaven/name description ![CDATA[ pThis is a reference for the Maven project descriptor used in Maven./p pAn XSD is available at:/p ul lia href=http://maven.apache.org/maven-v3_0_0.xsd;http://maven.apache.org/maven-v3_0_0.xsd/a for Maven 1.1./li lia href=http://maven.apache.org/maven-v4_0_0.xsd;http://maven.apache.org/maven-v4_0_0.xsd/a for Maven 2.0./li **where http://maven.apache.org/maven-v4_0_0.xsd looks like** xs:element name=scm minOccurs=0 type=Scm − xs:annotation xs:documentation source=version4.0.0/xs:documentation − xs:documentation source=description Specification for the SCM used by the project, such as CVS, Subversion, etc. /xs:documentation /xs:annotation /xs:element **where scm ComplexType is defined as *** xs:complexType name=Scm − xs:annotation xs:documentation source=version4.0.0/xs:documentation /xs:annotation − xs:all − xs:element name=connection minOccurs=0 type=xs:string − xs:annotation xs:documentation source=version4.0.0/xs:documentation − xs:documentation source=description The source control management system URL that describes the repository and how to connect to the repository. For more information, see the a href=http://maven.apache.org/scm/scm-url-format.html;URL format/a and a href=http://maven.apache.org/scm/scms-overview.html;list of supported SCMs/a. This connection is read-only. /xs:documentation /xs:annotation /xs:element − xs:element name=developerConnection minOccurs=0 type=xs:string − xs:annotation xs:documentation source=version4.0.0/xs:documentation − xs:documentation source=description Just like codeconnection/code, but for developers, i.e. this scm connection will not be read only. /xs:documentation /xs:annotation /xs:element − xs:element name=tag minOccurs=0 type=xs:string default=HEAD − xs:annotation xs:documentation source=version4.0.0/xs:documentation − xs:documentation source=description The tag of current code. By default, it's set to HEAD during development. /xs:documentation /xs:annotation /xs:element − xs:element name=url minOccurs=0 type=xs:string − xs:annotation xs:documentation source=version4.0.0/xs:documentation − xs:documentation source=description The URL to the project's browsable SCM repository, such as ViewVC or Fisheye. /xs:documentation /xs:annotation /xs:element /xs:all /xs:complexType the additional elements could be added to child elements of a new 'Scm2' element which is of name=Scm (ComplexType Scm) 1)is it possible to accurately identify the name and type of all additional elements for new element Scm2 ? 2)what is mares next? Martin __ excruciatingly long disclaimer goes here Date: Tue, 26 Jul 2011 20:34:19 -0400 Subject: Re: POM5 proposal From: bimargul...@gmail.com To: dev@maven.apache.org It's not a work of art, but it gives us something to elaborate that isn't just a thread in the email archive. https://cwiki.apache.org/confluence/display/MAVEN/POM-5+compatibility+design On Tue, Jul 26, 2011 at 8:23 PM, Benson Margulies bimargul...@gmail.com wrote: Duh. I someone didn't end up watching that issue. Off I go to paste. On Tue, Jul 26, 2011 at 8:20 PM, Brett Porter br...@apache.org wrote: Are you sure? https://issues.apache.org/jira/browse/INFRA-3792 I hadn't read it either, assuming you were about to shortly move it once I saw that resolved… I guess the loop wasn't closed. - Brett On 27/07/2011, at 10:14 AM, Benson Margulies wrote: No. I can't paste anything into our wiki at ASF. I don't have edit access, and John asked infra for help in giving me edit access, and I don't think that any help has been forthcoming so far. On Tue, Jul 26, 2011 at 8:10 PM, Mark Struberg strub...@yahoo.de wrote: sorry, have no google account (and refuse to create one). Cant you just paste it into our Wiki? LieGrue, strub --- On Wed, 7/27/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: POM5 proposal To: Maven Developers List dev@maven.apache.org Date: Wednesday, July 27, 2011, 12:07 AM Ping? anybody read this? On Sun, Jul 24, 2011 at 9:14 AM, Benson Margulies bimargul...@gmail.com wrote: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail:
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
settings.xml can include pluginManagement in a profile? I thought you could only include a few things like repos and properties, at least that's what the docs say. http://maven.apache.org/ref/3.0.3/maven-settings/settings.html On 07/25/2011 06:43 AM, Benson Margulies wrote: I don't know about plugin-registry.xml, but you can distribute a settings.xml for use with -gs that has an active-by-default profile with a pluginManagement section that does the job. On Mon, Jul 25, 2011 at 3:02 AM, Kasun Gajasinghe kasu...@gmail.com wrote: Hi, I have a requirement where I need to specify specific versions for a set of (basic) plugins. Adding the versions to the pom isn't an option because we need to set the plugin versions for a vast number of _unrelated_ builds. As I've found at [1], I've manually created a plugin-registry.xml file with needed plugin versions added. In addition to that, I've created maven-metadata-local.xml file in the m2 repo under the plugin directories, pointing to latest and release versions. But, unfortunately, these specified versions were not picked up by mvn. I needed latest maven-compiler-plugin version 2.3.2, but it always try to use 2.0.2. I've noticed that [1] is somewhat outdated because --check-plugin-latest parameter doesn't available anymore. So, I'm asking, does the plugin-registry.xml is still used by maven? If not what is the mechanism for specifying specific plugin versions (apart from current/parent pom)? (I've seen in some posts that the plugin-registry.xml isn't used anymore, but debug mode shows that mvn retrieves data from that file. ) Apparently, maven-metada-local.xml isn't created automatically for me either. How I can instruct mvn to do that? My plugin-registry.xml is at [2]. (There wasn't a template for that. So, hope the format is correct!). maven-metadata-local.xml of maven-compiler-plugin is at [3]. I'm using official apache maven-2.2.1 build. Your help is much appreciated. [1] http://maven.apache.org/guides/introduction/introduction-to-plugin-registry.html [2] http://pastebin.com/yprQU2D2 [3] http://pastebin.com/Y375dwMg Thanks, --Kasun -- ~~~***'***~~~ Kasun Gajasinghe, University of Moratuwa, Sri Lanka. Blog: http://blog.kasunbg.org Twitter: http://twitter.com/kasunbg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: POM5 proposal
Hi Benson Thanks for your proposal! IMHO the pom5 should include some tags like wiki/ or qualityManagement/ and the javadoc api/ see MPIR-149 MJAVADOC-32 Cheers, Vincent 2011/7/24 Benson Margulies bimargul...@gmail.com: Since I can't edit the Wiki, I created: https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Set specific plugin versions for a project - issue in plugin-registry.xml/maven-metada-local.xml
On 27 Jul 2011, at 01:27, Ansgar Konermann ansgar.konerm...@googlemail.com wrote: Am 26.07.2011 00:56, schrieb Kasun Gajasinghe: So, doesn't having an intermediary layer that will point to newer set of plugins is justified? Sure. Simplest solution that will work: use your own parent pom with an updated pluginManagement section. As I explained before, parent pom thing has few caveats. Btw, lot of problems occured to me because of the maven super pom, which, apparently has some hard-coded (quite old) plugin versions. (As I've read [1], the super pom is something like Java's java.lang.Object that every class inherits properties from.) So, I could get over some issues if I can patch the plugin versions in super pom according to our needs. Unfortunately, I can't find it exists in source. Can anyone shed a light on where I could find the super pom? Thanks, Kasun [1] http://maven.apache.org/pom.html#The_Super_POM Ansgar - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
