[VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
Hi all guys, I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.1, based on RC1 We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=18380 where [MSKINS-38] is the major issue that drove the new RC There are three new issues in JIRA related to fluido: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11430status=1 Staging repo: https://repository.apache.org/content/repositories/maven-118/ Staging site (not synched yet at the time of writing): http://maven.apache.org/skins/maven-fluido-skin-1.2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote will stay open for 72 hours and will close ~on Fri 30th at 10:00am GMT. Please PMCs cast your votes! Many thanks in advance, all the best, -Simo [ ] +1 let's get it rmblee! [ ] +0 fine, but... [ ] -1 nope, because... http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
+1 2012/3/27 Simone Tripodi simonetrip...@apache.org: Hi all guys, I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.1, based on RC1 We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=18380 where [MSKINS-38] is the major issue that drove the new RC There are three new issues in JIRA related to fluido: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11430status=1 Staging repo: https://repository.apache.org/content/repositories/maven-118/ Staging site (not synched yet at the time of writing): http://maven.apache.org/skins/maven-fluido-skin-1.2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote will stay open for 72 hours and will close ~on Fri 30th at 10:00am GMT. Please PMCs cast your votes! Many thanks in advance, all the best, -Simo [ ] +1 let's get it rmblee! [ ] +0 fine, but... [ ] -1 nope, because... http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
On Tue, 27 Mar 2012 10:01:16 +0200 Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.1, based on RC1 oh yeah :) +1 non binding thanks, tony. We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=18380 where [MSKINS-38] is the major issue that drove the new RC There are three new issues in JIRA related to fluido: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11430status=1 Staging repo: https://repository.apache.org/content/repositories/maven-118/ Staging site (not synched yet at the time of writing): http://maven.apache.org/skins/maven-fluido-skin-1.2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote will stay open for 72 hours and will close ~on Fri 30th at 10:00am GMT. Please PMCs cast your votes! Many thanks in advance, all the best, -Simo [ ] +1 let's get it rmblee! [ ] +0 fine, but... [ ] -1 nope, because... http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
Greetings, On Tue, Mar 27, 2012 at 4:01 AM, Simone Tripodi simonetrip...@apache.org wrote: Staging repo: https://repository.apache.org/content/repositories/maven-118/ I'm using topbar and sidebar basic menus, but I'm not seeing any bread crumbs being created in the little area underneath the left and right nav areas. I do see the last publish date and project version, but no bread crumbs. Must I take an explicit action to get them displayed? I don't see anything special in http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.2.1/src/site/site.xml?revision=1305760view=markup -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-release pull request: fixes for branching submodules
Github user lweller closed the pull request at https://github.com/apache/maven-release/pull/1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
+1, such a small but crucial thing we missed last time. Looking much better now. thanks, -Robert Op Tue, 27 Mar 2012 12:39:19 +0200 schreef Tony Chemit che...@codelutin.com: On Tue, 27 Mar 2012 10:01:16 +0200 Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.1, based on RC1 oh yeah :) +1 non binding thanks, tony. We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=18380 where [MSKINS-38] is the major issue that drove the new RC There are three new issues in JIRA related to fluido: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11430status=1 Staging repo: https://repository.apache.org/content/repositories/maven-118/ Staging site (not synched yet at the time of writing): http://maven.apache.org/skins/maven-fluido-skin-1.2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote will stay open for 72 hours and will close ~on Fri 30th at 10:00am GMT. Please PMCs cast your votes! Many thanks in advance, all the best, -Simo [ ] +1 let's get it rmblee! [ ] +0 fine, but... [ ] -1 nope, because... http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
Hi Jesse!! Breadcrumbs usually are defined inside the breadcrumbs element in site.xml: in the case of the fluido skin site, they are defined in the skin parent site descriptor[1] that are merged with the ones of maven parent and then inherited via menu ref=parent/. A little complex chain. Anyway, if you need to define breadcrumbs, just deine them and they should appear :P HTH, have a nice day! -Simo [1] https://svn.apache.org/repos/asf/maven/skins/trunk/maven-skins/src/site/site.xml http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Tue, Mar 27, 2012 at 3:01 PM, Jesse Farinacci jie...@gmail.com wrote: Greetings, On Tue, Mar 27, 2012 at 4:01 AM, Simone Tripodi simonetrip...@apache.org wrote: Staging repo: https://repository.apache.org/content/repositories/maven-118/ I'm using topbar and sidebar basic menus, but I'm not seeing any bread crumbs being created in the little area underneath the left and right nav areas. I do see the last publish date and project version, but no bread crumbs. Must I take an explicit action to get them displayed? I don't see anything special in http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.2.1/src/site/site.xml?revision=1305760view=markup -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - 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: Security trouble
Why don't you just fix the parsers in older mavens (ie. make a new release of old-maven-version-x w/fixed parser) that allows for changes in newer versions? Seems like if you can never add new information to the pom to solve problems/add features in Maven 3 w/o completely breaking Maven 2, then Maven 3 really can not effectively grow and mature. On Wednesday, March 21, 2012 at 6:57 AM, Brian Fox wrote: On Wed, Mar 21, 2012 at 4:35 AM, Sascha Scholz sascha.sch...@gmail.com (mailto:sascha.sch...@gmail.com) wrote: Hi, On Tue, Mar 20, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org (mailto:ol...@apache.org) wrote: BTW do we consider adding a warning in 3.0.5 if id != host and fail in 3.0.6 or fail directly in 3.0.5 Why not deprecate the id entry then instead of forcing users to set both to the same value? The xml parsing of older maven's isn't flexible enough to allow this. BTW, I don't see that preemptive authentication makes things worse regarding security because an attacker could answer with a 401 to get the credentials even without preemptive authentication. Correct. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org (mailto:dev-unsubscr...@maven.apache.org) For additional commands, e-mail: dev-h...@maven.apache.org (mailto:dev-h...@maven.apache.org)
Re: Security trouble
2012/3/27 Jason Dillon ja...@planet57.com: Why don't you just fix the parsers in older mavens (ie. make a new release of old-maven-version-x w/fixed parser) that allows for changes in newer versions? Seems like if you can never add new information to the pom to solve problems/add features in Maven 3 w/o completely breaking Maven 2, then Maven 3 really can not effectively grow and mature. Agree. Furthermore the change will be in settings.xml not in pom. On Wednesday, March 21, 2012 at 6:57 AM, Brian Fox wrote: On Wed, Mar 21, 2012 at 4:35 AM, Sascha Scholz sascha.sch...@gmail.com (mailto:sascha.sch...@gmail.com) wrote: Hi, On Tue, Mar 20, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org (mailto:ol...@apache.org) wrote: BTW do we consider adding a warning in 3.0.5 if id != host and fail in 3.0.6 or fail directly in 3.0.5 Why not deprecate the id entry then instead of forcing users to set both to the same value? The xml parsing of older maven's isn't flexible enough to allow this. BTW, I don't see that preemptive authentication makes things worse regarding security because an attacker could answer with a 401 to get the credentials even without preemptive authentication. Correct. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org (mailto:dev-unsubscr...@maven.apache.org) For additional commands, e-mail: dev-h...@maven.apache.org (mailto:dev-h...@maven.apache.org) -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: substitute a repository with another one in pom.xml?
You can create a mirror. If you supply the right id, it will simply work. http://maven.apache.org/guides/mini/guide-mirror-settings.html -- -- Aldrin Leal, ald...@leal.eng.br / http://meadiciona.com/aldrinleal On Tue, Mar 27, 2012 at 11:17 AM, ryenus blatt rye...@gmail.com wrote: hello, in pom.xml, is it possible to setup a substitution rule to replace a repository with another one? e.g.: repository idxxx/id urlhttp://yyy.org//url subsitutehttp://zzz.org//substitute /repository the reason is, in case the repository zzz.org is down, with the substitution rule set, maven can immediately turn to yyy.org, instead of try zzz.org and wait and fail then turn to yyy.org, the latter, which is the current situation, would waste a lot of time if their are too many (e.g. 100+) artifacts supposed to be fetched from zzz.org. my case? maven.glassfish.org is down and it took me more than 30 mins to run mvn eclipse:eclipse, the project is https://github.com/ikeike443/HudsonPluginForPlay
Re: [VOTE] Release Apache Maven Fluido Skin 1.2.1 based on RC1
+1 notice I just created MSKINS-40: not really critical, should not block this release since the table issue is really too much, but annoying Regards, Hervé Le mardi 27 mars 2012 10:01:16 Simone Tripodi a écrit : Hi all guys, I'm opening a thread vote today for releasing Apache Maven Fluido Skin 1.2.1, based on RC1 We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName= Htmlversion=18380 where [MSKINS-38] is the major issue that drove the new RC There are three new issues in JIRA related to fluido: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11430sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-118/ Staging site (not synched yet at the time of writing): http://maven.apache.org/skins/maven-fluido-skin-1.2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote will stay open for 72 hours and will close ~on Fri 30th at 10:00am GMT. Please PMCs cast your votes! Many thanks in advance, all the best, -Simo [ ] +1 let's get it rmblee! [ ] +0 fine, but... [ ] -1 nope, because... http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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: [PROPOSAL] Merge the Doxia site into the Maven site
The Doxia site expert is Vincent Siveton: I hope he can express his opinion Doxia (base + sitetools + tools) deserves IMHO the dedicated menus from the actual Doxia site [1] to let people understand: it can/should be improved, but if we merge the Doxia site with regular Maven site, we loose this dedicated menu: I don't think this will help. But you're right with the JIRA report being inappropriate: Doxia site doesn't cover only Doxia base, which is [2]. I'm sure that this menu could be made more explicit to help people understand the relation between Doxia site and each 3 components: removing the JIRA configuration is the first step. Since infra hasn't problems with having a few number of sub-sites being treated as dedicated CMS site, I don't see any problem with maintaining Doxia site. To sum up: - +1 to JIRA configuration removel from Doxia site - -1 to merging into Maven regular site Regards, Hervé [1] http://maven.apache.org/doxia/index.html [2] http://maven.apache.org/doxia/doxia/index.html Le lundi 26 mars 2012 22:13:17 Dennis Lundberg a écrit : Hi When I saw some of the commits by Hervé on the CMS integration it hit me: Why do we have a separate site module for the Doxia site? Unless there are any difficult technical hurdles standing in the way, why don't we just merge it into the regular Maven site? I had a quick look at the POM and the only odd things in there is a configuration snippet for doxia-maven-plugin that is injected into the generated site somewhere, as well as creating some output files (RTF and PDF) from a Doxia book example which are then copied to the generated site using maven-antrun-plugin. There's also a JIRA report in the Doxia site, which in my opinion is wrong since Doxia is not one project anymore but rather an umbrella like Plugins or Shared. So the solution would be to remove the report from the site and add it to the project sites of Doxia, Doxia Site Tools and Doxia Tools. Thoughts? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
