Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.4
Karl & Richard, Karl, I've addressed the issue with the NOTICE file so I think we're alright there. Richard, was your response an implicit +1? From the release procedure documentation I need three votes, and I just want to be sure you've voted positively before I perform the release. thx, ken On Thu, Jan 26, 2012 at 11:22 PM, Karl Pauls wrote: > +1 on the release if the NOTICE as soon as it is fixed in trunk. > > regards, > > Karl > > On Thu, Jan 26, 2012 at 2:50 PM, Ken Gilmer wrote: >> Thanks for your feedback Richard and Karl. Well, given my luck with >> exploding stuff in wonderful strange ways, I'd prefer the "fix it in >> trunk and continue with the given release" route. But, I'm also happy >> to fix the NOTICE and roll a new release if anyone would prefer me to >> do that. >> >> thx, >> ken >> >> On Thu, Jan 26, 2012 at 10:41 PM, Karl Pauls wrote: >>> On Thu, Jan 26, 2012 at 2:35 PM, Richard S. Hall >>> wrote: On 1/26/12 8:09, Ken Gilmer wrote: > > Hi Richard, > > On Thu, Jan 26, 2012 at 9:32 PM, Richard S. Hall > wrote: >> >> The complete bundle includes OSGi classes, but does not list them in the >> NOTICE file. It's not clear to me if this is a requirement, since they >> OSGi >> artifacts themselves don't include a NOTICE, but we generally do include >> them in the NOTICE file for the framework JARs. > > In my memory I'd checked the http-bundle module and followed it but > now that I check again I can see that it does in fact include the OSGi > classes in the NOTICE. I can add that. > >> Also, I noticed that the DEPs file for the complete bundle was the old >> format while the core bundle was auto-generated, was there a reason for >> this? > > That is very strange. It took me a bit to figure out what you meant. > On my local machine where I did the build the jars both contain the > old format (meaning, not auto generated). But when I download the > jars from the repo I can see that the complete bundle has the auto > generated DEPENDENCIES file. I was under assumption that what I was > building locally was what was being sent to the repo. Yeah, I certainly don't know what's going on...I depend on Karl for releasing stuff. ;-) The DEPs file stuff isn't so important anyway, I only mention for reasons of consistency...my real question is about the NOTICE. If others think it isn't important, then we are probably good to go. >>> >>> I'd say it is up to the Release Manager (i.e., Ken in this case). The >>> osgi jars don't contain a NOTICE so they don't have to be mentioned. I >>> guess I just fix it in trunk and go ahead with the release unless it >>> is easy for you to re-roll at this time. Just let us know what you >>> want to do... >>> >>> regards, >>> >>> Karl >>> Thanks. -> richard > > thx > ken > >> -> richard >> >> >> On 1/20/12 0:57, Ken Gilmer wrote: >>> >>> Hello, >>> >>> We resolved 3 defects and added 3 features in this release: >>> >>> >>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22Lightweight+HTTP+Service%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide >>> >>> There are currently no outstanding issues. >>> >>> Staging repository: >>> https://repository.apache.org/content/repositories/orgapachefelix-108/ >>> >>> You can use this UNIX script to download the release and verify the >>> signatures: >>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh >>> >>> Usage: >>> sh check_staged_release.sh 108 /tmp/felix-staging >>> >>> Please vote to approve this release: >>> >>> [ ] +1 Approve the release >>> [ ] -1 Veto the release (please provide specific comments) >>> >>> This vote will be open for 72 hours. >>> >>> >>> >>> -- >>> Karl Pauls >>> karlpa...@gmail.com >>> http://twitter.com/karlpauls >>> http://www.linkedin.com/in/karlpauls >>> https://profiles.google.com/karlpauls > > > > -- > Karl Pauls > karlpa...@gmail.com > http://twitter.com/karlpauls > http://www.linkedin.com/in/karlpauls > https://profiles.google.com/karlpauls
[jira] [Resolved] (FELIX-3338) Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype
[ https://issues.apache.org/jira/browse/FELIX-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved FELIX-3338. - Resolution: Fixed Fix Version/s: metatype-1.0.6 Implemented support in the relevant objects. You can now get a list of optional attributes for such objects. > Add support for optional attributes in the MetaDataReader as defined in the > XML schema for metatype > --- > > Key: FELIX-3338 > URL: https://issues.apache.org/jira/browse/FELIX-3338 > Project: Felix > Issue Type: Improvement > Components: Metatype Service >Affects Versions: metatype-1.0.4 >Reporter: Marcel Offermans >Assignee: Marcel Offermans > Fix For: metatype-1.0.6 > > > If you look at the metatype spec, 105.8 shows the XML schema for metatype. We > have a parser for it called MetaDataReader, and it basically converts the XML > file into a tree of Java objects (MetaData and related). The schema, in > several locations, allows you to use optional attributes (scan the schema for > ). Our parser currently does not have a way to read such > attributes though, but it should! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work stopped] (FELIX-3338) Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype
[ https://issues.apache.org/jira/browse/FELIX-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-3338 stopped by Marcel Offermans. > Add support for optional attributes in the MetaDataReader as defined in the > XML schema for metatype > --- > > Key: FELIX-3338 > URL: https://issues.apache.org/jira/browse/FELIX-3338 > Project: Felix > Issue Type: Improvement > Components: Metatype Service >Affects Versions: metatype-1.0.4 >Reporter: Marcel Offermans >Assignee: Marcel Offermans > > If you look at the metatype spec, 105.8 shows the XML schema for metatype. We > have a parser for it called MetaDataReader, and it basically converts the XML > file into a tree of Java objects (MetaData and related). The schema, in > several locations, allows you to use optional attributes (scan the schema for > ). Our parser currently does not have a way to read such > attributes though, but it should! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (FELIX-3338) Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype
[ https://issues.apache.org/jira/browse/FELIX-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-3338 started by Marcel Offermans. > Add support for optional attributes in the MetaDataReader as defined in the > XML schema for metatype > --- > > Key: FELIX-3338 > URL: https://issues.apache.org/jira/browse/FELIX-3338 > Project: Felix > Issue Type: Improvement > Components: Metatype Service >Affects Versions: metatype-1.0.4 >Reporter: Marcel Offermans >Assignee: Marcel Offermans > > If you look at the metatype spec, 105.8 shows the XML schema for metatype. We > have a parser for it called MetaDataReader, and it basically converts the XML > file into a tree of Java objects (MetaData and related). The schema, in > several locations, allows you to use optional attributes (scan the schema for > ). Our parser currently does not have a way to read such > attributes though, but it should! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3338) Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype
Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype --- Key: FELIX-3338 URL: https://issues.apache.org/jira/browse/FELIX-3338 Project: Felix Issue Type: Improvement Components: Metatype Service Affects Versions: metatype-1.0.4 Reporter: Marcel Offermans If you look at the metatype spec, 105.8 shows the XML schema for metatype. We have a parser for it called MetaDataReader, and it basically converts the XML file into a tree of Java objects (MetaData and related). The schema, in several locations, allows you to use optional attributes (scan the schema for ). Our parser currently does not have a way to read such attributes though, but it should! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-3338) Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype
[ https://issues.apache.org/jira/browse/FELIX-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans reassigned FELIX-3338: --- Assignee: Marcel Offermans > Add support for optional attributes in the MetaDataReader as defined in the > XML schema for metatype > --- > > Key: FELIX-3338 > URL: https://issues.apache.org/jira/browse/FELIX-3338 > Project: Felix > Issue Type: Improvement > Components: Metatype Service >Affects Versions: metatype-1.0.4 >Reporter: Marcel Offermans >Assignee: Marcel Offermans > > If you look at the metatype spec, 105.8 shows the XML schema for metatype. We > have a parser for it called MetaDataReader, and it basically converts the XML > file into a tree of Java objects (MetaData and related). The schema, in > several locations, allows you to use optional attributes (scan the schema for > ). Our parser currently does not have a way to read such > attributes though, but it should! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Metatype: Parsing optional data with MetaDataReader
Welcome Frederic! You can argue that the current implementation already allows this, as it does not trip over optional attributes: it simply ignores them. :) But I will create a Jira issue and code to include them in the resulting Java objects. On Feb 4, 2012, at 14:41 PM, Frederic Esnault wrote: > I'd say that if the spec allows that, Felix should allow it too. > My first post here, hi everyone :) > Frederic > > On Sat, Feb 4, 2012 at 2:33 PM, Marcel Offermans < > marcel.offerm...@luminis.nl> wrote: > >> Hi all, >> >> If you look at the metatype spec, 105.8 shows the XML schema for metatype. >> We have a parser for it called MetaDataReader, and it basically converts >> the XML file into a tree of Java objects (MetaData and related). The >> schema, in several locations, allows you to use optional attributes (scan >> the schema for ). Our parser currently does not have a way >> to read such attributes though. >> >> Since it's my itch, I'd like to add support for that, but before I do the >> work I wanted to first discuss it here. Any thoughts? >> >> Greetings, Marcel >> >>
