[jira] [Commented] (KARAF-3286) karaf-maven-plugin does not merge bundle entry with URL parameters

2014-10-15 Thread Ralf Steppacher (JIRA)

[ 
https://issues.apache.org/jira/browse/KARAF-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172093#comment-14172093
 ] 

Ralf Steppacher commented on KARAF-3286:


No, it does not work with 3.0.2 either. The exact line that fails merging looks 
like this:

{code:xml}bundlemvn:${project.groupId}/base/${project.version}/$Export-Package=an.api.package/bundle{code}

The produced feature.xml contains the following two lines:

{code:xml}
bundlemvn:ch.vivates.ams/base/3.0.0-SNAPSHOT/$Export-Package=an.api.package/bundle
bundlemvn:ch.vivates.ams/base/3.0.0-SNAPSHOT/bundle
{code}

 karaf-maven-plugin does not merge bundle entry with URL parameters
 --

 Key: KARAF-3286
 URL: https://issues.apache.org/jira/browse/KARAF-3286
 Project: Karaf
  Issue Type: Bug
  Components: karaf-tooling
Affects Versions: 3.0.1
Reporter: Ralf Steppacher

 If a template contains an entry with URL parameters, e.g.
 {code:xml}bundlewrap:mvn:jboss/jbossall-client/4.2.3.GA/$Bundle-SymbolicName=jbossall-clientamp;Bundle-Version=4.2.3.GA/bundle{code}
 then it is not merged with a maven compile dependency. Instead the resulting 
 feature.xml contains two entries for that bundle.



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


[jira] [Created] (KARAF-3288) karaf script doesn't start on Solaris if JAVA_HOME is not set

2014-10-15 Thread Kevin Earls (JIRA)
Kevin Earls created KARAF-3288:
--

 Summary: karaf script doesn't start on Solaris if JAVA_HOME is not 
set
 Key: KARAF-3288
 URL: https://issues.apache.org/jira/browse/KARAF-3288
 Project: Karaf
  Issue Type: Bug
Affects Versions: 3.0.1
 Environment: Solaris
Reporter: Kevin Earls
Priority: Minor


On Solaris the karat script fails with the error JVM must be greater than 1.6 
if JAVA_HOME is not set.  (On 2.4 it also fails but with the message exec: a 
tracked alias for /usr/bin/java: not found).  

This fails because the locateJava() function depends on the output of `type 
java` to set JAVA_HOME and determine what version of java it's using.  On most 
platforms type java returns something like java is /path/to/java, but on 
solaris it returns java is a tracked alias for /path/to/java

The fix just requires a change to the expression used to chop off the leading 
text.  I will submit a pull request for this.




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


[jira] [Created] (KARAF-3289) Add a while loop command

2014-10-15 Thread Guillaume Nodet (JIRA)
Guillaume Nodet created KARAF-3289:
--

 Summary: Add a while loop command
 Key: KARAF-3289
 URL: https://issues.apache.org/jira/browse/KARAF-3289
 Project: Karaf
  Issue Type: New Feature
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 4.0.0


The loop, combined with the new expression parser from KARAF-3264 will allow 
the following things:

{code}
karaf@root() a = 0 ; while { ((a  10)) } { echo $a ; ((a += 1)) }
0
1
2
3
4
5
6
7
8
9
{code}



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


[jira] [Updated] (KARAF-3264) What is the AND operator in shell:if ?

2014-10-15 Thread Guillaume Nodet (JIRA)

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

Guillaume Nodet updated KARAF-3264:
---
Fix Version/s: 4.0.0

 What is the AND operator in shell:if ?
 --

 Key: KARAF-3264
 URL: https://issues.apache.org/jira/browse/KARAF-3264
 Project: Karaf
  Issue Type: Question
  Components: karaf-documentation, karaf-shell
Affects Versions: 2.3.7
Reporter: Niels Bertram
Assignee: Guillaume Nodet
Priority: Minor
 Fix For: 4.0.0


 I have tried to create an shell:if condition that tests for multiple AND / OR 
 operators but I am unable to find any useful documentation in KARAF or FELIX 
 nor did anyone respond to user forum emails or was there any hint in unit 
 tests as to how to construct a if condition with multiple operants.
 Using the debugger, I can see in {{org.apache.felix.gogo.runtime.Closure}} 
 that there is something amiss when executing my code but I tried quite a few 
 permutations without any luck.
 Example of what I thought the most likely syntax it should be but fail, fail, 
 fail ... any chance someone with some scripting credentials is able to 
 comment? I am offering to write it up with a few examples for the developer 
 documentation!
 {code}
 foo = foo
 bar = bar
 if { ($foo equals foo)($bar equals bar) } { echo yes foo and bar } { 
 echo no foo and bar }
 {code}
 another one I tried:
 {code}
 foo = foo
 bar = bar
 if { $foo equals foo  $bar equals bar } { echo yes foo and bar } { 
 echo no foo and bar }
 {code}
 or this one:
 {code}
 foo = foo
 bar = bar
 if { [ $foo equals foo , $bar equals bar ] } { echo yes foo and bar } { 
 echo no foo and bar }
 {code}



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


[jira] [Commented] (KARAF-3289) Add a while loop command

2014-10-15 Thread Guillaume Nodet (JIRA)

[ 
https://issues.apache.org/jira/browse/KARAF-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172383#comment-14172383
 ] 

Guillaume Nodet commented on KARAF-3289:


Though the code itself does not depend on the expression parser, it's quite 
useless without it.

 Add a while loop command
 

 Key: KARAF-3289
 URL: https://issues.apache.org/jira/browse/KARAF-3289
 Project: Karaf
  Issue Type: New Feature
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 4.0.0


 The loop, combined with the new expression parser from KARAF-3264 will allow 
 the following things:
 {code}
 karaf@root() a = 0 ; while { ((a  10)) } { echo $a ; ((a += 1)) }
 0
 1
 2
 3
 4
 5
 6
 7
 8
 9
 {code}



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


[jira] [Commented] (KARAF-3289) Add a while loop command

2014-10-15 Thread Guillaume Nodet (JIRA)

[ 
https://issues.apache.org/jira/browse/KARAF-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172385#comment-14172385
 ] 

Guillaume Nodet commented on KARAF-3289:


Master: 
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=ad559c07a71f83d86fd832ac756c3b316ebac2ac

 Add a while loop command
 

 Key: KARAF-3289
 URL: https://issues.apache.org/jira/browse/KARAF-3289
 Project: Karaf
  Issue Type: New Feature
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 4.0.0


 The loop, combined with the new expression parser from KARAF-3264 will allow 
 the following things:
 {code}
 karaf@root() a = 0 ; while { ((a  10)) } { echo $a ; ((a += 1)) }
 0
 1
 2
 3
 4
 5
 6
 7
 8
 9
 {code}



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


[jira] [Created] (KARAF-3290) Upgrade to felix gogo runtime 0.14.0

2014-10-15 Thread Guillaume Nodet (JIRA)
Guillaume Nodet created KARAF-3290:
--

 Summary: Upgrade to felix gogo runtime 0.14.0
 Key: KARAF-3290
 URL: https://issues.apache.org/jira/browse/KARAF-3290
 Project: Karaf
  Issue Type: New Feature
Reporter: Guillaume Nodet






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


[jira] [Updated] (KARAF-3290) Upgrade to felix gogo runtime 0.14.0

2014-10-15 Thread Guillaume Nodet (JIRA)

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

Guillaume Nodet updated KARAF-3290:
---
Issue Type: Dependency upgrade  (was: New Feature)

 Upgrade to felix gogo runtime 0.14.0
 

 Key: KARAF-3290
 URL: https://issues.apache.org/jira/browse/KARAF-3290
 Project: Karaf
  Issue Type: Dependency upgrade
Reporter: Guillaume Nodet





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


[jira] [Assigned] (KARAF-3288) karaf script doesn't start on Solaris if JAVA_HOME is not set

2014-10-15 Thread JIRA

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

Jean-Baptiste Onofré reassigned KARAF-3288:
---

Assignee: Jean-Baptiste Onofré

 karaf script doesn't start on Solaris if JAVA_HOME is not set
 -

 Key: KARAF-3288
 URL: https://issues.apache.org/jira/browse/KARAF-3288
 Project: Karaf
  Issue Type: Bug
Affects Versions: 3.0.1
 Environment: Solaris
Reporter: Kevin Earls
Assignee: Jean-Baptiste Onofré
Priority: Minor

 On Solaris the karat script fails with the error JVM must be greater than 
 1.6 if JAVA_HOME is not set.  (On 2.4 it also fails but with the message 
 exec: a tracked alias for /usr/bin/java: not found).  
 This fails because the locateJava() function depends on the output of `type 
 java` to set JAVA_HOME and determine what version of java it's using.  On 
 most platforms type java returns something like java is /path/to/java, but 
 on solaris it returns java is a tracked alias for /path/to/java
 The fix just requires a change to the expression used to chop off the leading 
 text.  I will submit a pull request for this.



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


[jira] [Created] (KARAF-3291) Upgrade to Pax Exam 4.3.0

2014-10-15 Thread JIRA
Jean-Baptiste Onofré created KARAF-3291:
---

 Summary: Upgrade to Pax Exam 4.3.0
 Key: KARAF-3291
 URL: https://issues.apache.org/jira/browse/KARAF-3291
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: karaf-test
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 3.0.3, 2.4.1






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


[jira] [Comment Edited] (KARAF-1583) karaf-maven-plugin ignores dependency on feature

2014-10-15 Thread Gary Kennedy (JIRA)

[ 
https://issues.apache.org/jira/browse/KARAF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173177#comment-14173177
 ] 

Gary Kennedy edited comment on KARAF-1583 at 10/16/14 12:23 AM:


+1
This would be a much better idea than having the plugin handle/aggregate 
{{repository}} tags (which I don't think 3.0.1 does).

At the moment we are using maven project properties to handle GAV across the 
project pom and the feature file. This will certainly make things a bit more 
tidy and robust.



was (Author: gktheone):
+1
This would be a much better idea than having the plugin handle/aggregate 
{code}repository{code} tags (which I don't think 3.0.1 does).

At the moment we are using maven project properties to handle GAV across the 
project pom and the feature file. This will certainly make things a bit more 
tidy and robust.


 karaf-maven-plugin ignores dependency on feature
 

 Key: KARAF-1583
 URL: https://issues.apache.org/jira/browse/KARAF-1583
 Project: Karaf
  Issue Type: Bug
  Components: karaf-tooling
Affects Versions: 3.0.0.RC1
Reporter: Brian Topping
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 3.0.3


 When a project has a dependency on a feature, the dependency should be 
 rendered in the features.xml generated by 
 {{karaf-maven-plugin:features-generate-descriptor}} as a {{repository}} 
 element.  
 I thought I added this, but it must have gotten lost in the patches and will 
 submit another patch after KARAF-1537 is applied.



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