[jira] [Deleted] (ACE-629) asd
[ https://issues.apache.org/jira/browse/ACE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-629: - > asd > --- > > Key: ACE-629 > URL: https://issues.apache.org/jira/browse/ACE-629 > Project: ACE > Issue Type: New Feature >Reporter: asd palkon >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Deleted] (ACE-612) Test_issue
[ https://issues.apache.org/jira/browse/ACE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-612: - > Test_issue > -- > > Key: ACE-612 > URL: https://issues.apache.org/jira/browse/ACE-612 > Project: ACE > Issue Type: Bug > Environment: test >Reporter: Kullanit Na nongkhai >Priority: Critical > > test -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (ACE-611) Exploding flame extinguishers
[ https://issues.apache.org/jira/browse/ACE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-611: - > Exploding flame extinguishers > - > > Key: ACE-611 > URL: https://issues.apache.org/jira/browse/ACE-611 > Project: ACE > Issue Type: Bug >Reporter: gajanan > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Deleted] (ACE-604) CLONE - Story prueba
[ https://issues.apache.org/jira/browse/ACE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-604: - > CLONE - Story prueba > > > Key: ACE-604 > URL: https://issues.apache.org/jira/browse/ACE-604 > Project: ACE > Issue Type: Story >Reporter: tati > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-602) Story prueba
[ https://issues.apache.org/jira/browse/ACE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-602: - > Story prueba > > > Key: ACE-602 > URL: https://issues.apache.org/jira/browse/ACE-602 > Project: ACE > Issue Type: Story >Reporter: tati > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-605) CLONE - task1
[ https://issues.apache.org/jira/browse/ACE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-605: - > CLONE - task1 > - > > Key: ACE-605 > URL: https://issues.apache.org/jira/browse/ACE-605 > Project: ACE > Issue Type: Sub-task >Reporter: tati > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-592) how to use Apache ACE web UI to remotely manage OSGi bundles on many server devices.
[ https://issues.apache.org/jira/browse/ACE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305996#comment-15305996 ] Marcel Offermans commented on ACE-592: -- Your first few questions I don't quite understand what you are asking for (I'm not a native speaker, so that could well be my fault). I am guessing you are interested to learn what exactly the rules are for naming features and distributions? They should be given unique names. Can you try explaining your question again? To answer your question about the deployment not working, what set of bundles did you try to deploy? Are you sure those bundles all resolve (and start)? One thing to diagnose this issue is to add the "-v" option to the ace-launcher, which will make it a lot more verbose. Usually then you will be able to figure out what is going wrong. If not, paste the output here so we can have a look. If possible, then also share the bundles you were trying to deploy. Your other questions: (1) Again, not sure what you are asking here. In the ACE UI you can click on a target to see what distributions, features and artifacts it is linked to (or on any other entity). You cannot start/stop/uninstall a bundle on the target, but you can remove a bundle from a feature and store that new configuration to uninstall it from all targets that had that feature installed. (2) The ace-launcher basically is an instance of Apache Felix with a management agent. So it already is integrated. What are you looking for? Using the management agent with a specific version of Felix, or? > how to use Apache ACE web UI to remotely manage OSGi bundles on many server > devices. > -- > > Key: ACE-592 > URL: https://issues.apache.org/jira/browse/ACE-592 > Project: ACE > Issue Type: Question > Components: Deployment >Reporter: robertbob > > > I'm trying to use Apache ACE web UI to remotely manage OSGi bundles on > many server devices. > > > I followed the documentations but I can't find out how to actually add > a target to the server. > > My steps are as follows ： > > 1. Start the ACE server > C:\ace\server-allinone > > java -Dorg.osgi.service.http.port=8080 > -Dorg.apache.ace.server=localhost:8080 -Dorg.apache.ace.obr=localhost:8080 > -jar server-allinone.jar > 2. Start an ACE target > C:\ace\target\bin > java -Dagent.identification.agentid=target2 > -Dagent.discovery.serverurls=http://localhost:8080 -jar ace-launcher.jar > > > 3.Provisioning software > > （1）Go to the ACE web-based UI, and click Retrieve in order to be > sure that you have the latest version of the repository. > If your target is up and running, it should be displayed in the > "Targets" column with a name of target-1; > > (2) Add the artifacts you want to deploy. This can be done in two > ways: either by dragging-and-dropping them > directly onto the "Actifacts" column (a blue border or line should > appear for the artifacts to be accepted). > Alternatively, you can use the + button above the "Artifacts" > column and using the "Upload" button >in the dialog presented for each artifact you want to add; > >(3) Create a new feature by clicking on the + button above the > Features column, give it a name and acknowledge the dialog; > >MY QUESTION: What is the rule of data fill ？ > >（4） Create a distribution by clicking on the + button above the > "Distributions" column, again give it a name >and acknowledge the dialog; > > MY QUESTION: What is the rule of data fill ？ > > （5） Next, you can create associations between your artifacts, > features, distributions and targets: > a. select one or more artifacts and drag them onto the feature > you created. > This will associate these artifacts to your feature; > b. select your feature and drag it onto your distribution, > creating an association between your feature > and distribution; > c. select your distribution and drag it onto your target to > associate your distribution to your target. > Verify your associations are correct by clicking your artifacts, features and > distributions. >Doing this should highlight the associations. > >（6） To persist the changes, you can use the Store button at the > top of the screen; > After a couple of seconds, the software is deployed onto the target. > If you used the Felix demonstration application, you
[jira] [Resolved] (ACE-590) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ACE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-590. -- Resolution: Fixed Deleted the release, will update the release docs to remind us of this. > Please delete old releases from mirroring system > > > Key: ACE-590 > URL: https://issues.apache.org/jira/browse/ACE-590 > Project: ACE > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Sebb >Assignee: Marcel Offermans > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > A good time to do this is shortly after the announce mail has been sent. > Please ensure that any release process documentation mentions this cleanup > step. > Thanks! > A good to > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-540) Cannot add Artifact
[
https://issues.apache.org/jira/browse/ACE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-540.
--
Resolution: Not A Problem
I've resolved this issue because I explained why it's not a problem, but
intended design.
> Cannot add Artifact
> ---
>
> Key: ACE-540
> URL: https://issues.apache.org/jira/browse/ACE-540
> Project: ACE
> Issue Type: Bug
> Components: UI
>Affects Versions: 2.0.1
>Reporter: Niels Schroeter
>
> When uploading an artifact, it does not show up in the artifacts column. When
> trying to upload it again, an error message pops up: "All 1 artifacts failed!
> Failed to add new object: entity already exists!"
> The artifact is org.apache.felix.deployment.rp.autoconf-0.1.8 (available via
> maven repo) and its manifest looks (fine, i guess )like this:
> {quote}
> Manifest-Version: 1.0
> Bundle-Description: A customizer bundle that publishes a Resource Proc
> essor service that processes configuration resources shipped in a Dep
> loyment Package.
> Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
> DeploymentPackage-Customizer: true
> Bundle-SymbolicName: org.apache.felix.deployment.rp.autoconf
> Built-By: jawi
> Bundle-ManifestVersion: 2
> Bnd-LastModified: 1452955859778
> Bundle-DocURL: http://www.apache.org/
> Bundle-Vendor: The Apache Software Foundation
> Import-Package: org.apache.felix.dm;version="[4.1,5)",org.osgi.framewo
> rk;version="[1.5,2)",org.osgi.service.cm;version="[1.3,2)",org.osgi.s
> ervice.deploymentadmin;version="[1.0,2)",org.osgi.service.deploymenta
> dmin.spi;version="[1.0,2)",org.osgi.service.event;version="[1.2,2)",o
> rg.osgi.service.log;version="[1.3,2)",org.osgi.service.metatype;versi
> on="[1.3,2)",org.osgi.util.tracker;version="[1.4,2)"
> Tool: Bnd-1.15.0
> Export-Package: org.osgi.service.deploymentadmin.spi;uses:="org.osgi.f
> ramework,org.osgi.service.deploymentadmin";version="1.0",org.osgi.ser
> vice.metatype;uses:="org.osgi.framework";version="1.2"
> Deployment-ProvidesResourceProcessor: org.osgi.deployment.rp.autoconf
> Bundle-Version: 0.1.8
> Bundle-Name: Apache Felix AutoConf Resource Processor
> Bundle-Activator: org.apache.felix.deployment.rp.autoconf.Activator
> Created-By: Apache Maven Bundle Plugin
> Build-Jdk: 1.8.0_45
> {quote}
> Note: this happens for many other artifacts aswell, i just picked this one
> since it is an official felix bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ACE-539) Latest release not listed on download site
[ https://issues.apache.org/jira/browse/ACE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-539. -- Resolution: Fixed I fixed this a few days ago, but forgot to update this issue. > Latest release not listed on download site > -- > > Key: ACE-539 > URL: https://issues.apache.org/jira/browse/ACE-539 > Project: ACE > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/ace/ >Reporter: Sebb >Assignee: Marcel Offermans >Priority: Critical > > The latest ACE release appears to be 2.1.0. > However the download page still says 2.0.1. > There don't seem to have been any Announce e-mails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-589) I-800-385-4895 Internet explorer technical support phone number USA/Canada, Call and get fix remotely online
[ https://issues.apache.org/jira/browse/ACE-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-589: - > I-800-385-4895 Internet explorer technical support phone number USA/Canada, > Call and get fix remotely online > > > Key: ACE-589 > URL: https://issues.apache.org/jira/browse/ACE-589 > Project: ACE > Issue Type: New Feature >Reporter: wen support > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-586) 1877$241$3596))))Pogo Customer Support Number 1877$241$3596))))Pogo Games Customer Service Number
[ https://issues.apache.org/jira/browse/ACE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-586: - > 1877$241$3596Pogo Customer Support Number 1877$241$3596Pogo Games > Customer Service Number > -- > > Key: ACE-586 > URL: https://issues.apache.org/jira/browse/ACE-586 > Project: ACE > Issue Type: Bug > Environment: 1877$241$3596Pogo Customer Support Number > 1877$241$3596Pogo Games Customer Service Number >Reporter: Neeraj rawat > > Pogo number 1877@241@3596@ (31) > pogo phone number 1877@241@3596@, pogo customer service phone number > 1877@241@3596@, pogo.com phone number 1877@241@3596@, pogo contact number > 1877@241@3596@, pogo customer service number 1877@241@3596@, pogo number > 1877@241@3596@, phone number 1877@241@3596@ for pogo, pogo help phone number > 1877@241@3596@, pogo support phone number 1877@241@3596@, pogo.com contact > number 1877@241@3596@, club pogo phone number 1877@241@3596@, pogo games > phone number 1877@241@3596@, pogo games customer service phone number > 1877@241@3596@, pogo.com customer service phone number 1877@241@3596@, pogo > telephone number 1877@241@3596@, phone number 1877@241@3596@ for pogo > customer support, pogo technical support number 1877@241@3596@, pogo.com > customer service number 1877@241@3596@, pogo contact phone number > 1877@241@3596@, pogo games contact number 1877@241@3596@… > Pogo Scrabble (16) > pogo scrabble, scrabble pogo, pogo games scrabble, free pogo scrabble, club > pogo scrabble, pogo scrabble games, pogo free games scrabble, free pogo games > scrabble, free scrabble game pogo, scrabble pogo.com, scrabble game pogo, > scrabble pogo free games, scrabble pogo free online, pogo club scrabble, > scrabble pogo games, scrabble by pogo > Club Pogo (16) > club pogo, club pogo games, free club pogo, pogo club, club pogo free, pogo > club games, club pogo free games, club pogo homepage, club pogo home page, > pogo club free, www club pogo, free pogo club, club pogo games club pogo > games, club pogo canasta, pogo club pogo, how to get free club pogo > Pogo Support (9) > pogo support, pogo tech support, pogo technical support, pogo games support, > pogo customer support, pogo phone support, pogo game support, pogo games > technical support, pogo chat support > Pogo Sign (32) > pogo.com sign in, pogo sign in, pogo sign in page, club pogo sign in, club > pogo member sign in, pogo com sign in member, club pogo sign in members only, > pogo club member sign in, club pogo sign in page, pogo games sign in, club > pogo sign page, pogo member sign in, pogo sign up, pogo com sign in page, > pogo sign in free games, pogo.com member sign in, pogo club sign in, sign in > pogo games, pogo scrabble sign in, club pogo games sign in… > Pogo Poppit (13) > pogo poppit, poppit pogo, pogo.com poppit, pogo games poppit, pogo poppit > game, pogo poppit app, poppit pogo games, poppit pogo game, pogo poppit > games, poppit on pogo, games pogo poppit, club pogo poppit, game pogo poppit > Pogo App (14) > pogo games app, pogo app, pogo.com app, pogo apps, club pogo app, pogo mobile > app, pogo game app, app for pogo games, free pogo games app, pogo games free > app, free pogo app, pogo payment app, pogo scrabble app, pogo tv app > Pogo Tv (13) > pogo tv games, pogo games tv, pogo.com tv, log on to www pogo tv games, pogo > tv free games, games pogo tv, free pogo tv games, tv pogo games, pogo tv new > games, pogo tv games free, game pogo tv, pogo game tv, log on to pogo tv games > Pogo Online (27) > pogo free online games, free online pogo games, pogo games online, free > online games pogo, pogo online games, pogo games free online, free pogo games > online, pogo free games online, pogo online free games, free games online > pogo, free pogo online games, online games pogo, online pogo games, club pogo > free online games, online games like pogo, online free pogo games, pogo games > online free, club pogo online games, pogo online, pogo online game… > Contact Pogo (11) > contact pogo by phone, contact pogo, contact pogo support, pogo contact, pogo > contacts, contact pogo games, how to contact pogo, how to contact pogo by > phone, pogo contact us, how to contact pogo by email, contact pogo.com > Pogo Service (7) > pogo.com customer service, pogo customer service, contact pogo customer > service, pogo games customer service, pogo merchant services, how do i > contact pogo customer service, pogo service > Free Poppit (28) > free poppit, free poppit game, pogo poppit free, poppit free pogo games, free > poppit games, free pogo poppit, poppit game free, free pogo games poppit, > pogo poppit game free, pogo free games poppit, free games pogo poppit, poppit >
[jira] [Deleted] (ACE-585) 1877$241 $3596 Pogo tech Support Number 1877$241 $3596 Pogo technical Support Number
[ https://issues.apache.org/jira/browse/ACE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-585: - > 1877$241 $3596 Pogo tech Support Number 1877$241 $3596 Pogo technical Support > Number > - > > Key: ACE-585 > URL: https://issues.apache.org/jira/browse/ACE-585 > Project: ACE > Issue Type: Bug > Environment: 1877$241 $3596 Pogo tech Support Number 1877$241 $3596 > Pogo technical Support Number >Reporter: Neeraj rawat > > Pogo number 1877@241@3596@ (31) > pogo phone number 1877@241@3596@, pogo customer service phone number > 1877@241@3596@, pogo.com phone number 1877@241@3596@, pogo contact number > 1877@241@3596@, pogo customer service number 1877@241@3596@, pogo number > 1877@241@3596@, phone number 1877@241@3596@ for pogo, pogo help phone number > 1877@241@3596@, pogo support phone number 1877@241@3596@, pogo.com contact > number 1877@241@3596@, club pogo phone number 1877@241@3596@, pogo games > phone number 1877@241@3596@, pogo games customer service phone number > 1877@241@3596@, pogo.com customer service phone number 1877@241@3596@, pogo > telephone number 1877@241@3596@, phone number 1877@241@3596@ for pogo > customer support, pogo technical support number 1877@241@3596@, pogo.com > customer service number 1877@241@3596@, pogo contact phone number > 1877@241@3596@, pogo games contact number 1877@241@3596@… > Pogo Scrabble (16) > pogo scrabble, scrabble pogo, pogo games scrabble, free pogo scrabble, club > pogo scrabble, pogo scrabble games, pogo free games scrabble, free pogo games > scrabble, free scrabble game pogo, scrabble pogo.com, scrabble game pogo, > scrabble pogo free games, scrabble pogo free online, pogo club scrabble, > scrabble pogo games, scrabble by pogo > Club Pogo (16) > club pogo, club pogo games, free club pogo, pogo club, club pogo free, pogo > club games, club pogo free games, club pogo homepage, club pogo home page, > pogo club free, www club pogo, free pogo club, club pogo games club pogo > games, club pogo canasta, pogo club pogo, how to get free club pogo > Pogo Support (9) > pogo support, pogo tech support, pogo technical support, pogo games support, > pogo customer support, pogo phone support, pogo game support, pogo games > technical support, pogo chat support > Pogo Sign (32) > pogo.com sign in, pogo sign in, pogo sign in page, club pogo sign in, club > pogo member sign in, pogo com sign in member, club pogo sign in members only, > pogo club member sign in, club pogo sign in page, pogo games sign in, club > pogo sign page, pogo member sign in, pogo sign up, pogo com sign in page, > pogo sign in free games, pogo.com member sign in, pogo club sign in, sign in > pogo games, pogo scrabble sign in, club pogo games sign in… > Pogo Poppit (13) > pogo poppit, poppit pogo, pogo.com poppit, pogo games poppit, pogo poppit > game, pogo poppit app, poppit pogo games, poppit pogo game, pogo poppit > games, poppit on pogo, games pogo poppit, club pogo poppit, game pogo poppit > Pogo App (14) > pogo games app, pogo app, pogo.com app, pogo apps, club pogo app, pogo mobile > app, pogo game app, app for pogo games, free pogo games app, pogo games free > app, free pogo app, pogo payment app, pogo scrabble app, pogo tv app > Pogo Tv (13) > pogo tv games, pogo games tv, pogo.com tv, log on to www pogo tv games, pogo > tv free games, games pogo tv, free pogo tv games, tv pogo games, pogo tv new > games, pogo tv games free, game pogo tv, pogo game tv, log on to pogo tv games > Pogo Online (27) > pogo free online games, free online pogo games, pogo games online, free > online games pogo, pogo online games, pogo games free online, free pogo games > online, pogo free games online, pogo online free games, free games online > pogo, free pogo online games, online games pogo, online pogo games, club pogo > free online games, online games like pogo, online free pogo games, pogo games > online free, club pogo online games, pogo online, pogo online game… > Contact Pogo (11) > contact pogo by phone, contact pogo, contact pogo support, pogo contact, pogo > contacts, contact pogo games, how to contact pogo, how to contact pogo by > phone, pogo contact us, how to contact pogo by email, contact pogo.com > Pogo Service (7) > pogo.com customer service, pogo customer service, contact pogo customer > service, pogo games customer service, pogo merchant services, how do i > contact pogo customer service, pogo service > Free Poppit (28) > free poppit, free poppit game, pogo poppit free, poppit free pogo games, free > poppit games, free pogo poppit, poppit game free, free pogo games poppit, > pogo poppit game free, pogo free games poppit, free games pogo poppit, poppit > free pogo game, pogo com poppit free
[jira] [Deleted] (ACE-587) 1877@241@3596 Pogo Support Number 1877@241@3596 Pogo Support Phone Number
[ https://issues.apache.org/jira/browse/ACE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-587: - > 1877@241@3596 Pogo Support Number 1877@241@3596 Pogo Support Phone Number > --- > > Key: ACE-587 > URL: https://issues.apache.org/jira/browse/ACE-587 > Project: ACE > Issue Type: Bug > Environment: 1877@241@3596 Pogo Support Number 1877@241@3596 Pogo > Support Phone Number >Reporter: Neeraj rawat > > Pogo number 1877@241@3596@ (31) > pogo phone number 1877@241@3596@, pogo customer service phone number > 1877@241@3596@, pogo.com phone number 1877@241@3596@, pogo contact number > 1877@241@3596@, pogo customer service number 1877@241@3596@, pogo number > 1877@241@3596@, phone number 1877@241@3596@ for pogo, pogo help phone number > 1877@241@3596@, pogo support phone number 1877@241@3596@, pogo.com contact > number 1877@241@3596@, club pogo phone number 1877@241@3596@, pogo games > phone number 1877@241@3596@, pogo games customer service phone number > 1877@241@3596@, pogo.com customer service phone number 1877@241@3596@, pogo > telephone number 1877@241@3596@, phone number 1877@241@3596@ for pogo > customer support, pogo technical support number 1877@241@3596@, pogo.com > customer service number 1877@241@3596@, pogo contact phone number > 1877@241@3596@, pogo games contact number 1877@241@3596@… > Pogo Scrabble (16) > pogo scrabble, scrabble pogo, pogo games scrabble, free pogo scrabble, club > pogo scrabble, pogo scrabble games, pogo free games scrabble, free pogo games > scrabble, free scrabble game pogo, scrabble pogo.com, scrabble game pogo, > scrabble pogo free games, scrabble pogo free online, pogo club scrabble, > scrabble pogo games, scrabble by pogo > Club Pogo (16) > club pogo, club pogo games, free club pogo, pogo club, club pogo free, pogo > club games, club pogo free games, club pogo homepage, club pogo home page, > pogo club free, www club pogo, free pogo club, club pogo games club pogo > games, club pogo canasta, pogo club pogo, how to get free club pogo > Pogo Support (9) > pogo support, pogo tech support, pogo technical support, pogo games support, > pogo customer support, pogo phone support, pogo game support, pogo games > technical support, pogo chat support > Pogo Sign (32) > pogo.com sign in, pogo sign in, pogo sign in page, club pogo sign in, club > pogo member sign in, pogo com sign in member, club pogo sign in members only, > pogo club member sign in, club pogo sign in page, pogo games sign in, club > pogo sign page, pogo member sign in, pogo sign up, pogo com sign in page, > pogo sign in free games, pogo.com member sign in, pogo club sign in, sign in > pogo games, pogo scrabble sign in, club pogo games sign in… > Pogo Poppit (13) > pogo poppit, poppit pogo, pogo.com poppit, pogo games poppit, pogo poppit > game, pogo poppit app, poppit pogo games, poppit pogo game, pogo poppit > games, poppit on pogo, games pogo poppit, club pogo poppit, game pogo poppit > Pogo App (14) > pogo games app, pogo app, pogo.com app, pogo apps, club pogo app, pogo mobile > app, pogo game app, app for pogo games, free pogo games app, pogo games free > app, free pogo app, pogo payment app, pogo scrabble app, pogo tv app > Pogo Tv (13) > pogo tv games, pogo games tv, pogo.com tv, log on to www pogo tv games, pogo > tv free games, games pogo tv, free pogo tv games, tv pogo games, pogo tv new > games, pogo tv games free, game pogo tv, pogo game tv, log on to pogo tv games > Pogo Online (27) > pogo free online games, free online pogo games, pogo games online, free > online games pogo, pogo online games, pogo games free online, free pogo games > online, pogo free games online, pogo online free games, free games online > pogo, free pogo online games, online games pogo, online pogo games, club pogo > free online games, online games like pogo, online free pogo games, pogo games > online free, club pogo online games, pogo online, pogo online game… > Contact Pogo (11) > contact pogo by phone, contact pogo, contact pogo support, pogo contact, pogo > contacts, contact pogo games, how to contact pogo, how to contact pogo by > phone, pogo contact us, how to contact pogo by email, contact pogo.com > Pogo Service (7) > pogo.com customer service, pogo customer service, contact pogo customer > service, pogo games customer service, pogo merchant services, how do i > contact pogo customer service, pogo service > Free Poppit (28) > free poppit, free poppit game, pogo poppit free, poppit free pogo games, free > poppit games, free pogo poppit, poppit game free, free pogo games poppit, > pogo poppit game free, pogo free games poppit, free games pogo poppit, poppit > free pogo game, pogo com poppit free games, free pogo poppit game,
[jira] [Created] (ACE-522) Upgrade the OSGi version to R5
Marcel Offermans created ACE-522: Summary: Upgrade the OSGi version to R5 Key: ACE-522 URL: https://issues.apache.org/jira/browse/ACE-522 Project: ACE Issue Type: Improvement Reporter: Marcel Offermans Our current codebase uses OSGi R4 (4.3.1). It's probably time to upgrade it to R6 (API wise and Felix). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-521) Upgrade the codebase to Java 8
Marcel Offermans created ACE-521: Summary: Upgrade the codebase to Java 8 Key: ACE-521 URL: https://issues.apache.org/jira/browse/ACE-521 Project: ACE Issue Type: Improvement Reporter: Marcel Offermans We are currently still compiling for Java 6. By now, Oracle has stopped supporting Java 7 so it probably makes sense to move our codebase to Java 8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-514) Upgrade to Dependency Manager 4
[ https://issues.apache.org/jira/browse/ACE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-514. -- Resolution: Fixed Committed the new version, adapted the code, ran the tests locally and launched the all-in-one version and did some smoke tests. Everything seems to work fine again. Upgrade to Dependency Manager 4 --- Key: ACE-514 URL: https://issues.apache.org/jira/browse/ACE-514 Project: ACE Issue Type: Improvement Components: Architecture Reporter: Marcel Offermans Assignee: Marcel Offermans The Apache Felix project recently released Dependency Manager 4 (the current release is 4.0.1). This upgrade fixes some concurrency issues, cleans up the API and support concurrency a lot better than before, resulting in faster startup times. It would be good to upgrade to this version, even though a couple of small things have changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-492) Update the project to use Bndtools 2.4.0
[ https://issues.apache.org/jira/browse/ACE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663151#comment-14663151 ] Marcel Offermans commented on ACE-492: -- The current build works with 2.4.1 (still using the Ant build). Bndtools 3.0.0 will probably be released soon, so we need to test against that one. Update the project to use Bndtools 2.4.0 Key: ACE-492 URL: https://issues.apache.org/jira/browse/ACE-492 Project: ACE Issue Type: Improvement Components: Build Reporter: Marcel Offermans Bndtools 2.4.0 has just been released, so we should probably spend some time upgrading the ACE build to work with it. This can probably be done in two steps: # Ensure that the current build works with 2.4.0. # Migrate to gradle, as that is the new build system for 2.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACE-459) Add BundleSymbolicName and Version to AuditLog/FeedBack on BundleEvents
[ https://issues.apache.org/jira/browse/ACE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans closed ACE-459. Resolution: Won't Fix As discussed in the comments, the requested information can already be obtained (albeit in a slightly more complicated way). Add BundleSymbolicName and Version to AuditLog/FeedBack on BundleEvents --- Key: ACE-459 URL: https://issues.apache.org/jira/browse/ACE-459 Project: ACE Issue Type: Improvement Components: Management Agent Affects Versions: 1.0.0 Reporter: Wilfried Sibla Priority: Minor Attachments: EventLogger.patch The LogViewer within the Target dialog on the ACE server only shows the id of the bundles (except directly during installation). It would be very helpful to have the BSN and version also there in case of problem diagnostics etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-390) Generate Maven POM files for bundles.
[ https://issues.apache.org/jira/browse/ACE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663155#comment-14663155 ] Marcel Offermans commented on ACE-390: -- The main goal is being able to upload our bundles to a Maven repository. We should probably take a closer look at the Dependency Manager 4 project, which also uses Bndtools and does that. Generate Maven POM files for bundles. - Key: ACE-390 URL: https://issues.apache.org/jira/browse/ACE-390 Project: ACE Issue Type: Task Components: Build Reporter: Marcel Offermans Sometimes you might want to use bundles in a Maven context. We currently have no support to generate a POM from a bundle and we want to add that so we can support various Maven repositories out there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-520) Only available serverurl gets blacklisted, broke our application
[ https://issues.apache.org/jira/browse/ACE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627758#comment-14627758 ] Marcel Offermans commented on ACE-520: -- One solution would be to add an option to disable blacklisting URLs (there are already features in the agent code for this). Alternatively one can argue if: a) blacklisting should happen if a URL is unreachable once and b) blacklisting should be forever (as both points assume a perfect and static network, which is not reality). Only available serverurl gets blacklisted, broke our application Key: ACE-520 URL: https://issues.apache.org/jira/browse/ACE-520 Project: ACE Issue Type: Bug Components: Management Agent Affects Versions: 2.0.1 Environment: Windows XP and up Reporter: Robert Mather We only have one ACE server running and it became unavailable for an extended period due to a maintenance window. All of our client applications (running the agent bundle) blacklisted the server address and failed to detect when the server came back online. Also, immediately following the agent blacklisting the server, our application's DS services silently stopped working (no indication they had been deactivated, just stopped communicating with our servers). We had to manually restart the application at all our customer locations to get them working again. The server and agent were taken from the latest release, 2.0.1, and we're using Felix release 5.0.0. The agent bundle is loaded from the Felix auto deploy directory. Here are the Felix and ACE settings we use: Felix: felix.auto.deploy.action=install,start,update # DEBUG level logging felix.log.level=4 ACE: agent.identification.agentid=removed agent.discovery.serverurls=removed agent.controller.syncinterval=420 agent.logging.level=DEBUG -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-503) Move CollectionCommands to gogo bundle
[ https://issues.apache.org/jira/browse/ACE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-503. -- Resolution: Fixed Committed the patch. Thanks for your contribution [~brampouwelse]! Move CollectionCommands to gogo bundle -- Key: ACE-503 URL: https://issues.apache.org/jira/browse/ACE-503 Project: ACE Issue Type: Improvement Affects Versions: 2.0.1 Reporter: Bram Pouwelse Assignee: Marcel Offermans Attachments: collectionCommands.patch Move the gogo collection support class CollectionCommands from org.apache.ace.client.rest to the gogo bundle (org.apache.ace.gogo) http://mail-archives.apache.org/mod_mbox/ace-users/201403.mbox/%3CCAKvr0DrONLytF8YpSrwTFvYL3v0Yspjdpx81PJmoihZiK1a%2BCg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-508) When rolling back the cause is not shown in the target's log
[ https://issues.apache.org/jira/browse/ACE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-508. -- Resolution: Fixed Committed a solution for this. When rolling back the cause is not shown in the target's log Key: ACE-508 URL: https://issues.apache.org/jira/browse/ACE-508 Project: ACE Issue Type: Improvement Reporter: Alexander Broekhuis Assignee: Marcel Offermans Priority: Minor Currently the Log of a target will show that deployment of a package has failed, but it does not show a cause or reason of the failure. For resolving the problem, this is needed. For example, if a ResourceProcessor fails with a ResourceProcessorException, that exception including the message could be added to the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACE-519) Broken links on ACE home page
[ https://issues.apache.org/jira/browse/ACE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans reassigned ACE-519: Assignee: Marcel Offermans Thanks for reporting this, I'll look into it! Broken links on ACE home page - Key: ACE-519 URL: https://issues.apache.org/jira/browse/ACE-519 Project: ACE Issue Type: Documentation Components: Site Reporter: Sascha Homeier Assignee: Marcel Offermans Priority: Minor Labels: documentation On the Apache ACE home page (https://ace.apache.org/) the following documentation links are broken and lead to a 404: * A brief introduction - https://ace.apache.org/user-doc/introduction.html * Developer Documentation - https://ace.apache.org/dev-doc/getting-started.html * Software Architecture - https://ace.apache.org/dev-doc/architecture.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-518) Adding a space to tag key causes error creating workspace
[
https://issues.apache.org/jira/browse/ACE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-518.
--
Resolution: Fixed
Committed a fix to both ensure that keys for tags and attributes will not
accept any string anymore and that the UI editor notifies the user when (s)he
tries to enter an invalid tag key.
Adding a space to tag key causes error creating workspace
-
Key: ACE-518
URL: https://issues.apache.org/jira/browse/ACE-518
Project: ACE
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Bree Van Oss
Assignee: Marcel Offermans
Priority: Minor
An ACE user accidentally added a space character to a tag name associated
with a Target, via the ACE UI. This resulted in the inability to login to the
ACE UI.
While investigating I found that via the Gogo shell, I could not create a
workspace. The command:
{code}
g! ws = (cw)
{code}
resulted in the following error:
{code}
gogo: ConversionException: com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
Debugging information
message : com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
cause-exception : java.lang.IllegalArgumentException
cause-message : com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
class :
org.apache.ace.client.repository.impl.RepositorySerializer
required-type :
org.apache.ace.client.repository.impl.RepositorySerializer
path: /repository/targets/target[10]/tags
line number : 126
---
{code}
If spaces are prohibited in tag names, the editor should enforce this
restriction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Deleted] (ACE-516) Test1
[ https://issues.apache.org/jira/browse/ACE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-516: - Test1 - Key: ACE-516 URL: https://issues.apache.org/jira/browse/ACE-516 Project: ACE Issue Type: Bug Reporter: Nimesh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-517) java.lang.OutOfMemoryError: GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/ACE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553676#comment-14553676 ] Marcel Offermans commented on ACE-517: -- Just to be sure, with the Apache ACE Web Admin you mean the Web UI? And with displaying bundle wiring you mean looking at the bundles, and their association to features, distributions and targets? To answer your question, ACE does not load all bundles into memory, but it does load all the metadata into memory so if you have a really big list of bundles inside the ACE repository you might run out of memory. What kind of memory settings are you using right now? And are you using the all in one server (that includes the Web UI) or are you running the server and client as separate processes? We need more information to establish if you ran into some memory leak or some other bug we should fix. java.lang.OutOfMemoryError: GC overhead limit exceeded -- Key: ACE-517 URL: https://issues.apache.org/jira/browse/ACE-517 Project: ACE Issue Type: Bug Components: Deployment Affects Versions: 2.0.1 Environment: centos Reporter: Ali Raza After deploying bundles using Apache ACE Command line client when i verify deployment using Apache ACE Web Admin. It does not show the pop displaying bundle wiring. Instead server console displays the following error: Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded As per my experience it could be because the bundle repository has grown and Apache Ace perhaps loads all the bundles into memory. Well I am not sure about that. I will thankful if someone could help in resolving this problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-517) java.lang.OutOfMemoryError: GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/ACE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554058#comment-14554058 ] Marcel Offermans commented on ACE-517: -- Ah, that's the part I missed in your initial description, you're invoking the resolver from the Web UI. We embed the Felix resolver, and invoke it with the bundles that are associated with the target plus the initial environment (which is that big text in the UI). Then we ask the resolver if this combination works. For some reason that runs out of memory. We should at least catch that case, and report back to the user. We should also investigate if an update to the resolver fixes this issue. I am pretty sure we are currently not using the latest resolver from Felix. java.lang.OutOfMemoryError: GC overhead limit exceeded -- Key: ACE-517 URL: https://issues.apache.org/jira/browse/ACE-517 Project: ACE Issue Type: Bug Components: Deployment Affects Versions: 2.0.1 Environment: centos Reporter: Ali Raza After deploying bundles using Apache ACE Command line client when i verify deployment using Apache ACE Web Admin. It does not show the pop displaying bundle wiring. Instead server console displays the following error: Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded As per my experience it could be because the bundle repository has grown and Apache Ace perhaps loads all the bundles into memory. Well I am not sure about that. I will thankful if someone could help in resolving this problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-518) Adding a space to tag key causes error creating workspace
[
https://issues.apache.org/jira/browse/ACE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552850#comment-14552850
]
Marcel Offermans commented on ACE-518:
--
I agree, we should check this in the UI.
Adding a space to tag key causes error creating workspace
-
Key: ACE-518
URL: https://issues.apache.org/jira/browse/ACE-518
Project: ACE
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Bree Van Oss
Priority: Minor
An ACE user accidentally added a space character to a tag name associated
with a Target, via the ACE UI. This resulted in the inability to login to the
ACE UI.
While investigating I found that via the Gogo shell, I could not create a
workspace. The command:
{code}
g! ws = (cw)
{code}
resulted in the following error:
{code}
gogo: ConversionException: com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
Debugging information
message : com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
cause-exception : java.lang.IllegalArgumentException
cause-message : com.thoughtworks.xstream.io.StreamException: :
expected = after attribute name (position: TEXT seen ...tags\n
monitoring FrequencyInSeconds... @126:40)
class :
org.apache.ace.client.repository.impl.RepositorySerializer
required-type :
org.apache.ace.client.repository.impl.RepositorySerializer
path: /repository/targets/target[10]/tags
line number : 126
---
{code}
If spaces are prohibited in tag names, the editor should enforce this
restriction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ACE-515) Running ant package-bin in the build folder throws an exception
Marcel Offermans created ACE-515: Summary: Running ant package-bin in the build folder throws an exception Key: ACE-515 URL: https://issues.apache.org/jira/browse/ACE-515 Project: ACE Issue Type: Bug Components: Build Affects Versions: next Reporter: Marcel Offermans If you checkout the code, then: cd build ant package-bin You get the following exception: BUILD FAILED ...ace/build/build.xml:156: java.lang.NoClassDefFoundError: aQute.lib.utf8properties.UTF8Properties not found, parent: AntClassLoader[...ace/cnf/plugins/biz.aQute.bnd/biz.aQute.bnd-2.2.0.jar] urls:[...ace/cnf/cache/biz.aQute.launcher/biz.aQute.launcher-1.4.0.jar] exception:java.lang.ClassNotFoundException: aQute.lib.utf8properties.UTF8Properties at aQute.bnd.osgi.Processor$CL.loadClass(Processor.java:1280) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2663) at java.lang.Class.getConstructor0(Class.java:3067) at java.lang.Class.getConstructor(Class.java:1817) ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-514) Upgrade to Dependency Manager 4
Marcel Offermans created ACE-514: Summary: Upgrade to Dependency Manager 4 Key: ACE-514 URL: https://issues.apache.org/jira/browse/ACE-514 Project: ACE Issue Type: Improvement Components: Architecture Reporter: Marcel Offermans The Apache Felix project recently released Dependency Manager 4 (the current release is 4.0.1). This upgrade fixes some concurrency issues, cleans up the API and support concurrency a lot better than before, resulting in faster startup times. It would be good to upgrade to this version, even though a couple of small things have changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-513) Improve workspace API
[
https://issues.apache.org/jira/browse/ACE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369432#comment-14369432
]
Marcel Offermans commented on ACE-513:
--
I agree completely with the first three bullets.
I am not a big fan of creating multiple commands for the same things.
Especially since the Gogo shell already provides an alias command that you can
use if you don't like the default command names.
Improve workspace API
-
Key: ACE-513
URL: https://issues.apache.org/jira/browse/ACE-513
Project: ACE
Issue Type: Improvement
Components: Client Repository
Affects Versions: 2.0.1
Reporter: J.W. Janssen
The current workspace API has a couple of drawbacks that makes it less
efficient when used in scripts. For example, the create methods ({{c*}}) do
not all return the created repository object, needing a lookup if you want to
do other stuff with that repository object after creation.
A list of proposed changes:
* let the create methods return the created object;
* the {{da}} method should accept an {{ArtifactObject}} instead of an
{{RepositoryObject}} (conform the other delete methods);
* {{lr}} and {{lrp}} both do the same thing: list resource processors. Remove
{{lr}} in favour of {{lrp}};
* expose the {{createArtifact}}, {{createFeature}}, etc from
{{WorkspaceImpl}} as this makes it easier to read in scripts (the shorthand
versions are useful when working directly in gogo shell).
Any thoughts, remarks?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Deleted] (ACE-510) a
[ https://issues.apache.org/jira/browse/ACE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-510: - a - Key: ACE-510 URL: https://issues.apache.org/jira/browse/ACE-510 Project: ACE Issue Type: Bug Reporter: C4 Priority: Trivial a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-508) When rolling back the cause is not shown in the target's log
[ https://issues.apache.org/jira/browse/ACE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278853#comment-14278853 ] Marcel Offermans commented on ACE-508: -- Correct, the agent running on the target will use the LogService if that is available locally. So if you use the ace-launcher.jar with the -v option, or have some other means to view the log, you can see such information there. The audit log in ACE however only logs success: false when a deployment package installation/update fails. Adding the cause would make sense, as that indeed gives people looking at the audit log on the ACE server (through the UI or some other means) a better overview of what is going on. If we can add the cause to the event as a property and then record that extra property in the audit log, that should be enough. When rolling back the cause is not shown in the target's log Key: ACE-508 URL: https://issues.apache.org/jira/browse/ACE-508 Project: ACE Issue Type: Improvement Reporter: Alexander Broekhuis Priority: Minor Currently the Log of a target will show that deployment of a package has failed, but it does not show a cause or reason of the failure. For resolving the problem, this is needed. For example, if a ResourceProcessor fails with a ResourceProcessorException, that exception including the message could be added to the log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-506) [[CLICKLIVE]]Stoke City vs Arsenal live stream football
[ https://issues.apache.org/jira/browse/ACE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-506: - [[CLICKLIVE]]Stoke City vs Arsenal live stream football - Key: ACE-506 URL: https://issues.apache.org/jira/browse/ACE-506 Project: ACE Issue Type: New JIRA Project Reporter: jon watson Watch Washington Nationals vs Atlanta Braves Live Online espngowatchespnidwashingtonnationalsvsatlantabraves Arsenal v Stoke City by live coverage of Sunday's Premier League game between Arsenal and Stoke City Arsenal vs Stoke City Date Time Live Stream TV Info and Preview Bleacher Report Arsenal vs Stoke City Premier League 201415 Where to watch live preview betting odds and possible XI International Business Times UK More news for Arsenal vs Stoke City live Watch Arsenal vs Stoke City live stream free ronaldo7netvideosportslivesportslivestreamhtml Watch Arsenal vs Stoke City stream Watch this game live and online for free Barclays Premier League January 11 2015 Arsenal vs Stoke City Date Time Live Stream TV Info and bleacherreport2324769arsenalvsstokecitydatetimelivestrea Stoke City will travel to the Emirates Stadium on Sunday hoping to claim what would be just their firstever away win against Arsenal in the Watch Arsenal vs Stoke City Live Stream free online barcelonastreamlivearsenallivestreamchannel1 Watch Arsenal vs Stoke Stream online Barclays Premier League Live Date Time 11 Jan 2015 Free Sports Online Live Streaming and Highlights Channel Live Schedule Arsenal Player playerarsenal › Home › Schedule 18 MEYLER DAVID Schedule Live at 1515 PostMatch Show Live at 1330 Arsenal v Stoke City LIVE Live at 1300 PreMatch Show Home · Schedule Arsenal vs Stoke City TV Channel Live Stream Info ibtimes › Sports › Soccer Arsenal can move up the EPL table with a victory over Stoke Sunday Petition · LIVE SOCCER~``~ Arsenal vs Stoke city live httpschangeorgsdfghjgbvcxzlivesoccerarsenalvsstokecit I think your are surfing internet for get your favorite teams match Arsenal vs Stoke city Season 2015 streaming TV link directly on your desktop Live Extra Schedule NBC Sports nbcsportsliveextraschedule WATCH LIVE College hockey Harvard vs All Games Available on Live Extra FOLLOW LIVE Russell Wilson answered Carolina's score with one of his own and the Seahwks took a Man City lose ground on Chelsea with Everton draw Arsenal vs Stoke City live stream Time TV schedule and sbnationarsenalstokecity2015epltimetvschedulelive Arsenal take on Stoke on Sunday smarting from a defeat to Southampton in their last league outing Arsenal vs Stoke City Live Online EPL Soccer httpsredditrarsenalstokecityments2s1h1a Arsenal vs Stoke City Live Streaming Soccer (Barclays Premier League) Watch all the games highlights and interviews live on your Laptop or Searches related to Arsenal vs Stoke City live watch arsenal vs stoke city live arsenal vs stoke city highlights arsenal vs stoke city video arsenal vs stoke tv arsenal vs stoke city 2010 arsenal vs stoke premier league arsenal v stoke video stoke v arsenal score Live Game panion Atlanta logo Atlanta Utah Q4 tv SportSouth ra 929 FM The Game Live Game panion Friday vs Washington logo image \Washington Wizards vs Atlanta Hawks Live StreamWatch Video for Washington at Atlanta live►► youtubewatch?vu6tQ71QEL3E Uploaded by Donald Clint Washington Wizards vs Atlanta Hawks Live StreamWatch Online NBA Basketball a hrefchannel Red Bull Battle Grounds About battlegroundsredbull of the world's best professional StarCraft 2 players duke it out live in Washington This year's circuit notched stops in Atlanta and Detroit in addition to North Searches related to Washington at Atlanta live washington atlanta promise washington atlanta bus washington atlanta high school washington atlanta hudl washington atlanta flights washington atlanta preview washington atlanta distance washington atlanta promise summary -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-504) Exodus: Gods And Kings en streaming VF HD DVDRIP
[ https://issues.apache.org/jira/browse/ACE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-504: - Exodus: Gods And Kings en streaming VF HD DVDRIP Key: ACE-504 URL: https://issues.apache.org/jira/browse/ACE-504 Project: ACE Issue Type: Bug Reporter: biboy man Exodus: Gods And Kings en streaming VF HD DVDRIP, ~regarder ~ Regarder Exodus Gods and Kings Film, Regarder Exodus Gods and Kings Streaming Film en francais Regarder Exodus Gods and Kings Streaming Film en francais - http://worldwidemovies.nation2.com/index.php?page=1258933296 Exodus Gods And Kings Exodus Gods And Kings film Exodus Gods And Kings film 2014 Exodus Gods And Kings streaming gratuit Exodus Gods And Kings en streaming VF Exodus Gods And Kings voir en streaming gratuit Exodus Gods And Kings film complet en Français Exodus Gods And Kings film en entier Exodus Gods And Kings film complet en Français Exodus Gods And Kings film complet Exodus Gods And Kings complet Exodus Gods And Kings en entier Exodus Gods And Kings film entier Exodus Gods And Kings streaming Exodus Gods And Kings 2014 télécharger regarder Exodus Gods And Kings en streaming Exodus Gods And Kings youtube film entier Exodus Gods And Kings streaming hd Exodus Gods And Kings streaming en entier Exodus Gods And Kings streaming film en entier streaming VF Exodus Gods And Kings streaming en entier gratuit Exodus Gods And Kings gratuit Exodus Gods And Kings Regarder Exodus Gods And Kings Regarder Gratuitment Exodus Gods And Kings regarder film Exodus Gods And Kings regarder film Online Exodus Gods And Kings regarder film en ligne Exodus Gods And Kings regarder film streaming Gratuitment Exodus Gods And Kings film entier streaming complet Exodus Gods And Kings Film Complet Streaming entièrement en Français HD Exodus Gods And Kings Film Complet Streaming VF Entier Français Exodus Gods And Kings En Entier Streaming VF Exodus Gods And Kings film gratuit Exodus Gods And Kings film Online Exodus Gods And Kings film en ligne Exodus Gods And Kings entier streaming Exodus Gods And Kings en entier film Exodus Gods And Kings en entier online Exodus Gods And Kings en entier en ligne Exodus Gods And Kings en entier Online Exodus Gods And Kings télécharger torrent lien Exodus Gods And Kings Gratuitment Film En Ligne Exodus Gods And Kings en entier VF Exodus Gods And Kings en entier VF en Français Exodus Gods And Kings télécharger gratuit Exodus Gods And Kings en ligne Exodus Gods And Kings streaming hd gratuit Exodus Gods And Kings dvdrip Exodus Gods And Kings film streaming en Français Exodus Gods And Kings film en entier streaming VF télécharger Exodus Gods And Kings gratuit film en entier télécharger Exodus Gods And Kings film en entier télécharger Exodus Gods And Kings gratuit film complet regarder Exodus Gods And Kings complètement en français regarder Exodus Gods And Kings film en entier gratuit regarder Exodus Gods And Kings film en entier regarder Exodus Gods And Kings en français regarder Exodus Gods And Kings le film complet Exodus Gods And Kings VF film Exodus Gods And Kings en ligne Exodus Gods And Kings film complet fr Exodus Gods And Kings streaming VF Exodus Gods And Kings sous-titre Exodus Gods And Kings film complet en ligne Exodus Gods And Kings gratuit Exodus Gods And Kings télécharger Exodus Gods And Kings trailer Exodus Gods And Kings bande-anounce Exodus Gods And Kings Français Exodus Gods And Kings fr Exodus Gods And Kings film en ligne HD Exodus Gods And Kings double en Français Exodus Gods And Kings dvd Exodus Gods And Kings youtube film entier Exodus Gods And Kings en ligne gratuit Exodus Gods And Kings regarder en ligne Exodus Gods And Kings film Exodus Gods And Kings movie Exodus Gods And Kings stream Exodus Gods And Kings VF Exodus Gods And Kings DVDRip torrent Exodus Gods And Kings allocine Exodus Gods And Kings dailymotion Exodus Gods And Kings metacafe Exodus Gods And Kings en streaming gratuit Exodus Gods And Kings bande annonce Exodus Gods And Kings sortie Exodus Gods And Kings streaming en Français -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-499) AceObrRepository doesn't work for repositories that require authentication
[ https://issues.apache.org/jira/browse/ACE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14233655#comment-14233655 ] Marcel Offermans commented on ACE-499: -- A possible enhancement of my proposed solution would be to proceed as follows if no BundleContext could be obtained: # Try to find a system property called connectionfactory and instantiate the class mentioned there. Inject that in the component. # If no system property is found, fallback to a default factory (that probably does not support authentication). TBH it's about time Bnd is refactored to use OSGi itself. :) AceObrRepository doesn't work for repositories that require authentication -- Key: ACE-499 URL: https://issues.apache.org/jira/browse/ACE-499 Project: ACE Issue Type: Bug Affects Versions: 2.0.1 Reporter: Bram Pouwelse The AceObrRepository (at least in the way it's used in the gogo support functions) doesn't support using a repository that requires authentication. I've tried adding a Registry to the plugin to provide a aQute.bnd.deployer.http.HttpBasicAuthURLConnector, this resolves the issue for read actions but the upload method still doesn't work. The UrlConnector interface currently only supports read actions so making this work would require a change in bnd. Discussed this issue with [~marrs], he proposed to obtain a BundleContext using FrameworkUtil to retrieve the Ace ConnectionFactory service. A possible drawback of this solution would be that this doesn't work in case the AceObrRepository is used from bnd(tools) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (ACE-498) 9X6!Watch Geordie Shore Season 9 Episode 6 Live Stream Free Video Replay Online
[ https://issues.apache.org/jira/browse/ACE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans deleted ACE-498: - 9X6!Watch Geordie Shore Season 9 Episode 6 Live Stream Free Video Replay Online --- Key: ACE-498 URL: https://issues.apache.org/jira/browse/ACE-498 Project: ACE Issue Type: Bug Reporter: rose rosal Watch the latest cinema movies online at Free Movie Linker, the best website of choice for streaming movies online HD free without the need to download or install any software. Instantly stream and watch movie content with the highest quality links or browse through our comprehensive movie library providing you with endless hours of fun! Video » http://w.atch.me/WpCTFx Video » http://w.atch.me/WpCTFx It’s been a while since we saw Charlotte Crosby’s naked body on Geordie Shore so tonight’s show will come as a bit of a treat to some. The Geordie lot are staying on a tour bus as they venture out to Gloucestershire for their latest Tash On Tours and with no shower on board Char was forced to look elsewhere for her morning freshen up. Charlotte manages to blag a shower in a nearby pub but finds herself back in hot water when she returns to the bus… ‘Great – the tash on tours bus is locked and the driver is nowhere to be seen,’ she explains. And bystander James is not amused… ‘F**k me, I only nipped into the pub for a pre-work pint! I come out and Charlotte’s naked with her f**ny out. What’s going on?!’ he quips. ‘Great, now here’s James with a massive gormless look on his face! What, James, have you never seen a woman in the nig before? Cock!’ adds Char. But that’s not the worst of it. Charlotte flies in to a rage when she spots Gaz chatting up another girl that night. Expect fireworks, people! It was nearly four years ago that the cast posed in a hot tub on the Quayside to launch the much talked about MTV show and next week Geordie Shore is back for its ninth series. Here’s all you need to know about the latest goings on in Newcastle’s wildest house! When does the new series air? Geordie Shore series 9 will begin at 10pm on MTV on Tuesday October 28. Who is going to be in it? All of the usual suspects are back for more Jager-fuelled antics which means that for the lasses there’s Vicky Pattinson, Charlotte Crosby, Holly Hagan and Marnie Simpson and for the lads we’ll be welcoming Gaz Beadle, James Tindale, Scott Timlin, Aaron Chalmers and Kyle Christie back onto our screens again. What is going to happen this time round? The series nine action will take place within the same four walls as its predecessors and there’s sure to be plenty of nights out, arguments and romance dramas as per usual but there will be one major difference- this time there is a head of house. Step forward Queen Vicky, who has always seen herself as the one who rules the roost so is set to revel in her newly instated position of power. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-495) LogStore creates the wrong IDs when there are no events but a lowest ID is set
Marcel Offermans created ACE-495: Summary: LogStore creates the wrong IDs when there are no events but a lowest ID is set Key: ACE-495 URL: https://issues.apache.org/jira/browse/ACE-495 Project: ACE Issue Type: Bug Components: Log Reporter: Marcel Offermans If you have events in the LogStore, and then set the lowest ID to a value higher than any of the existing event IDs, and then create another event, it will get the wrong ID because for an empty store, the lowest ID is ignored when generating a new ID. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-495) LogStore creates the wrong IDs when there are no events but a lowest ID is set
[ https://issues.apache.org/jira/browse/ACE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-495. -- Resolution: Fixed Fix Version/s: next Assignee: Marcel Offermans Committed a fix. LogStore creates the wrong IDs when there are no events but a lowest ID is set -- Key: ACE-495 URL: https://issues.apache.org/jira/browse/ACE-495 Project: ACE Issue Type: Bug Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next If you have events in the LogStore, and then set the lowest ID to a value higher than any of the existing event IDs, and then create another event, it will get the wrong ID because for an empty store, the lowest ID is ignored when generating a new ID. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-494) When the lowest ID in a LogStore is set, in some cases ranges are returned that don't take that into account.
Marcel Offermans created ACE-494: Summary: When the lowest ID in a LogStore is set, in some cases ranges are returned that don't take that into account. Key: ACE-494 URL: https://issues.apache.org/jira/browse/ACE-494 Project: ACE Issue Type: Bug Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans When the lowest ID in a LogStore is set, in some cases ranges are returned that don't take that into account. For example, if you had 1-20 in the store, and then set the lowest ID to 20, you should end up with just 20 (and when you fetch the events that is indeed what you get) but the range returned still reports 1-20. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-493) When adding an out of sequence event to a LogStore, it gets cleared.
Marcel Offermans created ACE-493: Summary: When adding an out of sequence event to a LogStore, it gets cleared. Key: ACE-493 URL: https://issues.apache.org/jira/browse/ACE-493 Project: ACE Issue Type: Bug Components: Log Affects Versions: 2.0.1 Reporter: Marcel Offermans Assignee: Marcel Offermans In normal cases, log events get added in sequence to a LogStore, but if they don't the log gets cleared by accident. Analysis of this bug shows that in that case, if you set no limit on the total number of events in the store, the events get deleted because it thinks it should have a limit of zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-493) When adding an out of sequence event to a LogStore, it gets cleared.
[ https://issues.apache.org/jira/browse/ACE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-493. -- Resolution: Fixed Committed a fix. When adding an out of sequence event to a LogStore, it gets cleared. Key: ACE-493 URL: https://issues.apache.org/jira/browse/ACE-493 Project: ACE Issue Type: Bug Components: Log Affects Versions: 2.0.1 Reporter: Marcel Offermans Assignee: Marcel Offermans In normal cases, log events get added in sequence to a LogStore, but if they don't the log gets cleared by accident. Analysis of this bug shows that in that case, if you set no limit on the total number of events in the store, the events get deleted because it thinks it should have a limit of zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-488) Upload of Artifact fails w/ null message
[ https://issues.apache.org/jira/browse/ACE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14204567#comment-14204567 ] Marcel Offermans commented on ACE-488: -- [~bjoern.petri], any update on this or can I close the issue? Upload of Artifact fails w/ null message Key: ACE-488 URL: https://issues.apache.org/jira/browse/ACE-488 Project: ACE Issue Type: Bug Reporter: Bjoern Petri Attachments: remote_service_admin_http.jar, screenshot.png The upload of the attached artifact fails with an error message saying All 1 Artifacts failed - null. I am not sure what is different from this artifact than from other artifacts - but it would already help to get a proper error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-489) submit button is disabled.
[ https://issues.apache.org/jira/browse/ACE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14204596#comment-14204596 ] Marcel Offermans commented on ACE-489: -- [~srinu], any update on this or can I close the issue? submit button is disabled. -- Key: ACE-489 URL: https://issues.apache.org/jira/browse/ACE-489 Project: ACE Issue Type: Bug Components: Build Affects Versions: 2.0.1 Environment: win7 Reporter: srinu Labels: build Fix For: 2.0.1 Original Estimate: 24h Remaining Estimate: 24h after entering user details the submit button is diaabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-492) Update the project to use Bndtools 2.4.0
Marcel Offermans created ACE-492: Summary: Update the project to use Bndtools 2.4.0 Key: ACE-492 URL: https://issues.apache.org/jira/browse/ACE-492 Project: ACE Issue Type: Improvement Components: Build Reporter: Marcel Offermans Bndtools 2.4.0 has just been released, so we should probably spend some time upgrading the ACE build to work with it. This can probably be done in two steps: # Ensure that the current build works with 2.4.0. # Migrate to gradle, as that is the new build system for 2.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-488) Upload of Artifact fails w/ null message
[ https://issues.apache.org/jira/browse/ACE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195933#comment-14195933 ] Marcel Offermans commented on ACE-488: -- You should use the log command in the shell, and if that does not work, try turning on debug logging first as explained here (at the bottom): http://felix.apache.org/documentation/subprojects/apache-felix-log.html Upload of Artifact fails w/ null message Key: ACE-488 URL: https://issues.apache.org/jira/browse/ACE-488 Project: ACE Issue Type: Bug Reporter: Bjoern Petri Attachments: remote_service_admin_http.jar, screenshot.png The upload of the attached artifact fails with an error message saying All 1 Artifacts failed - null. I am not sure what is different from this artifact than from other artifacts - but it would already help to get a proper error message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-490) Add support for setting a lowest event ID in the server LogStore
Marcel Offermans created ACE-490: Summary: Add support for setting a lowest event ID in the server LogStore Key: ACE-490 URL: https://issues.apache.org/jira/browse/ACE-490 Project: ACE Issue Type: Improvement Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans Currently, the server LogStore can only be configured to either hold on to all events, or set a limit (per log). In some cases it would make sense to be able to set the lowest ID that the store should hold on to. A sample use case would be when events get processed and can be discarded when they have been processed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-491) Add support for propagating the lowest ID
Marcel Offermans created ACE-491: Summary: Add support for propagating the lowest ID Key: ACE-491 URL: https://issues.apache.org/jira/browse/ACE-491 Project: ACE Issue Type: Improvement Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans In ACE-490 support is added for setting a lowest event ID for the server LogStore. In some cases it makes sense to propagate such a setting across the network (when synchronizing logs). This issue is about adding support to the servlet and sync task for doing this (in different modes: none, push, pull, pushpull). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-489) submit button is disabled.
[ https://issues.apache.org/jira/browse/ACE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188213#comment-14188213 ] Marcel Offermans commented on ACE-489: -- Can you clarify what steps you took, what you were expecting and what actually happened? I tried adding a new user and that seems to work. I do not know why you expect the submit button to become active. It is for submitting changes to the artifacts, features, distributions and targets so it is unrelated to user management. submit button is disabled. -- Key: ACE-489 URL: https://issues.apache.org/jira/browse/ACE-489 Project: ACE Issue Type: Bug Components: Build Affects Versions: 2.0.1 Environment: win7 Reporter: srinu Labels: build Fix For: 2.0.1 Original Estimate: 24h Remaining Estimate: 24h after entering user details the submit button is diaabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-488) Upload of Artifact fails w/ null message
[
https://issues.apache.org/jira/browse/ACE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181435#comment-14181435
]
Marcel Offermans commented on ACE-488:
--
Checked the jar file, and its structure looks okay: the manifest is the first
entry.
Checked the manifest, and what I miss is a header that indicates the version
of the manifest (introduced in OSGi R4):
{code}
Bundle-ManifestVersion: 2
{code}
I think that could be the reason why the UI complains. If you use the shell,
there are different ways to upload an artifact and depending on the way you
choose, you can circumvent the file type checks that the UI always performs.
That explains why you can make it work with the shell.
[~bjoern.petri], could you take a look if this is indeed the issue?
Upload of Artifact fails w/ null message
Key: ACE-488
URL: https://issues.apache.org/jira/browse/ACE-488
Project: ACE
Issue Type: Bug
Reporter: Bjoern Petri
Attachments: remote_service_admin_http.jar, screenshot.png
The upload of the attached artifact fails with an error message saying All 1
Artifacts failed - null. I am not sure what is different from this artifact
than from other artifacts - but it would already help to get a proper error
message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ACE-486) Add a method to the server LogStore to create new events
[ https://issues.apache.org/jira/browse/ACE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-486. -- Resolution: Fixed Implemented this, and added a test for it. Add a method to the server LogStore to create new events Key: ACE-486 URL: https://issues.apache.org/jira/browse/ACE-486 Project: ACE Issue Type: Improvement Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans Currently, the server based LogStore has a service interface that was designed to only support replication scenarios. However, in some cases it could be beneficial if this store also supported adding new events, such as when a server or relay also wants to log audit data (or something else). Therefore it makes sense to support a method to create new events, similar to the method that is available in the target LogStore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-485) Extend the LogSyncTask configuration to only synchronize a single targetID
Marcel Offermans created ACE-485: Summary: Extend the LogSyncTask configuration to only synchronize a single targetID Key: ACE-485 URL: https://issues.apache.org/jira/browse/ACE-485 Project: ACE Issue Type: Improvement Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans Currently, the server based LogSyncTask will always try to synchronize all logs for all targets. In some scenarios it might be of benefit to allow synchronization of only a single target log (or a list). That allows us to setup replication scenarios where not everything goes to every node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-485) Extend the LogSyncTask configuration to only synchronize a single targetID
[ https://issues.apache.org/jira/browse/ACE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-485. -- Resolution: Fixed Implemented and committed code for this. Extend the LogSyncTask configuration to only synchronize a single targetID -- Key: ACE-485 URL: https://issues.apache.org/jira/browse/ACE-485 Project: ACE Issue Type: Improvement Components: Log Reporter: Marcel Offermans Assignee: Marcel Offermans Currently, the server based LogSyncTask will always try to synchronize all logs for all targets. In some scenarios it might be of benefit to allow synchronization of only a single target log (or a list). That allows us to setup replication scenarios where not everything goes to every node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACE-487) Cleaning up the LogStore does not work.
Marcel Offermans created ACE-487: Summary: Cleaning up the LogStore does not work. Key: ACE-487 URL: https://issues.apache.org/jira/browse/ACE-487 Project: ACE Issue Type: Bug Components: Log Affects Versions: 2.0.1 Reporter: Marcel Offermans Assignee: Marcel Offermans Even though we have a test for it, there is a bug in cleaning up the LogStore. It does not correctly truncate the number of events to the maximum number that is configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-487) Cleaning up the LogStore does not work.
[ https://issues.apache.org/jira/browse/ACE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-487. -- Resolution: Fixed Fixed. Cleaning up the LogStore does not work. --- Key: ACE-487 URL: https://issues.apache.org/jira/browse/ACE-487 Project: ACE Issue Type: Bug Components: Log Affects Versions: 2.0.1 Reporter: Marcel Offermans Assignee: Marcel Offermans Even though we have a test for it, there is a bug in cleaning up the LogStore. It does not correctly truncate the number of events to the maximum number that is configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (ACE-483) Daemon Script + Managed Shutdown of Targets
[ https://issues.apache.org/jira/browse/ACE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans reopened ACE-483: -- Forgot to add two folders. Daemon Script + Managed Shutdown of Targets --- Key: ACE-483 URL: https://issues.apache.org/jira/browse/ACE-483 Project: ACE Issue Type: Improvement Components: Launcher Reporter: Niclas Hedhman Assignee: Marcel Offermans Attachments: ace-1.patch I am submitting a patch for a. The Tomcat start/stop script for daemon execution of the ACE Management Agent. b. Rename of the run-target/ project to run-develop/ and let the target.jar be moved to develop/debug-target.jar in the distribution. c. run-target/ now contains the script in a) and an ace.policy file which defaults to AllPermission, for people to use via the -security argument. It ends up with a target/bin and target/conf directory in the dist zip. d. Changes to some code that doesn't comply with stricter Java Generics compiler in Java8/Java9. One can't have Properties sent to a method that takes DictionaryString,?. Not exhaustive change across all modules. e. Refactored some code to get rid of some Warnings from the build output. Such as the OptionBuilder. f. Bouncing of baselines that BndTools is shouting about. I am not particularly familiar with BndTools, and uncertain how the run-target should be set up. Perhaps it shouldn't exist at all, and that the script+conf should sit in the launcher sub-project instead. Assistance is greatly appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-483) Daemon Script + Managed Shutdown of Targets
[ https://issues.apache.org/jira/browse/ACE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-483. -- Resolution: Fixed Committed the missing scripts and conf folders. Daemon Script + Managed Shutdown of Targets --- Key: ACE-483 URL: https://issues.apache.org/jira/browse/ACE-483 Project: ACE Issue Type: Improvement Components: Launcher Reporter: Niclas Hedhman Assignee: Marcel Offermans Attachments: ace-1.patch I am submitting a patch for a. The Tomcat start/stop script for daemon execution of the ACE Management Agent. b. Rename of the run-target/ project to run-develop/ and let the target.jar be moved to develop/debug-target.jar in the distribution. c. run-target/ now contains the script in a) and an ace.policy file which defaults to AllPermission, for people to use via the -security argument. It ends up with a target/bin and target/conf directory in the dist zip. d. Changes to some code that doesn't comply with stricter Java Generics compiler in Java8/Java9. One can't have Properties sent to a method that takes DictionaryString,?. Not exhaustive change across all modules. e. Refactored some code to get rid of some Warnings from the build output. Such as the OptionBuilder. f. Bouncing of baselines that BndTools is shouting about. I am not particularly familiar with BndTools, and uncertain how the run-target should be set up. Perhaps it shouldn't exist at all, and that the script+conf should sit in the launcher sub-project instead. Assistance is greatly appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-478) Disable baselining for agent.launcher project
[
https://issues.apache.org/jira/browse/ACE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161833#comment-14161833
]
Marcel Offermans commented on ACE-478:
--
A review of the underlying issues shows that these have been resolved in
Bnd/Bndtools. That leaves us with the question if we want to leverage those
solutions and re-enable baselining for the launcher. [~jajans] what do you
think?
Disable baselining for agent.launcher project
-
Key: ACE-478
URL: https://issues.apache.org/jira/browse/ACE-478
Project: ACE
Issue Type: Improvement
Reporter: J.W. Janssen
Priority: Blocker
The baseline support in Bndtools has a bug that prevents the
{{agent.launcher}} project to properly baseline.
Apparently, Bndtools verifies the timestamps of embedded resources and since
the launcher embeds the latest version of the ACE agent (with a different
timestamp) this will always yield baseline errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACE-423) Remove the FileBasedProvider
[ https://issues.apache.org/jira/browse/ACE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161837#comment-14161837 ] Marcel Offermans commented on ACE-423: -- I think that is a good suggestion. Remove the FileBasedProvider Key: ACE-423 URL: https://issues.apache.org/jira/browse/ACE-423 Project: ACE Issue Type: Bug Reporter: Marcel Offermans The FileBasedProvider was a bundle we used in the early days of ACE to get started quickly with a very simple file based repository. The code for that has since been replaced by the RepositoryBasedProvider. I propose we remove support for the FileBasedProvider completely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-229) Expose OBR metadata through service
[ https://issues.apache.org/jira/browse/ACE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161846#comment-14161846 ] Marcel Offermans commented on ACE-229: -- This feature has been open for quite some time. I am not confident it is something we really need. [~jajans] what's your take on this, since you brought it up? Expose OBR metadata through service --- Key: ACE-229 URL: https://issues.apache.org/jira/browse/ACE-229 Project: ACE Issue Type: New Feature Components: OBR Reporter: J.W. Janssen Priority: Minor You can put and retrieve individual bundles to/from the OBR, but there's no means to get/query the metadata of that repository other than by manually parsing the repository.xml file. It would be handy if the metadata of an OBR is exposed as service, so that, for example, the current Vaadin client can use it to show its contents. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACE-481) SVN trunk does not compile
[ https://issues.apache.org/jira/browse/ACE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans closed ACE-481. Resolution: Fixed Thanks for confirming that! SVN trunk does not compile -- Key: ACE-481 URL: https://issues.apache.org/jira/browse/ACE-481 Project: ACE Issue Type: Bug Reporter: Stephen Evanchik I checked out the svn trunk and attempted an ant build from the command-line which failed: [javac] 67 problems (67 warnings) [copy] Copying 3 files to /home/evanchsa/src/ace.svn/trunk/org.apache.ace.log/bin [copy] Copied 1 empty directory to 1 empty directory under /home/evanchsa/src/ace.svn/trunk/org.apache.ace.log/bin build: [bnd] 1 Errors [bnd] org.apache.ace.log:org.apache.ace.log.server.servlet: The bundle version 1.0.1 is too low, must be at least 1.0.2 BUILD FAILED /home/evanchsa/src/ace.svn/trunk/cnf/build-template.xml:58: The following error occurred while executing this line: /home/evanchsa/src/ace.svn/trunk/cnf/build-template.xml:117: Command build failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACE-482) Uploading an invalid bundle to ACE OBR, makes it unresponsive
[ https://issues.apache.org/jira/browse/ACE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans reassigned ACE-482: Assignee: Marcel Offermans Uploading an invalid bundle to ACE OBR, makes it unresponsive - Key: ACE-482 URL: https://issues.apache.org/jira/browse/ACE-482 Project: ACE Issue Type: Bug Components: OBR Affects Versions: 2.0.1 Reporter: Philipp Buluschek Assignee: Marcel Offermans Priority: Minor Using BndTools and the ACE Repo plugin, I uploaded the bundle com.vaadin.shared.deps:1.0.3. This bundle is malformed, as its manifest contains the version string 15.0.rebased, which is not a valid OSGi version. This results in the ACE server throwing and exception (see below) and not accepting any new uploads. The OBR should probably cleanly reject invalid bundles. Error in /home/virtual/ACE/apache-ace-2.0.1-bin/server-allinone/store : invalid version 15.0.rebased: non-numeric rebased java.lang.IllegalArgumentException: invalid version 15.0.rebased: non-numeric rebased at org.osgi.framework.Version.parseInt(Version.java:170) at org.osgi.framework.Version.init(Version.java:134) at org.osgi.impl.bundle.obr.resource.VersionRange.init(VersionRange.java:52) at org.osgi.impl.bundle.obr.resource.ManifestEntry.addParameter(ManifestEntry.java:97) at org.osgi.impl.bundle.obr.resource.Manifest.getEntries(Manifest.java:215) at org.osgi.impl.bundle.obr.resource.Manifest.entry(Manifest.java:130) at org.osgi.impl.bundle.obr.resource.Manifest.parse(Manifest.java:78) at org.osgi.impl.bundle.obr.resource.Manifest.init(Manifest.java:46) at org.osgi.impl.bundle.obr.resource.BundleInfo.init(BundleInfo.java:63) at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:200) at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:191) at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:191) at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:191) at org.osgi.impl.bundle.bindex.Index.recurse(Index.java:191) at org.osgi.impl.bundle.bindex.Index.main(Index.java:114) at org.apache.ace.obr.metadata.bindex.BIndexMetadataGenerator.generateMetadata(BIndexMetadataGenerator.java:45) at org.apache.ace.obr.storage.file.BundleFileStore.synchronizeMetadata(BundleFileStore.java:73) at org.apache.ace.obr.storage.file.BundleFileStore.get(BundleFileStore.java:81) at org.apache.ace.obr.servlet.BundleServlet.doGet(BundleServlet.java:202) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at org.apache.ace.obr.servlet.BundleServlet.service(BundleServlet.java:289) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:654) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:369) at
[jira] [Assigned] (ACE-475) Ace agent server discovery broken with -s shortcut
[
https://issues.apache.org/jira/browse/ACE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans reassigned ACE-475:
Assignee: Marcel Offermans
Ace agent server discovery broken with -s shortcut
Key: ACE-475
URL: https://issues.apache.org/jira/browse/ACE-475
Project: ACE
Issue Type: Bug
Components: Management Agent
Affects Versions: 2.0.1
Reporter: Arjan Schaaf
Assignee: Marcel Offermans
Fix For: next
When you start an agent with a command like:
{code}
java -jar ace-launcher.jar -a target-name -s
http://ace-server.example.com:8080
{code}
instead of
{code}
java -Dagent.discovery.serverurls=http://ace-server.example.com:8080 -jar
ace-launcher.jar -a target-name
{code}
I'll end up with loggings that indicate that the launcher does not know with
Ace Server to connect with:
{code}
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (feedbackChannel(auditlog)) No identification or server
URL present, cannot send feedback!
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (controller) Sync received retry exception from server.
Rescheduled in 10 seconds...
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ACE-479) Launcher configuration has no effect (regression)
[
https://issues.apache.org/jira/browse/ACE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans reassigned ACE-479:
Assignee: Marcel Offermans
Launcher configuration has no effect (regression)
-
Key: ACE-479
URL: https://issues.apache.org/jira/browse/ACE-479
Project: ACE
Issue Type: Bug
Components: Launcher
Affects Versions: 2.0.1
Reporter: Bram de Kruijff
Assignee: Marcel Offermans
Launcher configuration options have no effect. Seems to be a regression from
ACE-445.
Analysis:
1) Launcher passes configuration of FRAMEWORK properties
2) ConfigurationHandler only looks at SYSTEM properties
Example:
{code}
java -jar org.apache.ace.agent.launcher.felix.jar -a Agent1 -s
http://172.17.8.201:8080
{code}
fails
{code}
java -Dagent.identification.agentid=Agent1
-Dagent.discovery.serverurls=http://172.17.8.201:8080 -jar
org.apache.ace.agent.launcher.felix.jar
{code}
succeeds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ACE-479) Launcher configuration has no effect (regression)
[
https://issues.apache.org/jira/browse/ACE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-479.
--
Resolution: Fixed
Committed a fix.
Launcher configuration has no effect (regression)
-
Key: ACE-479
URL: https://issues.apache.org/jira/browse/ACE-479
Project: ACE
Issue Type: Bug
Components: Launcher
Affects Versions: 2.0.1
Reporter: Bram de Kruijff
Assignee: Marcel Offermans
Launcher configuration options have no effect. Seems to be a regression from
ACE-445.
Analysis:
1) Launcher passes configuration of FRAMEWORK properties
2) ConfigurationHandler only looks at SYSTEM properties
Example:
{code}
java -jar org.apache.ace.agent.launcher.felix.jar -a Agent1 -s
http://172.17.8.201:8080
{code}
fails
{code}
java -Dagent.identification.agentid=Agent1
-Dagent.discovery.serverurls=http://172.17.8.201:8080 -jar
org.apache.ace.agent.launcher.felix.jar
{code}
succeeds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ACE-475) Ace agent server discovery broken with -s shortcut
[
https://issues.apache.org/jira/browse/ACE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-475.
--
Resolution: Cannot Reproduce
Committed a fix.
Ace agent server discovery broken with -s shortcut
Key: ACE-475
URL: https://issues.apache.org/jira/browse/ACE-475
Project: ACE
Issue Type: Bug
Components: Management Agent
Affects Versions: 2.0.1
Reporter: Arjan Schaaf
Assignee: Marcel Offermans
Fix For: next
When you start an agent with a command like:
{code}
java -jar ace-launcher.jar -a target-name -s
http://ace-server.example.com:8080
{code}
instead of
{code}
java -Dagent.discovery.serverurls=http://ace-server.example.com:8080 -jar
ace-launcher.jar -a target-name
{code}
I'll end up with loggings that indicate that the launcher does not know with
Ace Server to connect with:
{code}
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (feedbackChannel(auditlog)) No identification or server
URL present, cannot send feedback!
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (controller) Sync received retry exception from server.
Rescheduled in 10 seconds...
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ACE-484) Add shell commands to delete entities based on filter conditions
Marcel Offermans created ACE-484: Summary: Add shell commands to delete entities based on filter conditions Key: ACE-484 URL: https://issues.apache.org/jira/browse/ACE-484 Project: ACE Issue Type: Improvement Components: Client Repository Affects Versions: 2.0.1 Reporter: Marcel Offermans The shell currently only supports deleting a single entity at a time, based on the entity itself. That often means first doing a query and then deleting the result of that query. By supporting commands that accept filter conditions, this code can be simplified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-484) Add shell commands to delete entities based on filter conditions
[ https://issues.apache.org/jira/browse/ACE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-484. -- Resolution: Fixed Assignee: Marcel Offermans Implemented. Add shell commands to delete entities based on filter conditions Key: ACE-484 URL: https://issues.apache.org/jira/browse/ACE-484 Project: ACE Issue Type: Improvement Components: Client Repository Affects Versions: 2.0.1 Reporter: Marcel Offermans Assignee: Marcel Offermans The shell currently only supports deleting a single entity at a time, based on the entity itself. That often means first doing a query and then deleting the result of that query. By supporting commands that accept filter conditions, this code can be simplified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACE-483) Daemon Script + Managed Shutdown of Targets
[ https://issues.apache.org/jira/browse/ACE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-483. -- Resolution: Fixed Applied the patch, see comments. Daemon Script + Managed Shutdown of Targets --- Key: ACE-483 URL: https://issues.apache.org/jira/browse/ACE-483 Project: ACE Issue Type: Improvement Components: Launcher Reporter: Niclas Hedhman Assignee: Marcel Offermans Attachments: ace-1.patch I am submitting a patch for a. The Tomcat start/stop script for daemon execution of the ACE Management Agent. b. Rename of the run-target/ project to run-develop/ and let the target.jar be moved to develop/debug-target.jar in the distribution. c. run-target/ now contains the script in a) and an ace.policy file which defaults to AllPermission, for people to use via the -security argument. It ends up with a target/bin and target/conf directory in the dist zip. d. Changes to some code that doesn't comply with stricter Java Generics compiler in Java8/Java9. One can't have Properties sent to a method that takes DictionaryString,?. Not exhaustive change across all modules. e. Refactored some code to get rid of some Warnings from the build output. Such as the OptionBuilder. f. Bouncing of baselines that BndTools is shouting about. I am not particularly familiar with BndTools, and uncertain how the run-target should be set up. Perhaps it shouldn't exist at all, and that the script+conf should sit in the launcher sub-project instead. Assistance is greatly appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACE-477) Add remove-headers to main Bnd file
[
https://issues.apache.org/jira/browse/ACE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans reassigned ACE-477:
Assignee: Marcel Offermans
Add remove-headers to main Bnd file
---
Key: ACE-477
URL: https://issues.apache.org/jira/browse/ACE-477
Project: ACE
Issue Type: Improvement
Reporter: J.W. Janssen
Assignee: Marcel Offermans
Priority: Blocker
We should add {{-removeheaders: Bnd-LastModified,Tool,Created-By}} to our
{{ext/defaults.bnd}} file in order to remove all headers that could
potentially lead to unwanted differences in bundles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ACE-477) Add remove-headers to main Bnd file
[
https://issues.apache.org/jira/browse/ACE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-477.
--
Resolution: Fixed
Applied the suggestion.
Also added Private-Package.
Add remove-headers to main Bnd file
---
Key: ACE-477
URL: https://issues.apache.org/jira/browse/ACE-477
Project: ACE
Issue Type: Improvement
Reporter: J.W. Janssen
Assignee: Marcel Offermans
Priority: Blocker
We should add {{-removeheaders: Bnd-LastModified,Tool,Created-By}} to our
{{ext/defaults.bnd}} file in order to remove all headers that could
potentially lead to unwanted differences in bundles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACE-479) Launcher configuration has no effect (regression)
[
https://issues.apache.org/jira/browse/ACE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157155#comment-14157155
]
Marcel Offermans commented on ACE-479:
--
This is related to ACE-475 and the problem at the moment seems to be specific
to discovery. The configuration handler *is* now looking at framework
properties, but the discover handler does not seem to try and pick up any of
those properties.
Launcher configuration has no effect (regression)
-
Key: ACE-479
URL: https://issues.apache.org/jira/browse/ACE-479
Project: ACE
Issue Type: Bug
Components: Launcher
Affects Versions: 2.0.1
Reporter: Bram de Kruijff
Launcher configuration options have no effect. Seems to be a regression from
ACE-445.
Analysis:
1) Launcher passes configuration of FRAMEWORK properties
2) ConfigurationHandler only looks at SYSTEM properties
Example:
{code}
java -jar org.apache.ace.agent.launcher.felix.jar -a Agent1 -s
http://172.17.8.201:8080
{code}
fails
{code}
java -Dagent.identification.agentid=Agent1
-Dagent.discovery.serverurls=http://172.17.8.201:8080 -jar
org.apache.ace.agent.launcher.felix.jar
{code}
succeeds
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACE-475) Ace agent server discovery broken with -s shortcut
[
https://issues.apache.org/jira/browse/ACE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157158#comment-14157158
]
Marcel Offermans commented on ACE-475:
--
The discovery handler is ignoring the framework property that is being set.
Ace agent server discovery broken with -s shortcut
Key: ACE-475
URL: https://issues.apache.org/jira/browse/ACE-475
Project: ACE
Issue Type: Bug
Components: Management Agent
Affects Versions: 2.0.1
Reporter: Arjan Schaaf
Fix For: next
When you start an agent with a command like:
{code}
java -jar ace-launcher.jar -a target-name -s
http://ace-server.example.com:8080
{code}
instead of
{code}
java -Dagent.discovery.serverurls=http://ace-server.example.com:8080 -jar
ace-launcher.jar -a target-name
{code}
I'll end up with loggings that indicate that the launcher does not know with
Ace Server to connect with:
{code}
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (feedbackChannel(auditlog)) No identification or server
URL present, cannot send feedback!
[WARNING] 13:45:34 (discovery) No valid server URL discovered?!
[WARNING] 13:45:34 (controller) Sync received retry exception from server.
Rescheduled in 10 seconds...
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ACE-483) Daemon Script + Managed Shutdown of Targets
[ https://issues.apache.org/jira/browse/ACE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans reassigned ACE-483: Assignee: Marcel Offermans Thanks for submitting this patch, Niclas! Daemon Script + Managed Shutdown of Targets --- Key: ACE-483 URL: https://issues.apache.org/jira/browse/ACE-483 Project: ACE Issue Type: Improvement Components: Launcher Reporter: Niclas Hedhman Assignee: Marcel Offermans Attachments: ace-1.patch I am submitting a patch for a. The Tomcat start/stop script for daemon execution of the ACE Management Agent. b. Rename of the run-target/ project to run-develop/ and let the target.jar be moved to develop/debug-target.jar in the distribution. c. run-target/ now contains the script in a) and an ace.policy file which defaults to AllPermission, for people to use via the -security argument. It ends up with a target/bin and target/conf directory in the dist zip. d. Changes to some code that doesn't comply with stricter Java Generics compiler in Java8/Java9. One can't have Properties sent to a method that takes DictionaryString,?. Not exhaustive change across all modules. e. Refactored some code to get rid of some Warnings from the build output. Such as the OptionBuilder. f. Bouncing of baselines that BndTools is shouting about. I am not particularly familiar with BndTools, and uncertain how the run-target should be set up. Perhaps it shouldn't exist at all, and that the script+conf should sit in the launcher sub-project instead. Assistance is greatly appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-481) SVN trunk does not compile
[ https://issues.apache.org/jira/browse/ACE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137006#comment-14137006 ] Marcel Offermans commented on ACE-481: -- From the looks of it, Jenkins ran out of memory somehow. I have scheduled a fresh build to see if that is still the case and that now failed with a failing test case: https://builds.apache.org/job/ACE-trunk/254/ At the same time, I have tried building ACE locally (trunk) and that worked for me (with Java 7 and 8) by going into the build project and launching: ant build. That works. Then did an ant deeptestng deeptest to run all the tests and that worked on my machine as well. So it seems at least we have a test that fails intermittently and I'm still not sure why the code won't build on your machine, [~evanchsa]. SVN trunk does not compile -- Key: ACE-481 URL: https://issues.apache.org/jira/browse/ACE-481 Project: ACE Issue Type: Bug Reporter: Stephen Evanchik I checked out the svn trunk and attempted an ant build from the command-line which failed: [javac] 67 problems (67 warnings) [copy] Copying 3 files to /home/evanchsa/src/ace.svn/trunk/org.apache.ace.log/bin [copy] Copied 1 empty directory to 1 empty directory under /home/evanchsa/src/ace.svn/trunk/org.apache.ace.log/bin build: [bnd] 1 Errors [bnd] org.apache.ace.log:org.apache.ace.log.server.servlet: The bundle version 1.0.1 is too low, must be at least 1.0.2 BUILD FAILED /home/evanchsa/src/ace.svn/trunk/cnf/build-template.xml:58: The following error occurred while executing this line: /home/evanchsa/src/ace.svn/trunk/cnf/build-template.xml:117: Command build failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACE-478) Disable baselining for agent.launcher project
[
https://issues.apache.org/jira/browse/ACE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998509#comment-13998509
]
Marcel Offermans commented on ACE-478:
--
Added two new issues to that issue in bndtools because the underlying issue is
in bnd (and it's even debatable if it's an issue in bnd or a limitation of zip
and the way baselining works... it's hard to detect this case without a lot of
special code for it).
Disable baselining for agent.launcher project
-
Key: ACE-478
URL: https://issues.apache.org/jira/browse/ACE-478
Project: ACE
Issue Type: Improvement
Reporter: J.W. Janssen
Priority: Blocker
The baseline support in Bndtools has a bug that prevents the
{{agent.launcher}} project to properly baseline.
Apparently, Bndtools verifies the timestamps of embedded resources and since
the launcher embeds the latest version of the ACE agent (with a different
timestamp) this will always yield baseline errors.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (ACE-476) Upgrade the release repo in svn to contain the 2.0.1 bundle artifacts for baselining.
Marcel Offermans created ACE-476: Summary: Upgrade the release repo in svn to contain the 2.0.1 bundle artifacts for baselining. Key: ACE-476 URL: https://issues.apache.org/jira/browse/ACE-476 Project: ACE Issue Type: Bug Components: Build Reporter: Marcel Offermans Assignee: Marcel Offermans Now that 2.0.1 is released, we should start baselining against that release in trunk. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (ACE-474) Clarify our getting started example (running targets)
Marcel Offermans created ACE-474: Summary: Clarify our getting started example (running targets) Key: ACE-474 URL: https://issues.apache.org/jira/browse/ACE-474 Project: ACE Issue Type: Improvement Components: Site Reporter: Marcel Offermans Fix For: next As discussed in this StackOverflow question, we could improve our documentation with some examples of how to run targets: http://stackoverflow.com/questions/23344642/adding-targets-in-apache-ace/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (ACE-471) Package dependencies build phase fails to include ECJ and the baseline repository.
Marcel Offermans created ACE-471: Summary: Package dependencies build phase fails to include ECJ and the baseline repository. Key: ACE-471 URL: https://issues.apache.org/jira/browse/ACE-471 Project: ACE Issue Type: Bug Components: Build Reporter: Marcel Offermans Assignee: Marcel Offermans The 2.0.0 release was just cancelled because these were missing. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (ACE-471) Package dependencies build phase fails to include ECJ and the baseline repository.
[ https://issues.apache.org/jira/browse/ACE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans resolved ACE-471. -- Resolution: Fixed Committed a fix. Double checked the release artifacts on my machine. They build correctly now (after unzipping src and deps). Package dependencies build phase fails to include ECJ and the baseline repository. -- Key: ACE-471 URL: https://issues.apache.org/jira/browse/ACE-471 Project: ACE Issue Type: Bug Components: Build Reporter: Marcel Offermans Assignee: Marcel Offermans The 2.0.0 release was just cancelled because these were missing. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-200) Exception on startup: org.osgi.service.cm.ConfigurationException: additionalObrDownloads : key missing
[ https://issues.apache.org/jira/browse/ACE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-200: - Fix Version/s: next Exception on startup: org.osgi.service.cm.ConfigurationException: additionalObrDownloads : key missing -- Key: ACE-200 URL: https://issues.apache.org/jira/browse/ACE-200 Project: ACE Issue Type: Bug Components: Build Reporter: Denis Koelewijn Assignee: Marcel Offermans Fix For: next On startup of pristine ace-target-devserver the following exception is thrown: 2011.10.31 10:15:52 ERROR - Bundle: org.apache.felix.configadmin - [org.osgi.service.cm.ConfigurationAdmin] - [org.osgi.service.cm.ManagedService, id=45, bundle=30]: Updating configuration property additionalObrDownloads caused a problem: key missing - org.osgi.service.cm.ConfigurationException: additionalObrDownloads : key missing at org.apache.ace.nodelauncher.amazon.AmazonNodeLauncher.getConfigProperty(AmazonNodeLauncher.java:303) at org.apache.ace.nodelauncher.amazon.AmazonNodeLauncher.getConfigProperty(AmazonNodeLauncher.java:295) at org.apache.ace.nodelauncher.amazon.AmazonNodeLauncher.updated(AmazonNodeLauncher.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.felix.dm.InvocationUtil.invokeMethod(InvocationUtil.java:70) at org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl.invokeUpdate(ConfigurationDependencyImpl.java:232) at org.apache.felix.dm.impl.dependencies.ConfigurationDependencyImpl.updated(ConfigurationDependencyImpl.java:190) at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160) at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104) at java.lang.Thread.run(Thread.java:680) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-453) the artefact org.apache.ace.feedback.common is missed in the build/bnd.bnd (dependson)
[ https://issues.apache.org/jira/browse/ACE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-453: - Fix Version/s: next the artefact org.apache.ace.feedback.common is missed in the build/bnd.bnd (dependson) -- Key: ACE-453 URL: https://issues.apache.org/jira/browse/ACE-453 Project: ACE Issue Type: Bug Reporter: Wilfried Sibla Assignee: Marcel Offermans Fix For: next -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-221) It should be possible to remove targets
[ https://issues.apache.org/jira/browse/ACE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-221: - Fix Version/s: next It should be possible to remove targets --- Key: ACE-221 URL: https://issues.apache.org/jira/browse/ACE-221 Project: ACE Issue Type: Improvement Components: UI Reporter: Paul Bakker Assignee: Marcel Offermans Priority: Minor Fix For: next Targets are sometimes used temporarily (e.g. for testing) and it should be possible to remove them afterwards to keep the UI clean over time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-305) Start level problems with devserver
[ https://issues.apache.org/jira/browse/ACE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-305: - Fix Version/s: next Start level problems with devserver --- Key: ACE-305 URL: https://issues.apache.org/jira/browse/ACE-305 Project: ACE Issue Type: Bug Components: Build Reporter: Tuomas Kiviaho Assignee: Marcel Offermans Fix For: next Pax runner script gives followind exception in certain cases. This is easily avoided by lowering start level for required bundles. java.lang.IllegalStateException: Can only register services while bundle is active or activating. at org.apache.felix.framework.Felix.registerService(Felix.java:3209) at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346) at org.apache.felix.http.base.internal.HttpServiceController.register(HttpServiceController.java:135) at org.apache.felix.http.base.internal.DispatcherServlet.init(DispatcherServlet.java:48) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685) at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:164) at org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:115) at org.apache.felix.http.jetty.internal.JettyService.run(JettyService.java:290) at java.lang.Thread.run(Thread.java:662) [INFO] Started jetty 6.1.x at port(s) HTTP:8082 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-462) Event incorrectly handles dictionary parameter
[ https://issues.apache.org/jira/browse/ACE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-462: - Fix Version/s: next Event incorrectly handles dictionary parameter -- Key: ACE-462 URL: https://issues.apache.org/jira/browse/ACE-462 Project: ACE Issue Type: Bug Reporter: J.W. Janssen Assignee: Marcel Offermans Priority: Critical Fix For: next In the construction of org.apache.ace.feedback.Event, a dictionary can be passed that is copied into the created event. However, the code walks through all values of the given dictionary, and handles them as keys, which is not correct. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-443) New management agent fails to install new version correclty
[
https://issues.apache.org/jira/browse/ACE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans updated ACE-443:
-
Fix Version/s: next
New management agent fails to install new version correclty
---
Key: ACE-443
URL: https://issues.apache.org/jira/browse/ACE-443
Project: ACE
Issue Type: Bug
Reporter: Jago de Vreede
Assignee: Marcel Offermans
Fix For: next
There are configuration issues when you create an update with a bundle and
configuration:
Debug output:
*DEBUG* update(properties={org.apache.felix.http.debug=true,
org.osgi.service.http.port=8080, org.apache.felix.log.storeDebug=true,
org.apache.felix.http.enable=true, org.apache.felix.http.timeout=60})
*DEBUG* Updating config org.apache.felix.http with
{org.osgi.service.http.port=8080, org.apache.felix.http.debug=true,
org.apache.felix.http.enable=true, org.apache.felix.http.timeout=60,
org.apache.felix.log.storedebug=true}
*DEBUG* No SynchronousConfigurationListeners to send CM_UPDATED event to.
*DEBUG* No ConfigurationListeners to send CM_UPDATED event to.
*DEBUG* Scheduling task Update: pid=org.apache.felix.http
*DEBUG* UpdateConfiguration(org.apache.felix.http) scheduled
*DEBUG* Running task Update: pid=org.apache.felix.http
*DEBUG* Updating configuration org.apache.felix.http to revision #2
*ERROR* Unexpected problem executing task
java.lang.NullPointerException
at
org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1701)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)
at java.lang.Thread.run(Thread.java:744)
*DEBUG* Registering service [org.osgi.service.cm.ManagedService, id=11,
bundle=7/osgi-dp:org.apache.felix.http.jetty]
*DEBUG* configure(ManagedService [org.osgi.service.cm.ManagedService, id=11,
bundle=7/osgi-dp:org.apache.felix.http.jetty])
*DEBUG* Scheduling task ManagedService Update: pid=[org.apache.felix.http]
*DEBUG* Running task ManagedService Update: pid=[org.apache.felix.http]
*DEBUG* Found cached configuration org.apache.felix.http bound to
osgi-dp:org.apache.felix.http.jetty
*DEBUG* canReceive=true: bundle=osgi-dp:org.apache.felix.http.jetty;
configuration=osgi-dp:org.apache.felix.http.jetty
*DEBUG* Updating service org.apache.felix.http with configuration
org.apache.felix.http@2
*DEBUG* [ManagedService Update: pid=[org.apache.felix.http]] scheduled
There is also a problem when you only install a configuration file (a
rollback occurs):
[INFO] 11:42:00 (controller) Installing streaming deployment update 2.0.0 =
3.0.0
[DEBUG] 11:42:10 (controller) Controller syncing...
[DEBUG] 11:42:10 (controller) Synchronizing feedback channels: [auditlog]
[DEBUG] 11:42:10 (controller) Feedback send succesfully for channel: auditlog
[DEBUG] 11:42:10 (controller) Checking for agent updates...
[DEBUG] 11:42:10 (controller) No need to install update: no newer agent
version available!
[DEBUG] 11:42:10 (controller) Checking for deployment updates...
[DEBUG] 11:42:10 (controller) Need to install update: newer deployment
version available!
[INFO] 11:42:10 (controller) Installing streaming deployment update 2.0.0 =
3.0.0
More information:
Running bundles:
54|Active |1|Apache Felix AutoConf Resource Processor (0.1.5)
263|Active |1|Apache Felix Gogo Runtime (0.10.0)
264|Active |1|Apache Felix Gogo Shell (0.10.0)
265|Active |1|Apache Felix Gogo Command (0.12.0)
267|Active |1|Apache Felix Configuration Admin Service (1.6.0)
268|Active |1|Apache Felix Dependency Manager (3.1.0)
269|Active |1|osgi.cmpn (4.3.1.201210102024)
270|Active |1|Apache Felix EventAdmin (1.3.2)
272|Active |1|Apache Felix Http Jetty (2.2.1)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACE-414) Check for new/already downloaded and completed DPs on startup
[ https://issues.apache.org/jira/browse/ACE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-414: - Fix Version/s: next Check for new/already downloaded and completed DPs on startup - Key: ACE-414 URL: https://issues.apache.org/jira/browse/ACE-414 Project: ACE Issue Type: Improvement Components: Deployment Affects Versions: 1.0.0 Reporter: Wilfried Sibla Assignee: Marcel Offermans Fix For: next if the new agent couldn't install a completely downloaded DP (e.g. caused by a JVM crash/OSGi container restart), the DP isn't installed after restart. The DP is downloadad again. This is not a good solution in embedded scenarios. A complete DP should/could be installed without any online checks. If there already is a new DP version on server side, it could be updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-451) DefaultController does not catch runtime exceptions during installation.
[ https://issues.apache.org/jira/browse/ACE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-451: - Fix Version/s: next DefaultController does not catch runtime exceptions during installation. Key: ACE-451 URL: https://issues.apache.org/jira/browse/ACE-451 Project: ACE Issue Type: Bug Components: Management Agent Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next Attachments: ACE-451.patch The default controller in its various doInstallUpdate(...) methods does not catch runtime exceptions that can occur. In this case, also nothing is logged back to the user. Fix these methods to explicitly catch all exceptions and properly log and respond to them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-426) Client bndrun is missing store config
[
https://issues.apache.org/jira/browse/ACE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans updated ACE-426:
-
Fix Version/s: next
Client bndrun is missing store config
-
Key: ACE-426
URL: https://issues.apache.org/jira/browse/ACE-426
Project: ACE
Issue Type: Bug
Components: Build
Reporter: Bram de Kruijff
Assignee: Marcel Offermans
Fix For: next
The run-client definition is missing some config. As a result clients
launched with this profile (which is used for the binary release) do not have
access to the auditlog.
{code}
g! dm notavail
[35] org.apache.ace.log.server.task
java.lang.Runnable,
org.apache.ace.log.LogSync(taskName=org.apache.ace.log.server.task.LogSyncTask,name=auditlog,description=Syncs
log (name=auditlog, mode=PULL) with a server.) unregistered
org.apache.ace.connectionfactory.ConnectionFactory service required
available
org.apache.ace.log.server.store.LogStore
((objectClass=org.apache.ace.log.server.store.LogStore)(name=auditlog))
service required unavailable
org.apache.ace.discovery.Discovery service required available
org.osgi.service.log.LogService service optional (not tracking)
[37] org.apache.ace.nodelauncher.amazon
org.apache.ace.nodelauncher.NodeLauncher(osgi.command.function={start,stop,properties},osgi.command.scope=node)
unregistered
org.apache.ace.nodelauncher.amazon configuration required unavailable
[39] org.apache.ace.nodelauncher.ui
org.apache.ace.webui.UIExtensionFactory(extension_point=target) unregistered
org.apache.ace.nodelauncher.NodeLauncher service required unavailable
org.osgi.service.log.LogService service optional (not tracking)
[46] org.apache.ace.log.server.store.file
org.apache.ace.log.server.store.LogStore(name=auditlog) unregistered
org.osgi.service.event.EventAdmin service optional (not tracking)
org.apache.ace.log.server.store.filebased configuration required
unavailable
[47] org.apache.ace.log.server.ui
org.apache.ace.webui.UIExtensionFactory(service.ranking=10,extension_point=target)
unregistered
org.apache.ace.log.server.store.LogStore service required unavailable
org.osgi.service.log.LogService service optional (not tracking)
[52] org.apache.ace.gogo
java.lang.Object(osgi.command.function={cleanup},osgi.command.scope=ace-log)
unregistered
org.apache.ace.log.server.store.LogStore service required unavailable
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACE-405) Split out ACE Bnd repository from gogo bundle
[ https://issues.apache.org/jira/browse/ACE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-405: - Fix Version/s: next Split out ACE Bnd repository from gogo bundle - Key: ACE-405 URL: https://issues.apache.org/jira/browse/ACE-405 Project: ACE Issue Type: Bug Components: OBR Reporter: Bram de Kruijff Assignee: Marcel Offermans Fix For: next The AceObrRepository embedded in the gogo bundle can be used as a Bnd(Tools) plugin allowing developers to use an ACE OBR as a writeable/release repository. However, as the gogo bundle embed bnd code this may conflict with other bnd libs on the flat ANT classpath during an offline build. Therefore this could should be split out into a separate clean bundle. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-419) Show how to create a custom agent controller in a unit test.
[ https://issues.apache.org/jira/browse/ACE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-419: - Fix Version/s: next Show how to create a custom agent controller in a unit test. Key: ACE-419 URL: https://issues.apache.org/jira/browse/ACE-419 Project: ACE Issue Type: Test Components: Management Agent Reporter: J.W. Janssen Assignee: Marcel Offermans Fix For: next Show how to use the Agent's API in a custom controller, in which user interaction is more explicit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-429) Upgrade the build to Bndtools 2.2.2
[ https://issues.apache.org/jira/browse/ACE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-429: - Fix Version/s: next Upgrade the build to Bndtools 2.2.2 --- Key: ACE-429 URL: https://issues.apache.org/jira/browse/ACE-429 Project: ACE Issue Type: Improvement Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next As discussed on the mailing list, we want to upgrade to Bndtools 2.2.2 and enable support for baselining. Baselining will give us a lot of tool support to ensure our code (bundles and exported packages) is semantically versioned. To leverage baselining support there are a couple of things we need to do: * We need the to start putting @ProviderType and @ConsumerType annotations on all our APIs. In fact, we need to “retrofit” this to our 1.0.0 release to ensure the baselining works correctly. These annotations are not magically available, but we can add them to the global build path (cnf/ext/defaults.bnd). * We need to keep a copy of all released bundles (the latest version of each) in a repository to baseline against. Because we don’t want our build to break when we’re off-line I propose we put them in a local repository. We probably need to build those artifacts with the Eclipse compiler to prevent problems that will otherwise occur because of differences between ecj and javac so: checkout with Eclipse, build, collect all bundles from generated folders and publish them into the releaserepo in cnf. We also want to add them to the -deps artifact so people can easily get started with a release with baselining enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-448) Continuous deployment does not handle fragments well
[ https://issues.apache.org/jira/browse/ACE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-448: - Fix Version/s: next Continuous deployment does not handle fragments well Key: ACE-448 URL: https://issues.apache.org/jira/browse/ACE-448 Project: ACE Issue Type: Bug Reporter: Bram de Kruijff Assignee: Marcel Offermans Fix For: next When creating a cd snapshot bundles continuous deployment does not consider fragments because it only checks for resource type 'osgi-bundle'. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-161) Create services that complement the tasks in the management agent
[ https://issues.apache.org/jira/browse/ACE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-161: - Fix Version/s: next Create services that complement the tasks in the management agent - Key: ACE-161 URL: https://issues.apache.org/jira/browse/ACE-161 Project: ACE Issue Type: Task Components: Management Agent Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next Currently, the functionality exposed by the management agent is visible via a set of tasks that can be scheduled. Whilst this is a common use case, it would be nice to also expose the same tasks as OSGi services so they can be invoked directly (in cases where a scheduler is not needed or wanted). There are a couple of tasks that can be complemented like this: - deployment - sync logs - subscriptions (still under construction). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-386) Support range headers when providing deployment packages.
[ https://issues.apache.org/jira/browse/ACE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-386: - Fix Version/s: next Support range headers when providing deployment packages. - Key: ACE-386 URL: https://issues.apache.org/jira/browse/ACE-386 Project: ACE Issue Type: Task Components: Deployment Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next When downloading deployment packages, we should report and respect range headers. This is part of our support for resuming partially downloaded deployment packages. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-435) DeploymentServlet does not always set the Content-Length
[
https://issues.apache.org/jira/browse/ACE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans updated ACE-435:
-
Fix Version/s: next
DeploymentServlet does not always set the Content-Length
Key: ACE-435
URL: https://issues.apache.org/jira/browse/ACE-435
Project: ACE
Issue Type: Bug
Components: Deployment
Reporter: J.W. Janssen
Assignee: Marcel Offermans
Fix For: next
The DeploymentServlet currently does not always set the Content-Length of the
deployment package. This makes that the agent cannot correctly determine the
number of bytes it should download and when it is ready downloading.
A quick glance indicates that we might need to leverage the use of
{{ContentRangeResponseWrapper}} for this...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (ACE-203) Include default eclipse settings in svn
[ https://issues.apache.org/jira/browse/ACE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-203: - Fix Version/s: next Include default eclipse settings in svn --- Key: ACE-203 URL: https://issues.apache.org/jira/browse/ACE-203 Project: ACE Issue Type: Improvement Components: Build Reporter: Denis Koelewijn Assignee: Marcel Offermans Fix For: next Attachments: eclipse-cleanup-settings.xml, eclipse-formatter-settings.xml Include default eclipse settings in the repository to simplify following the formatting rules as described on the website. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-370) Using configuration templates fails
[ https://issues.apache.org/jira/browse/ACE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated ACE-370: - Fix Version/s: next Using configuration templates fails --- Key: ACE-370 URL: https://issues.apache.org/jira/browse/ACE-370 Project: ACE Issue Type: Bug Components: Client Repository Affects Versions: 1.0.0 Reporter: Marcel Offermans Assignee: Marcel Offermans Fix For: next When you start using configuration templates, ACE keeps generating new deployments. The cause seems to be that during the generation of new filled out templates, these get uploaded and lost in the OBR. The effect is that another update is triggered. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (ACE-348) Ace server unavailable after (re)start
[
https://issues.apache.org/jira/browse/ACE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans updated ACE-348:
-
Fix Version/s: next
Ace server unavailable after (re)start
--
Key: ACE-348
URL: https://issues.apache.org/jira/browse/ACE-348
Project: ACE
Issue Type: Bug
Environment: ace trunk / linux x64 / java version 1.7.0_17
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Reporter: Bram de Kruijff
Assignee: Marcel Offermans
Fix For: next
Every now and then the server is unavailable over http throwing a 503. It's a
timing issue and seems to be reported at
https://issues.apache.org/jira/browse/FELIX-3846
{code}
HTTP ERROR 503
Problem accessing /ace. Reason:
java.lang.IllegalStateException: Can only register services while bundle
is active or activating.
Caused by:
javax.servlet.UnavailableException: java.lang.IllegalStateException: Can only
register services while bundle is active or activating.
at
org.mortbay.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:415)
at
org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:458)
at
org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:164)
at
org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:115)
at
org.apache.felix.http.jetty.internal.JettyService.run(JettyService.java:290)
at java.lang.Thread.run(Thread.java:722)
{code}
Same problem reported in the log.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
