Re: [VOTE] Release Apache Felix Http Components

[Ken Gilmer]

+1 (nb)

On Thu, Feb 28, 2019, 1:00 AM Timothy Ward  wrote:

> +1
>
> > On 27 Feb 2019, at 09:31, David Bosschaert 
> wrote:
> >
> > +1
> >
> > David
> >
> > On Tue, 26 Feb 2019 at 15:05, Carsten Ziegeler 
> wrote:
> >
> >> We solved four issues in http base 4.0.6:
> >>
> >> https://issues.apache.org/jira/projects/FELIX/versions/12344179
> >>
> >> We solved four issues in http bridge 4.0.6
> >> https://issues.apache.org/jira/projects/FELIX/versions/12344181
> >>
> >> We solved eight issues in http jetty 4.0.8
> >> https://issues.apache.org/jira/projects/FELIX/versions/12344180
> >>
> >> Staging repositories:
> >> https://repository.apache.org/content/repositories/orgapachefelix-1289
> >>
> >> 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 1289 /tmp/felix-staging
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >> Regards
> >> Carsten
> >>
> >> --
> >> Carsten Ziegeler
> >> Adobe Research Switzerland
> >> cziege...@apache.org
> >>
>
>

Re: [ANN] New committer: Tim Ward

[Ken Gilmer]

Welcome Tim :)

On Tue, Nov 13, 2018, 7:26 AM Pierre De Rop  Welcome Tim !!
>
> cheers
> Pierre
>
> On Tue, Nov 13, 2018 at 4:21 PM Carsten Ziegeler 
> wrote:
>
> > Welcome Tim!
> >
> > Carsten
> >
> > Am 13.11.2018 um 15:03 schrieb Karl Pauls:
> > > The Project Management Committee (PMC) for Apache Felix
> > > has invited Tim Ward to become a committer and we are pleased
> > > to announce that he has accepted.
> > >
> > > Please welcome Tim.
> > >
> > > Tim, you might want to introduce yourself.
> > >
> >
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>

Re: [VOTE] Release HttpLite 0.1.6

[Ken Gilmer]

+1 non binding

On May 5, 2017 3:32 AM, "Raymond Auge"  wrote:

> +1 (non-binding)
>
> On May 5, 2017 04:50, "David Bosschaert" 
> wrote:
>
> > +1
> >
> > David
> >
> > On 5 May 2017 at 08:26, Guillaume Nodet  wrote:
> >
> > > I've prepared a release to fix the following bug:
> > >  [FELIX-5624] HttpLite complete bundle has wrong ranges for package
> > imports
> > >
> > > The staging repository is available at:
> > >https://repository.apache.org/content/repositories/
> > orgapachefelix-1178
> > >
> > > The tag is available at :
> > >
> > > http://svn.apache.org/repos/asf/felix/releases/org.apache.
> > > felix.httplite.reactor-0.1.6/
> > >
> > > Please review and vote !
> > >
> > >
> > > --
> > > 
> > > Guillaume Nodet
> > >
> >
>

Re: [VOTE] Release Felix httplite version 0.1.5

[Ken Gilmer]

+1 (Non-binding)

On Mon, Nov 28, 2016 at 6:50 AM, Benson Margulies 
wrote:

> Hmm. I am inclined to write a JIRA to clean that up later; for the
> typical trivial use case of the 'lite' package, I don't think it's a
> big risk. We'll see if we get any votes.
>
> On Sun, Nov 27, 2016 at 10:50 PM, Chetan Mehrotra
>  wrote:
> > Hi Benson,
> >
> > On Sat, Nov 26, 2016 at 2:29 AM, Benson Margulies 
> wrote:
> >>   * [FELIX-5422] - httplite should accept more date formats.
> >
> > I think the commit done [0] for this issue has some issue. See the
> > mail sent on that at [1].
> >
> > Chetan Mehrotra
> > [0] https://github.com/apache/felix/commit/
> 3812f7eaa6168ebedb520c871d94ccab9958b68c
> > [1] https://lists.apache.org/thread.html/d1ffe9ccb0d577c697974c8781fa22
> 04ae99e02011fe619f335efa8c@%3Cdev.felix.apache.org%3E
>

[jira] [Commented] (FELIX-3811) http service should allow the interfaces bound to be configured

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660345#comment-14660345
 ] 

Ken Gilmer commented on FELIX-3811:
---

Sure, I'll work on that.

> http service should allow the interfaces bound to be configured
> ---
>
> Key: FELIX-3811
> URL: https://issues.apache.org/jira/browse/FELIX-3811
> Project: Felix
>  Issue Type: Wish
>  Components: Lightweight HTTP Service
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>Priority: Minor
>  Labels: patch
> Attachments: httplite.bind.patch
>
>
> As I primarily use the lightweight http service to debug using the webconsole 
> it would be nice to only bind it to the local interface to limit access to 
> the webconsole. This could be done by providing a configuration paramater to 
> specify the host address to bind to and could also be useful for those 
> running lightweight http on multihomed hosts.
> I have created a patch against 0.1.5-SNAPSHOT that includes such 
> functionality. It uses org.apache.felix.http.host as the configuration key 
> but this could be changed. The semantics of what should be done when the host 
> specified cannot be resolved (eg: InetAddress.getByName() fails) may also be 
> worth changing. Presently it just binds to all interfaces if it is unable to 
> resolve/parse the address. Failing closed would be better in my opinion but 
> might not be the most intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Accept PojoSR code donation

[Ken Gilmer]

+1 (non binding)


On Thu, Mar 6, 2014 at 3:25 AM, David Jencks  wrote:

> +1
>
> david jencks
>
> On Mar 5, 2014, at 6:49 AM, Guillaume Nodet  wrote:
>
> > Karl Pauls is willing to donate PojoSR (
> https://code.google.com/p/pojosr/)
> > to Felix.
> >
> > This vote is about officially accepting the donation.
> >
> > [ ] +1  Accept PojoSR code into Felix
> > [ ] -1 Do not
> >
> > Cheers,
> > Guillaume Nodet
>
>

Re: [VOTE] framework 4.2.0 and related subproject releases

[Ken Gilmer]

+1 (non binding)

Thx,
ken


On Wed, Feb 6, 2013 at 8:58 AM, Jan Willem Janssen <
janwillem.jans...@luminis.eu> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2/6/13 12:19 AM, Karl Pauls wrote:
> > [x] +1 Approve the release
>
> +1 (non-binding)
>
> - --
> Met vriendelijke groeten | Kind regards
>
> Jan Willem Janssen | Software Architect
> +31 631 765 814
>
> /My world is:/
>
> Luminis Technologies B.V.
> IJsselburcht 3
> 6825 BS  Arnhem
> +31 88 586 46 30
>
> http://www.luminis-technologies.com
> http://www.luminis.eu
>
> KvK (CoC) 09 16 28 93
> BTW (VAT) NL8169.78.566.B.01
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJREmGJAAoJEKF/mP2eHDc4X3IP/0UeA6MT86v7dfdGpFSY2qRu
> OuQqkvGNHrw7t5LlCo/y7+by9HLWJLiDhJAtfSz8k1IbvyI/KFq7BXt3M3V1evFC
> sjxDP5rZBUSpLJk8zT4a4wIWqMewl0DpJnpuzdcqmIDnpYfNUQq8t7EUdYuSB6aE
> d1bFWBGDKsKwgjylS+y+ZrXEN5SoryOodBmYs2UYt6FJLql8be7pL4VdD2+O8icL
> Ng7czpv+nnQujjL+CrsXmL89zfj0LQY2oEPAZu9w9hMFaWwbtt7JY6a0ddVvKioX
> 308O0ah3lccepYMWlvVxF1v9SwxmPAabPWhr4Cdjswc93RvVmA+CseC9xIkdADYM
> TyYVHisAQp6ONnJE1NRMS+M1McKhSoNk/ImSqd1/nf+tUuOTRzA4SDwPNJhObwzk
> ih169bhzoSLKu4dJyupZAsHrqswQ9QfNgtbt8EQPQh7dyuHyLtjtuhHan9znRubQ
> Dq/v5AqIE+ilYMWkvPHkWHB7hOML4+nKrsyxFKExP1TMjeH0Ne7wsR6y63E46zYo
> NFSJTfHESuth6mzmegjD2zMvYpuHDI5Y2Tng/RMq2Qj88boNRFyZ4gRf8LzXyDoT
> BwioNq2OGMlFcvqoJGJ7yRmv9GAhdDXtebRafZwkstMzDjOzXX/Q1/CyDnyrDw6v
> pckrf5K5O0nXxYtRVncx
> =bZMJ
> -END PGP SIGNATURE-
>
>

Re: [VOTE] Release Apache Felix Web Console 4.0.0 and plugins

[Ken Gilmer]

FYI the httplite bug should be fixed as of rev 1423137.

thx,
ken


On Mon, Jun 4, 2012 at 8:39 AM, Pierre De Rop wrote:

> Mon, 04 Jun
> 2012 12:27:48 GMT
>

[jira] [Resolved] (FELIX-3811) http service should allow the interfaces bound to be configured

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3811.
---

Resolution: Fixed

Applied Ed's patch and a minor update for consistent code style.  All tests 
pass.

> http service should allow the interfaces bound to be configured
> ---
>
> Key: FELIX-3811
> URL: https://issues.apache.org/jira/browse/FELIX-3811
> Project: Felix
>  Issue Type: Wish
>  Components: Lightweight HTTP Service
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>Priority: Minor
>  Labels: patch
> Attachments: httplite.bind.patch
>
>
> As I primarily use the lightweight http service to debug using the webconsole 
> it would be nice to only bind it to the local interface to limit access to 
> the webconsole. This could be done by providing a configuration paramater to 
> specify the host address to bind to and could also be useful for those 
> running lightweight http on multihomed hosts.
> I have created a patch against 0.1.5-SNAPSHOT that includes such 
> functionality. It uses org.apache.felix.http.host as the configuration key 
> but this could be changed. The semantics of what should be done when the host 
> specified cannot be resolved (eg: InetAddress.getByName() fails) may also be 
> worth changing. Presently it just binds to all interfaces if it is unable to 
> resolve/parse the address. Failing closed would be better in my opinion but 
> might not be the most intuitive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (FELIX-3811) http service should allow the interfaces bound to be configured

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on FELIX-3811 started by Ken Gilmer.

> http service should allow the interfaces bound to be configured
> ---
>
> Key: FELIX-3811
> URL: https://issues.apache.org/jira/browse/FELIX-3811
> Project: Felix
>  Issue Type: Wish
>  Components: Lightweight HTTP Service
>Reporter: Ed Schaller
>    Assignee: Ken Gilmer
>Priority: Minor
>  Labels: patch
> Attachments: httplite.bind.patch
>
>
> As I primarily use the lightweight http service to debug using the webconsole 
> it would be nice to only bind it to the local interface to limit access to 
> the webconsole. This could be done by providing a configuration paramater to 
> specify the host address to bind to and could also be useful for those 
> running lightweight http on multihomed hosts.
> I have created a patch against 0.1.5-SNAPSHOT that includes such 
> functionality. It uses org.apache.felix.http.host as the configuration key 
> but this could be changed. The semantics of what should be done when the host 
> specified cannot be resolved (eg: InetAddress.getByName() fails) may also be 
> worth changing. Presently it just binds to all interfaces if it is unable to 
> resolve/parse the address. Failing closed would be better in my opinion but 
> might not be the most intuitive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FELIX-3811) http service should allow the interfaces bound to be configured

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer reassigned FELIX-3811:
-

Assignee: Ken Gilmer

> http service should allow the interfaces bound to be configured
> ---
>
> Key: FELIX-3811
> URL: https://issues.apache.org/jira/browse/FELIX-3811
> Project: Felix
>  Issue Type: Wish
>  Components: Lightweight HTTP Service
>Reporter: Ed Schaller
>    Assignee: Ken Gilmer
>Priority: Minor
>  Labels: patch
> Attachments: httplite.bind.patch
>
>
> As I primarily use the lightweight http service to debug using the webconsole 
> it would be nice to only bind it to the local interface to limit access to 
> the webconsole. This could be done by providing a configuration paramater to 
> specify the host address to bind to and could also be useful for those 
> running lightweight http on multihomed hosts.
> I have created a patch against 0.1.5-SNAPSHOT that includes such 
> functionality. It uses org.apache.felix.http.host as the configuration key 
> but this could be changed. The semantics of what should be done when the host 
> specified cannot be resolved (eg: InetAddress.getByName() fails) may also be 
> worth changing. Presently it just binds to all interfaces if it is unable to 
> resolve/parse the address. Failing closed would be better in my opinion but 
> might not be the most intuitive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [RESULT] [VOTE] Release Apache Felix Web Console 4.0.0 and plugins

[Ken Gilmer]

Sorry so late to this thread, recently realized I could search my mail for
"httplite".  I will look into addressing this bug shortly.

Thanks
ken



On Sun, Jun 10, 2012 at 8:18 PM, Felix Meschberger wrote:

> And with the correct subject:
>
> Am 10.06.2012 um 20:13 schrieb Felix Meschberger:
>
> > Hi
> >
> > Time to tally the vote:
> >
> >  +1 Felix Meschberger*, Richard Hall*, Jamie Goodyear,
> > Carsten Ziegeler*, Karl Pauls*, Alex Karasulu*,
> > Clement Escoffier*, Pierre de Rop
> >   0 -
> >  -1 -
> >
> > Thus this release passes with 8 +1 votes (6 of which binding). No other
> votes have been cast.
> >
> > I will now publish the artifacts and add them to down load page.
> >
> > Re "No changelog in OBR plugin": This has been added to SVN in the
> meantime and will be in the next release.
> >
> > Re "Failure on httplite": I tend to think that this really comes from
> httplite. Nevertheless, if this is really a problem of the Web Console, it
> will be fixed in the next release.
> >
> > Regards
> > Felix
> >
> > Am 01.06.2012 um 11:45 schrieb Felix Meschberger:
> >
> >> Hi,
> >>
> >> This is a large vote on the Web Console and a number of plugins
> extracted from the web console or updated since the last release.
> >>
> >> I bumped the Web Console to version 4 because it now only comes in the
> "bare" variant. That is the JSON and Commons FileUpload dependencies are
> not part of the Web Console bundle any longer and must be installed
> separately. For JSON, the Geronimo JSON bundle may be used while the
> Commons FileUpload library already comes as a bundle.
> >>
> >> In addition a number of plugins have been ripped out of the Web Console
> into separate bundles: DS and OBR. The Memory Usage plugin has been
> updated. The Package Admin and UPnP plugins are new plugins.
> >>
> >> Here are the links to the JIRA fixed versions:
> >>
> >> Web Console 4.0.0
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12316160
> >>
> >> DS Plugin 1.0
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12317872
> >>
> >> Memory Usage Plugin 1.0.4
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12314875
> >>
> >> OBR Plugin 1.0
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12317956
> >>
> >> PackageAdmin Plugin 1.0.0
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12316672
> >>
> >> UPnP Plugin 1.0.2
> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12314879
> >>
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefelix-174/
> >>
> >> 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 174 /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 at least 72 hours (due to weekend and large
> number of artifacts).
> >>
> >> Regards
> >> Felix
> >
>
>

[jira] [Commented] (FELIX-3547) NPE in httplite on android creating Locale.

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501643#comment-13501643
 ] 

Ken Gilmer commented on FELIX-3547:
---

Patch committed in revision 1411974.  Thanks again Ed!

> NPE in httplite on android creating Locale.
> ---
>
> Key: FELIX-3547
> URL: https://issues.apache.org/jira/browse/FELIX-3547
> Project: Felix
>  Issue Type: Bug
>  Components: Lightweight HTTP Service
> Environment: Android 2.3.x
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>  Labels: patch
> Attachments: HttpServletRequestImpl.3547.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> httplite/core/src/main/java/org/apache/felix/httplite/servlet/HttpServletRequestImpl.java
>  contains the following at line 86:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language" ), System.getProperty( "user.country" ) );
> On Android (at least 2.3, other versions not tried) this produces a 
> NullPointerException when HttpServletRequestImpl is constructed because the 
> Locale constructor cannot handle null and neither property is defined by 
> default on Android.
> This is trivial to work around with code like:
> if(System.getProperty("user.language")==null)
> System.setProperty("user.language", 
> Locale.getDefault().getLanguage());
> if(System.getProperty("user.country")==null)
> System.setProperty("user.country", Locale.getDefault().getCountry());
> A easy solution is to replace the above line with:
> private final Locale m_locale = Locale.getDefault();
> This would cause each instance to have the same Local object. Although I 
> would be surprised if this is an issue the following would also work:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language", Locale.getDefault().getLanguage() ), System.getProperty( 
> "user.country" ) , Locale.getDefault().getCountry());
> I'm using httplite with the felx web console for debugging. Other than this 
> bug and needing to set an uncaught exception handler so android doesn't force 
> close the app all is working well (the memory usage plugin of coarse dose not 
> work because it depends on jmx which android doesn't have.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-3547) NPE in httplite on android creating Locale.

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501185#comment-13501185
 ] 

Ken Gilmer commented on FELIX-3547:
---

I'm sorry but I did not see this when it was filed in June.  I will work on 
getting it resolved in SVN ASAP, and thanks for the patch Ed!

> NPE in httplite on android creating Locale.
> ---
>
> Key: FELIX-3547
> URL: https://issues.apache.org/jira/browse/FELIX-3547
> Project: Felix
>  Issue Type: Bug
>  Components: Lightweight HTTP Service
> Environment: Android 2.3.x
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>  Labels: patch
> Attachments: HttpServletRequestImpl.3547.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> httplite/core/src/main/java/org/apache/felix/httplite/servlet/HttpServletRequestImpl.java
>  contains the following at line 86:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language" ), System.getProperty( "user.country" ) );
> On Android (at least 2.3, other versions not tried) this produces a 
> NullPointerException when HttpServletRequestImpl is constructed because the 
> Locale constructor cannot handle null and neither property is defined by 
> default on Android.
> This is trivial to work around with code like:
> if(System.getProperty("user.language")==null)
> System.setProperty("user.language", 
> Locale.getDefault().getLanguage());
> if(System.getProperty("user.country")==null)
> System.setProperty("user.country", Locale.getDefault().getCountry());
> A easy solution is to replace the above line with:
> private final Locale m_locale = Locale.getDefault();
> This would cause each instance to have the same Local object. Although I 
> would be surprised if this is an issue the following would also work:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language", Locale.getDefault().getLanguage() ), System.getProperty( 
> "user.country" ) , Locale.getDefault().getCountry());
> I'm using httplite with the felx web console for debugging. Other than this 
> bug and needing to set an uncaught exception handler so android doesn't force 
> close the app all is working well (the memory usage plugin of coarse dose not 
> work because it depends on jmx which android doesn't have.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FELIX-3547) NPE in httplite on android creating Locale.

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer reassigned FELIX-3547:
-

Assignee: Ken Gilmer

> NPE in httplite on android creating Locale.
> ---
>
> Key: FELIX-3547
> URL: https://issues.apache.org/jira/browse/FELIX-3547
> Project: Felix
>  Issue Type: Bug
>  Components: Lightweight HTTP Service
> Environment: Android 2.3.x
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>  Labels: patch
> Attachments: HttpServletRequestImpl.3547.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> httplite/core/src/main/java/org/apache/felix/httplite/servlet/HttpServletRequestImpl.java
>  contains the following at line 86:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language" ), System.getProperty( "user.country" ) );
> On Android (at least 2.3, other versions not tried) this produces a 
> NullPointerException when HttpServletRequestImpl is constructed because the 
> Locale constructor cannot handle null and neither property is defined by 
> default on Android.
> This is trivial to work around with code like:
> if(System.getProperty("user.language")==null)
> System.setProperty("user.language", 
> Locale.getDefault().getLanguage());
> if(System.getProperty("user.country")==null)
> System.setProperty("user.country", Locale.getDefault().getCountry());
> A easy solution is to replace the above line with:
> private final Locale m_locale = Locale.getDefault();
> This would cause each instance to have the same Local object. Although I 
> would be surprised if this is an issue the following would also work:
> private final Locale m_locale = new Locale( System.getProperty( 
> "user.language", Locale.getDefault().getLanguage() ), System.getProperty( 
> "user.country" ) , Locale.getDefault().getCountry());
> I'm using httplite with the felx web console for debugging. Other than this 
> bug and needing to set an uncaught exception handler so android doesn't force 
> close the app all is working well (the memory usage plugin of coarse dose not 
> work because it depends on jmx which android doesn't have.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: More work on Felix application examples

[Ken Gilmer]

I could be wrong but it seems the most common stumbling block for a lot of
new people is getting Jetty running on Felix using the Apache HTTP
bundle(s).  Perhaps this is already covered well in the documentation but
if not it would IMHO be a valuable thing to have...

thx,
ken


On Mon, Nov 12, 2012 at 1:29 AM, Felix Meschberger wrote:

> +1
>
> Regards
> Felix
>
> Am 12.11.2012 um 04:22 schrieb Richard S. Hall:
>
> > The more examples, the better, as far as I am concerned.
> >
> > -> richard
> >
> > On 11/11/12 06:05, Benedikt Ritter wrote:
> >> Hi,
> >>
> >> a while back I did some work on the examples provided on the felix web
> site
> >> (see Jira Issues [1,2,3,4] and ML thread [5]). Now after I have
> finished my
> >> master thesis, I want to get involved again. I thought about doing some
> >> more work in the examples section.
> >>
> >> The SimpleShape examples show the use of low level OSGi APIs, so it
> would
> >> make sense to provide examples for the higher level APIs as well. Right
> now
> >> I'm thinking of adapting the SimpleShape example to Declarative Services
> >> and to iPOJO.
> >>
> >> So the only question is: Is the community interested in more example
> >> material? (I would do the required documentation work for the web site
> as
> >> well)
> >>
> >> Regards,
> >> Benedikt
> >>
> >> [1] https://issues.apache.org/jira/browse/FELIX-3376
> >> [2] https://issues.apache.org/jira/browse/FELIX-3376
> >> [3] https://issues.apache.org/jira/browse/FELIX-3382
> >> [4] https://issues.apache.org/jira/browse/FELIX-3379
> >> [5] http://www.mail-archive.com/dev@felix.apache.org/msg25640.html
> >>
> >
>
>

Re: [VOTE] Release Apache Felix Configuration Admin 1.6.0

[Ken Gilmer]

+1 (non binding)

Thanks,
ken


On Mon, Oct 22, 2012 at 9:34 AM, Carsten Ziegeler wrote:

> +1
>
> Carsten
>
> 2012/10/22 David Bosschaert :
> > +1 (non binding)
> >
> > Best regards,
> >
> > David
> >
> > On 20 October 2012 11:36, Felix Meschberger  wrote:
> >> Hi,
> >>
> >> Here is the Apache Felix Configuration Admin 1.6.0 release implementing
> the most recent Configuration Admin Specification Version 1.5.
> >>
> >> The issues completed in this release are listed in the release notes at
> (also attached at the end of this message):
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100&version=12320945
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefelix-144/
> >>
> >> 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 144 /tmp/felix-staging
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Release
> >> [ ] -1 Don't release, because ...
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> Regards
> >> Felix
> >>
> >> ** Bug
> >> * [FELIX-3532] - Source artifact is not being generated
> >> * [FELIX-3596] - Config Admin should track
> >>  SynchronousConfigurationListeners
> >> * [FELIX-3721] - Configuration not always provided upon
> >>  initial service registration
> >> ** Improvement
> >> * [FELIX-3577] - Refactor helpers and service trackers
> >> * [FELIX-3622] - ConfigurationManager.listConfigurations
> >>  may not always properly log the
> >>  configuration PID
> >> ** Task
> >> * [FELIX-3479] - [Config Admin 1.5] Implement
> >>  Configuration.getChangeCount()
> >> * [FELIX-3480] - [Config Admin 1.5] Implement support for
> >>  SynchronousConfigurationListener
> >> * [FELIX-3481] - [Config Admin 1.5] Implement support for
> >>  Targeted PIDs
> >> * [FELIX-3483] - [Config Admin 1.5] Export cm API at version 1.5
> >> * [FELIX-3554] - Prevent same configuration to be delivered
> >>  multiple times
> >> * [FELIX-3562] - Use OSGi Configuration Admin 1.5 API classes
> >> * [FELIX-3578] - ConfigAdmin Maven build does not have Maven
> >>  convention *-sources.jar artifacts
> >>
>
>
>
> --
> Carsten Ziegeler
> cziege...@apache.org
>

Re: [VOTE] Accept the JAAS Contribution by Chetan Mehrotra

[Ken Gilmer]

+1

Thanks,
ken

On Thu, Oct 11, 2012 at 10:00 AM, Alex Karasulu wrote:

> +1
>
> On Thu, Oct 11, 2012 at 4:00 PM, Karl Pauls  wrote:
>
> > +1
> >
> > regards,
> >
> > Karl
> >
> > On Thu, Oct 11, 2012 at 2:54 PM, Richard S. Hall 
> > wrote:
> > > +1
> > >
> > > -> richard
> > >
> > >
> > > On 10/11/12 05:52 , Felix Meschberger wrote:
> > >>
> > >> Hi all
> > >>
> > >> As previously discussed, Chetan offers the contribution of a bundle to
> > >> simplify integration of JAAS functionality in OSGi applications.
> > >>
> > >> The source is attached to FELIX-3705 [1] which also contains a link to
> > the
> > >> list discussions.
> > >>
> > >> Please vote:
> > >>
> > >>[ ] +1 accept the contribution
> > >>[ ]  0 don't care
> > >>[ ] -1 don't accept, because 
> > >>
> > >> The vote will be open for 72 hours.
> > >>
> > >> Upon a successfull vote, the process will continue with the official
> IP
> > >> Clearance process [2].
> > >>
> > >> Regards
> > >> Felix
> > >>
> > >> [1] https://issues.apache.org/jira/browse/FELIX-3705
> > >> [2] http://incubator.apache.org/ip-clearance/index.html
> > >
> > >
> >
> >
> >
> > --
> > Karl Pauls
> > karlpa...@gmail.com
> > http://twitter.com/karlpauls
> > http://www.linkedin.com/in/karlpauls
> > https://profiles.google.com/karlpauls
> >
>
>
>
> --
> Best Regards,
> -- Alex
>

Re: [VOTE] Release fileinstall 3.2.6

[Ken Gilmer]

+1 (non-binding)

Thanks,
ken

On Thu, Sep 27, 2012 at 9:08 AM, Felix Meschberger wrote:

> +1
>
> One minor thing: The binary bundle also contains the
> ConfigurationHandler.java source class. Is that by intent or by accident ?
>
> Regards
> Felix
>
> Am 25.09.2012 um 15:06 schrieb Guillaume Nodet:
>
> > We solved 2 issues in this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100&version=12321748
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-038/
> >
> > The tag is available at:
> >
> http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.fileinstall-3.2.6/
> >
> > 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 038 /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.
> >
> > --
> > 
> > Guillaume Nodet
> > 
> > Blog: http://gnodet.blogspot.com/
> > 
> > FuseSource, Integration everywhere
> > http://fusesource.com
>
>

Re: [VOTE] framework 4.0.3 and related subproject releases

[Ken Gilmer]

+1 (non binding)

thx
ken

On Mon, Jul 2, 2012 at 11:38 PM, Sahoo  wrote:

> +1.
>
> I did a quick test with GlassFish and found no issues as expected.
>
> Sahoo
>
>
> On Monday 02 July 2012 02:36 AM, Karl Pauls wrote:
>
>> I would like to call a vote on the following subproject releases:
>>
>> framework  4.0.3
>> main 4.0.3
>> main.distribution 4.0.3
>>
>>
>> Staging repositories:
>> https://repository.apache.org/**content/repositories/**
>> orgapachefelix-001/
>>
>> 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 001 /tmp/felix-staging
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>
>

Re: [VOTE] Release Felix Configuration Admin version 1.4.0

[Ken Gilmer]

Hello :)

+1 (non binding)

thx
ken


On Wed, May 30, 2012 at 11:19 AM, Clement Escoffier <
clement.escoff...@gmail.com> wrote:

> +1,
>
> Regards,
>
> Clement
>
> On 30.05.2012, at 15:20, Felix Meschberger wrote:
>
> > Hi,
> >
> > This is a vote on version 1.4.0 of the Felix Configuration Admin Service
> implementation. The corner stones of this release a re compliance with the
> latest Configuration Admin Service specification (version 1.4 as published
> in Compendium 4.3 specification).
> >
> > At the same time, this is basically the same code, which is also used as
> the reference implementation for the Configuration Admin 1.4 specification.
> As such this release, of course also passes the CT for the Configuration
> Admin 1.4.
> >
> > The main big difference to earlier releases of this bundle is, that this
> build requires a Java 5 or newer platform to run because the embedded OSGi
> classes are compiled for Java 5 and are using generics. Great care has
> nevertheless been taken to not actually require Java 5 platform or API
> features. So, after recompiling the OSGi classes and this bundle using the
> target "jsr14" this bundle is expected to run on Java 1.4 compliant
> platforms.
> >
> > The next release coming soon will implement version 1.5 of the
> Configuration Admin specification to be published in the upcoming
> Compendium 5 specification.
> >
> > We solved 22 issues in this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100&version=12316414
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-157/
> >
> > 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 157 /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.
> >
> > Regards
> > Felix
>
>

Re: [VOTE] Release FileInstall 3.2.0

[Ken Gilmer]

+1 (non-binding)

thx
ken

On Tue, Mar 20, 2012 at 8:20 PM, Andreas Pieber  wrote:
> +1 (non-binding)
>
> Kind regards,
> Andreas
>
> On Mon, Mar 19, 2012 at 15:07, Guillaume Nodet  wrote:
>> Hi,
>>
>> Given the number of improvements, I've chosen to upgrade to a new
>> minor release instead of a micro one.
>>
>> Please take some time to test as there has been important improvements
>> that could (hopefully not) lead to regressions.
>>
>> We solved 18 issues in this
>> release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316135&styleName=Html&projectId=12310100
>> There are still 6 outstanding
>> issues:https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22File+Install%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachefelix-091/
>> 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 091 /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 at least 72 hours.
>>
>>
>> --
>> 
>> Guillaume Nodet
>> 
>> Blog: http://gnodet.blogspot.com/
>> 
>> FuseSource, Integration everywhere
>> http://fusesource.com

Re: [VOTE] shell 1.4.3 release

[Ken Gilmer]

+1 (non-binding)

thx,
ken

[RESULT] [VOTE] Release Felix Lightweight HTTP Service version 0.1.4

[Ken Gilmer]

Hi,

The vote has passed with the following result :

  +1 (binding): Carsten Ziegeler, Richard S. Hall, Karl Pauls
  +1 (non binding): Arjun Panday

I will copy this release to the Felix dist directory and
promote the artifacts to the central Maven repository.

Thanks!
ken

Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.4

[Ken Gilmer]

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

Re: [VOTE] Release Service Diagnostics Plugin version 0.1.1

[Ken Gilmer]

+1 (Non-binding)

thx,
ken

On Mon, Jan 30, 2012 at 7:04 PM, Arjun Panday
 wrote:
> Hi,
>
> According to the doc, "the decision is officially determined solely by
> whether at least three +1 votes were registered".
>
> So far I have one binding vote by Carsten and one non binding by Pierre.
>
> Does anyone else have an opinion on this release?
>
> Felix, have you checked the new directory structure?
>
>
> Thanks everyone,
> Arjun
>
>
>
>
>
> On 01/25/2012 10:08 AM, Carsten Ziegeler wrote:
>>
>> +1
>>
>> Carsten
>>
>> 2012/1/20 Arjun Panday:
>>>
>>> Hi everyone,
>>>
>>> Second attempt at releasing the Service Diagnostics WebConsole Plugin.
>>> I've simply refactored the POMs by moving the parent role out of the
>>> reactor
>>> POM. The directory structure seems cleaner. Let me know.
>>>
>>> Here's the staging repository:
>>> https://repository.apache.org/content/repositories/orgapachefelix-110/
>>>
>>>
>>> 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 010 /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.
>>>
>>> Thanks,
>>> -arjun
>>>
>>>
>>>
>>>
>>>
>>
>>
>

Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.4

[Ken Gilmer]

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

Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.4

[Ken Gilmer]

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.

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.

Re: [ANN] Xander added as committer

[Ken Gilmer]

That's great, welcome Xander!

On Sat, Jan 21, 2012 at 6:23 AM, Pierre De Rop  wrote:
> Welcome to you, Xander
>
> /pierre
>
> On Fri, Jan 20, 2012 at 8:42 PM, Marcel Offermans <
> marcel.offerm...@luminis.nl> wrote:
>
>> I just wanted to announce that Xander has been accepted as a Felix
>> committer for his continued work on the Dependency Manager. Congratulations
>> Xander, and welcome on board!
>>
>> Greetings, Marcel
>>
>>

Re: Release problem - need help

[Ken Gilmer]

Karl,

  Ah, yes I see the root of my troubles; I was trying to use the root
of my project as the name of my "core" module.  I can see from other
subprojects that this isn't kosher, and that each module has to have a
name more than just the root subproject id.  I've renamed the minimum
project from 'org.apache.felix.httplite' to
'org.apache.felix.httplite.core' and that problem has been fixed.
Thanks again for your help Karl!

-ken

On Thu, Jan 19, 2012 at 11:19 PM, Karl Pauls  wrote:
> You are trying to release the minium project. Did you adapt its scm
> tag too? If it is pointing to the reactor root (as it is in svn atm)
> it will try to recursively release the reactor. Fix it and it should
> work - Don't ask me why :-D
>
> regards,
>
> Karl
>
> On Thu, Jan 19, 2012 at 2:24 PM, Ken Gilmer  wrote:
>> Hi Karl,
>>
>>  Thanks for your ideas, that certainly helps!  Yes the SCM stuff is
>> incorrect for my 'complete' target and that is probably why it's hanging
>> up.
>>
>>  Trying to follow your advice regarding the parent pom version...I am not
>> sure what you mean.  When I look at other projects that have the same
>> pattern (eventadmin), they use the same version.  I tried updating to
>> version 2 as is in the http project but received a maven error that that
>> version does not exist.  It seems like most of the subprojects that have
>> reactor/module builds use 1.0.4.  What am I missing?
>>
>>  Regarding "... try to release the individual targets and not the
>> reactor.." how can I do this?  When I perform the release process in the
>> 'minimum' directory (my first target) when I get to the 'mvn
>> release:perform' stage I can see in the console output that maven
>> propagates to the parent and other subproject poms, and tries to release
>> the other subproject's snapshot.  Finally it fails with the error below.
>>  How can I release just the minimum and complete targets?
>>
>> Thanks!
>> ken
>>
>> ~~~
>> kgilmer@x220:~/dev/repos/felix-trunk/httplite/minimum$ mvn release:clean &&
>> mvn release:prepare
>> ...
>> kgilmer@x220:~/dev/repos/felix-trunk/httplite/minimum$ mvn release:perform
>> ...
>> [INFO] [INFO] Installing
>> /home/kgilmer/dev/repos/felix-trunk/httplite/minimum/target/checkout/pom.xml
>> to
>> /home/kgilmer/.m2/repository/org/apache/felix/org.apache.felix.httplite.reactor/1-SNAPSHOT/org.apache.felix.httplite.reactor-1-SNAPSHOT.pom
>> [INFO] [INFO]
>> [INFO] [INFO] --- maven-deploy-plugin:2.4:deploy (default-deploy) @
>> org.apache.felix.httplite.reactor ---
>> [INFO] [INFO]
>> 
>> [INFO] [INFO] Reactor Summary:
>> [INFO] [INFO]
>> [INFO] [INFO] Apache Felix Lightweight HTTP Service . SUCCESS
>> [20.910s]
>> [INFO] [INFO] Apache Felix Lightweight HTTP Service . SUCCESS
>> [19.977s]
>> [INFO] [INFO] Apache Felix Lightweight HTTP Service Reactor . FAILURE
>> [3.634s]
>> [INFO] [INFO]
>> 
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO]
>> 
>> [INFO] [INFO] Total time: 45.258s
>> [INFO] [INFO] Finished at: Thu Jan 19 22:04:58 JST 2012
>> [INFO] [INFO] Final Memory: 34M/283M
>> [INFO] [INFO]
>> 
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on
>> project org.apache.felix.httplite.reactor: Failed to deploy
>> artifacts/metadata: No connector available to access repository
>> apache.snapshots (scp://
>> people.apache.org/www/people.apache.org/repo/m2-snapshot-repository) of
>> type default using the available factories WagonRepositoryConnectorFactory
>> -> [Help 1]
>>
>>
>>
>> On Tue, Jan 17, 2012 at 6:23 AM, Karl Pauls  wrote:
>>
>>> Your reactor pom is on a very old version of the felix parent pom.
>>> That is why you get the errors you see. However, we don't release the
>>> reactors but typically the indiviual targets.
>>>
>>> I think the reason they are going wrong is that your scm tag is not
>>> correct. It points in both cases (targets) to the root of your project
>>> (where the reactor is) but it should point to the subfolder of the
>>> actual target in that root ie.,
>>>
>

[VOTE] Release Felix Lightweight HTTP Service version 0.1.4

[Ken Gilmer]

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.

Re: Release problem - need help

[Ken Gilmer]

Hi Karl,

  Thanks for your ideas, that certainly helps!  Yes the SCM stuff is
incorrect for my 'complete' target and that is probably why it's hanging
up.

 Trying to follow your advice regarding the parent pom version...I am not
sure what you mean.  When I look at other projects that have the same
pattern (eventadmin), they use the same version.  I tried updating to
version 2 as is in the http project but received a maven error that that
version does not exist.  It seems like most of the subprojects that have
reactor/module builds use 1.0.4.  What am I missing?

 Regarding "... try to release the individual targets and not the
reactor.." how can I do this?  When I perform the release process in the
'minimum' directory (my first target) when I get to the 'mvn
release:perform' stage I can see in the console output that maven
propagates to the parent and other subproject poms, and tries to release
the other subproject's snapshot.  Finally it fails with the error below.
 How can I release just the minimum and complete targets?

Thanks!
ken

~~~
kgilmer@x220:~/dev/repos/felix-trunk/httplite/minimum$ mvn release:clean &&
mvn release:prepare
...
kgilmer@x220:~/dev/repos/felix-trunk/httplite/minimum$ mvn release:perform
...
[INFO] [INFO] Installing
/home/kgilmer/dev/repos/felix-trunk/httplite/minimum/target/checkout/pom.xml
to
/home/kgilmer/.m2/repository/org/apache/felix/org.apache.felix.httplite.reactor/1-SNAPSHOT/org.apache.felix.httplite.reactor-1-SNAPSHOT.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.4:deploy (default-deploy) @
org.apache.felix.httplite.reactor ---
[INFO] [INFO]

[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] Apache Felix Lightweight HTTP Service . SUCCESS
[20.910s]
[INFO] [INFO] Apache Felix Lightweight HTTP Service . SUCCESS
[19.977s]
[INFO] [INFO] Apache Felix Lightweight HTTP Service Reactor . FAILURE
[3.634s]
[INFO] [INFO]

[INFO] [INFO] BUILD FAILURE
[INFO] [INFO]

[INFO] [INFO] Total time: 45.258s
[INFO] [INFO] Finished at: Thu Jan 19 22:04:58 JST 2012
[INFO] [INFO] Final Memory: 34M/283M
[INFO] [INFO]

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on
project org.apache.felix.httplite.reactor: Failed to deploy
artifacts/metadata: No connector available to access repository
apache.snapshots (scp://
people.apache.org/www/people.apache.org/repo/m2-snapshot-repository) of
type default using the available factories WagonRepositoryConnectorFactory
-> [Help 1]



On Tue, Jan 17, 2012 at 6:23 AM, Karl Pauls  wrote:

> Your reactor pom is on a very old version of the felix parent pom.
> That is why you get the errors you see. However, we don't release the
> reactors but typically the indiviual targets.
>
> I think the reason they are going wrong is that your scm tag is not
> correct. It points in both cases (targets) to the root of your project
> (where the reactor is) but it should point to the subfolder of the
> actual target in that root ie.,
>
> 
>scm:svn:
> http://svn.apache.org/repos/asf/felix/trunk/httplite
>scm:svn:
> https://svn.apache.org/repos/asf/felix/trunk/httplite
> 
>http://svn.apache.org/repos/asf/felix/trunk/httplite
> 
> 
>
> should become:
>
> 
>scm:svn:
> http://svn.apache.org/repos/asf/felix/trunk/httplite/complete
>scm:svn:
> https://svn.apache.org/repos/asf/felix/trunk/httplite/complete
> 
>
> http://svn.apache.org/repos/asf/felix/trunk/httplite/complete
> 
>
>
> Then try to release the individual targets and not the reactor. Does this
> help?
>
>
> regards,
>
> Karl
>
> On Wed, Jan 11, 2012 at 1:41 AM, Ken Gilmer  wrote:
> > Hi guys,
> >
> >  I'm still unable to follow the Felix release process without error.  I
> > did find one issue with my POMs not having the proper level of nesting
> when
> > referring to the parent POM.  I fixed this to match what's currently in
> the
> > eventadmin sub project.  I have tried doing the release process both on
> > each target and on the parent (reactor) pom.  Both produce errors.
> >
> > When trying to release per target (not reactor /httplite/minimum), I get
> to
> > the 'mvn deploy' stage.  After some uploading, I get to:
> > [INFO] [INFO] Retrieving previous build number from apache.snapshots
> > [INFO]
> > Maven never returns from this.  I ca

Release problem - need help

[Ken Gilmer]

Hi guys,

  I'm still unable to follow the Felix release process without error.  I
did find one issue with my POMs not having the proper level of nesting when
referring to the parent POM.  I fixed this to match what's currently in the
eventadmin sub project.  I have tried doing the release process both on
each target and on the parent (reactor) pom.  Both produce errors.

When trying to release per target (not reactor /httplite/minimum), I get to
the 'mvn deploy' stage.  After some uploading, I get to:
[INFO] [INFO] Retrieving previous build number from apache.snapshots
[INFO]
Maven never returns from this.  I can see in some of the build output that
maven is building and deploying my other target (httplite.complete) as
well, so I'm thinking that releasing at the target level may be incorrect.

When trying to release the whole subproject (/httplite) I get to the 'mvn
deploy' stage.  I am prompted for my password after "[INFO] Retrieving
previous build number from apache.snapshots".  After this I see:

Uploading: scp://
people.apache.org/www/people.apache.org/repo/m2-snapshot-repository/org/apache/felix/org.apache.felix.httplite.reactor/1-SNAPSHOT/org.apache.felix.httplite.reactor-1-20120111.002634-1.pom
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error deploying artifact: Exit code: 1 - mkdir: /www/
people.apache.org/repo/m2-snapshot-repository/org/apache/felix/org.apache.felix.httplite.reactor:
Permission denied

Logging into people.apache.org, in /www/
people.apache.org/repo/m2-snapshot-repository/org/apache/felix/ I can see
there is only one directory from 2009 so I suspect that maven is doing the
wrong thing and I should not be releasing from the root level.

At this point I'm not sure how to proceed with the release.  Any
suggestions or ideas on how to perform a release with multiple modules
(like http, eventadmin, deployadmin, etc.) would be greatly appreciated.

thx
ken

Re: Using Animal Sniffer (was: [jira] [Resolved] (FELIX-3287) Light HTTP Service Java 1.3)

[Ken Gilmer]

Hi Felix,

  That's a great idea, thanks!  I updated (revision 1229793) the root
httplite POM to include the Animal Sniffer plugin and it seems to be
working.  I cannot be certain, but maven downloads Animal Sniffer artifacts
and I get more build output.  I do not see a definitive "source valid"
message from the plugin but assume that since the build is successful that
the plugin didn't find any invalid source.

cheers
ken

On Wed, Jan 11, 2012 at 1:07 AM, Carsten Ziegeler wrote:

> +1
>
> Carsten
>
> 2012/1/9 Felix Meschberger :
> > Hi,
> >
> > We currently try to be strictly Java 1.3 by setting compiler source and
> target to 1.3 in the parent POM.
> >
> > How about adding the Codehaus Animal Sniffer plugin configured to ensure
> Java 1.3 API use ?
> >
> > (The WebConsole has the animal sniffer plugin configured for Java 1.4
> because we use regular expressions and some other Java 1.4 API)
> >
> > Regards
> > Felix
> >
> >
> > Am 08.01.2012 um 06:01 schrieb Ken Gilmer (Resolved) (JIRA):
> >
> >>
> >> [
> https://issues.apache.org/jira/browse/FELIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >>
> >> Ken Gilmer resolved FELIX-3287.
> >> ---
> >>
> >>Resolution: Fixed
> >>
> >> All known non-Java-1.3-compatible code has been updated.
> >>
> >>> Light HTTP Service Java 1.3
> >>> ---
> >>>
> >>>Key: FELIX-3287
> >>>URL: https://issues.apache.org/jira/browse/FELIX-3287
> >>>Project: Felix
> >>> Issue Type: Improvement
> >>> Components: Lightweight HTTP Service
> >>>   Reporter: Yann Diorcet
> >>>   Assignee: Ken Gilmer
> >>>Attachments: patch1.patch
> >>>
> >>>
> >>> Almost all the code is compatible with Java 1.3 except
> ServletPrintWriter (Charset stuff).
> >>> Is it possible to make the code compatible with CDC
> (minimum/foundation)?
> >>
> >> --
> >> 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
> >>
> >>
> >
>
>
>
> --
> Carsten Ziegeler
> cziege...@apache.org
>

Re: Error deploying artifact: Failed to transfer file

[Ken Gilmer]

Hi Arjun,

  FYI, I did not encounter a 401 error so far during my latest release of
httplite.

thx,
ken


On Wed, Jan 4, 2012 at 7:39 PM, Arjun Panday <
arjun.pan...@alcatel-lucent.com> wrote:

> Hi Ken,
>
> No, I've tried again just now and keep getting the 401 error.
> I don't know if others are still facing the same issue.
> If it works for you let me know!
>
> Thanks,
> Arjun
>
>
>
> On 01/04/2012 02:48 AM, Ken Gilmer wrote:
>
>> Sorry I can't provide any help in fixing this but am wondering...is it
>> working now?  I'm planning on a httplite release shortly.
>>
>> thx!
>> ken
>>
>> On Fri, Dec 30, 2011 at 4:51 PM, Arjun Panday
>> >
>>  wrote:
>>
>>> Thanks Carsten,
>>>
>>> I guess I should not proceed with the release without this step, so I'll
>>> just try again later.
>>>
>>> Regards,
>>> Arjun
>>>
>>>
>>> On 12/30/2011 07:36 AM, Carsten Ziegeler wrote:
>>>
>>>> Hi,
>>>>
>>>> I see the same error when the Apache Jenkins instance tries to deploy
>>>> snapshots of Sling, so I fear it's rather a problem with the snapshot
>>>> repository than with your settings.
>>>>
>>>> Regards
>>>> Carsten
>>>>
>>>> 2011/12/30 Arjun 
>>>> Panday
>>>> >:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> It's my turn to go through the ring of fire and attempt a release :)
>>>>>
>>>>> "mvn release:prepare -DdryRun=true" was successful and i'm now trying
>>>>> to
>>>>> publish a snapshot, but I get the infamous 401 HTTP error:
>>>>>
>>>>> [INFO] Error deploying artifact: Failed to transfer file:
>>>>>
>>>>> https://repository.apache.org/**content/repositories/**
>>>>> snapshots/org/apache/felix/**servicediagnostics/0.1.0-**
>>>>> SNAPSHOT/servicediagnostics-0.**1.0-20111229.225958-1.pom<https://repository.apache.org/content/repositories/snapshots/org/apache/felix/servicediagnostics/0.1.0-SNAPSHOT/servicediagnostics-0.1.0-20111229.225958-1.pom>
>>>>> .
>>>>> Return code is: 401
>>>>>
>>>>> I know it's supposed to be something with my settings.xml but I can't
>>>>> figure
>>>>> out what. Below is my settings.xml with the apache servers, username
>>>>> and
>>>>> password (removed!). Am I missing a server entry? Can someone help me
>>>>> figure
>>>>> out what I did wrong?
>>>>>
>>>>> I also checked my pom's parent:
>>>>> 
>>>>> org.apache.felix
>>>>> felix-parent
>>>>> 2.1
>>>>> ../../pom/pom.**xml
>>>>> 
>>>>>
>>>>> Thanks,
>>>>> Arjun
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> apache.snapshots.https
>>>>> apanday
>>>>> {encrypted password}
>>>>> 
>>>>> 
>>>>> 
>>>>> apache.website
>>>>> apanday
>>>>> 664
>>>>> 775
>>>>> 
>>>>> 
>>>>> 
>>>>> apache.releases.https
>>>>> apanday
>>>>> {encrypted password}
>>>>> 
>>>>> 
>>>>> 
>>>>> stagingSite
>>>>> apanday
>>>>> 664
>>>>> 775
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> release
>>>>> 
>>>>> {encrypted password}
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>
>

maven locks up during release:perform

[Ken Gilmer]

Hi everyone,

  I'm working on a release for httplite, and am able to get to the 'mvn
release:perform' stage but during this, maven locks up with:

...
[INFO] [INFO] [bundle:deploy {execution: default-deploy}]
[INFO] [INFO] Remote OBR update disabled (enable with -DremoteOBR)
[INFO] [INFO]

[INFO] [INFO] Building Apache Felix Lightweight HTTP Service Reactor
[INFO] [INFO]task-segment: [deploy]
[INFO] [INFO]

[INFO] [INFO] [site:attach-descriptor {execution:
default-attach-descriptor}]
[INFO] [INFO] [install:install {execution: default-install}]
[INFO] [INFO] Installing
/home/kgilmer/dev/repos/felix-trunk/httplite/minimum/target/checkout/pom.xml
to
/home/kgilmer/.m2/repository/org/apache/felix/org.apache.felix.httplite.reactor/1-SNAPSHOT/org.apache.felix.httplite.reactor-1-SNAPSHOT.pom
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] [INFO] Retrieving previous build number from apache.snapshots


>From this point mvn doesn't seem return.  New in this release is two
subprojects 'minimal' and 'complete'.  I infer from the release
documentation that the release procedure is to be applied to each
subproject.  It seems that the lockup is occuring in the parent "group"
pom, org.apache.felix.httplite.reactor.  Is this correct?  Is there
something special I have to do to the parent pom before releasing each
subproject?

thx,
ken

[jira] [Resolved] (FELIX-3287) Light HTTP Service Java 1.3

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3287.
---

Resolution: Fixed

All known non-Java-1.3-compatible code has been updated.

> Light HTTP Service Java 1.3
> ---
>
> Key: FELIX-3287
> URL: https://issues.apache.org/jira/browse/FELIX-3287
> Project: Felix
>  Issue Type: Improvement
>  Components: Lightweight HTTP Service
>Reporter: Yann Diorcet
>    Assignee: Ken Gilmer
> Attachments: patch1.patch
>
>
> Almost all the code is compatible with Java 1.3 except ServletPrintWriter 
> (Charset stuff).
> Is it possible to make the code compatible with CDC (minimum/foundation)?

--
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: Error deploying artifact: Failed to transfer file

[Ken Gilmer]

Sorry I can't provide any help in fixing this but am wondering...is it
working now?  I'm planning on a httplite release shortly.

thx!
ken

On Fri, Dec 30, 2011 at 4:51 PM, Arjun Panday
 wrote:
> Thanks Carsten,
>
> I guess I should not proceed with the release without this step, so I'll
> just try again later.
>
> Regards,
> Arjun
>
>
> On 12/30/2011 07:36 AM, Carsten Ziegeler wrote:
>>
>> Hi,
>>
>> I see the same error when the Apache Jenkins instance tries to deploy
>> snapshots of Sling, so I fear it's rather a problem with the snapshot
>> repository than with your settings.
>>
>> Regards
>> Carsten
>>
>> 2011/12/30 Arjun Panday:
>>>
>>> Hi everyone,
>>>
>>> It's my turn to go through the ring of fire and attempt a release :)
>>>
>>> "mvn release:prepare -DdryRun=true" was successful and i'm now trying to
>>> publish a snapshot, but I get the infamous 401 HTTP error:
>>>
>>> [INFO] Error deploying artifact: Failed to transfer file:
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/felix/servicediagnostics/0.1.0-SNAPSHOT/servicediagnostics-0.1.0-20111229.225958-1.pom.
>>> Return code is: 401
>>>
>>> I know it's supposed to be something with my settings.xml but I can't
>>> figure
>>> out what. Below is my settings.xml with the apache servers, username and
>>> password (removed!). Am I missing a server entry? Can someone help me
>>> figure
>>> out what I did wrong?
>>>
>>> I also checked my pom's parent:
>>> 
>>> org.apache.felix
>>> felix-parent
>>> 2.1  
>>> ../../pom/pom.xml
>>> 
>>>
>>> Thanks,
>>> Arjun
>>>
>>> 
>>> 
>>> 
>>> 
>>> apache.snapshots.https
>>> apanday
>>> {encrypted password}
>>> 
>>> 
>>> 
>>> apache.website
>>> apanday
>>> 664
>>> 775
>>> 
>>> 
>>> 
>>> apache.releases.https
>>> apanday
>>> {encrypted password}
>>> 
>>> 
>>> 
>>> stagingSite  
>>> apanday
>>> 664
>>> 775
>>> 
>>> 
>>> 
>>> 
>>> release
>>> 
>>> {encrypted password}
>>> 
>>> 
>>> 
>>> 
>>>
>>
>>
>

[jira] [Resolved] (FELIX-3291) Add support for cookies

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3291.
---

Resolution: Fixed

Fixed in revision 1225141.

> Add support for cookies
> ---
>
> Key: FELIX-3291
> URL: https://issues.apache.org/jira/browse/FELIX-3291
> Project: Felix
>  Issue Type: Task
>  Components: Lightweight HTTP Service
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>
> Currently the cookie support in the servlet container throws 
> UnimplementedAPIException.  Implement cookie support.

--
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-3291) Add support for cookies

[Ken Gilmer (Created) (JIRA)]

Add support for cookies
---

 Key: FELIX-3291
 URL: https://issues.apache.org/jira/browse/FELIX-3291
 Project: Felix
  Issue Type: Task
  Components: Lightweight HTTP Service
Reporter: Ken Gilmer
Assignee: Ken Gilmer


Currently the cookie support in the servlet container throws 
UnimplementedAPIException.  Implement cookie support.

--
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] [Commented] (FELIX-3287) Light HTTP Service Java 1.3

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174134#comment-13174134
 ] 

Ken Gilmer commented on FELIX-3287:
---

Yann, thanks for your patch.  I've applied, tested, and committed it to SVN.  
Good catch on the versioning errors and using StringTokenizer makes the split() 
function much more concise!

> Light HTTP Service Java 1.3
> ---
>
> Key: FELIX-3287
> URL: https://issues.apache.org/jira/browse/FELIX-3287
> Project: Felix
>  Issue Type: Improvement
>  Components: Lightweight HTTP Service
>Reporter: Yann Diorcet
>Assignee: Ken Gilmer
> Attachments: patch1.patch
>
>
> Almost all the code is compatible with Java 1.3 except ServletPrintWriter 
> (Charset stuff).
> Is it possible to make the code compatible with CDC (minimum/foundation)?

--
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] [Commented] (FELIX-3287) Light HTTP Service Java 1.3

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173392#comment-13173392
 ] 

Ken Gilmer commented on FELIX-3287:
---

Hi Yann,  in trunk, ServletPrintWriter.java has already been removed.  The only 
other incompatibility I'm aware of is String.split() which I've also just now 
removed and replaced with an internal implementation.  I have compiled against 
the CDC implementation PhoneME Advanced and do not get any errors.  You should 
be able to build from trunk and I also plan on a new release (0.2.0) shortly.  
It would be nice to know if trunk works for you in your CDC environment, please 
let me know if you get a chance to test.

> Light HTTP Service Java 1.3
> ---
>
> Key: FELIX-3287
> URL: https://issues.apache.org/jira/browse/FELIX-3287
> Project: Felix
>  Issue Type: Improvement
>  Components: Lightweight HTTP Service
>Reporter: Yann Diorcet
>Assignee: Ken Gilmer
>
> Almost all the code is compatible with Java 1.3 except ServletPrintWriter 
> (Charset stuff).
> Is it possible to make the code compatible with CDC (minimum/foundation)?

--
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-3287) Light HTTP Service Java 1.3

[Ken Gilmer (Assigned) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer reassigned FELIX-3287:
-

Assignee: Ken Gilmer

> Light HTTP Service Java 1.3
> ---
>
> Key: FELIX-3287
> URL: https://issues.apache.org/jira/browse/FELIX-3287
> Project: Felix
>  Issue Type: Improvement
>  Components: Lightweight HTTP Service
>Reporter: Yann Diorcet
>    Assignee: Ken Gilmer
>
> Almost all the code is compatible with Java 1.3 except ServletPrintWriter 
> (Charset stuff).
> Is it possible to make the code compatible with CDC (minimum/foundation)?

--
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] [Resolved] (FELIX-3276) Provide minimal and complete targets.

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3276.
---

Resolution: Fixed

Fixed in revision 1214805.

> Provide minimal and complete targets.  
> ---
>
> Key: FELIX-3276
> URL: https://issues.apache.org/jira/browse/FELIX-3276
> Project: Felix
>  Issue Type: Task
>  Components: Lightweight HTTP Service
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>
> Provide separate targets for minimal bundle (including only httplite code) 
> and complete (including all dependencies).

--
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-3276) Provide minimal and complete targets.

[Ken Gilmer (Created) (JIRA)]

Provide minimal and complete targets.  
---

 Key: FELIX-3276
 URL: https://issues.apache.org/jira/browse/FELIX-3276
 Project: Felix
  Issue Type: Task
  Components: Lightweight HTTP Service
Reporter: Ken Gilmer
Assignee: Ken Gilmer


Provide separate targets for minimal bundle (including only httplite code) and 
complete (including all dependencies).

--
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] [Resolved] (FELIX-3275) HTTP Service allows registration of servlets and resources with invalid resources.

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3275.
---

Resolution: Fixed
  Assignee: Ken Gilmer

Fixed in revision 1214765.

> HTTP Service allows registration of servlets and resources with invalid 
> resources.
> --
>
> Key: FELIX-3275
> URL: https://issues.apache.org/jira/browse/FELIX-3275
> Project: Felix
>  Issue Type: Bug
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>Priority: Minor
>
> OSGi R4 Compendium 102.4 
> Alias must begin with '/' character.  Captured in test 
> /org.apache.felix.httplite/src/test/java/org/apache/felix/httplite/osgi/test/cases/TestOSGiService.java
>  testCannotRegisterInvalidAlias()

--
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-3275) HTTP Service allows registration of servlets and resources with invalid resources.

[Ken Gilmer (Created) (JIRA)]

HTTP Service allows registration of servlets and resources with invalid 
resources.
--

 Key: FELIX-3275
 URL: https://issues.apache.org/jira/browse/FELIX-3275
 Project: Felix
  Issue Type: Bug
Reporter: Ken Gilmer
Priority: Minor


OSGi R4 Compendium 102.4 

Alias must begin with '/' character.  Captured in test 
/org.apache.felix.httplite/src/test/java/org/apache/felix/httplite/osgi/test/cases/TestOSGiService.java
 testCannotRegisterInvalidAlias()

--
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] [Resolved] (FELIX-3274) When a servlet impl writes to PrintWriter, trailing null byte appended to stream.

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3274.
---

Resolution: Fixed

Fixed in committed revision 1214756.

> When a servlet impl writes to PrintWriter, trailing null byte appended to 
> stream.
> -
>
> Key: FELIX-3274
> URL: https://issues.apache.org/jira/browse/FELIX-3274
> Project: Felix
>  Issue Type: Bug
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>
> Issue captured in test 
> /org.apache.felix.httplite/src/test/java/org/apache/felix/httplite/osgi/test/cases/TestServletContainer.java
>  test testGETResponseStringContent().

--
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-3274) When a servlet impl writes to PrintWriter, trailing null byte appended to stream.

[Ken Gilmer (Created) (JIRA)]

When a servlet impl writes to PrintWriter, trailing null byte appended to 
stream.
-

 Key: FELIX-3274
 URL: https://issues.apache.org/jira/browse/FELIX-3274
 Project: Felix
  Issue Type: Bug
Reporter: Ken Gilmer
Assignee: Ken Gilmer


Issue captured in test 
/org.apache.felix.httplite/src/test/java/org/apache/felix/httplite/osgi/test/cases/TestServletContainer.java
 test testGETResponseStringContent().



--
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] [Resolved] (FELIX-3253) Fails to resolve urls with multiple successive path seperators

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3253.
---

Resolution: Fixed

Fixed in commit 1214740.

> Fails to resolve urls with multiple successive path seperators
> --
>
> Key: FELIX-3253
> URL: https://issues.apache.org/jira/browse/FELIX-3253
> Project: Felix
>  Issue Type: Bug
>  Components: Lightweight HTTP Service
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>Priority: Minor
>
>  it doesn't like requests with double-slashes while testing it
> with the Felix webconsole:
>java.io.IOException: Unable to find resource: /res//imgs/logo.png
> at
> org.apache.felix.httplite.server.ResourceHandler.handle(ResourceHandler.java:89)
> at org.apache.felix.httplite.server.Connection.process(Connection.java:240)
> at
> org.apache.felix.httplite.server.ThreadPool.processConnections(ThreadPool.java:298)
> at
> org.apache.felix.httplite.server.ThreadPool.access$000(ThreadPool.java:35)
> at org.apache.felix.httplite.server.ThreadPool$1.run(ThreadPool.java:193)
> at java.lang.Thread.run(Thread.java:680)

--
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: [VOTE] Release Felix iPOJO Manipulator version 1.8.2

[Ken Gilmer]

+1 (non-binding)

thx
ken

On Wed, Dec 14, 2011 at 12:14 AM, Felix Meschberger  wrote:
> +1
>
> Regards
> Felix
>
> Am 06.12.2011 um 18:52 schrieb Clement Escoffier:
>
>> Hi,
>>
>> It's time to cut a release of the iPOJO Manipulator project (1.8.2).
>>
>> The release is a bit different this time, has I've released a couple of 
>> artifacts in once (we have aggregated all manipulator front-end in one Maven 
>> reactor), so this releases contains:
>> * org.apache.felix.ipojo.metadata 1.6.0
>> * org.apache.felix.ipojo.manipulator 1.8.2
>> * maven-ipojo-plugin 1.8.2
>> * ipojo-ant-task 1.8.2
>> * bnd-ipojo-plugin 1.8.2 (new module)
>> * manipulator-project (1.8.2)
>>
>> (the changelog is included below)
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachefelix-294/
>>
>> 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 294 /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 (at least).
>>
>> Regards,
>>
>> Clement
>>
>> Changelog:
>> ** Bug
>>    * [FELIX-2825] - The maven-ipojo-plugin does not replace component 
>> classes in WAR files
>>    * [FELIX-2829] - The maven-ipojo-plugin archetype descriptor is not 
>> conform
>>    * [FELIX-2833] - The maven-ipojo-plugin  does not support manipulating 
>> artifact with a classifier
>>    * [FELIX-3012] - "Duplicate name&signature" problem
>>    * [FELIX-3098] - iPOJO new manipulator crashes when using a custom 
>> reporter
>>    * [FELIX-3145] - VerifyError on Java 7
>>    * [FELIX-3249] - iPOJO Bnd Plugin do not write all the metadatas in the 
>> manifest
>>
>> ** Improvement
>>    * [FELIX-3017] - The manipulator should return the original class if it's 
>> already manipulated
>>    * [FELIX-3078] - Introduce resource abstraction in the iPOJO manipulator
>>    * [FELIX-3079] - Adapt the Ant task and the maven plugin to use the new 
>> manipulator capabilities
>>    * [FELIX-3080] - Implement a BND plugin for iPOJO
>>    * [FELIX-3131] - Elements and attributes should conserve the insertion 
>> order
>>    * [FELIX-3204] - @Temporal should handle instantiation-time properties
>>    * [FELIX-3244] - Manipulator : DefaultManifestBuilder should be more 
>> extensible
>

Re: Suggestions on OSGi-context testing

[Ken Gilmer]

Thanks Karl,

That fixed it.  Now I'm off and running writing unit tests!

Thanks
Ken

On Dec 12, 2011, at 5:00 AM, Karl Pauls  wrote:

> Yeah, I see - you have the osgi.core 4.1 as a dependency. Try to
> remove it (pojosr probably has all classes you need embeded) or update
> to 4.2.
> 
> regards,
> 
> Karl
> 
> On Sun, Dec 11, 2011 at 8:49 PM, Karl Pauls  wrote:
>> Hi Ken,
>> 
>> that used to be a problem with older versions of the framework util
>> shipped with osgi. Is it possible that you somehow have an osgi.core
>> jar < 4.2 on the classpath in front of pojosr? If so, try to
>> remove/exclude it or reorder your dependencies. A possible test is as
>> well to use felix instead of pojosr - it should have the same issue
>> (assuming it ends-up in the same classpath location as pojosr - you
>> should be able to see the classpath with mvn -X ).
>> 
>> regards,
>> 
>> Karl
>> 
>> On Sat, Dec 10, 2011 at 7:46 AM, Ken Gilmer  wrote:
>>> Hi Karl,
>>> 
>>>  Thanks for the additional guidance.  So I spent some time setting up
>>> a vanilla maven osgi bundle project.  I was able to add pojosr and
>>> create a simple test case that started my bundle, retrieved the
>>> service via the pojosr service registry, and executed the service.
>>> 
>>>  I then moved to integrating pojosr into httplite so I could begin
>>> writing tests.  As my bundle starts in my test case, I ran into a
>>> problem where "org.osgi.vendor.framework" is an undefined system
>>> property.  I did some digging and determined that the FrameworkUtil
>>> class tries to be dynamically loaded based on the root classname as
>>> defined by "org.osgi.vendor.framework".  Setting to this to
>>> "org.osgi.framework", (which is the root package name for the class
>>> contained in pojosr) resulted in a stack overflow.  The FrameworkUtil
>>> in the Felix framework is available but has all sorts of private
>>> dependencies and is not easy to pull out into my own package. It
>>> appears that the pojosr implementation is just calling itself, or
>>> expecting another class to be available?  Any suggestions?
>>> 
>>> thx
>>> ken
>>> 
>>> On Thu, Dec 8, 2011 at 6:58 PM, Karl Pauls  wrote:
>>>> On Thu, Dec 8, 2011 at 8:59 AM, Ken Gilmer  wrote:
>>>>> Thanks Andreas, Karl, and Arjun!
>>>>> 
>>>>> Andreas,
>>>>> 
>>>>>  I spent some time learning the basics of Pax Exam.  One of my
>>>>> particular requirements is JUnit3/Java1.4.  I see it mentioned in a
>>>>> JIRA issue that support has been added but cannot find a suitable
>>>>> example of how this works.  Ideally for me, the Pax Exam documentation
>>>>> would contain the initial description of what Pax Exam is, and then
>>>>> want to see only a maven-based project with:
>>>>> 
>>>>> a) a service definition (public api)
>>>>> b) some implementation (private)
>>>>> c) a test that gets the service and executes a method via junit
>>>>> d) the minimal POM that builds the regular bundle and also runs the junit 
>>>>> test
>>>>> 
>>>>>  The existing example code is helpful but doesn't really answer my
>>>>> immediate needs of getting started quickly, (as one who is not too
>>>>> familiar with Maven yet).
>>>>> 
>>>>> Karl,
>>>>> 
>>>>>  Regarding PojoSR, I probably do not need a full OSGi framework for
>>>>> my tests, so it could be suitable for me.  However I need a bit more
>>>>> guidance on how to set up running a test (I can visualize how to
>>>>> compose a test) in Maven.  Can you point me to an existing pom.xml
>>>>> that uses PojoSR to execute JUnit tests against a service?
>>>> 
>>>> I guess there are (at least could be) several approaches which also
>>>> depend on your needs. One public example I know of is the work
>>>> Guillaume Nodet (and maybe others) did for fuse:
>>>> 
>>>> https://github.com/fusesource/fuse/tree/master/fabric/fabric-itests/fabric-pojosr
>>>> 
>>>> Does that help?
>>>> 
>>>>>  Regarding bnd, it seems to utilize Ant makefiles.  I'd like to avoid
>>>>> that if possible.  Nothing against Ant, in fact I have my own
>>>>> Ant-based osgi test f

[jira] [Resolved] (FELIX-3266) PrintWriter in HttpServletResponse does not send string content to client

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3266.
---

Resolution: Fixed
  Assignee: Ken Gilmer

> PrintWriter in HttpServletResponse does not send string content to client
> -
>
> Key: FELIX-3266
> URL: https://issues.apache.org/jira/browse/FELIX-3266
> Project: Felix
>  Issue Type: Bug
>  Components: Lightweight HTTP Service
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>
> The following snippet will fail to send "Hello" to HTTP client:
>protected void doGet(HttpServletRequest req, HttpServletResponse resp) 
> throws ServletException, IOException {
>   resp.getWriter().print("Hello");
>   }
> Only resp.getOutputStream() will work in version 0.1.2.

--
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-3266) PrintWriter in HttpServletResponse does not send string content to client

[Ken Gilmer (Created) (JIRA)]

PrintWriter in HttpServletResponse does not send string content to client
-

 Key: FELIX-3266
 URL: https://issues.apache.org/jira/browse/FELIX-3266
 Project: Felix
  Issue Type: Bug
  Components: Lightweight HTTP Service
Reporter: Ken Gilmer



The following snippet will fail to send "Hello" to HTTP client:

   protected void doGet(HttpServletRequest req, HttpServletResponse resp) 
throws ServletException, IOException {

resp.getWriter().print("Hello");
}

Only resp.getOutputStream() will work in version 0.1.2.

--
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: Suggestions on OSGi-context testing

[Ken Gilmer]

Hi Karl,

  Thanks for the additional guidance.  So I spent some time setting up
a vanilla maven osgi bundle project.  I was able to add pojosr and
create a simple test case that started my bundle, retrieved the
service via the pojosr service registry, and executed the service.

  I then moved to integrating pojosr into httplite so I could begin
writing tests.  As my bundle starts in my test case, I ran into a
problem where "org.osgi.vendor.framework" is an undefined system
property.  I did some digging and determined that the FrameworkUtil
class tries to be dynamically loaded based on the root classname as
defined by "org.osgi.vendor.framework".  Setting to this to
"org.osgi.framework", (which is the root package name for the class
contained in pojosr) resulted in a stack overflow.  The FrameworkUtil
in the Felix framework is available but has all sorts of private
dependencies and is not easy to pull out into my own package. It
appears that the pojosr implementation is just calling itself, or
expecting another class to be available?  Any suggestions?

thx
ken

On Thu, Dec 8, 2011 at 6:58 PM, Karl Pauls  wrote:
> On Thu, Dec 8, 2011 at 8:59 AM, Ken Gilmer  wrote:
>> Thanks Andreas, Karl, and Arjun!
>>
>> Andreas,
>>
>>  I spent some time learning the basics of Pax Exam.  One of my
>> particular requirements is JUnit3/Java1.4.  I see it mentioned in a
>> JIRA issue that support has been added but cannot find a suitable
>> example of how this works.  Ideally for me, the Pax Exam documentation
>> would contain the initial description of what Pax Exam is, and then
>> want to see only a maven-based project with:
>>
>> a) a service definition (public api)
>> b) some implementation (private)
>> c) a test that gets the service and executes a method via junit
>> d) the minimal POM that builds the regular bundle and also runs the junit 
>> test
>>
>>  The existing example code is helpful but doesn't really answer my
>> immediate needs of getting started quickly, (as one who is not too
>> familiar with Maven yet).
>>
>> Karl,
>>
>>  Regarding PojoSR, I probably do not need a full OSGi framework for
>> my tests, so it could be suitable for me.  However I need a bit more
>> guidance on how to set up running a test (I can visualize how to
>> compose a test) in Maven.  Can you point me to an existing pom.xml
>> that uses PojoSR to execute JUnit tests against a service?
>
> I guess there are (at least could be) several approaches which also
> depend on your needs. One public example I know of is the work
> Guillaume Nodet (and maybe others) did for fuse:
>
> https://github.com/fusesource/fuse/tree/master/fabric/fabric-itests/fabric-pojosr
>
> Does that help?
>
>>  Regarding bnd, it seems to utilize Ant makefiles.  I'd like to avoid
>> that if possible.  Nothing against Ant, in fact I have my own
>> Ant-based osgi test framework, but I'd like to keep the test stuff as
>> simple as I can and keep things in Maven.
>
> It might not be impossible to hook it up to maven (if nothing else, by
> executing the and file from there). I think it is mostly based on bnd
> and the ant files are just very lightweight wrappers around it but I
> can't say whether it would be easy or not. You can see an example in
> ricks sandbox (the example requires you to use ant to execute the
> tests but it uses maven to get the thing assembled iirc) :
>
> http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>
> regards,
>
> Karl
>
>> Arjun,
>>
>>  For me, the most difficult part is the Maven integration.  I want
>> the tests to run and fail as part of the build.  In any case it's good
>> to know you've got that, I'll check it out.
>>
>> thx,
>> ken
>>
>>
>>
>> On Tue, Dec 6, 2011 at 6:56 PM, Karl Pauls  wrote:
>>> To use PojoSR for testing with your dependencies from maven I guess
>>> you could just use the exec-maven-plugin, hook it up to the test phase
>>> and have it start with all dependencies from the test scope.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>> On Tue, Dec 6, 2011 at 9:25 AM, Karl Pauls  wrote:
>>>> If you are looking for real integration testing, Pax Exam is probably
>>>> what you want.
>>>>
>>>> However, if you want to test you services without a full OSGi
>>>> framework you might want to have  a look at PojoSR:
>>>>
>>>> http://pojosr.googlecode.com
>>>>
>>>> I know that some people use it for JUnit testing their services.
>>>> Fina

Re: JIRA permissions

[Ken Gilmer]

> If you go to this page:
>
>    https://issues.apache.org/jira/browse/FELIX
>
> Do you see a "versions" tab on the side?

Yes

> If so, click it and in there do you
> see a "manage versions" link near the top?

No

>
> You are logged in right? Just checking... :-)

Yes :-)  (Good to check, I make these kinds of mistakes all the time :) )

One thing I noticed is in my profile my account is "kgil...@gmail.com"
which is what I setup before I was a committer.  Is there possibly
another kgilmer account (@apache.org?) that I'm not seeing?

thx
ken

>
> -> richard

Re: Suggestions on OSGi-context testing

[Ken Gilmer]

Thanks Andreas, Karl, and Arjun!

Andreas,

  I spent some time learning the basics of Pax Exam.  One of my
particular requirements is JUnit3/Java1.4.  I see it mentioned in a
JIRA issue that support has been added but cannot find a suitable
example of how this works.  Ideally for me, the Pax Exam documentation
would contain the initial description of what Pax Exam is, and then
want to see only a maven-based project with:

a) a service definition (public api)
b) some implementation (private)
c) a test that gets the service and executes a method via junit
d) the minimal POM that builds the regular bundle and also runs the junit test

  The existing example code is helpful but doesn't really answer my
immediate needs of getting started quickly, (as one who is not too
familiar with Maven yet).

Karl,

  Regarding PojoSR, I probably do not need a full OSGi framework for
my tests, so it could be suitable for me.  However I need a bit more
guidance on how to set up running a test (I can visualize how to
compose a test) in Maven.  Can you point me to an existing pom.xml
that uses PojoSR to execute JUnit tests against a service?

  Regarding bnd, it seems to utilize Ant makefiles.  I'd like to avoid
that if possible.  Nothing against Ant, in fact I have my own
Ant-based osgi test framework, but I'd like to keep the test stuff as
simple as I can and keep things in Maven.

Arjun,

  For me, the most difficult part is the Maven integration.  I want
the tests to run and fail as part of the build.  In any case it's good
to know you've got that, I'll check it out.

thx,
ken



On Tue, Dec 6, 2011 at 6:56 PM, Karl Pauls  wrote:
> To use PojoSR for testing with your dependencies from maven I guess
> you could just use the exec-maven-plugin, hook it up to the test phase
> and have it start with all dependencies from the test scope.
>
> regards,
>
> Karl
>
> On Tue, Dec 6, 2011 at 9:25 AM, Karl Pauls  wrote:
>> If you are looking for real integration testing, Pax Exam is probably
>> what you want.
>>
>> However, if you want to test you services without a full OSGi
>> framework you might want to have  a look at PojoSR:
>>
>> http://pojosr.googlecode.com
>>
>> I know that some people use it for JUnit testing their services.
>> Finally, bnd itself can be used for testing (we use that in the
>> framework) and it is used by the OSGi ct.
>>
>> regards,
>>
>> Karl
>>
>> On Tue, Dec 6, 2011 at 9:17 AM, Andreas Pieber  wrote:
>>> Hey Ken,
>>>
>>> You might want to give Pax Exam a look for integration tests with OSGi:
>>> http://team.ops4j.org/wiki/display/paxexam/Pax+Exam
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> On Tue, Dec 6, 2011 at 09:11, Ken Gilmer  wrote:
>>>
>>>> Hi,
>>>>
>>>>  I'd like to begin adding some test cases to the httplite bundle.  Ideally
>>>> I'd like my tests executed within an OSGi context so I don't have to mock
>>>> anything, and the test environment is as close as possible to a real
>>>> instance.  Also I'd like my tests to execute as part of the maven build
>>>> process.  Can anyone suggest an existing and somewhat current Felix project
>>>> that does this or provide other suggestions?
>>>>
>>>> Thanks!
>>>> ken
>>>>
>>
>>
>>
>> --
>> 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

Re: JIRA permissions

[Ken Gilmer]

On Thu, Dec 8, 2011 at 4:19 PM, Richard S. Hall  wrote:
> On 12/8/11 2:09, Ken Gilmer wrote:
>>
>> Richard,
>>
>>   I was just following the link on the release page, which goes to:
>>
>>
>> https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310100
>
>
> Under "versions" on the above page, I see a "Show all" link under the
> handful of versions it shows me. That takes me to the management page where
> I can enter a new version, do you see that too?

No, when the page loads all I get is:

Error
You cannot edit the configuration of this project.
Click here to see a list of all the projects

Clicking on "here" loads another page which says:

You do not have the permissions to administer any projects, or there
are none created.

>
>
>>
>>   In any case, I do not see a manage link on the Versions page, and
>> 'manage' does not appear on the page.  I also do not see any options
>> to edit versions when I go to the httplite component page.  I'm
>> guessing it's a permissions issue...?
>
>
> Could be, but you are a member of the felix-developers group, which seems
> like it should be enough...but as I stated, JIRA has been messed up for me
> for a while...

Hmmmph.

>
>
> -> richard
>
>>
>> thx,
>> ken
>>
>> On Thu, Dec 8, 2011 at 3:55 PM, Richard S. Hall
>>  wrote:
>>>
>>> On 12/8/11 1:38, Ken Gilmer wrote:
>>>>
>>>> Hi Richard,
>>>>
>>>>   Well I assume (not very familiar with JIRA) that I'm trying to
>>>> create a release version.  Currently there are none defined.  From
>>>> this step:
>>>>
>>>> "Update JIRA
>>>>
>>>> Go to Admin section on the FELIX JIRA and mark the Y.Z version as
>>>> released - create version Y.Z+1, if that hasn't already been done."
>>>
>>>
>>> Which "admin" section are you going to? For versions, you need to go into
>>> the "versions" tab and then select "manage"...there you'll create a
>>> version
>>> like "http.lite-0.x.y" or whatever...
>>>
>>> Keep in mind that when you create versions, you need to manually sort
>>> them
>>> in the list of versions. This is a pain in the new JIRA versioning UI
>>> since
>>> you need to create a new version at the top and then drag it all the way
>>> down into place...we have lots of versioned subprojects.
>>>
>>> This won't impact you on this first version, but in the next it will. If
>>> you
>>> don't sort them, then they show up out of order in various places in the
>>> JIRA UI.
>>>
>>> Lately, JIRA hasn't been allowing me to create versions at all (it
>>> complains
>>> something about a project with key undefined), I ask Karl to do it for
>>> me,
>>> so hopefully you'll have better luck...
>>>
>>> ->  richard
>>>
>>>> thx,
>>>> ken
>>>>
>>>> On Thu, Dec 8, 2011 at 3:35 PM, Richard S. Hall
>>>>  wrote:
>>>>>
>>>>> What exactly are you trying to do?
>>>>>
>>>>>
>>>>> On 12/8/11 1:23, Ken Gilmer wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>   Following the release guide, I am trying to update JIRA with the
>>>>>> release
>>>>>> version of httplite, but get this error when loading the page: You
>>>>>> cannot
>>>>>> edit the configuration of this project.  Can someone help me please?
>>>>>>
>>>>>> thanks!
>>>>>> ken
>>>>>>
>

Re: JIRA permissions

[Ken Gilmer]

Richard,

  I was just following the link on the release page, which goes to:

https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310100

  In any case, I do not see a manage link on the Versions page, and
'manage' does not appear on the page.  I also do not see any options
to edit versions when I go to the httplite component page.  I'm
guessing it's a permissions issue...?

thx,
ken

On Thu, Dec 8, 2011 at 3:55 PM, Richard S. Hall  wrote:
> On 12/8/11 1:38, Ken Gilmer wrote:
>>
>> Hi Richard,
>>
>>   Well I assume (not very familiar with JIRA) that I'm trying to
>> create a release version.  Currently there are none defined.  From
>> this step:
>>
>> "Update JIRA
>>
>> Go to Admin section on the FELIX JIRA and mark the Y.Z version as
>> released - create version Y.Z+1, if that hasn't already been done."
>
>
> Which "admin" section are you going to? For versions, you need to go into
> the "versions" tab and then select "manage"...there you'll create a version
> like "http.lite-0.x.y" or whatever...
>
> Keep in mind that when you create versions, you need to manually sort them
> in the list of versions. This is a pain in the new JIRA versioning UI since
> you need to create a new version at the top and then drag it all the way
> down into place...we have lots of versioned subprojects.
>
> This won't impact you on this first version, but in the next it will. If you
> don't sort them, then they show up out of order in various places in the
> JIRA UI.
>
> Lately, JIRA hasn't been allowing me to create versions at all (it complains
> something about a project with key undefined), I ask Karl to do it for me,
> so hopefully you'll have better luck...
>
> -> richard
>
>>
>> thx,
>> ken
>>
>> On Thu, Dec 8, 2011 at 3:35 PM, Richard S. Hall
>>  wrote:
>>>
>>> What exactly are you trying to do?
>>>
>>>
>>> On 12/8/11 1:23, Ken Gilmer wrote:
>>>>
>>>> Hi,
>>>>
>>>>   Following the release guide, I am trying to update JIRA with the
>>>> release
>>>> version of httplite, but get this error when loading the page: You
>>>> cannot
>>>> edit the configuration of this project.  Can someone help me please?
>>>>
>>>> thanks!
>>>> ken
>>>>
>

Re: JIRA permissions

[Ken Gilmer]

Hi Richard,

  Well I assume (not very familiar with JIRA) that I'm trying to
create a release version.  Currently there are none defined.  From
this step:

"Update JIRA

Go to Admin section on the FELIX JIRA and mark the Y.Z version as
released - create version Y.Z+1, if that hasn't already been done."

thx,
ken

On Thu, Dec 8, 2011 at 3:35 PM, Richard S. Hall  wrote:
> What exactly are you trying to do?
>
>
> On 12/8/11 1:23, Ken Gilmer wrote:
>>
>> Hi,
>>
>>   Following the release guide, I am trying to update JIRA with the release
>> version of httplite, but get this error when loading the page: You cannot
>> edit the configuration of this project.  Can someone help me please?
>>
>> thanks!
>> ken
>>
>

JIRA permissions

[Ken Gilmer]

Hi,

  Following the release guide, I am trying to update JIRA with the release
version of httplite, but get this error when loading the page: You cannot
edit the configuration of this project.  Can someone help me please?

thanks!
ken

Suggestions on OSGi-context testing

[Ken Gilmer]

Hi,

  I'd like to begin adding some test cases to the httplite bundle.  Ideally
I'd like my tests executed within an OSGi context so I don't have to mock
anything, and the test environment is as close as possible to a real
instance.  Also I'd like my tests to execute as part of the maven build
process.  Can anyone suggest an existing and somewhat current Felix project
that does this or provide other suggestions?

Thanks!
ken

[jira] [Resolved] (FELIX-3256) Remove Ant build file from Lightweight HTTP Service bundle.

[Ken Gilmer (Resolved) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer resolved FELIX-3256.
---

Resolution: Fixed

Removed file.

> Remove Ant build file from Lightweight HTTP Service bundle.
> ---
>
> Key: FELIX-3256
> URL: https://issues.apache.org/jira/browse/FELIX-3256
> Project: Felix
>  Issue Type: Task
>  Components: Lightweight HTTP Service
>    Reporter: Ken Gilmer
>    Assignee: Ken Gilmer
>Priority: Minor
>
> The ant build file is no longer needed now that the maven build is working.  
> Should be removed from repo.

--
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

[RESULT] [VOTE] Release Felix Lightweight HTTP Service version 0.1.2

[Ken Gilmer]

Hi,

The vote has passed with the following result :

  +1 (binding): Felix Meschberger, Carsten Ziegeler, Marcel Offermans,
Karl Pauls, Rob Walker, Richard S. Hall, Stuart McCulloch
  +1 (non binding): Jean-Baptiste Onofré

I will copy this release to the Felix dist directory and
promote the artifacts to the central Maven repository.

Thanks for everyone's help in getting me back on the happy path for my
first release!  I fell off pretty quickly in the beginning.

Best,
ken

Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.2

[Ken Gilmer]

Hi Marcel and Felix,

  The ant file was for my use in testing before I had the maven build
working and will be removed in the next release.  I created a JIRA for
this: https://issues.apache.org/jira/browse/FELIX-3256.

thx,
ken

On Mon, Dec 5, 2011 at 5:11 PM, Felix Meschberger wrote:

> Hi,
>
> Am 05.12.2011 um 08:46 schrieb Marcel Offermans:
>
> > +1
> >
> > A few small notes (based on the -source-release.zip):
> >
> > - The build.xml script does not seem to work for me, relies on being run
> on Linux. You should probably make a note of such requirements in the
> README file (or, somehow make it work on other platforms).
> > - The build.xml mentions version 0.1.1 (should be 0.1.2).
>
> Do we really need a build.xml ? This makes maintenance extremely hard and
> I doubt its use in our context ...
>
> Regards
> Felix
>
>

[jira] [Created] (FELIX-3256) Remove Ant build file from Lightweight HTTP Service bundle.

[Ken Gilmer (Created) (JIRA)]

Remove Ant build file from Lightweight HTTP Service bundle.
---

 Key: FELIX-3256
 URL: https://issues.apache.org/jira/browse/FELIX-3256
 Project: Felix
  Issue Type: Task
  Components: Lightweight HTTP Service
Reporter: Ken Gilmer
Assignee: Ken Gilmer
Priority: Minor


The ant build file is no longer needed now that the maven build is working.  
Should be removed from repo.

--
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-3253) Fails to resolve urls with multiple successive path seperators

[Ken Gilmer (Created) (JIRA)]

Fails to resolve urls with multiple successive path seperators
--

 Key: FELIX-3253
 URL: https://issues.apache.org/jira/browse/FELIX-3253
 Project: Felix
  Issue Type: Bug
  Components: Lightweight HTTP Service
Reporter: Ken Gilmer
Assignee: Ken Gilmer
Priority: Minor


 it doesn't like requests with double-slashes while testing it
with the Felix webconsole:

   java.io.IOException: Unable to find resource: /res//imgs/logo.png
at
org.apache.felix.httplite.server.ResourceHandler.handle(ResourceHandler.java:89)
at org.apache.felix.httplite.server.Connection.process(Connection.java:240)
at
org.apache.felix.httplite.server.ThreadPool.processConnections(ThreadPool.java:298)
at
org.apache.felix.httplite.server.ThreadPool.access$000(ThreadPool.java:35)
at org.apache.felix.httplite.server.ThreadPool$1.run(ThreadPool.java:193)
at java.lang.Thread.run(Thread.java:680)

--
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: [VOTE] Release Felix Lightweight HTTP Service version 0.1.2

[Ken Gilmer]

Stuart,

  Thanks!  I've opened an issue based on your previous comments:

https://issues.apache.org/jira/browse/FELIX-3253

-ken


On Sun, Dec 4, 2011 at 8:12 AM, Stuart McCulloch  wrote:

> On 3 Dec 2011, at 23:05, Ken Gilmer wrote:
>
> > Hi Stuart,
> >
> >  Ah, nice catch.  I don't remember explicitly testing for this scenario
> so
> > it probably is a defect.  I looked into creating a JIRA for it.  Under
> > Components I was unable to add the service.  My JIRA account predates my
> > ASF membership so I imagine something will need to happen before I'm able
> > to add the component...?
>
> Hi Ken,
>
> I created https://issues.apache.org/jira/browse/FELIX/component/12316915and 
> added you as the component lead.
>
> --
> Cheers, Stuart
>
> > Thx!
> > ken
> >
> > On Sat, Dec 3, 2011 at 9:07 AM, Stuart McCulloch 
> wrote:
> >
> >> On 1 December 2011 07:35, Ken Gilmer  wrote:
> >>
> >>> Hi,
> >>>
> >>> We solved a few packaging issues not recorded in jira.
> >>>
> >>> Staging repository:
> >>> https://repository.apache.org/content/repositories/orgapachefelix-282/
> >>>
> >>> 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 282 /tmp/felix-staging
> >>>
> >>> Please vote to approve this release:
> >>>
> >>> [ ] +1 Approve the release
> >>> [ ] -1 Veto the release (please provide specific comments)
> >>>
> >>
> >> +1 thanks for persevering with this release!  signatures, checksums, and
> >> RAT report all look good
> >>
> >> I did notice it doesn't like requests with double-slashes while testing
> it
> >> with the Felix webconsole:
> >>
> >>   java.io.IOException: Unable to find resource: /res//imgs/logo.png
> >> at
> >>
> >>
> org.apache.felix.httplite.server.ResourceHandler.handle(ResourceHandler.java:89)
> >> at
> org.apache.felix.httplite.server.Connection.process(Connection.java:240)
> >> at
> >>
> >>
> org.apache.felix.httplite.server.ThreadPool.processConnections(ThreadPool.java:298)
> >> at
> >>
> org.apache.felix.httplite.server.ThreadPool.access$000(ThreadPool.java:35)
> >> at
> org.apache.felix.httplite.server.ThreadPool$1.run(ThreadPool.java:193)
> >> at java.lang.Thread.run(Thread.java:680)
> >>
> >> but I don't think that should hold up this particular release.
> >>
> >> This vote will be open for 72 hours.
> >>>
> >>
> >> --
> >> Cheers, Stuart
> >>
>
>

Re: [VOTE] Release Felix Lightweight HTTP Service version 0.1.2

[Ken Gilmer]

Hi Stuart,

  Ah, nice catch.  I don't remember explicitly testing for this scenario so
it probably is a defect.  I looked into creating a JIRA for it.  Under
Components I was unable to add the service.  My JIRA account predates my
ASF membership so I imagine something will need to happen before I'm able
to add the component...?

Thx!
ken



On Sat, Dec 3, 2011 at 9:07 AM, Stuart McCulloch  wrote:

> On 1 December 2011 07:35, Ken Gilmer  wrote:
>
> > Hi,
> >
> > We solved a few packaging issues not recorded in jira.
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-282/
> >
> > 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 282 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
>
> +1 thanks for persevering with this release!  signatures, checksums, and
> RAT report all look good
>
> I did notice it doesn't like requests with double-slashes while testing it
> with the Felix webconsole:
>
>java.io.IOException: Unable to find resource: /res//imgs/logo.png
> at
>
> org.apache.felix.httplite.server.ResourceHandler.handle(ResourceHandler.java:89)
> at org.apache.felix.httplite.server.Connection.process(Connection.java:240)
> at
>
> org.apache.felix.httplite.server.ThreadPool.processConnections(ThreadPool.java:298)
> at
> org.apache.felix.httplite.server.ThreadPool.access$000(ThreadPool.java:35)
> at org.apache.felix.httplite.server.ThreadPool$1.run(ThreadPool.java:193)
> at java.lang.Thread.run(Thread.java:680)
>
> but I don't think that should hold up this particular release.
>
> This vote will be open for 72 hours.
> >
>
> --
> Cheers, Stuart
>

Re: svn tag failure during release:prepare

[Ken Gilmer]

Stuart & Richard,

  Thanks!  I appreciate the added details, as it helps me understand what's
going on.  Amending the pom.xml with your updates fixed the problem.  I've
cleaned up the aborted attempts in svn, let me know if I've missed anything.

-ken



On Thu, Dec 1, 2011 at 1:54 PM, Stuart McCulloch  wrote:

> On 1 Dec 2011, at 04:48, Richard S. Hall wrote:
>
> > If it's a replication issue, then you may have to wait a little bit for
> it to forget about it.
> >
> > Additionally, I did notice that there is a 0.1.1 tag of httplite in
> releases, so that needs to be removed if you haven't already done so.
>
> FYI, the pom.xml in trunk still has some 0.1.2 entries left from the
> aborted release:
>
>  
>scm:svn:
> http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> 
>scm:svn:
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> 
>
> http://svn.apache.org/viewvc/felix/releases/?root=Apache-SVN/org.apache.felix.httplite-0.1.2
> 
>  
>
> which would explain svn's confusion - these entries should be:
>
>  
>scm:svn:
> http://svn.apache.org/repos/asf/felix/trunk/httplite
>scm:svn:
> https://svn.apache.org/repos/asf/felix/trunk/httplite
> 
>http://svn.apache.org/repos/asf/felix/trunk/httplite
>  
>
> PS. you can always use the "mvn release:rollback" command to revert the
> poms when "release:prepare" fails (as long as you haven't done
> "release:clean")
>
>
> http://maven.apache.org/plugins/maven-release-plugin/examples/rollback-release.html
>
> HTH
>
> > -> richard
> >
> > On 11/30/11 23:13, Ken Gilmer wrote:
> >> Thanks Bruno and Felix for your suggestions.  I have tried 'svn update'
> and
> >> mvn release:prepare' multiple times but continue to get a build
> failure.  I
> >> went back to the beginning of the release process.  The build error I'm
> >> getting now is slightly different:
> >>
> >> [INFO] Building Apache Felix Lightweight HTTP Server
> >> [INFO]task-segment: [release:prepare] (aggregator-style)
> >> [INFO]
> >> 
> >> [INFO] [release:prepare {execution: default-cli}]
> >> [INFO] Resuming release from phase 'scm-tag'
> >> [INFO] Tagging release with the label org.apache.felix.httplite-0.1.2...
> >> [INFO] Executing: /bin/sh -c cd
> >> /home/kgilmer/dev/repos/felix-trunk/httplite&&  svn --non-interactive
> copy
> >> --file /tmp/maven-scm-1734538187.commit
> >>
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> >>
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> >> [INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
> >> [INFO]
> >> 
> >> [ERROR] BUILD FAILURE
> >> [INFO]
> >> 
> >> [INFO] Unable to tag SCM
> >> Provider message:
> >> The svn tag command failed.
> >> Command output:
> >> svn: Path '
> >>
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> '
> >> does not exist in revision 1208948
> >>
> >> I have looked in the repo and indeed `org.apache.felix.httplite-0.1.2`
> does
> >> not exist.  So, I'm assuming that there is an automated step that copies
> >> from trunk to releases, and that is somehow failing.  Any suggestions on
> >> how to resolve this problem?
> >>
> >> thx,
> >> ken
> >>
> >> On Tue, Nov 29, 2011 at 10:09 PM, Felix Meschberger >wrote:
> >>
> >>> Hi,
> >>>
> >>> This is a known problem with the way the Subversion repo is replicated.
> >>>
> >>> Just svn update and run mvn release:prepare one more time (maybe
> >>> repeatedly) until the things work.
> >>>
> >>> Regards
> >>> Felix
> >>>
> >>>
> >>> Am 29.11.2011 um 10:29 schrieb Ken Gilmer:
> >>>
> >>>> Hi,
> >>>>
> >>>>  I'm going for attempt #2 to release the httplite bundle.  I have
> >>> upgraded
> >>>> the parent pom version in the local pom.xml.  In following the release
> >>>> procedure ev

[VOTE] Release Felix Lightweight HTTP Service version 0.1.2

[Ken Gilmer]

Hi,

We solved a few packaging issues not recorded in jira.

Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-282/

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 282 /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.

Re: svn tag failure during release:prepare

[Ken Gilmer]

Thanks Bruno and Felix for your suggestions.  I have tried 'svn update' and
mvn release:prepare' multiple times but continue to get a build failure.  I
went back to the beginning of the release process.  The build error I'm
getting now is slightly different:

[INFO] Building Apache Felix Lightweight HTTP Server
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO]

[INFO] [release:prepare {execution: default-cli}]
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label org.apache.felix.httplite-0.1.2...
[INFO] Executing: /bin/sh -c cd
/home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive copy
--file /tmp/maven-scm-1734538187.commit
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
[INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path '
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2'
does not exist in revision 1208948

I have looked in the repo and indeed `org.apache.felix.httplite-0.1.2` does
not exist.  So, I'm assuming that there is an automated step that copies
from trunk to releases, and that is somehow failing.  Any suggestions on
how to resolve this problem?

thx,
ken

On Tue, Nov 29, 2011 at 10:09 PM, Felix Meschberger wrote:

> Hi,
>
> This is a known problem with the way the Subversion repo is replicated.
>
> Just svn update and run mvn release:prepare one more time (maybe
> repeatedly) until the things work.
>
> Regards
> Felix
>
>
> Am 29.11.2011 um 10:29 schrieb Ken Gilmer:
>
> > Hi,
> >
> >  I'm going for attempt #2 to release the httplite bundle.  I have
> upgraded
> > the parent pom version in the local pom.xml.  In following the release
> > procedure everything looks alright until I get to the 'mvn
> release:prepare'
> > step which fails with:
> >
> > [INFO] Checking in modified POMs...
> > [INFO] Executing: /bin/sh -c cd
> > /home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive
> > commit --file /tmp/maven-scm-1280215403.commit --targets
> > /tmp/maven-scm-4132652216088199281-targets
> > [INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
> > [INFO] Tagging release with the label org.apache.felix.httplite-0.1.2...
> > [INFO] Executing: /bin/sh -c cd
> > /home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive
> copy
> > --file /tmp/maven-scm-899510912.commit --revision 1207801
> >
> https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite
> >
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
> > [INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
> > [INFO]
> > 
> > [ERROR] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Unable to tag SCM
> > Provider message:
> > The svn tag command failed.
> > Command output:
> > svn: Path '
> >
> https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite
> '
> > does not exist in revision 1207801
> >
> > It looks to me that the tag path is being incorrectly with
> > 'felix-parent-2.1' rather than 'org.apache.felix.httplite-0.1.2', however
> > I'm not sure what the problem with the pom is.  Before upgrading the pom
> I
> > did not see this issue.  Any ideas?
> >
> > thx,
> > ken
>
>

Re: [VOTE] Release Felix maven-bundle-plugin version 2.3.6

[Ken Gilmer]

+1

thx,
ken

On Tue, Nov 29, 2011 at 2:31 AM, Stuart McCulloch  wrote:

> Hi folks,
>
> We solved 17 issues in this release:
>
>
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22maven-bundle-plugin-2.3.6%22
>
> There are still some outstanding issues:
>
>   https://issues.apache.org/jira/browse/FELIX/component/12311143
>
> Staging repository:
>
>   https://repository.apache.org/content/repositories/orgapachefelix-264/
>
> Maven site docs:
>
>
> http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.3.6/doc/site/index.html
>
> 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 264 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve this release
> [ ] -1 Veto this release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> --
> Cheers, Stuart

svn tag failure during release:prepare

[Ken Gilmer]

Hi,

  I'm going for attempt #2 to release the httplite bundle.  I have upgraded
the parent pom version in the local pom.xml.  In following the release
procedure everything looks alright until I get to the 'mvn release:prepare'
step which fails with:

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
/home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive
commit --file /tmp/maven-scm-1280215403.commit --targets
/tmp/maven-scm-4132652216088199281-targets
[INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
[INFO] Tagging release with the label org.apache.felix.httplite-0.1.2...
[INFO] Executing: /bin/sh -c cd
/home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive copy
--file /tmp/maven-scm-899510912.commit --revision 1207801
https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
[INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path '
https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite'
does not exist in revision 1207801

It looks to me that the tag path is being incorrectly with
'felix-parent-2.1' rather than 'org.apache.felix.httplite-0.1.2', however
I'm not sure what the problem with the pom is.  Before upgrading the pom I
did not see this issue.  Any ideas?

thx,
ken

Re: svn commit: r1207016 - in /felix/trunk/httplite: doc/changelog.txt pom.xml

[Ken Gilmer]

Richard,

  Ah, that makes sense...  So the release version literal is specified not
in the pom but via the prompt from running "mvn release:prepare" during the
release process.  I was confused but now I think I'm clear.

Thanks,
ken


On Tue, Nov 29, 2011 at 3:19 PM, Richard S. Hall wrote:

> Ken,
>
> Just an FYI, generally you keep the development version odd in the pom
> (e.g., 0.1.1-SNAPSHOT) and then when you use maven to release it you change
> it to even during the release process (e.g., 0.1.2). So that way there is
> never a development build of the even version ever (i.e., 0.1.2-SNAPSHOT).
>
> Not that any of this is super important, so don't worry too much about it
> this time...
>
> -> richard
>
> On 11/28/11 3:27, kgil...@apache.org wrote:
>
>> Author: kgilmer
>> Date: Mon Nov 28 08:27:58 2011
>> New Revision: 1207016
>>
>> URL: 
>> http://svn.apache.org/viewvc?**rev=1207016&view=rev
>> Log:
>> httplite: bump version to 1.2 to conform to dev/stable release version
>> convention.
>>
>> Modified:
>> felix/trunk/httplite/doc/**changelog.txt
>> felix/trunk/httplite/pom.xml
>>
>> Modified: felix/trunk/httplite/doc/**changelog.txt
>> URL: http://svn.apache.org/viewvc/**felix/trunk/httplite/doc/**
>> changelog.txt?rev=1207016&r1=**1207015&r2=1207016&view=diff
>> ==**==**
>> ==
>> --- felix/trunk/httplite/doc/**changelog.txt (original)
>> +++ felix/trunk/httplite/doc/**changelog.txt Mon Nov 28 08:27:58 2011
>> @@ -1,3 +1,3 @@
>> -Initial Release 0.1.1
>> +Initial Release 0.1.2
>>  -
>>
>>
>> Modified: felix/trunk/httplite/pom.xml
>> URL: http://svn.apache.org/viewvc/**felix/trunk/httplite/pom.xml?**
>> rev=1207016&r1=1207015&r2=**1207016&view=diff
>> ==**==**
>> ==
>> --- felix/trunk/httplite/pom.xml (original)
>> +++ felix/trunk/httplite/pom.xml Mon Nov 28 08:27:58 2011
>> @@ -27,7 +27,7 @@
>>bundle
>>Apache Felix Lightweight HTTP Server
>>A minimal HTTP Service implementation.
>> -   0.1.1-SNAPSHOT
>> +   0.1.2-SNAPSHOT
>>org.apache.felix.**httplite
>>
>>
>>
>>
>>

[CANCEL] initial httplite 0.1.1 release

[Ken Gilmer]

Hi,

  Current release is cancelled given issues below.

kindly,
ken

On Tue, Nov 22, 2011 at 11:20 PM, Richard S. Hall wrote:

> The NOTICE file is not correct. It doesn't have the correct name (i.e.,
> the first line), it should be "Apache Felix Lightweight HTTP Server". Also,
> the copyright year is 2006...this clearly isn't correct. :-) The
> DEPENDENCIES file is not in the JAR's META-INF directory either.
>
> I think the issue is you are using an older parent pom instead of the
> newest released one that handles the NOTICE/DEPENDENCIES files differently
> (then you'll no longer need these files in your root directory). Take a
> look at framework or configadmin for an example of how to set things up
> with the new parent pom. You should be able to compare your resulting
> NOTICE/DEPS files to those see if they look similar.
>
> Also note that we generally use x.y.odd-SNAPSHOT to denote a development
> release and x.y.even to denote a stable release. The reason for this is if
> you develop with x.y.z-SNAPSHOT then release x.y.z as a stable reease, then
> in OSGi version numbering x.y.z-SNAPSHOT > x.y.z. Following an odd/even
> numbering scheme avoids this annoyance.
>
> The initial release version in changelog.txt is 0.1.0, but this artifact
> is 0.1.1...which is it?
>
> Overall, this is pretty close. I think if you re-roll it after updating to
> the newest released parent pom and fix some of these other little mistakes,
> then it will be good to go. Thanks!
>
> -> richard
>
>
> On 11/20/2011 11:37 PM, Ken Gilmer wrote:
>
>> Hi,
>> I would like to call a vote for the initial release of the lightweight
>> HTTP Service implementation (httplite), version 0.1.1.  This is my
>> first attempt at a release so if you see something that looks wrong it
>> probably is :).
>> Staging repository:
>> https://repository.apache.org/**content/repositories/**
>> orgapachefelix-227/<https://repository.apache.org/content/repositories/orgapachefelix-227/>
>> 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<http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh>
>> Usage:
>> sh check_staged_release.sh 227 /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.
>>
>>

[VOTE] initial httplite 0.1.1 release

[Ken Gilmer]

Hi,
I would like to call a vote for the initial release of the lightweight
HTTP Service implementation (httplite), version 0.1.1.  This is my
first attempt at a release so if you see something that looks wrong it
probably is :).
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-227/
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 227 /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.

Release Question

[Ken Gilmer]

Hi, I'm following the documentation provided at
http://felix.apache.org/site/release-management-nexus.html with the goal of
pushing an initial release of the "Light HTTP Service" bundle.  In my POM
the version specified is 0.1.1-SNAPSHOT.  In the docs it says "make sure
there are no snapshots in the POMs to be released". If I remove the
SNAPSHOT label the dry run fails with "You don't have a SNAPSHOT project in
the reactor projects list."  I am guessing that "snapshots in the POM"
refers to something other than the version.  Am I alright to proceed with
0.1.1-SNAPSHOT?

thx!
ken

Re: [VOTE] framework 4.0.2 and related subproject releases

[Ken Gilmer]

+1

On Mon, Nov 21, 2011 at 6:08 AM, Karl Pauls  wrote:

> I would like to call a vote on the following subproject releases:
>
> framework  4.0.2
> framework.security 2.0.1
> main 4.0.2
> main.distribution 4.0.2
>
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-225/
>
> 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 225 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>

Re: Added httplite to the root modules list in /pom.xml

[Ken Gilmer]

Got it, I will familiarize myself with the release process and check with
Marcel regarding the documentation, as that is a good first step.  Thanks
Karl and Richard!

-ken

On Wed, Oct 26, 2011 at 12:04 AM, Richard S. Hall wrote:

> On 10/25/11 09:24 , Ken Gilmer wrote:
>
>> Hi Richard,
>>
>>   Ok good to know.  So what steps do I take so that httplite is consumable
>> and documented on the Felix website?  I mean listed on the build page (
>> http://felix.apache.org/site/**downloads.cgi<http://felix.apache.org/site/downloads.cgi>)
>> and a doc page (
>> http://felix.apache.org/site/**apache-felix-log.html<http://felix.apache.org/site/apache-felix-log.html>
>> )?
>>
>
> To create a web page, you just need permission on the wiki. I think someone
> (Marcel, perhaps) has to add you to the felix-dev group since I don't see
> how to do it.
>
> Regarding downloads, as Karl pointed out, that involves going through the
> release process. The first time for that is sometimes tricky, since all of
> the rules have to be followed, but hopefully it won't be bad for this since
> it is reasonably self contained and the newest parent pom tries to simplify
> life a little.
>
> So, feel free to try to figure out how to do a release from the docs and
> ask questions...and be prepared that it might take more than one attempt to
> get it done. :-)
>
> -> richard
>
>
>
>> thx,
>> ken
>>
>> On Tue, Oct 25, 2011 at 10:06 PM, Richard S. Hall**
>> wrote:
>>
>>  Yeah, I wouldn't worry too much about it...the root build is always
>>> flaky.
>>> I don't think most people build from the root. We should either clean it
>>> up
>>> or get rid of it.
>>>
>>> ->  richard
>>>
>>>
>>> On 10/25/11 02:32 , Ken Gilmer wrote:
>>>
>>>  Hi,
>>>>
>>>>   In order to get the httplite bundle to build along with the rest I
>>>> added
>>>> to the modules section of the root pom.xml.  I have tested it and it
>>>> seems
>>>> ok to me but I'm new to the Felix build system and Maven.  If there are
>>>> problems the commit is r1188527.
>>>>
>>>> thx
>>>> ken
>>>>
>>>>
>>>>

Re: Added httplite to the root modules list in /pom.xml

[Ken Gilmer]

Hi Richard,

  Ok good to know.  So what steps do I take so that httplite is consumable
and documented on the Felix website?  I mean listed on the build page (
http://felix.apache.org/site/downloads.cgi) and a doc page (
http://felix.apache.org/site/apache-felix-log.html)?

thx,
ken

On Tue, Oct 25, 2011 at 10:06 PM, Richard S. Hall wrote:

> Yeah, I wouldn't worry too much about it...the root build is always flaky.
> I don't think most people build from the root. We should either clean it up
> or get rid of it.
>
> -> richard
>
>
> On 10/25/11 02:32 , Ken Gilmer wrote:
>
>> Hi,
>>
>>   In order to get the httplite bundle to build along with the rest I added
>> to the modules section of the root pom.xml.  I have tested it and it seems
>> ok to me but I'm new to the Felix build system and Maven.  If there are
>> problems the commit is r1188527.
>>
>> thx
>> ken
>>
>>

Added httplite to the root modules list in /pom.xml

[Ken Gilmer]

Hi,

  In order to get the httplite bundle to build along with the rest I added
to the modules section of the root pom.xml.  I have tested it and it seems
ok to me but I'm new to the Felix build system and Maven.  If there are
problems the commit is r1188527.

thx
ken

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126371#comment-13126371
 ] 

Ken Gilmer commented on FELIX-538:
--

Ok, source has been committed and updated with org.apache.felix.httplite 
package namespace.  Maven pom has been updated to produce httplite bundle.  Yet 
to be tested.

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
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] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126334#comment-13126334
 ] 

Ken Gilmer commented on FELIX-538:
--

Well for now I'll move forward with 'httplite', and I can change it later if 
something else is desired.  Looks like my write permissions are alright, see 
commit 1182646 (http://svn.apache.org/viewvc?view=revision&revision=1182646).



> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
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] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125699#comment-13125699
 ] 

Ken Gilmer commented on FELIX-538:
--

Alright, I think I'm all setup now to add the sources to SVN (assuming I'm 
supposed to do that).  I'm guess that the base dir of the project should be:
felix/trunk/http/lightweight.  Is this correct?

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
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] [Commented] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123814#comment-13123814
 ] 

Ken Gilmer commented on FELIX-3084:
---

Just checking, anything I need to do for this?  It's not clear to me from the 
review page what the current status is...

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>Reporter: Ken Gilmer
>  Labels: software
> Attachments: GRANT.pdf, org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
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] [Commented] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117009#comment-13117009
 ] 

Ken Gilmer commented on FELIX-3084:
---

Ok, got it.  I've received confirmation that both documents have been received 
by the foundation.

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>Reporter: Ken Gilmer
>  Labels: software
> Attachments: GRANT.pdf, org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
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] [Commented] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116173#comment-13116173
 ] 

Ken Gilmer commented on FELIX-3084:
---

I have attached the signed grant form to this issue.  I did not see any 
directions on where it should go so assumed attaching it here was best.  I also 
sent the signed ICLA PDF to the address specified in the agreement.

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>Reporter: Ken Gilmer
>  Labels: software
> Attachments: GRANT.pdf, org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
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] [Updated] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer updated FELIX-3084:
--

Attachment: GRANT.pdf

Signed Software Grant form.

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>    Reporter: Ken Gilmer
>  Labels: software
> Attachments: GRANT.pdf, org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
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] [Commented] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115974#comment-13115974
 ] 

Ken Gilmer commented on FELIX-3084:
---

Great news!  Ok, I'll do that today.

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>Reporter: Ken Gilmer
>  Labels: software
> Attachments: org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
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] [Commented] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103431#comment-13103431
 ] 

Ken Gilmer commented on FELIX-3084:
---

How are we doing on this?

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>Reporter: Ken Gilmer
>  Labels: software
> Attachments: org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached[6] to this issue is an implementation of the OSGi 
> HTTP Service specification version 1.2.  The code is based on Richard's 
> original server which is also referenced in FELIX-538, and the remaining code 
> was developed by me, with the exception of a few classes which were adapted 
> from existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
> 6: MD5SUM 47580996a8c364890518222494d4d26b  
> org.apache.felix.http.lightweight-src.tar.gz  
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090838#comment-13090838
 ] 

Ken Gilmer commented on FELIX-538:
--

Ok, I have (I hope) the code in reasonable shape for submission and have 
created a JIRA as requested: https://issues.apache.org/jira/browse/FELIX-3084



> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer updated FELIX-3084:
--

Description: 
This issue is created as part of the process outlined in the "Contributing 
Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
The source code attached[6] to this issue is an implementation of the OSGi HTTP 
Service specification version 1.2.  The code is based on Richard's original 
server which is also referenced in FELIX-538, and the remaining code was 
developed by me, with the exception of a few classes which were adapted from 
existing Felix sources[2].

Design constraints for this project were backwards compatibility, simplicity, 
and size.  The code base consists of 23 Java files in 3 packages.  The source 
is divided into "osgi", "server", and "servlet" packages according to the 
primary purpose of the class, and interfaces are utilized to keep the three 
domains fairly isolated[3].  The minimal compiled jar which does not include 
the servlet API or OSGi API currently is 41Kb, and the dependency-free jar with 
all necessary APIs is 125Kb.  An Ant script is provided that will build the 
jars and a CI server is also available for binary builds[4] and javadocs[5].

In terms of features the server doesn't offer:
-HTTPS
-Authentication
-Cookie support
-Session support

In addition several aspects of the Servlet implementation have not been tested 
including:
-Multipart POST
-DELETE
-PUT
-Non-default character encodings

And as of the submission several Servlet API methods are unimplemented in (all 
unimplemented methods throw 
org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
-HttpServletRequest(Impl)
-HttpServletResponse(Impl)

However the core functionality has been implemented and tested and the Felix 
Web Admin application can be hosted with this HTTP Service implementation.

I plan in continuing to use the service in personal and professional projects 
and would be happy to continue to add unimplemented features and maintain the 
code base as a Felix committer.

Thanks!
Ken Gilmer

1: https://issues.apache.org/jira/browse/FELIX-538
2: 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
3: 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
5: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
6: MD5SUM 47580996a8c364890518222494d4d26b  
org.apache.felix.http.lightweight-src.tar.gz  
 

  was:
This issue is created as part of the process outlined in the "Contributing 
Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
The source code attached to this issue is an implementation of the OSGi HTTP 
Service specification version 1.2.  The code is based on Richard's original 
server which is also referenced in FELIX-538, and the remaining code was 
developed by me, with the exception of a few classes which were adapted from 
existing Felix sources[2].

Design constraints for this project were backwards compatibility, simplicity, 
and size.  The code base consists of 23 Java files in 3 packages.  The source 
is divided into "osgi", "server", and "servlet" packages according to the 
primary purpose of the class, and interfaces are utilized to keep the three 
domains fairly isolated[3].  The minimal compiled jar which does not include 
the servlet API or OSGi API currently is 41Kb, and the dependency-free jar with 
all necessary APIs is 125Kb.  An Ant script is provided that will build the 
jars and a CI server is also available for binary builds[4] and javadocs[5].

In terms of features the server doesn't offer:
-HTTPS
-Authentication
-Cookie support
-Session support

In addition several aspects of the Servlet implementation have not been tested 
including:
-Multipart POST
-DELETE
-PUT
-Non-default character encodings

And as of the submission several Servlet API methods are unimplemented in (all 
unimplemented methods throw 
org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
-HttpServletRequest(Impl)
-HttpServletResponse(Impl)

However the core functionality has been implemented and tested and the Felix 
Web Admin application can be hosted with this HTTP Service implementation.

I plan in continuing to use the service in personal and professional projects 
and would be happy to continue to add unimplemented features and maintain the 
code base as a Felix committer.

Thanks!
Ken Gilmer

1: https://issues.apache.or

[jira] [Updated] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer updated FELIX-3084:
--

Attachment: org.apache.felix.http.lightweight-src.tar.gz

Source code

> Submission of source code for review of software grant for lightweight HTTP 
> service implementation.
> ---
>
> Key: FELIX-3084
> URL: https://issues.apache.org/jira/browse/FELIX-3084
> Project: Felix
>  Issue Type: Task
>  Components: HTTP Service
>    Reporter: Ken Gilmer
>  Labels: software
> Attachments: org.apache.felix.http.lightweight-src.tar.gz
>
>
> This issue is created as part of the process outlined in the "Contributing 
> Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
> The source code attached to this issue is an implementation of the OSGi HTTP 
> Service specification version 1.2.  The code is based on Richard's original 
> server which is also referenced in FELIX-538, and the remaining code was 
> developed by me, with the exception of a few classes which were adapted from 
> existing Felix sources[2].
> Design constraints for this project were backwards compatibility, simplicity, 
> and size.  The code base consists of 23 Java files in 3 packages.  The source 
> is divided into "osgi", "server", and "servlet" packages according to the 
> primary purpose of the class, and interfaces are utilized to keep the three 
> domains fairly isolated[3].  The minimal compiled jar which does not include 
> the servlet API or OSGi API currently is 41Kb, and the dependency-free jar 
> with all necessary APIs is 125Kb.  An Ant script is provided that will build 
> the jars and a CI server is also available for binary builds[4] and 
> javadocs[5].
> In terms of features the server doesn't offer:
> -HTTPS
> -Authentication
> -Cookie support
> -Session support
> In addition several aspects of the Servlet implementation have not been 
> tested including:
> -Multipart POST
> -DELETE
> -PUT
> -Non-default character encodings
> And as of the submission several Servlet API methods are unimplemented in 
> (all unimplemented methods throw 
> org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
> -HttpServletRequest(Impl)
> -HttpServletResponse(Impl)
> However the core functionality has been implemented and tested and the Felix 
> Web Admin application can be hosted with this HTTP Service implementation.
> I plan in continuing to use the service in personal and professional projects 
> and would be happy to continue to add unimplemented features and maintain the 
> code base as a Felix committer.
> Thanks!
> Ken Gilmer
> 1: https://issues.apache.org/jira/browse/FELIX-538
> 2: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
> 3: 
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
>  
> /plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
> 4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
> 5: 
> https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
>   
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-3084) Submission of source code for review of software grant for lightweight HTTP service implementation.

[Ken Gilmer (JIRA)]

Submission of source code for review of software grant for lightweight HTTP 
service implementation.
---

 Key: FELIX-3084
 URL: https://issues.apache.org/jira/browse/FELIX-3084
 Project: Felix
  Issue Type: Task
  Components: HTTP Service
Reporter: Ken Gilmer


This issue is created as part of the process outlined in the "Contributing 
Source Code" Felix page as suggested by Richard Hall in issue FELIX-538[1].  
The source code attached to this issue is an implementation of the OSGi HTTP 
Service specification version 1.2.  The code is based on Richard's original 
server which is also referenced in FELIX-538, and the remaining code was 
developed by me, with the exception of a few classes which were adapted from 
existing Felix sources[2].

Design constraints for this project were backwards compatibility, simplicity, 
and size.  The code base consists of 23 Java files in 3 packages.  The source 
is divided into "osgi", "server", and "servlet" packages according to the 
primary purpose of the class, and interfaces are utilized to keep the three 
domains fairly isolated[3].  The minimal compiled jar which does not include 
the servlet API or OSGi API currently is 41Kb, and the dependency-free jar with 
all necessary APIs is 125Kb.  An Ant script is provided that will build the 
jars and a CI server is also available for binary builds[4] and javadocs[5].

In terms of features the server doesn't offer:
-HTTPS
-Authentication
-Cookie support
-Session support

In addition several aspects of the Servlet implementation have not been tested 
including:
-Multipart POST
-DELETE
-PUT
-Non-default character encodings

And as of the submission several Servlet API methods are unimplemented in (all 
unimplemented methods throw 
org.apache.felix.http.lightweight.servlet.UnimplementedAPIException):
-HttpServletRequest(Impl)
-HttpServletResponse(Impl)

However the core functionality has been implemented and tested and the Felix 
Web Admin application can be hosted with this HTTP Service implementation.

I plan in continuing to use the service in personal and professional projects 
and would be happy to continue to add unimplemented features and maintain the 
code base as a Felix committer.

Thanks!
Ken Gilmer

1: https://issues.apache.org/jira/browse/FELIX-538
2: 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/DefaultContextImpl.java,
 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/Logger.java
3: 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationHandler.java,
 
/plain-http-service/src/main/java/org/apache/felix/http/lightweight/osgi/ServiceRegistrationResolver.java
4: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/
5: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
  
 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085587#comment-13085587
 ] 

Ken Gilmer commented on FELIX-538:
--

Ok, when I feel the code is in decent enough shape to be submitted as a grant, 
I'll follow the directions you supplied.  Yes, I am already using the code 
instead of Jetty for work projects and would be happy to continue maintaining 
it.

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084949#comment-13084949
 ] 

Ken Gilmer commented on FELIX-538:
--

POST, PUT, DELETE, query string parsing and POST parameters are now 
'implemented' but not tested much.  The Felix Web Console now appears to fully 
work when run with the lightweight server.  The build now produces a minimal 
jar that is 40Kb that *should* run under J2SE 1.4, but I cannot be sure since 
I'm compiling against the OpenJDK class libraries.  The "full" bundle is 140Kb 
with the relevant OSGi compendium and Servlet 2.4 API classes.

Can anyone suggest good ways of exercising the service?  What criteria need to 
me met for the project to be added to Felix?  

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083872#comment-13083872
 ] 

Ken Gilmer commented on FELIX-538:
--

I've reached a functional milestone where the service is able to load the 
default page for the Felix Web Console.  There is much left to be done but I 
feel this marks a point where I'm over the initial hump of getting the service 
working.

My next step will be HTTP methods PUT, POST, and DELETE.

Currently the project weighs in at 33 classes.  The compiled jar is about 84Kb.

I've also added an ant script and cloudbees hosted Jenkins automated build for 
anyone wishing to take a look: 
https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/

Javadoc: 
https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
 

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Gilmer updated FELIX-538:
-

Attachment: Screenshot-Apache Felix Web Console - Bundles - Chromium.png

Screenshot of Felix Web Console hosted by Lightweight HTTP Service.

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
> Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service

[Ken Gilmer (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081509#comment-13081509
 ] 

Ken Gilmer commented on FELIX-538:
--

While most of the Servlet implementation code is not yet implemented, the 
existing code now is able to host resources and basic servlets that only 
require doGet() in informal testing.

> Create a really lightweight version of the HTTP Service
> ---
>
> Key: FELIX-538
> URL: https://issues.apache.org/jira/browse/FELIX-538
> Project: Felix
>  Issue Type: New Feature
>  Components: HTTP Service
>Reporter: Richard S. Hall
>Priority: Minor
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira