Planning to remove rosters from active podlings
All, This coming weekend (9/29) I plan to remove the roster sections from all podling status pages. Podling rosters are meant to be managed in Whimsy. The roster in the status page is redundant and end up out of sync. In place of the roster, I will be adding a link automatically to all podling rosters. John
[REMINDER] Policies around Publicity & Press
All Podlings, In recent days I've been contacted about several publicity issues that have gone a bit off kilter. I wanted to remind podlings two very import policies. 1. Podlings MUST coordinate with the Public Relations Committee with all publicity activities. 2. The Press Team MUST review any press releases or similar communication referencing a podling before it is published. Relevant Links: https://incubator.apache.org/guides/branding.html#publicity_activities https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process Please reach out with any concerns. Regards, John D. Ament VP, Apache Incubator
Dist Area permissions problem
All, Please be advised that the infra team is aware of a permission problem that is affecting podlings ability to write to the incubator dist area. This may cause you to be unable to create staged releases and promote those to the public mirrors. You can track the status in https://issues.apache.org/jira/browse/INFRA-14609 . Likewise, I want to make the podlings aware of a permission problem from the weekend where git permissions were a little off. That has since been fixed. Apologies for any inconvenience. John
Is Freemarker becoming too process heavy? (was Re: Proposed policy change: Don't require CLA from contributos)
All, I'm concerned with some of these threads I'm seeing w/r/t Freemarker. While I'm not a mentor on the project, I've been a user for a while and have been curious about Freemarker at Apache. I would not cite a CouchDB process from their old wiki. First, its not clear if this is the most recent version (it mentions a migration to the new wiki and an external website which are red flags to me). Second, CouchDB has a much different model and contributor set than other projects do. I would cite a legal JIRA, and as far as I know everyone was already following this guide. I would also cite our legal guidelines https://www.apache.org/licenses/#clas in particular where it makes sense to expect an ICLA on file. In general, ASF expects ICLAs for large enough contributions. The size is at the discretion of the PMC receiving the contribution. We do require ICLAs for committers to join a project (to receive an account, to receive write access) and many projects simply follow that model - you need an ICLA at that point in time. I would encourage Freemarker to keep things simple, especially since the total number of contributors is at 13. John On Wed, Jun 21, 2017 at 6:48 AM Daniel Dekany wrote: > Currently we strictly require a CLA (by which I mean an ICLA or CCLA) > for any contributions to be accepted, as > http://freemarker.org/contribute.html says. > > This practice was inherited from the pre-ASF times, when without > lawyers available, we tried to be on the safe side. But based on > https://issues.apache.org/jira/browse/LEGAL-156 and > https://wiki.apache.org/couchdb/CommitPolicy and some other mails we > can make things simpler for contributors (not to be confused with > committers). > > So I propose that we say that: > > - People sending contributions with GitHub pull requests need no CLA. > But, before merging, we must check that: > - The mail about the pull request was received to > notificati...@freemarker.incubator.apache.org, so that there's > a record of this even in the ASF infrastructure. > - The files in the pull request has the standard ASF copyright > headers, or no copyright headers in files where that's normally > not present. There's no other conflicting copyright information > included either (like a such LICENSE file). > - People sending in patches as attachment to FreeMarker Jira issues > need no CLA. But, before merging, we must check that: > - It's clear from the wording of the issue that the user wishes to > contribute (as opposed to, for example, just showing an example). > - Copyright headers are in order, just as with GitHub pull request. > > If someone contributes a bigger feature, yet they isn't a committer, > we might still ask a CLA though. But that can be dealt with when such > thing happens. > > -- > Thanks, > Daniel Dekany > >
Re: Help with Travis e-mail notifications, someone?
There's an open issue between ASF and Travis on this. They use a mailer program that generated random from addresses in the email (I forget the actual header name). This causes all of the travis emails to end up in moderation. Do you know if they're ending up in moderation for freemarker as well? John On Sat, Jun 17, 2017 at 6:23 AM Pradeep Murugesan < pradeepmuruge...@outlook.com> wrote: > Hi, > > > I was trying this. It is actually working with my email. But with the > apache DL was not getting the notifications. > > > Will take a deeper look this week. > > > Pradeep. > > > From: Daniel Dekany > Sent: Friday, June 16, 2017 10:03:30 PM > To: Daniel Dekany > Subject: Re: Help with Travis e-mail notifications, someone? > > Anyone? > > > Wednesday, June 7, 2017, 7:16:13 PM, Daniel Dekany wrote: > > > Guys, > > > > Can someone do the research and set up Travis failure notifications so > > that we get an e-mail about them to > > notificati...@freemarker.incubator.apache.org? I did some research, > > but no obvious solution has jumped at me. Simply setting the > > notification e-mail address in .travis.yml won't work as far as I > > know, because of Travis security restrictions regarding the e-mail > > addresses. I have peeked into some existing Apache projects, and > > either there was nothing notification related in .travis.yml, or it > > was some webhook (`notifications: webhooks`) to some random IM service > > (I guess). > > > > -- > Thanks, > Daniel Dekany > >
[DRAFT] What the new Status Pages potentially look like
All, We're piloting a new format for the podling status pages. Specifically, the current status page leaves a lot to be desired - it's basically crafted html, there's no structure and its hard to find missing items. The end goal is to have a web form editable in Whimsy, but until we get more input on what the content looks like I don't want to make changes like that. I'm asking at this point for podlings to take a look at the status output, potentially update their own content, and see if they like the output. If you navigate to https://whimsy.apache.org/roster/ppmc/ (authentication is via your ASF committer username/password) and find your podling, you'll see your current roster as well as your current status information. The status pages can be found in SVN at this directory https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/ Some more information can be found at https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E If you're not sure what to fill out, feel free to reach out. John
[NOTICE] Managing Podling Rosters
Podlings, I wanted to raise a point to all, hence the direct emails. The Whimsy PMC has put together a roster tool for managing the committers in a podling. Rather than managing the committer list in your status file, this will keep track and make sure we list out everyone's valid IDs. If you haven't accessed it, it can be found at https://whimsy.apache.org/roster/ppmc/ The Incubator guide has been updated to reflect this http://incubator.apache.org/guides/ppmc.html#podling+rosters Please reach out if you have any questions. John
Re: New committer: Woonsan Ko
On Sun, Feb 12, 2017 at 1:42 PM Daniel Dekany wrote: > The Project Management Committee (PMC) for Apache FreeMarker > (incubating) has invited Woonsan Ko to become a committer and we are > pleased to announce that he has accepted. > Please note - there is no PMC for Freemarker at this time. There is a PPMC, but formally Freemarker is considered a sub-project of the incubator. > > Woonsan Ko has been an active FreeMarker user for years while using > FreeMarker as primary template engine for web content management > applications. He is willing to contribute more and help the Apache > FreeMarker community more proactively. He is working at Hippo, a > BloomReach company, as a lead solution architect. He has been > contributing to Apache Portals and Apache Commons SCXML projects as > well for years. > > Being a committer enables easier contribution to the project since > there is no need to go via the patch submission process. This should > enable better productivity. > > -- > Thanks, > Daniel Dekany > >
Re: Parsing XML Files in Freemarker templates
On Sun, Jan 15, 2017 at 5:43 AM Daniel Dekany wrote: > Sunday, January 15, 2017, 12:39:12 AM, John D. Ament wrote: > > > Hi, > > > > I was wondering, are there any features in freemarker that would allow me > > to parse an XML file and loop through its contents? This would need to > be > > directly within the freemarker template. > > > > John > > If you really have to load the XML file from the template (which is > unusual), then write a TemplateMethodModelEx that calls > freemarker.ext.dom.NodeModel.parse(InputSource). The result can be > traversed as described at http://freemarker.org/docs/xgui.html. > > Of course, normally, you load the XML before that template is called, > and pass the W3C DOM Node or the NodeModel to it through the > data-model. > Hmm so the real reason I wanted to do it directly was to avoid adding code. Sounds like I'd still have to make code changes. Ok. Thanks! > > -- > Thanks, > Daniel Dekany > >
Parsing XML Files in Freemarker templates
Hi, I was wondering, are there any features in freemarker that would allow me to parse an XML file and loop through its contents? This would need to be directly within the freemarker template. John
Re: Avoiding "-incubating" suffix in Maven version for non-org.apache Maven group?
On Tue, Dec 27, 2016 at 12:51 PM Daniel Dekany wrote: > Tuesday, December 27, 2016, 5:57:11 PM, John D. Ament wrote: > > > Daniel, > > > > Funny that you bring this up, its in alignment to the doc changes I've > > proposed on the incubator list (if you could take a look). The incubator > > policy on what the archive should be is here: > > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > > Indeed, it doesn't require "-incubating" in the Maven version. So is > your proposal about specifically stating that "-incubating" is not > required in the Maven version? > > My proposal is to state that -incubating was never a mandate in the maven artifact. The only requirement the incubator has put forth is that the release artifact (source tarball) contains -incubating in the name somewhere (typically in a suffix) and has a DISCLAIMER indicating its incubating status, from an ASF standpoint. Users complain about what you're bringing up all the time, it makes seemingly mature projects appear immature due to the maven coordinate when in fact that was never the ask. > > Specifically it requires that the *release archive* contains > "-incubating" > > not that the underlying artifacts contain "-incubating." So as far as I > am > > concerned, the individual maven/ant/gradle components that go into the > > release do not need the suffix. Only the source tarball, and probably > the > > bin tarball. > > > > Changing the name, description, etc wouldn't be required. but I would > > expect one of your graduation goals to be to move to org.apache as your > > maven coordinates, even if they're duplicated by the old org.freemarker > > coordinates. > > Basically yes. Though I will try to "exploit" that for doing at least > some non-BC API cleanups, and ideally much more. > > I'm not sure what you mean by BC in either place where its used in this email thread. > > (note this email is purely from a IPMC member's perspective, don't take > it > > as verbatim) > > So I assume I should re-post this mail to incubator-general. Should I > still offer adding "(incubating)" to the "name" in the POM? My concern > there is that the project "name" was changed from "FreeMarker" to > "Apache FreeMarker", which I believe meant to be done for incubating > project. And so then in the POM we end up with "Apache " > without "incubating" anywhere around (as we remove that from the > "version""). > That's up to you. The official ASF guide is here: http://www.apache.org/dev/publishing-maven-artifacts.html It makes no reference to what should be in name, groupId or artifactId. There are customs and best practices, but no mandates on the content. John > > > John > > > > On Tue, Dec 27, 2016 at 11:47 AM Daniel Dekany > wrote: > > > >> I plan to send the below mail to gene...@incubator.apache.org. What do > >> you think? > >> > >> > >> Hello, > >> > >> There's a project in Incubator called FreeMarker, with these Maven > >> coordinates: > >> > >> org.freemarker > >> freemarker > >> 2.3.25-incubating > >> > >> It's org.freemarker because it was like that for a decade or so, > >> before attempting incubation. There's a plan for a non-BC line that > >> can switch to org.apache, but that's irrelevant now. > >> > >> The "-incubating" in the Maven version is confusing for the users, as > >> it looks as the version number of an ustable release. For those not > >> working in the Java ecosystem, note that users will usually just grab > >> the latest version from the Maven Central Repo based on the version > >> string, without looking at the project home page, at least if it's > >> only a 3rd version number change. (See [*] if you care about some more > >> clues.) > >> > >> So, as the groupId doesn't contain org.apache, is there any chance > >> that instead of putting "-incubating" into the Maven POM "version", we > >> change the Maven POM "name" from "Apache FreeMarker" to "Apache > >> FreeMarker (incubating)"? We would leave the version number as > >> 2.x.x-incubating everywhere else, like in the file names of the > >> releases downloadable from apache.org, in the documentation, etc. I > >> believe this change would be beneficial for the users. > >> > >> *: It certainly doesn't help that http://mvnrepository.com > >>automatically marks these incubating versions with red (~ alpha). > >>Anyway, on the same place 2.3.23, the last non-Apache release from > >>1.5 years ago, has suspiciously high usage compared to the two > >>"-incubating" releases following it. Spring has also stuck at > >>2.3.23, which is strange. > >> > >> -- > >> Thanks, > >> Daniel Dekany > >> > >> > > -- > Thanks, > Daniel Dekany > >
Re: Avoiding "-incubating" suffix in Maven version for non-org.apache Maven group?
Daniel, Funny that you bring this up, its in alignment to the doc changes I've proposed on the incubator list (if you could take a look). The incubator policy on what the archive should be is here: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Specifically it requires that the *release archive* contains "-incubating" not that the underlying artifacts contain "-incubating." So as far as I am concerned, the individual maven/ant/gradle components that go into the release do not need the suffix. Only the source tarball, and probably the bin tarball. Changing the name, description, etc wouldn't be required. but I would expect one of your graduation goals to be to move to org.apache as your maven coordinates, even if they're duplicated by the old org.freemarker coordinates. (note this email is purely from a IPMC member's perspective, don't take it as verbatim) John On Tue, Dec 27, 2016 at 11:47 AM Daniel Dekany wrote: > I plan to send the below mail to gene...@incubator.apache.org. What do > you think? > > > Hello, > > There's a project in Incubator called FreeMarker, with these Maven > coordinates: > > org.freemarker > freemarker > 2.3.25-incubating > > It's org.freemarker because it was like that for a decade or so, > before attempting incubation. There's a plan for a non-BC line that > can switch to org.apache, but that's irrelevant now. > > The "-incubating" in the Maven version is confusing for the users, as > it looks as the version number of an ustable release. For those not > working in the Java ecosystem, note that users will usually just grab > the latest version from the Maven Central Repo based on the version > string, without looking at the project home page, at least if it's > only a 3rd version number change. (See [*] if you care about some more > clues.) > > So, as the groupId doesn't contain org.apache, is there any chance > that instead of putting "-incubating" into the Maven POM "version", we > change the Maven POM "name" from "Apache FreeMarker" to "Apache > FreeMarker (incubating)"? We would leave the version number as > 2.x.x-incubating everywhere else, like in the file names of the > releases downloadable from apache.org, in the documentation, etc. I > believe this change would be beneficial for the users. > > *: It certainly doesn't help that http://mvnrepository.com >automatically marks these incubating versions with red (~ alpha). >Anyway, on the same place 2.3.23, the last non-Apache release from >1.5 years ago, has suspiciously high usage compared to the two >"-incubating" releases following it. Spring has also stuck at >2.3.23, which is strange. > > -- > Thanks, > Daniel Dekany > >
Including an external file in a template
Hi, Suppose I have a local .txt file. Is there an easy way that I can import the contents of this file? John
Re: Podling Report Reminder - October 2016
It's a community effort, please feel free to make changes. FWIW I don't see a release from freemarker in the past 3 months. The report also doesn't show much signs of growth. On Oct 7, 2016 00:40, "Jacopo Cappellato" wrote: > In this report, under the section "Not yet ready to graduate", Freemarker > is listed under the group "No release". > However this is not accurate since Freemarker did a release in the > Incubator: > > http://freemarker.org/freemarkerdownload.html > > Would it be possible to update this section? Freemarker should be moved to > the group "Community growth" > > Thank you, > > Jacopo > > On Fri, Oct 7, 2016 at 7:27 AM, wrote: > >> Dear podling, >> >> This email was sent by an automated system on behalf of the Apache >> Incubator PMC. It is an initial reminder to give you plenty of time to >> prepare your quarterly board report. >> >> The board meeting is scheduled for Wed, 19 October 2016, 10:30 am PDT. >> The report for your podling will form a part of the Incubator PMC >> report. The Incubator PMC requires your report to be submitted 2 weeks >> before the board meeting, to allow sufficient time for review and >> submission (Wed, October 05). >> >> Please submit your report with sufficient time to allow the Incubator >> PMC, and subsequently board members to review and digest. Again, the >> very latest you should submit your report is 2 weeks prior to the board >> meeting. >> >> Thanks, >> >> The Apache Incubator PMC >> >> Submitting your Report >> >> -- >> >> Your report should contain the following: >> >> * Your project name >> * A brief description of your project, which assumes no knowledge of >> the project or necessarily of its field >> * A list of the three most important issues to address in the move >> towards graduation. >> * Any issues that the Incubator PMC or ASF Board might wish/need to be >> aware of >> * How has the community developed since the last report >> * How has the project developed since the last report. >> >> This should be appended to the Incubator Wiki page at: >> >> http://wiki.apache.org/incubator/October2016 >> >> Note: This is manually populated. You may need to wait a little before >> this page is created from a template. >> >> Mentors >> --- >> >> Mentors should review reports for their project(s) and sign them off on >> the Incubator wiki page. Signing off reports shows that you are >> following the project - projects that are not signed may raise alarms >> for the Incubator PMC. >> >> Incubator PMC >> > >
Re: freemarker asf branding
Just to be clear. I do not consider the logo to be a requirement. It is a should. We prefer to see the logo, but its not a requirement as of now. That doesn't mean it won't become a requirement. John On Fri, Jul 1, 2016 at 4:11 PM Daniel Dekany wrote: > There was no attachment in your mail. > > The only information I have found is "Incubator Logo Podlings websites > SHOULD contain the Apache Incubator Project logo as sign of > affiliation.". There's not even link to the logo, not to mention to > the source of the logo (which I suppose is > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/images/egg-logo-source.svg > ). > So the whole thing is totally informal. Surely they won't complain if > you re-rasterize the SVG in a different resolution, nor that if you > remove that black border. > > > Friday, July 1, 2016, 7:39:33 PM, Lee wrote: > > > Hey Sergio, > > > > I'll update the website with the logo. I was thinking of putting it > > in the left column on the website. Is that visible enough? Are we > > allowed to remove the border from the logo? The left-column is 210px > > wide and the logo is 229px. If I remove the border and the > > whitespace then it's 207px and fits nicely (see attached). If we > > can't remove the border, can we resize it? > > > > Thanks, > > Evangelia > > > > On Fri, Jul 1, 2016 at 12:07 AM, Sergio Fernández > wrote: > > Those who follow general@incubator, IPMC has started (led by John D. > > Ament) to audit podlings' branding: > > > > https://wiki.apache.org/incubator/BrandingAuditJune2016 > > > > FreeMarker is fine. But "Podlings websites SHOULD contain the Apache > > Incubator Project logo as sign of affiliation". Since it's a "SHOULD" is > > fine; but I'd recommend to add the Incubator logo somewhere in the site > > template. > > > > Thanks! > > > > -- > > Sergio Fernández > > Partner Technology Manager > > Redlink GmbH > > m: +43 6602747925 > > e: sergio.fernan...@redlink.co > > w: http://redlink.co > > > > -- > Thanks, > Daniel Dekany > >
Re: freemarker asf branding
On Jul 1, 2016 03:09, "Sergio Fernández" wrote: > > Those who follow general@incubator, IPMC has started (led by John D. > Ament) to audit podlings' branding: > > https://wiki.apache.org/incubator/BrandingAuditJune2016 > > FreeMarker is fine. But "Podlings websites SHOULD contain the Apache > Incubator Project logo as sign of affiliation". Since it's a "SHOULD" is > fine; but I'd recommend to add the Incubator logo somewhere in the site > template. Nope the disclaimer is in violation unless someone can send me a link to an approval of the rewording. > > Thanks! > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 > e: sergio.fernan...@redlink.co > w: http://redlink.co
Re: [mentors] Check out FreeMarker status page
On Sun, Jun 26, 2016 at 1:01 PM Daniel Dekany wrote: > I'm asking this primarily from mentors: > http://incubator.apache.org/projects/freemarker.html > > There are two thins to note: > > - "Add all active committers in the STATUS file." > What STATUS file? > The file at content/projects/freemarker.xml which renders as http://incubator.apache.org/projects/freemarker.html > > - For many things I have just added a year instead of year-month-day. > I hope nobody will care. > Yep, IPMC will care. You'll want to list out all of your reports - if you can include 04/2016 as well. Many of the dates you have for 07/2015 should be the day you entered incubation, which is 2015-07-01 Your name search should be a link to the podlingnamesearch JIRA for freemarker, I can't find one for the project, so I would recommend that you create one. > > -- > Thanks, > Daniel Dekany > >
Re: Podling Report Reminder - April 2016
Hi David, I'm subscribed to both infra and incubator. I don't see your email. Do you see it in the mail archives? If not, you probably need to subscribe to those lists using your non-apache email. If you're not sure how to setup apache emails, you can review this doc: https://reference.apache.org/committer/email John On Fri, Apr 8, 2016 at 1:36 PM David E Jones wrote: > > Thank Daniel, you are correct and that is where I sent the request last > time. I sent another request and hopefully someone will notice it… or maybe > I’m going about it wrong in some way or other just sending a general email > there (I don’t know… missing something special in the subject or sending > from my @apache.org address (which I don’t have anything setup to do), > etc). > > -David > > > > On 7 Apr 2016, at 23:27, Daniel Dekany wrote: > > > > It has to be requested on gene...@incubator.apache.org, not from Infra. > > > > > > Friday, April 8, 2016, 5:30:10 AM, David E Jones wrote: > > > >>> On 4 Apr 2016, at 23:34, Daniel Dekany wrote: > >>> > >>> I.e., to Mentors, please sign it off on > >>> http://wiki.apache.org/incubator/April2016! > >>> > >> > >> +1 from me. > >> > >> I still don’t have permission for this on wiki.apache.org (have > >> sent request to infra), ie the page shows as immutable. > >> > >> -David > >> > >> > > > > -- > > Thanks, > > Daniel Dekany > > > >
Re: Someone wants to help with the JBoss IDE plugin?
What if you just push eclipse plugins and skip jboss ide? On Apr 6, 2016 19:22, "Daniel Dekany" wrote: > Someone could still figure out if we can legally offer our own JBoss > FreeMarker IDE build for download, and how is it best to distribute > (like should we host our own update site somewhere?). > > Why? As I have said earlier, FreeMarker IDE fixes get into JBoss IDE > releases with quite big delay. Like I have some 4 months old pull > requests, quite simple ones, but none of them is merged in yet. I have > asked about it, and was told that maybe they will find time reviewing > them for the JBoss IDE release for Eclipse Neon. I guess that will be > a few more months. So, we could release updates with a half a year > less delay or such, which is clearly significant. > > > Monday, September 28, 2015, 12:10:08 AM, Daniel Dekany wrote: > > > So it's on http://freemarker.org/contribute.html, but... > > > > - I just want to emphasize that it's quite important for the success > > of the project. People need to edit the templates with something, > > and efficiently. For you convenience, the pending Jira issues: > > > > > https://issues.jboss.org/browse/JBIDE-20512?jql=project%20%3D%20JBIDE%20AND%20status%20in%20%28Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22%29%20AND%20component%20%3D%20freemarker > > > > - You can help even if you aren't into Eclipse plugin development! A > > problem is currently that the release of the plugin seems to be > > bound to the release of the JBoss Tools project which is very > > infrequent for our purpose. Maybe the fixes should just be > > back-ported into the previous JBoss Tools branch too solve that, and > > that's not done, but I really don't know. In any case, currently, > > FreeMarker IDE release cycles are way too slow [*]. A solution for > > this should be figured out, and discussed with the JBoss Tools guys. > > Like, just as an example, maybe we should set up our own plugin > > update site, and do the builds ourselves, but then legal issues has > > to be considered, and if that could interfere with the JBoss Tools > > installation of the users. > > > > *: For example, I have asked to increase the FreeMarker version in > >2.3.23. And sure it was done in the repo quickly (thanks to Denis > >Golovin who has also squashed several FreeMarker IDE bugs), but > >it's scheduled for JBoss Tools 4.4.0. That, I guess, is about 12 > >months away! Until that, FreeMarker IDE won't handle the new > >features of 2.3.23, which was released months ago. Or, FreeMarker > >IDE was pretty much unusably broken in 4.2.0. Months ago, it was > >fixed, and now its quite usable. Big difference. But for most user > >that will only become visible in 4.3.0, which is has only entered > >CR1 state not very long ago. Now, it all could be kind of OK, if > >there were JBoss IDE dependencies in FreeMarker IDE, or the other > >way around, but as far as I see there's pretty much none. So > >technically FreeMarker IDE could be released independently. > > > > -- > Thanks, > Daniel Dekany > >
Re: FreeMarker 2.3.24-incubating missing sources in Maven Central
I was able to download the files fine from maven central. John On Mon, Apr 4, 2016 at 2:29 PM Daniel Dekany wrote: > Thanks for reporting this! I have opened an Infra issue for this: > https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11591 > > Some technical details: The source artifact is there on > > https://repository.apache.org/content/repositories/releases/org/freemarker/freemarker/2.3.24-incubating/ > , > from where the artifacts automatically go to the Central. I'm not sure > if mere mortals can force re-synchronization, especially as Maven > Central repo artifacts, once uploaded, are final. Let's hope Infra can > help... > > > Monday, April 4, 2016, 5:10:56 PM, Emmeran Seehuber wrote: > > > Hi, > > > > I just upgraded my FreeMarker dependency to 2.3.24. For some > > reason, there are no sources in Maven Central. They are listed (see > > > http://search.maven.org/#artifactdetails%7Corg.freemarker%7Cfreemarker%7C2.3.24-incubating%7Cjar > > < > http://search.maven.org/#artifactdetails|org.freemarker|freemarker|2.3.24-incubating|jar > >) > > but if you click on the sources-jar, you get a 404. See > > > https://repo1.maven.org/maven2/org/freemarker/freemarker/2.3.24-incubating/freemarker-2.3.24-incubating-sources.jar > > < > https://repo1.maven.org/maven2/org/freemarker/freemarker/2.3.24-incubating/freemarker-2.3.24-incubating-sources.jar > > > > > > Something has gone wrong here. Would you mind re-uploading the > source-artefact? > > > > Thanks and keep up the good work! > > > > cu, > > Emmy > > -- > > > > Mit freundlichen Grüßen aus Augsburg > > > > Emmeran Seehuber > > Dipl. Inf. (FH) > > Schrannenstraße 8 > > 86150 Augsburg > > USt-IdNr.: DE266070804 > > > > -- > Thanks, > Daniel Dekany > >
Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)
On Thu, Mar 24, 2016 at 3:54 PM Daniel Dekany wrote: > I believe that PPMC member votes aren't binding, only IPCM member > votes are. Maybe I said otherwise earlier, but then I was wrong. So, > that was actually "+1 non-binding". > > The official incubator stance is that a PPMC is recommending a release. The IPMC is what actually votes on it. You don't really need to be worried about binding/non-binding in this case. John > > Thursday, March 24, 2016, 1:26:49 PM, Lee wrote: > > > +1 for release (binding) > > > > On Wednesday, March 23, 2016, Jacopo Cappellato < > jacopo.cappell...@gmail.com> > > wrote: > > > >> +1 for both releases (binding) > >> > >> The release files look good, I have built the jar from source files and > >> tested in the OFBiz framework. > >> > >> Jacopo > >> > >> > >> > >> On Mon, Mar 21, 2016 at 12:02 AM, Daniel Dekany >> > wrote: > >> > >> > Hi all, > >> > > >> > Please vote on releasing FreeMarker 2.3.24-incubating! This will be > >> > our first stable release (not just a Release Candidate) from the ASF. > >> > If this voting passes, another similar voting will be started on > >> > gene...@incubator.apache.org , and if that passes too, > >> then we can > >> > release this version. > >> > > >> > Release Notes: > >> > > http://freemarker.org/builds/2.3.24-unvoted/_html/versions_2_3_24.html > >> > > >> > Before proceed, you should know that FreeMarker 2.3.x, for a long > >> > time, always releases a normal and a "gae" variant on the same time, > >> > which are technically two independent source trees (Git branches). The > >> > "gae" variant contains a few small modification in the Java source > >> > code to be Google App Engine compliant, and has freemarker-gae as the > >> > Maven artifact name. Otherwise the normal and the "gae" branches are > >> > identical. Hence they will be voted on together. > >> > > >> > The commits to be voted upon are: > >> > - Normal (non-gae) variant: > >> > > >> > > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 > >> > Commit hash: 4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 > >> > - "gae" variant: > >> > > >> > > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4b8df1fd03c21495e646ac1721734811564317f5 > >> > Commit hash: 4b8df1fd03c21495e646ac1721734811564317f5 > >> > > >> > The artifacts to be voted upon are located here: > >> > > >> > > >> > https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/source/ > >> > where the source release artifacts are: > >> > - Normal (non-gae) variant: > >> > apache-freemarker-2.3.24-incubating-src.tar.gz > >> > - "gae" variant: > >> > apache-freemarker-gae-2.3.24-incubating-src.tar.gz > >> > > >> > See the README inside them for build instructions! > >> > > >> > Release artifacts are signed with the following key: > >> > https://people.apache.org/keys/committer/ddekany.asc > >> > > >> > Note that for convenience, we also provide binaries: > >> > > >> > > >> > https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/binaries/ > >> > and Maven artifacts in the ASF staging repository: > >> > > >> > https://repository.apache.org/content/repositories/staging/org/freemarker/ > >> > > >> > Please try out the package and vote! > >> > > >> > The vote is open for a minimum of 72 hours or until the necessary > number > >> of > >> > votes (3 binding +1s) is reached. > >> > > >> > [ ] +1 Release this package as Apache FreeMarker 2.3.24-incubating > >> > [ ] 0 I don't feel strongly about it, but I'm okay with the release > >> > [ ] -1 Do not release this package because... > >> > > >> > Please add "(binding)" if your vote is binding. > >> > > >> > -- > >> > Thanks, > >> > Daniel Dekany > >> > > >> > > >> > > -- > Thanks, > Daniel Dekany > >
Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)
Ok. got it figured out. Was a local install issue with recent updates. Anyways here's my +1 on your release. I'm an IPMC member but not on your PPMC. Notes on the release - Your notice includes some information about binaries in the source release. Is there anyway you could generate those files on the fly? I suspect they're test only dependencies. - Do you need to include the dtd's for web.xml? John On Mon, Mar 21, 2016 at 3:26 PM Daniel Dekany wrote: > I can't reproduce this. I have deleted all the Ivy caches, and it > still finds and downloads org.freemarker#docgen;2.0-branch-head fine. > The only thing I can think of is that earlier there was some > semi-successful ivy repo setup, and now it stays broken. So, try to > issue `ant clean-deps`, then also delete `~/.ivy`, and then try `ant` > again. Please store the full log of the last (i.e., the things that > Ant writes to the stdout), and in case it still fails, send it to me. > > -- > Thanks, > Daniel Dekany > > > Monday, March 21, 2016, 11:50:00 AM, John D. Ament wrote: > > > I do have ivy installed > > > > This is what I get from running ivy > > > > :: problems summary :: > > > > WARNINGS > > > > module not found: org.freemarker#docgen;2.0-branch-head > > > > > > local: tried > > > > > > > > > /Users/johnament/.ivy2/local/org.freemarker/docgen/2.0-branch-head/ivys/ivy.xml > > > > > > -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: > > > > > > > > > /Users/johnament/.ivy2/local/org.freemarker/docgen/2.0-branch-head/jars/docgen.jar > > > > > > shared: tried > > > > > > > > > /Users/johnament/.ivy2/shared/org.freemarker/docgen/2.0-branch-head/ivys/ivy.xml > > > > > > -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: > > > > > > > > > /Users/johnament/.ivy2/shared/org.freemarker/docgen/2.0-branch-head/jars/docgen.jar > > > > > > public: tried > > > > > > > > > https://repo1.maven.org/maven2/org/freemarker/docgen/2.0-branch-head/docgen-2.0-branch-head.pom > > > > > > -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: > > > > > > > > > https://repo1.maven.org/maven2/org/freemarker/docgen/2.0-branch-head/docgen-2.0-branch-head.jar > > > > > > :: > > > > > > :: UNRESOLVED DEPENDENCIES :: > > > > > > :::::::::: > > > > > > :: org.freemarker#docgen;2.0-branch-head: not found > > > > > > :: > > > > > > > > > > :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS > > > > On Mon, Mar 21, 2016 at 3:35 AM Daniel Dekany > wrote: > > > >> You haven't installed Ivy apparently. (But see the README.) > >> > >> -- > >> Thanks, > >> Daniel Dekany > >> > >> > >> Monday, March 21, 2016, 2:06:49 AM, John D. Ament wrote: > >> > >> > BTW - this is the error I get > >> > > >> > Johns-MBP-2:apache-freemarker-2.3.24-incubating-src johnament$ ant > >> compile > >> > Buildfile: > >> > > >> > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml > >> > [copy] Copying 1 file to > >> > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build > >> >[delete] Deleting: > >> > > >> > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp > >> > > >> > _autoget-deps: > >> > [copy] Copying 1 file to > >> > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build > >> >[delete] Deleting: > >> > > >> > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp > >> > > >> > update-deps: > >> > [echo] Getting dependencies... > >> > [echo] --- > >> > > >> > BUILD FAILED > >> > > >> > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml:951: > >> > The following error occurred while executing this line: > >> > > >> > /Users/johnament/Downloads/apache-freemarker-2.3.24
Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)
I do have ivy installed This is what I get from running ivy :: problems summary :: WARNINGS module not found: org.freemarker#docgen;2.0-branch-head local: tried /Users/johnament/.ivy2/local/org.freemarker/docgen/2.0-branch-head/ivys/ivy.xml -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: /Users/johnament/.ivy2/local/org.freemarker/docgen/2.0-branch-head/jars/docgen.jar shared: tried /Users/johnament/.ivy2/shared/org.freemarker/docgen/2.0-branch-head/ivys/ivy.xml -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: /Users/johnament/.ivy2/shared/org.freemarker/docgen/2.0-branch-head/jars/docgen.jar public: tried https://repo1.maven.org/maven2/org/freemarker/docgen/2.0-branch-head/docgen-2.0-branch-head.pom -- artifact org.freemarker#docgen;2.0-branch-head!docgen.jar: https://repo1.maven.org/maven2/org/freemarker/docgen/2.0-branch-head/docgen-2.0-branch-head.jar :: :: UNRESOLVED DEPENDENCIES :: :: :: org.freemarker#docgen;2.0-branch-head: not found :: :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS On Mon, Mar 21, 2016 at 3:35 AM Daniel Dekany wrote: > You haven't installed Ivy apparently. (But see the README.) > > -- > Thanks, > Daniel Dekany > > > Monday, March 21, 2016, 2:06:49 AM, John D. Ament wrote: > > > BTW - this is the error I get > > > > Johns-MBP-2:apache-freemarker-2.3.24-incubating-src johnament$ ant > compile > > Buildfile: > > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml > > [copy] Copying 1 file to > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build > >[delete] Deleting: > > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp > > > > _autoget-deps: > > [copy] Copying 1 file to > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build > >[delete] Deleting: > > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp > > > > update-deps: > > [echo] Getting dependencies... > > [echo] --- > > > > BUILD FAILED > > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml:951: > > The following error occurred while executing this line: > > > /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml:959: > > Problem: failed to create task or type > > antlib:org.apache.ivy.ant:settings > > Cause: The name is undefined. > > Action: Check the spelling. > > Action: Check that any custom tasks/types have been declared. > > Action: Check that any / declarations have taken > place. > > No types or tasks have been defined in this namespace yet > > > > This appears to be an antlib declaration. > > Action: Check that the implementing library exists in one of: > > -/usr/local/Cellar/ant/1.9.6/libexec/lib > > -/Users/johnament/.ant/lib > > -a directory added on the command line with the -lib argument > > > > > > Total time: 0 seconds > > > > On Sun, Mar 20, 2016 at 8:48 PM John D. Ament > wrote: > > Daniel, > > > > Do you have build instructions somewhere? > > > > > > John > > > > > > On Sun, Mar 20, 2016 at 7:02 PM Daniel Dekany > wrote: > > Hi all, > > > > Please vote on releasing FreeMarker 2.3.24-incubating! This will be > > our first stable release (not just a Release Candidate) from the ASF. > > If this voting passes, another similar voting will be started on > > gene...@incubator.apache.org, and if that passes too, then we can > > release this version. > > > > Release Notes: > > http://freemarker.org/builds/2.3.24-unvoted/_html/versions_2_3_24.html > > > > Before proceed, you should know that FreeMarker 2.3.x, for a long > > time, always releases a normal and a "gae" variant on the same time, > > which are technically two independent source trees (Git branches). The > > "gae" variant contains a few small modification in the Java source > > code to be Google App Engine compliant, and has freemarker-gae as the > > Maven artifact name. Otherwise the normal and the "gae" branches are > > identical. Hence they will be voted on together. > > > > The commits to be voted upon are: > > - Normal (non-gae) variant: > > > > >
Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)
BTW - this is the error I get Johns-MBP-2:apache-freemarker-2.3.24-incubating-src johnament$ ant compile Buildfile: /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml [copy] Copying 1 file to /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build [delete] Deleting: /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp _autoget-deps: [copy] Copying 1 file to /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build [delete] Deleting: /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build/version.properties.tmp update-deps: [echo] Getting dependencies... [echo] --- BUILD FAILED /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml:951: The following error occurred while executing this line: /Users/johnament/Downloads/apache-freemarker-2.3.24-incubating-src/build.xml:959: Problem: failed to create task or type antlib:org.apache.ivy.ant:settings Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any / declarations have taken place. No types or tasks have been defined in this namespace yet This appears to be an antlib declaration. Action: Check that the implementing library exists in one of: -/usr/local/Cellar/ant/1.9.6/libexec/lib -/Users/johnament/.ant/lib -a directory added on the command line with the -lib argument Total time: 0 seconds On Sun, Mar 20, 2016 at 8:48 PM John D. Ament wrote: > Daniel, > > Do you have build instructions somewhere? > > John > > > On Sun, Mar 20, 2016 at 7:02 PM Daniel Dekany wrote: > >> Hi all, >> >> Please vote on releasing FreeMarker 2.3.24-incubating! This will be >> our first stable release (not just a Release Candidate) from the ASF. >> If this voting passes, another similar voting will be started on >> gene...@incubator.apache.org, and if that passes too, then we can >> release this version. >> >> Release Notes: >> http://freemarker.org/builds/2.3.24-unvoted/_html/versions_2_3_24.html >> >> Before proceed, you should know that FreeMarker 2.3.x, for a long >> time, always releases a normal and a "gae" variant on the same time, >> which are technically two independent source trees (Git branches). The >> "gae" variant contains a few small modification in the Java source >> code to be Google App Engine compliant, and has freemarker-gae as the >> Maven artifact name. Otherwise the normal and the "gae" branches are >> identical. Hence they will be voted on together. >> >> The commits to be voted upon are: >> - Normal (non-gae) variant: >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 >> Commit hash: 4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 >> - "gae" variant: >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4b8df1fd03c21495e646ac1721734811564317f5 >> Commit hash: 4b8df1fd03c21495e646ac1721734811564317f5 >> >> The artifacts to be voted upon are located here: >> >> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/source/ >> where the source release artifacts are: >> - Normal (non-gae) variant: >> apache-freemarker-2.3.24-incubating-src.tar.gz >> - "gae" variant: >> apache-freemarker-gae-2.3.24-incubating-src.tar.gz >> >> See the README inside them for build instructions! >> >> Release artifacts are signed with the following key: >> https://people.apache.org/keys/committer/ddekany.asc >> >> Note that for convenience, we also provide binaries: >> >> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/binaries/ >> and Maven artifacts in the ASF staging repository: >> https://repository.apache.org/content/repositories/staging/org/freemarker/ >> >> Please try out the package and vote! >> >> The vote is open for a minimum of 72 hours or until the necessary number >> of >> votes (3 binding +1s) is reached. >> >> [ ] +1 Release this package as Apache FreeMarker 2.3.24-incubating >> [ ] 0 I don't feel strongly about it, but I'm okay with the release >> [ ] -1 Do not release this package because... >> >> Please add "(binding)" if your vote is binding. >> >> -- >> Thanks, >> Daniel Dekany >> >>
Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)
Daniel, Do you have build instructions somewhere? John On Sun, Mar 20, 2016 at 7:02 PM Daniel Dekany wrote: > Hi all, > > Please vote on releasing FreeMarker 2.3.24-incubating! This will be > our first stable release (not just a Release Candidate) from the ASF. > If this voting passes, another similar voting will be started on > gene...@incubator.apache.org, and if that passes too, then we can > release this version. > > Release Notes: > http://freemarker.org/builds/2.3.24-unvoted/_html/versions_2_3_24.html > > Before proceed, you should know that FreeMarker 2.3.x, for a long > time, always releases a normal and a "gae" variant on the same time, > which are technically two independent source trees (Git branches). The > "gae" variant contains a few small modification in the Java source > code to be Google App Engine compliant, and has freemarker-gae as the > Maven artifact name. Otherwise the normal and the "gae" branches are > identical. Hence they will be voted on together. > > The commits to be voted upon are: > - Normal (non-gae) variant: > > https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 > Commit hash: 4a723fc1e89c3f258b00e6ee40ba3c60d076aa89 > - "gae" variant: > > https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4b8df1fd03c21495e646ac1721734811564317f5 > Commit hash: 4b8df1fd03c21495e646ac1721734811564317f5 > > The artifacts to be voted upon are located here: > > https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/source/ > where the source release artifacts are: > - Normal (non-gae) variant: > apache-freemarker-2.3.24-incubating-src.tar.gz > - "gae" variant: > apache-freemarker-gae-2.3.24-incubating-src.tar.gz > > See the README inside them for build instructions! > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/ddekany.asc > > Note that for convenience, we also provide binaries: > > https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/binaries/ > and Maven artifacts in the ASF staging repository: > https://repository.apache.org/content/repositories/staging/org/freemarker/ > > Please try out the package and vote! > > The vote is open for a minimum of 72 hours or until the necessary number of > votes (3 binding +1s) is reached. > > [ ] +1 Release this package as Apache FreeMarker 2.3.24-incubating > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Please add "(binding)" if your vote is binding. > > -- > Thanks, > Daniel Dekany > >
Loading templates locale aware?
I was wondering, how does template loading work with locale aware requests? For example, I may have template files like: - registration_en_txt.ftl - registration_fr_txt.ftl Ideally, I'd like to specify my locale when fetching the template to separate out the locating and language awareness. I don't see any information that could be passed around with this information. If I look at https://github.com/apache/incubator-freemarker/blob/2.3-gae/src/main/java/freemarker/cache/TemplateLoader.java I don't see the locale passed in when trying to get a template. John
