Are you saying that we can not do a release the old way even if it is
still on the old parent pom?
regards,
Karl
On Mon, Apr 27, 2009 at 3:15 AM, Stuart McCulloch mccu...@gmail.com wrote:
On 27 Apr 2009, at 05:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the
Answering my own question: yes - the reason is that the repo is not
synced anymore.
I'm not sure I think that is a reason to fail the release however. I
will contact some people to see whether we can get around it this
time. Until then I pause this vote.
regards,
Karl
On Mon, Apr 27, 2009 at
2009/4/27 Karl Pauls karlpa...@gmail.com
Are you saying that we can not do a release the old way even if it is
still on the old parent pom?
that's correct ... because in order to avoid conflicts between the old and
new routes (and to make sure that developers don't short-cut the staging
[
https://issues.apache.org/jira/browse/FELIX-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703028#action_12703028
]
Felix Meschberger commented on FELIX-1053:
--
This is actually a regression
[
https://issues.apache.org/jira/browse/FELIX-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-1059:
---
Fix Version/s: (was: felix-1.6.1)
felix-1.8.0
DynamicImport-Package
[
https://issues.apache.org/jira/browse/FELIX-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-1059:
---
Component/s: Specification compliance
DynamicImport-Package matches more packages than
[
https://issues.apache.org/jira/browse/FELIX-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-1034.
Resolution: Fixed
Assignee: Richard S. Hall
I have committed a fix for this, please
[
https://issues.apache.org/jira/browse/FELIX-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reopened FELIX-993:
-
The fix applied creates a regression with another test where services need to
be replaced
[
https://issues.apache.org/jira/browse/FELIX-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-1059.
Resolution: Fixed
Assignee: Richard S. Hall
I have committed a fix for this, please
[
https://issues.apache.org/jira/browse/FELIX-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703049#action_12703049
]
Felix Meschberger commented on FELIX-993:
-
Committed a fix in Rev. 768910. See
On 4/27/09 5:57 AM, Guillaume Nodet wrote:
It seems the consensus for the code is to move it to
https://svn.apache.org/repos/asf/felix/trunk/karaf
So i'll go ahead and move the servicemix kernel trunk there asap.
We still need to settle the problems of:
* package name: org.apache.karaf
Yes, they do. The definition of a subproject is imho just something
controlled by a given TLP.
The way its infrastructure is set up has nothing to do with that. A
lot of TLP uses multiple JIRA and confluence spaces for different
reasons.
On Mon, Apr 27, 2009 at 12:03, Richard S. Hall
The ServiceMix Kernel trunk is now read-only and has been moved to:
https://svn.apache.org/repos/asf/felix/trunk/karaf/
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
I think we should start with the FELIX infra and then see whether we
need to create a new one when the need is there.
About the package renaming, I'm in favour of going with
org.apache.felix.karaf just because it emphasizes that felix is not
about the framework. If we make an exception then this
On 4/27/09 6:07 AM, Guillaume Nodet wrote:
Yes, they do. The definition of a subproject is imho just something
controlled by a given TLP.
The way its infrastructure is set up has nothing to do with that. A
lot of TLP uses multiple JIRA and confluence spaces for different
reasons.
My
Cool! Are we gonna setup a Karaf mailing list too?
2009/4/27 Guillaume Nodet gno...@gmail.com:
The ServiceMix Kernel trunk is now read-only and has been moved to:
https://svn.apache.org/repos/asf/felix/trunk/karaf/
--
Cheers,
Guillaume Nodet
Blog:
2009/4/27 James Strachan james.strac...@gmail.com
Cool! Are we gonna setup a Karaf mailing list too?
please consider using the existing Felix mailing lists as I'm already
subscribed to more lists than I'd like ;)
also I'm sure that many Felix users and developers would also be interested
in
I don't have any objections, but I just want to point that making
Felix TLP less tied to the Felix framework would imply that the
framework can be referred to as something else than Apache Felix
imho.
The discussion about raising visibility of Felix subprojects has
already been raised in the
Agreed. If the traffic becomes too much, we can reconsider this
option later without much impact.
I'm more concerned about the package name / jira instance which
impacts compatibility / tracability if changed.
On Mon, Apr 27, 2009 at 13:01, Stuart McCulloch mccu...@gmail.com wrote:
2009/4/27
2009/4/27 Guillaume Nodet gno...@gmail.com
As James mentioned in the other thread, subprojects may also have
dedicated mailing lists that are usually in xxx-...@tlp.apache.org /
xxx-us...@tlp.apache.org ...
the downside of separate lists is that this severely reduces the possible
interaction
It seems the consensus for the code is to move it to
https://svn.apache.org/repos/asf/felix/trunk/karaf
So i'll go ahead and move the servicemix kernel trunk there asap.
We still need to settle the problems of:
* package name: org.apache.karaf vs org.apache.felix.karaf
* jira issue
As James mentioned in the other thread, subprojects may also have
dedicated mailing lists that are usually in xxx-...@tlp.apache.org /
xxx-us...@tlp.apache.org ...
On Mon, Apr 27, 2009 at 12:03, Richard S. Hall he...@ungoverned.org wrote:
On 4/27/09 5:57 AM, Guillaume Nodet wrote:
It seems the
Ok, I'm not really convinced, but since it seems there is a lot of
reluctance I think we should aim for:
* packages in org.apache.felix.karaf
* use existing FELIX infrastructure (mailing list, jira tracker,
confluence space)
I think we should start with the above and reconsider later if there
2009/4/27 Guillaume Nodet gno...@gmail.com
Ok, I'm not really convinced, but since it seems there is a lot of
reluctance I think we should aim for:
* packages in org.apache.felix.karaf
* use existing FELIX infrastructure (mailing list, jira tracker,
confluence space)
I think we should
Sounds good to me.
regards,
Karl
On Mon, Apr 27, 2009 at 1:42 PM, Stuart McCulloch mccu...@gmail.com wrote:
2009/4/27 Guillaume Nodet gno...@gmail.com
Ok, I'm not really convinced, but since it seems there is a lot of
reluctance I think we should aim for:
* packages in
[
https://issues.apache.org/jira/browse/FELIX-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on FELIX-1046 started by Felix Meschberger.
Upgrade parent pom reference to new parent pom (for repository.a.o deployment)
[
https://issues.apache.org/jira/browse/FELIX-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-1046.
Resolution: Fixed
Upgraded project to Felix-Parent pom 1.2.0 in Rev. 768968
Upgrade
Guillaume Nodet wrote:
Ok, I'm not really convinced, but since it seems there is a lot of
reluctance I think we should aim for:
* packages in org.apache.felix.karaf
* use existing FELIX infrastructure (mailing list, jira tracker,
confluence space)
I think we should start with the above
On 4/27/09 7:36 AM, Guillaume Nodet wrote:
Ok, I'm not really convinced, but since it seems there is a lot of
reluctance I think we should aim for:
* packages in org.apache.felix.karaf
* use existing FELIX infrastructure (mailing list, jira tracker,
confluence space)
I think we should
On 4/27/09 7:02 AM, Guillaume Nodet wrote:
I don't have any objections, but I just want to point that making
Felix TLP less tied to the Felix framework would imply that the
framework can be referred to as something else than Apache Felix
imho.
The discussion about raising visibility of Felix
I'm fine with the agreed upon approach, but I also wanted to clarify some of
what Guillaume originally proposed because I never saw any of this mentioned
in this thread.
Within ServiceMix we had already split Kernel/Karaf and other larger parts
of our project (components, NMR, etc.) into separate
Well, I certainly don't know which approach is best. So far, I don't
think we have run into too much difficulty with our all-in-one approach.
At least it doesn't seem like there is an enormous amount of unrelated
traffic. We shall see if this takes us to a new level.
- richard
On 4/27/09
Confluence allows moving a hierachy of pages to be moved across
spaces, so it should be quite easy to move most of the content.
When you edit a page, you have a location box under the title that can
be used for that.
2009/4/27 Chris Custine ccust...@apache.org:
If nobody else has the task, I
-- Forwarded message --
From: Chris Custine ccust...@apache.org
Date: Mon, Apr 27, 2009 at 10:32 AM
Subject: Re: [Karaf] Moving svn trunk
To: d...@servicemix.apache.org
On Mon, Apr 27, 2009 at 4:39 AM, Charles Moulliard cmoulli...@gmail.comwrote:
What is foreseen with the wiki
2009/4/27 Stuart McCulloch mccu...@gmail.com
On 27 Apr 2009, at 05:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the framework and main 1.6.1 subproject
releases.
The source and binary release archives, signature files, SHA and MD5
message digests for each are
On Mon, Apr 27, 2009 at 7:01 AM, Stuart McCulloch mccu...@gmail.com wrote:
2009/4/27 Guillaume Nodet gno...@gmail.com
As James mentioned in the other thread, subprojects may also have
dedicated mailing lists that are usually in xxx-...@tlp.apache.org /
xxx-us...@tlp.apache.org ...
the
+1
Two minor issues:
The copyright year in the two notice files should contain 2009.
Regards,
Clement
On 27.04.2009, at 18:45, Stuart McCulloch wrote:
2009/4/27 Stuart McCulloch mccu...@gmail.com
On 27 Apr 2009, at 05:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote
[
https://issues.apache.org/jira/browse/FELIX-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703304#action_12703304
]
Carsten Ziegeler commented on FELIX-1010:
-
I would opt for using different
I am not sure how it works precisely, but I believe our wiki is not open
to everyone with ICLAs, but I am not opposed to this. For Felix, the
wiki is our web site (or at least the content from which our web site is
generated). Not sure if this is how it is at ServiceMix. Not sure if
that makes
[
https://issues.apache.org/jira/browse/FELIX-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated FELIX-1000:
Attachment: FELIX-1000-27_04_2009.patch.txt
I dont't give up ;-)
Apllied patch includes
[
https://issues.apache.org/jira/browse/FELIX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-1049.
---
Resolution: Fixed
Added the two columns in Revision: 769154
Display symbolic name and
[
https://issues.apache.org/jira/browse/FELIX-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-1052:
---
Fix Version/s: shell-1.2.0
Summary: Add log shell command (was: [PATCH] Log shell
[
https://issues.apache.org/jira/browse/FELIX-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-1020:
---
Assignee: Carsten Ziegeler
Footer redered before content in bundle plugin
[
https://issues.apache.org/jira/browse/FELIX-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703360#action_12703360
]
Carsten Ziegeler commented on FELIX-1020:
-
Hi Thomas,
I can't reproduce this
Great! Then the vote can continue. Thanks!
regards,
Karl
On Mon, Apr 27, 2009 at 6:45 PM, Stuart McCulloch mccu...@gmail.com wrote:
2009/4/27 Stuart McCulloch mccu...@gmail.com
On 27 Apr 2009, at 05:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the framework and
+1
On Sun, Apr 26, 2009 at 23:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the framework and main 1.6.1 subproject
releases.
The source and binary release archives, signature files, SHA and MD5
message digests for each are available as zip and tar.gz here:
+1
On Mon, Apr 27, 2009 at 12:48 AM, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the framework and main 1.6.1 subproject
releases.
The source and binary release archives, signature files, SHA and MD5
message digests for each are available as zip and tar.gz here:
[
https://issues.apache.org/jira/browse/FELIX-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703502#action_12703502
]
Kristian Koehler commented on FELIX-1000:
-
OK. This is odd because of my test.
+1
2009/4/27 Stuart McCulloch mccu...@gmail.com
On 27 Apr 2009, at 05:48, Karl Pauls karlpa...@gmail.com wrote:
I would like to call a vote on the framework and main 1.6.1 subproject
releases.
The source and binary release archives, signature files, SHA and MD5
message digests for each
+1
Carsten
--
Carsten Ziegeler
cziege...@apache.org
50 matches
Mail list logo
