You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (Created) (JIRA)" <ji...@apache.org> on 2011/12/05 00:06:39 UTC
[jira] [Created] (KARAF-1086) Create Kar for Karaf demos
Create Kar for Karaf demos
--------------------------
Key: KARAF-1086
URL: https://issues.apache.org/jira/browse/KARAF-1086
Project: Karaf
Issue Type: Task
Components: karaf-demo
Affects Versions: 3.0.0
Reporter: Jamie goodyear
Assignee: David Jencks
Fix For: 3.0.0
>From IRC discussion:
{code}
djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
djencks: we could have a kar per demo or one that installs all the demos
yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
jamieg: very true, but it should according to the docs [18:17]
djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
2.x assemblies will pretty much stay as they are [18:18]
djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
jamieg: Please feel free to jump in :)
djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
and others [18:20]
djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
jamieg: good question :) [18:21]
djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
jamieg: or if we go for 'all' its simple at least
djencks: do we gain anything from individual demos?
djencks: an demo archtype could be useful for custom distro builders
...
djencks: perhaps all for 3.0, then individual for 3.1?
djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
djencks: I'll start with an "all" and see how it goes [18:24]
jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
djencks: (in particular me :-) [18:24]
jamieg: hehe [18:24]
djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1086) Create Kar for Karaf demos
Posted by "Jamie goodyear (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164406#comment-13164406 ]
Jamie goodyear commented on KARAF-1086:
---------------------------------------
Enable filtering of resources.
Both pom and readme files can be filtered in place - might make for easier maintenance then a separate filtered-resources file just for the readme.
$ svn ci
Sending branding/pom.xml
Transmitting file data .
Committed revision 1211441.
> Create Kar for Karaf demos
> --------------------------
>
> Key: KARAF-1086
> URL: https://issues.apache.org/jira/browse/KARAF-1086
> Project: Karaf
> Issue Type: Task
> Components: karaf-demo
> Affects Versions: 3.0.0
> Reporter: Jamie goodyear
> Assignee: David Jencks
> Fix For: 3.0.0
>
>
> From IRC discussion:
> {code}
> djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
> jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
> djencks: we could have a kar per demo or one that installs all the demos
> yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
> which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
> jamieg: very true, but it should according to the docs [18:17]
> djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
> jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
> 2.x assemblies will pretty much stay as they are [18:18]
> djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
> jamieg: Please feel free to jump in :)
> djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
> and others [18:20]
> djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
> jamieg: good question :) [18:21]
> djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
> jamieg: or if we go for 'all' its simple at least
> djencks: do we gain anything from individual demos?
> djencks: an demo archtype could be useful for custom distro builders
> ...
> djencks: perhaps all for 3.0, then individual for 3.1?
> djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
> djencks: I'll start with an "all" and see how it goes [18:24]
> jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
> djencks: (in particular me :-) [18:24]
> jamieg: hehe [18:24]
> djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1086) Create Kar for Karaf demos
Posted by "David Jencks (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168533#comment-13168533 ]
David Jencks commented on KARAF-1086:
-------------------------------------
The source directory structure is certainly unusual, but it results in being able to package a source maven project into a kar at an appropriate location without any maven plugin configurations. I spent a few hours trying to create a source jar for the (embedded) demo project and unpacking it and repacking it into a kar but couldn't get anything to work. All my attempts were very much more complicated and seemed really unmaintainable so when I thought of just using the expected directory structure for a kar I used it. I think having a simple and reliable way to generate demos is the most important goal here: very few people are going to be writing demos.
It would be easy to write a demo archetype that produced a project with the unusual directory structure ready for the actual demo to be inserted. A demo packaging is also possible but I don't think expected usage warrants the work to maintain it.
> Create Kar for Karaf demos
> --------------------------
>
> Key: KARAF-1086
> URL: https://issues.apache.org/jira/browse/KARAF-1086
> Project: Karaf
> Issue Type: Task
> Components: karaf-demo
> Affects Versions: 3.0.0
> Reporter: Jamie goodyear
> Assignee: David Jencks
> Fix For: 3.0.0
>
> Attachments: Zrzut ekranu 2011-12-13 (godz. 16.53.54).png
>
>
> From IRC discussion:
> {code}
> djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
> jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
> djencks: we could have a kar per demo or one that installs all the demos
> yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
> which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
> jamieg: very true, but it should according to the docs [18:17]
> djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
> jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
> 2.x assemblies will pretty much stay as they are [18:18]
> djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
> jamieg: Please feel free to jump in :)
> djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
> and others [18:20]
> djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
> jamieg: good question :) [18:21]
> djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
> jamieg: or if we go for 'all' its simple at least
> djencks: do we gain anything from individual demos?
> djencks: an demo archtype could be useful for custom distro builders
> ...
> djencks: perhaps all for 3.0, then individual for 3.1?
> djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
> djencks: I'll start with an "all" and see how it goes [18:24]
> jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
> djencks: (in particular me :-) [18:24]
> jamieg: hehe [18:24]
> djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-1086) Create Kar for Karaf demos
Posted by "Jamie goodyear (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear resolved KARAF-1086.
-----------------------------------
Resolution: Fixed
The karaf 3.0 demos have been updated to kar format.
> Create Kar for Karaf demos
> --------------------------
>
> Key: KARAF-1086
> URL: https://issues.apache.org/jira/browse/KARAF-1086
> Project: Karaf
> Issue Type: Task
> Components: karaf-demo
> Affects Versions: 3.0.0
> Reporter: Jamie goodyear
> Assignee: David Jencks
> Fix For: 3.0.0
>
> Attachments: Zrzut ekranu 2011-12-13 (godz. 16.53.54).png
>
>
> From IRC discussion:
> {code}
> djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
> jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
> djencks: we could have a kar per demo or one that installs all the demos
> yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
> which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
> jamieg: very true, but it should according to the docs [18:17]
> djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
> jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
> 2.x assemblies will pretty much stay as they are [18:18]
> djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
> jamieg: Please feel free to jump in :)
> djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
> and others [18:20]
> djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
> jamieg: good question :) [18:21]
> djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
> jamieg: or if we go for 'all' its simple at least
> djencks: do we gain anything from individual demos?
> djencks: an demo archtype could be useful for custom distro builders
> ...
> djencks: perhaps all for 3.0, then individual for 3.1?
> djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
> djencks: I'll start with an "all" and see how it goes [18:24]
> jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
> djencks: (in particular me :-) [18:24]
> jamieg: hehe [18:24]
> djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1086) Create Kar for Karaf demos
Posted by "Łukasz Dywicki (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Łukasz Dywicki updated KARAF-1086:
----------------------------------
Attachment: Zrzut ekranu 2011-12-13 (godz. 16.53.54).png
Structure of demos.
> Create Kar for Karaf demos
> --------------------------
>
> Key: KARAF-1086
> URL: https://issues.apache.org/jira/browse/KARAF-1086
> Project: Karaf
> Issue Type: Task
> Components: karaf-demo
> Affects Versions: 3.0.0
> Reporter: Jamie goodyear
> Assignee: David Jencks
> Fix For: 3.0.0
>
> Attachments: Zrzut ekranu 2011-12-13 (godz. 16.53.54).png
>
>
> From IRC discussion:
> {code}
> djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
> jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
> djencks: we could have a kar per demo or one that installs all the demos
> yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
> which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
> jamieg: very true, but it should according to the docs [18:17]
> djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
> jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
> 2.x assemblies will pretty much stay as they are [18:18]
> djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
> jamieg: Please feel free to jump in :)
> djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
> and others [18:20]
> djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
> jamieg: good question :) [18:21]
> djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
> jamieg: or if we go for 'all' its simple at least
> djencks: do we gain anything from individual demos?
> djencks: an demo archtype could be useful for custom distro builders
> ...
> djencks: perhaps all for 3.0, then individual for 3.1?
> djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
> djencks: I'll start with an "all" and see how it goes [18:24]
> jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
> djencks: (in particular me :-) [18:24]
> jamieg: hehe [18:24]
> djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1086) Create Kar for Karaf demos
Posted by "Łukasz Dywicki (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168462#comment-13168462 ]
Łukasz Dywicki commented on KARAF-1086:
---------------------------------------
Hey Jamie,
I currently have a dump provider demo pending to do. But the whole structure makes me a bit afraid. Why we need to change whole directory structure, move the source code to resources and so on instead of simply adding a features fot them and KARs? As far as I understanded KARs was responsible for wrapping features. We might do the resource filtering without all these moves, don't you think? Now our demos code looks exactly like archetypes. This might make people scary.
Best regards,
Lukasz
> Create Kar for Karaf demos
> --------------------------
>
> Key: KARAF-1086
> URL: https://issues.apache.org/jira/browse/KARAF-1086
> Project: Karaf
> Issue Type: Task
> Components: karaf-demo
> Affects Versions: 3.0.0
> Reporter: Jamie goodyear
> Assignee: David Jencks
> Fix For: 3.0.0
>
>
> From IRC discussion:
> {code}
> djencks: right so I think the next thing would be to start working on a kar project for the demos [18:15]
> jamieg: I'm going to split my JIRA for the kar demo in two -- one for the features-maven plugin and the other for the karaf-maven plugin. They approach creating kars differently [18:15]
> djencks: we could have a kar per demo or one that installs all the demos
> yes.... AFAIK the features-maven-plugin doesn't actually work to create kars
> which is why I've been hoping 3.0 could be released sooner rather than later [18:16]
> jamieg: very true, but it should according to the docs [18:17]
> djencks: and, everything I've been saying is only about trunk/3.0.... [18:17]
> jamieg: Oh yes, that i assumed :) I wouldn't change the packaging of demos on a micro release
> 2.x assemblies will pretty much stay as they are [18:18]
> djencks: I think it would be great to find out if the manual instructions are correct and comprehensible enough for someone other than me to set up a working kar project to install the demos but if you like I could come up with at least a start [18:19]
> jamieg: Please feel free to jump in :)
> djencks: I've been learning the kar functionality from the docs and from chatting with you ;)
> and others [18:20]
> djencks: ok do you think it would be better to have each demo individually installable or have all the demos in one kar? [18:20]
> jamieg: good question :) [18:21]
> djencks:if we decided "individually" we could have a demo archetype but it ends up with almost twice as many projects [18:22]
> jamieg: or if we go for 'all' its simple at least
> djencks: do we gain anything from individual demos?
> djencks: an demo archtype could be useful for custom distro builders
> ...
> djencks: perhaps all for 3.0, then individual for 3.1?
> djencks: gets things done fast for 3.0 then build our better functionality for 3.1? [18:22]
> djencks: I'll start with an "all" and see how it goes [18:24]
> jamieg: (just trying to manage feature creep - a lot of people are really calling for 3.0.0) [18:24]
> djencks: (in particular me :-) [18:24]
> jamieg: hehe [18:24]
> djencks: ok, good, we have a plan.... have to go now for a bit... thanks!
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira