Hi Carsten,
There is currently a single issue (SLING-933 [1]) open. We have a
request by Aaron Zeckoski to also include SLING-933 [2] in the release.
For SLING-933 I will have to wait a few hours for the Apache Felix SCR
bundle 1.0.8 to hit the central maven repository, at which time I will
then
Hello everyone,
I'm planning to do the release next monday or tuesday.
We have two missing pieces atm, one is the Felix framework 1.6.1 release
(which should be available now) and the Felix SCR 1.0.8 implementation
(which should be available by monday).
So if you think that we need to anything in
Hi,
Carsten Ziegeler schrieb:
> Jukka Zitting wrote:
>> Hi,
>>
>> On Wed, Apr 29, 2009 at 2:53 PM, Felix Meschberger
>> wrote:
>>> Jukka Zitting schrieb:
Ping. Anyone interested in pushing out a new release?
>>> I am not sure how interested he really is ;-) But IIRC Carsten agreed to
>>> st
Jukka Zitting wrote:
> Hi,
>
> On Wed, Apr 29, 2009 at 2:53 PM, Felix Meschberger wrote:
>> Jukka Zitting schrieb:
>>> Ping. Anyone interested in pushing out a new release?
>> I am not sure how interested he really is ;-) But IIRC Carsten agreed to
>> stand in as the RM for it.
>
> Yeah, I saw t
Hi,
On Wed, Apr 29, 2009 at 2:53 PM, Felix Meschberger wrote:
> Jukka Zitting schrieb:
>> Ping. Anyone interested in pushing out a new release?
>
> I am not sure how interested he really is ;-) But IIRC Carsten agreed to
> stand in as the RM for it.
Yeah, I saw that. Just pinging on whether we'r
Hi,
Jukka Zitting schrieb:
> Ping. Anyone interested in pushing out a new release?
I am not sure how interested he really is ;-) But IIRC Carsten agreed to
stand in as the RM for it.
Regards
Felix
Hi,
Ping. Anyone interested in pushing out a new release?
BR,
Jukka Zitting
Hi Felix
> First of all: We are perfectly aware of this situation, but fail to be
> able to really cope with it in the sense of updating all docs, due to
> overfilled time tables (you know the problem ;-) ).
yes, you're totally right, I know exactly the problem :-)
> One thing you could do, exce
On Fri, Apr 3, 2009 at 1:53 PM, Felix Meschberger wrote:
> I have created a documentation page at [1] which should shortly appear
> on our site (follow Development -> Integrating Scripting Languages ->
> XSLT ...)
Thanks! Just added a note that the xproc module uses the Cocoon 3
pipeline engine.
> I have created a documentation page at [1] which should shortly appear
> on our site (follow Development -> Integrating Scripting Languages ->
> XSLT ...)
>
> This page may be edited directly in the SLINGxSITE wiki to update the site.
Thanks Felix. I´ll work at it soon.
Juanjo.
Hi,
Bertrand Delacretaz schrieb:
> Hi,
>
> 2009/4/1 Juan José Vázquez Delgado :
>> Bertrand said:
>>> SLING-893 Pipeline support - still in the whiteboard, right? I'm going
>>> to test it today.
>> As discussed in [1], pipeline support stuff has been already saved in
>> contrib [2]. I´m going to
>> > Just wondering, if the xpl
>> > file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
>> > the .html extension in this example to the script?
>> > I would have guessed /apps/xproc/sling/servlet/default/html.xpl ..
>>
>> Because of resource type is "xproc", you have:
>>
>> /
Hi
2009/4/3 Juan José Vázquez Delgado
> > Just wondering, if the xpl
> > file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
> > the .html extension in this example to the script?
> > I would have guessed /apps/xproc/sling/servlet/default/html.xpl ..
>
> Because of resource
Hi,
> Exciting stuff for an old xslt head like myself.
Yeap, XST is still the best option in a lot of situations.
> Just wondering, if the xpl
> file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
> the .html extension in this example to the script?
> I would have guessed /
Hi Mike,
Mike Müller schrieb:
> Hi all,
>
> First of all, I would like to thank all of you for the big efforts to enhance
> and refine sling step by step. I'm watching the project since a few months
> for now and tested sling in a few simple projects - and it really is very
> easy to use it ri
Exciting stuff for an old xslt head like myself. Just wondering, if the xpl
file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
the .html extension in this example to the script?
I would have guessed /apps/xproc/sling/servlet/default/html.xpl ..
Regards,
Erik Buene
2009/4/1
Hi there,
I heard a rumor that day is planning a sling training in the near
future? Is that so and if yes, could that lead to a better documentation
for sling?
Ruben
Dominik Süß wrote:
Hi Mike,
you're not the only one who did address this issue. This pops up in the
mailing list from time-t
Hi Mike,
you're not the only one who did address this issue. This pops up in the
mailing list from time-to-time and on conventions like ApacheCon last week.
The main problem about that seams that the commiters are involved in a lot
of projects (as well the apache projects as the day products). Sin
Hi all,
First of all, I would like to thank all of you for the big efforts to enhance
and refine sling step by step. I'm watching the project since a few months for
now and tested sling in a few simple projects - and it really is very easy to
use it right from scratch.
But to be honest, it's r
2009/4/1 Juan José Vázquez Delgado :
> ...I hope to have samples and more improvements soon...
It would be cool to explain to the Cocoon community what you've done,
and maybe some parts could be of general interest and could move
there?
Ideally, describing what you've done on the wiki in terms of
>>> SLING-893 Pipeline support - still in the whiteboard, right? I'm going
>>> to test it today.
>>
>> As discussed in [1], pipeline support stuff has been already saved in
>> contrib [2]. I´m going to close SLING-893 and open new issues for
>> enhancements
>
> Great, thanks!
>
> I made minor i
Hi,
2009/4/1 Juan José Vázquez Delgado :
> Bertrand said:
>> SLING-893 Pipeline support - still in the whiteboard, right? I'm going
>> to test it today.
>
> As discussed in [1], pipeline support stuff has been already saved in
> contrib [2]. I´m going to close SLING-893 and open new issues for
> e
> SLING-893 Pipeline support - still in the whiteboard, right? I'm going
> to test it today.
As discussed in [1], pipeline support stuff has been already saved in
contrib [2]. I´m going to close SLING-893 and open new issues for
enhancements.
BTW, we have some contrib tests failing too (SLING-869
I think we should just update to the latest Felix framework and then
release. Everything else can be fixed later on. With bundles we can just
release separate bundles frequently.
The only real issue I see atm are the failing tests.
Carsten
--
Carsten Ziegeler
cziege...@apache.org
On Wed, Apr 1, 2009 at 9:37 AM, Felix Meschberger wrote:
> ...I assume that, given the vote passes, we should release Sling next week
Shouldn't we rather ask which issues need to (or can easily be) solved
before releasing?
(and I also have a POLL coming up w.r.t scripting in general, but that
Hi,
Vidar Ramdal schrieb:
> On Wed, Apr 1, 2009 at 9:37 AM, Felix Meschberger wrote:
>> Hi all,
>>
>> Just wanted to inform you all (at least the ones not sitting on
>> felix-dev@), that the Felix project is currently voting on the 1.6.0
>> release of the Felix framework. I tested Sling with the
On Wed, Apr 1, 2009 at 9:37 AM, Felix Meschberger wrote:
> Hi all,
>
> Just wanted to inform you all (at least the ones not sitting on
> felix-dev@), that the Felix project is currently voting on the 1.6.0
> release of the Felix framework. I tested Sling with the release
> candidate and apart from
Hi all,
Just wanted to inform you all (at least the ones not sitting on
felix-dev@), that the Felix project is currently voting on the 1.6.0
release of the Felix framework. I tested Sling with the release
candidate and apart from a small issue in Sling [1], it works flawlessly.
I assume that, giv
+1
BR,
Juanjo.
On Tue, Jan 6, 2009 at 12:38 PM, Felix Meschberger wrote:
> Hi all,
>
>
> After all the enhancements and bugfixes to Sling in the last months
> since the first release, I think it is about time to consider a new
> release.
>
> I think we should push forward the release in a few s
Hi,
On Tue, Jan 6, 2009 at 2:14 PM, Felix Meschberger wrote:
> Jukka Zitting schrieb:
>> Are you planning to release the components separately or as a single
>> package, i.e. will this be a "Sling release" or a set of "Sling
>> component releases"?
On Tue, Jan 6, 2009 at 2:14 PM, Felix Meschberger wrote:
> ...After that, we should probably start getting a routine at releasing
> single components as we promised ;-)...
Yes - it's a bit slow right now as our incubating status requires two
72-hours votes (one here and one in the Incubator PMC),
> Are you planning to release the components separately or as a single
> package, i.e. will this be a "Sling release" or a set of "Sling
> component releases"?
This will probably again (for ease of processing) be a full Sling
release, just like the first one.
After th
Alexander Saar schrieb:
> Hi all,
>
> Am 06.01.2009 um 12:38 schrieb Felix Meschberger:
>
>> After all the enhancements and bugfixes to Sling in the last months
>> since the first release, I think it is about time to consider a new
>> release.
> good to hear that ;)
>
>> I think we should push
single
package, i.e. will this be a "Sling release" or a set of "Sling
component releases"?
BR,
Jukka Zitting
Hi all,
Am 06.01.2009 um 12:38 schrieb Felix Meschberger:
After all the enhancements and bugfixes to Sling in the last months
since the first release, I think it is about time to consider a new
release.
good to hear that ;)
I think we should push forward the release in a few steps:
(1) Re
On Tue, Jan 6, 2009 at 12:38 PM, Felix Meschberger wrote:
> ...I think we should push forward the release in a few steps:..
I agree with the proposed steps.
-Bertrand
+1
Carsten
Felix Meschberger wrote:
> Hi all,
>
>
> After all the enhancements and bugfixes to Sling in the last months
> since the first release, I think it is about time to consider a new release.
>
> I think we should push forward the release in a few steps:
>
> (1) Remove Dependency Manag
Hi all,
After all the enhancements and bugfixes to Sling in the last months
since the first release, I think it is about time to consider a new release.
I think we should push forward the release in a few steps:
(1) Remove Dependency Management from the parent pom (see [1]).
(2) Release Sling P
Greg Klebus wrote:
Thanks, that helps me a lot.
Does that mean that the compiled release (*) will be available in
maven repositories also around 25th June in the best case?
Yes, after the vote is successfully finished, I deploy the artifacts
directly into a maven repository. From there they're
Carsten
On Thu, Jun 12, 2008 at 11:14 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ok, the honest answer is that we don't have a fixed date - it happens when
> it happens :) For sure, that answer does not satisfy, so I can outline the
> best case scenario.
Good answer :)
> I'll adjust the n
Hi,
ok, the honest answer is that we don't have a fixed date - it happens
when it happens :) For sure, that answer does not satisfy, so I can
outline the best case scenario.
I'll adjust the notice files and the other stuff as discussed tomorrow.
Hopefully others can help with the readme file
On Thu, Jun 12, 2008 at 10:44 AM, Greg Klebus <[EMAIL PROTECTED]> wrote:
>
> Some people really want it, now^H^H^H a.s.a.p. :)
I can only second that. I understand legal discussions, but
nevertheless the attraction of sling far outweighs that. our project
would benefit extremely.
so yeah, what's
Hi Carsten
I hate to do what makes me (as a product mgr) frown a lot... but
what's the current ETA for Sling release?
I'm aware of the "license and notice files" discussion [1] - somewhat
painful, but better done before the release in any case.
[1] http://markmail.org/mess
Hi,
Am Mittwoch, den 04.06.2008, 19:31 +0200 schrieb Carsten Ziegeler:
> The depenencies are now all set to 2.0.1-incubator-SNAPSHOT. Once the
> release is out to the maven repos, we will revert this to
> 2.0.0-incubator where appropriate.
Very good.
I would suggest we revert _all_ cross-depen
Roy T. Fielding wrote:
But the NOTICE files are not for describing build dependencies.
They exist to satisfy the copyright license of packaged distributions.
If the notices aren't required by the bits in the package, then they don't
belong in NOTICE. That means there will be a different NOTICE f
On Jun 3, 2008, at 11:45 PM, Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 12:35 AM, Roy T. Fielding
<[EMAIL PROTECTED]> wrote:
...I'd rather have a set of hand-edited NOTICE files that accurately
reflect each of the release packages
I see your point, and thanks for your changes in e
The depenencies are now all set to 2.0.1-incubator-SNAPSHOT. Once the
release is out to the maven repos, we will revert this to
2.0.0-incubator where appropriate.
Carsten
Carsten Ziegeler wrote:
I'm finished with building the release artifacts. Please note that our
current trunk is not builda
I'm finished with building the release artifacts. Please note that our
current trunk is not buildable due to this. The artifacts reference the
release versions which are not available in a public maven repository
and the versions in our svn are set to the next snapshot.
I'll correct this asap
On Wed, Jun 4, 2008 at 4:12 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> If noone stops me I'll start to build the release candidates now
RAT reports some missing licenses, see below. I'll fix the java files
now (except commons/json which is ok, right?), please have a look at
the rest, I
If noone stops me I'll start to build the release candidates now
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
On Wed, Jun 4, 2008 at 3:00 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Unfortunately, I have to say, that the NOTICE files are partly
> inaccurate and incomplete
Make sure to look at the notice fragments under
http://svn.apache.org/repos/asf/incubator/sling/trunk/etc/notice/notices
Hi,
I was distracted with other work and could not yet post my NOTICE
inspection results.
Unfortunately, I have to say, that the NOTICE files are partly
inaccurate and incomplete.
I will post my findings (should they diverge from what Carsten has
found) to the reponend SLING-495 issue.
Regards
Ok, can I have a short ok from other committers that they think the
notice files are ok now?
I'll check them myself now and would like to start the build process
afterwards.
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
On Wed, Jun 4, 2008 at 9:35 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ...I think we should make the final changes (as discussed recently here),
> recheck the notice files and then I can go ahead and make the release
> candidates...
Yes, I'm cleaning up the NOTICE files based on Roy's late
Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 12:35 AM, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
...I'd rather have a set of hand-edited NOTICE files that accurately
reflect each of the release packages
I see your point, and thanks for your changes in etc/notice/notices,
that will he
On Wed, Jun 4, 2008 at 12:35 AM, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
> ...I'd rather have a set of hand-edited NOTICE files that accurately
> reflect each of the release packages
I see your point, and thanks for your changes in etc/notice/notices,
that will help a lot.
The nice thing (
On Jun 3, 2008, at 5:41 AM, Felix Meschberger wrote:
Am Dienstag, den 03.06.2008, 14:32 +0200 schrieb Bertrand Delacretaz:
On Tue, Jun 3, 2008 at 1:52 PM, Bertrand Delacretaz
<[EMAIL PROTECTED]> wrote:
...I'm generating the NOTICEs as we speak, ETA 30 minutes...
Done (took 34 minutes, sorry ;
Hi,
On Tue, Jun 3, 2008 at 5:37 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Dienstag, den 03.06.2008, 17:31 +0300 schrieb Jukka Zitting:
>> Anyway, if your component depends for example on log4j 1.2.15, it's
>> much better to explicitly exclude such transitive dependencies than to
>> mar
Yes, please ;-)
Regards
Felix
Am Dienstag, den 03.06.2008, 16:47 +0200 schrieb Carsten Ziegeler:
> Ok, can we release?
>
> Carsten
>
>
2008/6/3 Carsten Ziegeler <[EMAIL PROTECTED]>:
> Ok, can we release?
+1 on creating the release artifacts.
Releasing requires a vote IIRC ;-)
-Bertrand
Ok, can we release?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Hi,
Am Dienstag, den 03.06.2008, 17:31 +0300 schrieb Jukka Zitting:
> Hi,
>
> On Tue, Jun 3, 2008 at 5:20 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> > Am Dienstag, den 03.06.2008, 17:14 +0300 schrieb Jukka Zitting:
> >> I'm trying to understand the issue, do you have an example of a case
Hi,
On Tue, Jun 3, 2008 at 5:20 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Dienstag, den 03.06.2008, 17:14 +0300 schrieb Jukka Zitting:
>> I'm trying to understand the issue, do you have an example of a case
>> where this would be troublesome?
>
> It is not directly troublesome, more li
Hi,
Am Dienstag, den 03.06.2008, 17:14 +0300 schrieb Jukka Zitting:
> Hi,
>
> On Tue, Jun 3, 2008 at 5:00 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> > The problem with compile is that it creates hard transitive
> > dependencies, which is not what you want when including library code
> > i
Hi,
On Tue, Jun 3, 2008 at 5:00 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> The problem with compile is that it creates hard transitive
> dependencies, which is not what you want when including library code
> into the bundle.
I'm trying to understand the issue, do you have an example of a
Hi,
Am Dienstag, den 03.06.2008, 15:57 +0200 schrieb Carsten Ziegeler:
> Bertrand Delacretaz wrote:
> > I agree, but aren't we abusing it already?
> >
> > We are marking dependencies as "provided", but including them in the
> > generated artifact using the maven-bundle-plugin.
> >
> > The correc
Bertrand Delacretaz wrote:
I agree, but aren't we abusing it already?
We are marking dependencies as "provided", but including them in the
generated artifact using the maven-bundle-plugin.
The correct scope (although it does not exist, and IIRC you said
custom scopes pose problems) might be "bu
On Tue, Jun 3, 2008 at 3:47 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Dienstag, den 03.06.2008, 15:41 +0200 schrieb Bertrand Delacretaz:
>> ...that the pinger pings way
>> too often currently, I'll create an issue for that unless there's one
>> already.
>
> Couldn't this be handled in t
Am Dienstag, den 03.06.2008, 15:41 +0200 schrieb Bertrand Delacretaz:
> On Tue, Jun 3, 2008 at 3:39 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> > ...Btw, anyone against changing the repository pinger (see SLING-505) and
> > remove the debug logs for the release? I'm currently trying to debug
On Tue, Jun 3, 2008 at 3:39 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ...Btw, anyone against changing the repository pinger (see SLING-505) and
> remove the debug logs for the release? I'm currently trying to debug
> something with log level set to debug and the log is growing like mad...
On Tue, Jun 3, 2008 at 3:29 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]>
>> wrote:
>>> ...One solution I could see is, that we
>>> mark all dependencies, which are included in a bundle as optional
> Sorry, but I think
Felix Meschberger wrote:
Hi,
Am Dienstag, den 03.06.2008, 15:29 +0200 schrieb Carsten Ziegeler:
Bertrand Delacretaz wrote:
On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
...One solution I could see is, that we
mark all dependencies, which are included in a bundl
Hi,
Am Dienstag, den 03.06.2008, 15:29 +0200 schrieb Carsten Ziegeler:
> Bertrand Delacretaz wrote:
> > On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> >
> >> ...One solution I could see is, that we
> >> mark all dependencies, which are included in a bundle as optio
Bertrand Delacretaz wrote:
On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
...One solution I could see is, that we
mark all dependencies, which are included in a bundle as optional. This
is done for the launchpad/app module to not include all dependencies and
transi
On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...One solution I could see is, that we
> mark all dependencies, which are included in a bundle as optional. This
> is done for the launchpad/app module to not include all dependencies and
> transitives into a project's
Hi,
Am Dienstag, den 03.06.2008, 15:01 +0200 schrieb Bertrand Delacretaz:
> On Tue, Jun 3, 2008 at 2:41 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ...I just looked at the NOTICE file in the engine and see that it includes
> > references to SLF4J and jcp.org. Interestingly neither is i
On Tue, Jun 3, 2008 at 2:41 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...I just looked at the NOTICE file in the engine and see that it includes
> references to SLF4J and jcp.org. Interestingly neither is included in
> the engine
Both of these have scope=provided, and right now the m
Hi,
Am Dienstag, den 03.06.2008, 14:32 +0200 schrieb Bertrand Delacretaz:
> On Tue, Jun 3, 2008 at 1:52 PM, Bertrand Delacretaz
> <[EMAIL PROTECTED]> wrote:
> > ...I'm generating the NOTICEs as we speak, ETA 30 minutes...
>
> Done (took 34 minutes, sorry ;-)
>
> Generating those NOTICEs and digg
On Tue, Jun 3, 2008 at 1:52 PM, Bertrand Delacretaz
<[EMAIL PROTECTED]> wrote:
> ...I'm generating the NOTICEs as we speak, ETA 30 minutes...
Done (took 34 minutes, sorry ;-)
Generating those NOTICEs and digging out the info for all the notice
fragments in etc/notice/notices/ was *much* more pai
Felix Meschberger wrote:
Hi,
Am Dienstag, den 03.06.2008, 11:13 +0200 schrieb Carsten Ziegeler:
I created a profile in our reactor pom with the modules we don't want to
include in our first release. I'm not sure if this list is
complete/correct, so please cross check.
I think we should try t
On Tue, Jun 3, 2008 at 1:48 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Apart from the NOTICE stuff, I would say we are ready for rock'n'roll,
> right ?...
Yes, I'm generating the NOTICEs as we speak, ETA 30 minutes.
-Bertrand
Hi,
Am Dienstag, den 03.06.2008, 11:13 +0200 schrieb Carsten Ziegeler:
> I created a profile in our reactor pom with the modules we don't want to
> include in our first release. I'm not sure if this list is
> complete/correct, so please cross check.
>
> I think we should try to build the releas
Hi,
I fixed SLING-502 so, this blocker is removed, I hope. I also closed
SLING-501 as duplicate of SLING-502.
In addition I descheduled SLING-421 (Update Servlet Resolution
Description) from the 2.0 release.
Remains the notices case ...
Are we on track ? ;-)
Regards
Felix
Am Dienstag, den 03.
Hi,
scanning our project reveals the following component factories:
jcr/jackrabbit-server : SlingServerRepository
jcr/jackrabbit-client : SlingClientRepository
jcr/classloader : RepositoryClassLoaderProviderImpl
engine: RequestLoggerService
I
Hi,
Am Dienstag, den 03.06.2008, 12:07 +0200 schrieb Carsten Ziegeler:
> Felix Meschberger wrote:
> > It _will_ run with the scr 1.0.0 snapshot, unless the immediate flag is
> > set, which is the real bug behind this. If the immediate flag is not
> > explicitly set to any value, both versions of S
Felix Meschberger wrote:
It _will_ run with the scr 1.0.0 snapshot, unless the immediate flag is
set, which is the real bug behind this. If the immediate flag is not
explicitly set to any value, both versions of SCR -- 1.0.0 and
1.0.1-SNAPSHOT -- assume their own default value valid in their cont
Hi,
Am Dienstag, den 03.06.2008, 11:58 +0200 schrieb Carsten Ziegeler:
> Felix Meschberger wrote:
> >
> > Actually, it would run ;-) The problem is the maven-scr-plugin which
> > always sets the immediate attribute to true (if not explicitly) set.
> > This is incorrect in connection with using th
Felix Meschberger wrote:
Actually, it would run ;-) The problem is the maven-scr-plugin which
always sets the immediate attribute to true (if not explicitly) set.
This is incorrect in connection with using the factory attribute (the
same happens for the jcr/jackrabbit-server and jcr/jackrabbit-c
Hi,
Am Dienstag, den 03.06.2008, 11:42 +0200 schrieb Carsten Ziegeler:
> Bertrand Delacretaz wrote:
> >
> > I'm finishing up the NOTICE stuff, I suggest regenerating *all* NOTICE
> > files with the mknotice script.
> >
> Great!
>
> > I'll modify the script to concatenate an optional local.notic
Bertrand Delacretaz wrote:
I'm finishing up the NOTICE stuff, I suggest regenerating *all* NOTICE
files with the mknotice script.
Great!
I'll modify the script to concatenate an optional local.notice.txt
file, found in the same directory as the module's pom.xml, to the end
of the NOTICE, for
On Tue, Jun 3, 2008 at 11:13 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> I created a profile in our reactor pom with the modules we don't want to
> include in our first release. I'm not sure if this list is complete/correct,
> so please cross check
Looks good to me.
>... I think we shou
I created a profile in our reactor pom with the modules we don't want to
include in our first release. I'm not sure if this list is
complete/correct, so please cross check.
I think we should try to build the release today, so what else needs to
be done?
Carsten
--
Carsten Ziegeler
[EMAIL PRO
Bertrand Delacretaz wrote:
On Mon, Jun 2, 2008 at 11:15 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Bertrand Delacretaz wrote:
...IIRC, Wicket has a way of combining multiple NOTICE files using Maven,
I'll have a look at that...
Afaik this is done by the maven remote resources plugin. I l
On Mon, Jun 2, 2008 at 11:15 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Bertrand Delacretaz wrote:
>> ...IIRC, Wicket has a way of combining multiple NOTICE files using Maven,
>> I'll have a look at that...
>>
> Afaik this is done by the maven remote resources plugin. I looked at it some
> m
Bertrand Delacretaz wrote:
On Mon, Jun 2, 2008 at 10:38 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
...Am Montag, den 02.06.2008, 10:36 +0200 schrieb Bertrand Delacretaz:
... I think we must update the NOTICE files of the launchpad/app and
webapp modules to mention all non-Apache dependen
Am Montag, den 02.06.2008, 10:41 +0200 schrieb Bertrand Delacretaz:
> On Fri, May 30, 2008 at 2:40 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> >> ...The final question is, what = which parts we want to release? ...
>
> > ...I would say: api, engine, jcr (api, base, classloader, contentloade
Hi,
Am Montag, den 02.06.2008, 10:43 +0200 schrieb Bertrand Delacretaz:
> On Mon, Jun 2, 2008 at 10:38 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ...Am Montag, den 02.06.2008, 10:36 +0200 schrieb Bertrand Delacretaz:
> >>... I think we must update the NOTICE files of the launchpad/app
On Mon, Jun 2, 2008 at 10:38 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Am Montag, den 02.06.2008, 10:36 +0200 schrieb Bertrand Delacretaz:
>>... I think we must update the NOTICE files of the launchpad/app and
>> webapp modules to mention all non-Apache dependencies, as listed by
>> mv
On Fri, May 30, 2008 at 2:40 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>> ...The final question is, what = which parts we want to release? ...
> ...I would say: api, engine, jcr (api, base, classloader, contentloader,
> jackrabbit-*, ocm, resource, webdav), launchpad/*, event, i18n,
> httpa
Hi,
Am Montag, den 02.06.2008, 10:36 +0200 schrieb Bertrand Delacretaz:
> On Fri, May 30, 2008 at 2:40 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> >> ...The final question is, what = which parts we want to release? ...
>
> > I would say: api, engine, jcr (api, base, classloader, contentloa
1 - 100 of 119 matches
Mail list logo
