Hi all,
I fixed the karaf-2.1.x archetypes issue this morning.
I launched a build on Jenkins which has been back to stable.
As reminder, maven 2.2.x is the supported version for Karaf 2.1.x and
Karaf 2.2.x. Maven 3 will be fully supported only on Karaf 3.0.x (I'm
working on the refactoring of the maven embedder).
@Jamie, we are ready to release Karaf 2.1.5 ;)
Regards
JB
On 04/26/2011 06:04 PM, Jean-Baptiste Onofré wrote:
Hi Jamie (and the others ;)),
the archetype itests issue that we have is due to a bug in maven
archetype plugin:
http://jira.codehaus.org/browse/ARCHETYPE-351
I made some tests by adding -DarchetypeRepository pointing to my local
maven repo and it works fine (the archetype used is the correct one).
In the itests, I also added the archetypeRepository property (pointing
on maven.getLocalRepositoryDirectory().getAbsolutePath()), but it
doesn't find the karaf command-archetype.
I think I'm not so far, I just need some more time to fix that.
Regards
JB
On 04/25/2011 07:40 PM, Jamie G. wrote:
Thanks JB :)
Cheers,
Jamie
On Mon, Apr 25, 2011 at 3:05 PM, Jean-Baptiste Onofré<[email protected]>
wrote:
As I said on IRC, I'm gonna take a look on that.
It seems that karaf-2.2.x branch build is also broken.
Regards
JB
On 04/25/2011 06:36 PM, Jamie G. wrote:
Just a heads up, I'm seeing an Command Archetype test case failure on
Jenkins for Karaf 2.1.x branch:
https://builds.apache.org/hudson/job/Karaf-2.1.x/lastBuild/org.apache.karaf.archetypes$archetypes-itests/testReport/org.apache.karaf.archetypes/CommandArchetypeTest/testCommand/
Strangely the jar it can not find is available in our snapshot repo:
https://repository.apache.org/content/groups/snapshots/org/apache/karaf/shell/org.apache.karaf.shell.console/2.1.99-SNAPSHOT/
On my own build systems I'm seeing some build runs succeed while
others fail unable to obtain the above jar. I'm not sure what is
causing this behavior at the moment, will continue to look into this.
Cheers,
Jamie
On Fri, Apr 22, 2011 at 6:54 PM, Jamie G.<[email protected]>
wrote:
After discussion on the IRC Karaf room, we believe that this update
version should not represent a break in functionality. This new
version does include some bug fixes so it should be a benefit if
included.
Cheers,
Jamie
On Wed, Apr 20, 2011 at 1:06 PM, Jamie G.<[email protected]>
wrote:
Thanks for providing a link to the discussion on JIRA. I'll hold off
on Karaf 2.1.5 until we have this particular issue resolved either
way
:)
Cheers,
Jamie
On Tue, Apr 19, 2011 at 4:30 PM, Achim
Nierbeck<[email protected]>
wrote:
We need to be carefull about the upgrade of felix here, we do have a
issue with 2.2.1 right now concerning Felix.
https://issues.apache.org/jira/browse/KARAF-534
regards, Achim
2011/4/19 Jamie G.<[email protected]>:
Hi Mike,
Will investigate.
On a side note things build and boot up using IBM JDK :)
Cheers,
Jamie
On Tue, Apr 19, 2011 at 2:22 PM, mikevan<[email protected]>
wrote:
jgoodyear wrote:
Our latest 2.1.x build on Jenkins went well:
https://builds.apache.org/hudson/job/Karaf-2.1.x/lastBuild/
I'll have a look at how it's faring on IBM JDK.
Cheers,
Jamie
On Tue, Apr 19, 2011 at 12:19 PM, Jean-Baptiste Onofré
<[email protected]> wrote:
Hi Jamie,
thanks for the update, I'm focusing on the 2.2.1 bugs but I will
take a
look on those also.
Regards
JB
On Tue 19/04/11 15:14 , "Jamie G." wrote::
Hi All,
I've been reviewing the status of the Karaf 2.1.5 patch. We
currently
have no open issues, as such I think this would be a good
time for
us
all to quickly review the Karaf 2.1.5 branch builds, test on
different
platforms, and report any issue observed. I think the community
could
get this update out in relatively short order along side the
Karaf
2.2.1 release.
Issues addressed in this patch:
Bug:
[KARAF-458] - Fix the karaf shell to look nice within Eclipse
console
[KARAF-472] - features-maven-plugin: TAB-characters in
feature-repository lead to resolution-errors in
add-features-to-repo
[KARAF-505] - Karaf should ignore the resolver attribute in a
features
descriptor
[KARAF-506] - The config shell commands offer no way to delete a
command
[KARAF-507] - The config shell completer does not allow
completion
of
factory based pids
[KARAF-508] - The config:edit create does not allow the
creation of
factory configs
[KARAF-509] - The config:update command does not save factory
configurations to the correct file
[KARAF-515] - Completion error
Improvement:
[KARAF-484] - Upgrade to Felix Framework 3.0.9
Cheers,
Jamie
Will upgrading to a newer version of Felix cause issues? This
seems
like
something too major for a minor release.
-----
Mike Van (aka karafman)
Karaf Team (Contributor)
--
View this message in context:
http://karaf.922171.n3.nabble.com/UPDATE-Apache-Karaf-2-1-5-status-tp2838620p2839348.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
