Revert to hand written notice files
---
Key: SLING-521
URL: https://issues.apache.org/jira/browse/SLING-521
Project: Sling
Issue Type: Task
Affects Versions: 2.0.1
Reporter: Carsten Ziegeler
[
https://issues.apache.org/jira/browse/SLING-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-504.
--
Resolution: Won't Fix
We revert the automated generation.
Use optional scope for dependencies
NOT involve quering for the key value.
So, I think, you can create the issue -- and fmeschbe says, he would be
happy to also get a patch ;-)
Thanks and Regards
Felix
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-503:
--
Assignee: Carsten Ziegeler
Disable SCR plugin for Factory Components
[
https://issues.apache.org/jira/browse/SLING-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-503:
---
Summary: Enable SCR plugin for Factory Components (was: Disable SCR plugin
for Factory
: Carsten Ziegeler
Fix For: 2.0.1
We should update to the Felix SCR Implementation 1.0.1 when it's ready. It
fixes a bug where we currently have a workaround.
The changes of Rev. 662747 are to be reverted.
See SLING-502
--
This message is automatically generated by JIRA.
-
You can
.
If it's not a major problem (and I think it isn't), we can live with
this and fix this for the next release. Doing it for this release would
mean rerunning the whole release process which I would like to avoid atm.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
--
Carsten Ziegeler
[EMAIL PROTECTED]
Jukka Zitting wrote:
Hi,
On Thu, Jun 5, 2008 at 8:54 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Hmm, don't know - noone came up with this *before* doing the release. :)
I was expecting that we'd do a single release, not dozens of them at
the same time. :-)
In the end I see no real
and launchpad webapp. In addition we will provide all
maven artifacts. I'll build all these from the tag created in c)
e) All upcoming releases will be single bundle releases.
I hope this is ok for everyone?
Carsten
Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 7:51 PM, Carsten Ziegeler [EMAIL
Bertrand Delacretaz wrote:
On Thu, Jun 5, 2008 at 11:41 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... e) All upcoming releases will be single bundle releases
I think Jukka has valid points here, but we don't need to decide on
this right now.
... I hope this is ok for everyone
?
Cheers,
Craig
-Original Message-
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 12:52 AM
To: sling-dev@incubator.apache.org
Subject: Re: Cannot find parent: org.apache.sling:sling for project
Mark wrote:
Hi All
I am trying to get started, however
to check my signature is at
http://people.apache.org/~cziegeler/releases/sling/
This is basically just one big release, so please cast your votes.
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Carsten Ziegeler wrote:
Hello everyone,
let's give it a second try. I cut a new candidate as outlined today.
I've put all release artifacts here:
http://people.apache.org/~cziegeler/releases/sling/
The releases are in
http://people.apache.org/~cziegeler/releases/sling/releases
with exceptions, I'll modify
the mknotice script now, to ignore #comment lines.
Ok, where are we now? :)
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.
Carsten
--
Carsten Ziegeler
[EMAIL
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]
Hi,
the following line needs to be added to the notice file in the
commons/json module:
This product includes software developed at http://json.org.
Don't know how to add this in the automated process?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reopened SLING-495:
There are still issues:
commons/json: This product includes software developed at http
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602268#action_12602268
]
Carsten Ziegeler commented on SLING-495:
commons/scheduler: This product includes
the based on Day
Software stuff in it. While this is true for most of our modules, it's
not for all.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
files is done in many other
projects and I thought that we have to give them attribution if we
include their stuff. Now, Roy removed these. I'm clueless what's right,
sorry.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 2:51 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...I just started to look at the new notice files and found several problems,
so I reopened the bug and added the info there...
See my comments in SLING-495 - I think the current state
Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 3:30 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
Easy - just remove the first line of etc/notice/notices/prefix.txt.
For now I left it because I think that's what Roy intendend, i.e. that
Apache Sling as a whole
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-495.
--
Resolution: Fixed
It seems that these are all non-issues, apart from mx4j which should be fixed
If noone stops me I'll start to build the release candidates now
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
and start the vote.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
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
org.apache.sling.scripting.javascript-2.0.0-incubator
org.apache.sling.scripting.jsp.taglib-2.0.0-incubator
org.apache.sling.servlets.get-2.0.0-incubator
org.apache.sling.servlets.post-2.0.0-incubator
org.apache.sling.servlets.resolver-2.0.0-incubator
So please cast your votes.
Thanks
Carsten
--
Carsten
file
required
for each differently packaged set of bits. We must do this by hand.
So this basically means that we only have to add something to the NOTICE
file if the license of an included project requires this, right?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
, you're right - will fix this asap.
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Mark wrote:
Hi All
I am trying to get started, however
( Am I missing a repository setting ? )
Hi, no this was a leftover from building the release candidate
yesterday. Sorry for the inconvenience. It should be fixed now.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
other parts do not meet the release
criteria - although I'm very confident that we did it right).
If you wish, you can extract all 50 packages into one directory and test
them at once :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Alexander Klimetschek wrote:
On Wed, Jun 4, 2008 at 7:51 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
org.apache.sling.i18n-2.0.0-incubator
I have some suggestions for changes to the i18n/message bundle node
types (although not finalized).
Could this artifact be released later? (AFAIK
: Event
Affects Versions: 2.0.0
Reporter: Carsten Ziegeler
In a clustered environment a job might be executed by the first free node.
Usually this should not cause any problems as the job event should contain all
necessary information. However in some cases it might not be possible
appear in the NOTICE file that is required by our license to be
displayed by downstream binary distributions like an About box.
Roy
--
Carsten Ziegeler
[EMAIL PROTECTED]
Reporter: Carsten Ziegeler
Usually jobs are executed in random manner (usually first one, first out), but
especially in a cluster this might not be true.
For some jobs it might be interesting to keep the order of execution.
--
This message is automatically generated by JIRA.
-
You can reply
: Carsten Ziegeler
It would be nice to specify a url mapping directly in the bundle header, like:
Sling-Initial-ContentSLING-INF/content/Sling-Initial-Content
Sling-Root-Mapping/apps/xyz/docroot,
/apps/abc/docroot/Sling-Root-Mapping
This would create two mappings:
- / to /apps/xyz/docroot
:)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
hit the issue from the first day. But until now,
mails were not sent to this list :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
and of course latest
Sling...so I'm wondering if we could fix this issue in a way that Sling
runs with the old SCR and the new one?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601875#action_12601875
]
Carsten Ziegeler commented on SLING-501:
This occurs due to the changes in FELIX-593
not using the scr plugin for the logger but hand
writing the xml file?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
week.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
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
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 bundle
notice file
seems to be wrong.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Affects Versions: 2.0.0
Reporter: Carsten Ziegeler
If debug logging is used, every two seconds a lot of debug messages are added
by the repository pinger. This makes the log nearly unusable as it grows way
too fast.
--
This message is automatically generated by JIRA.
-
You can reply
as optional and provided to what we do...not optimal though.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Ok, can we release?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-505.
--
Resolution: Fixed
Unfortunately this is not the only component involved in debug logging
. As dependencies
do not change that often, I would prefer doing it by hand.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
the queue
to our custom handler?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
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
the logger to level DEBUG and provide the logs?
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
keep all the duplicates in our code base, what about removing
stuff that we don't use like the cookies stuff etc?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
. But removing
parts might be confusing.
Hmm, I think it's more confusing to have a big lib where only three
classes are used from :) But either way works for me.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
the setProperty method on
the mock object.
WDYT?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-483.
--
Resolution: Fixed
I've disabled javadocs where we don't need them and excluded private packages
is, what = which parts we want to release? I think
there are some bundles/modules which we don't need to include in a first
cut.
WDYT?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-486:
---
Fix Version/s: (was: 2.0.0)
2.0.1
As this is not a bug in Sling
initialized.
WDYT?
-Bertrand
--
Carsten Ziegeler
[EMAIL PROTECTED]
Hi,
it seems that the continuum mails are not sent to our sling-commits list
anymore. Sending mails from continuum in general works. Are they stuck
in some moderation queue?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Affects Versions: 2.0.0
Reporter: Carsten Ziegeler
Fix For: 2.0.0
When a bundle containing a servlet filter is updated, the old already disposed
instance is still used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
[
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600475#action_12600475
]
Carsten Ziegeler commented on SLING-486:
Further debugging seems to reveal
[
https://issues.apache.org/jira/browse/SLING-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600471#action_12600471
]
Carsten Ziegeler commented on SLING-486:
Yes, I did refresh - here are some updates
and I get
the continuum mails; I'll check the sender the next time I get a mail :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Components: Event
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: 2.0.0
A job can be configured when the job event is sent with a number of retries
indicating how often the job should be rescheduled if something goes wrong.
If this configuration
[
https://issues.apache.org/jira/browse/SLING-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599577#action_12599577
]
Carsten Ziegeler commented on SLING-462:
Looking at the code, I curently can't see
[
https://issues.apache.org/jira/browse/SLING-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-462:
--
Assignee: Carsten Ziegeler
Endless loop in JobEventHandler
[
https://issues.apache.org/jira/browse/SLING-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-452.
--
Resolution: Fixed
Cleaned up the list and added some new components.
Check jira components
/content/home.html
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-460.
Resolution: Fixed
The order of the attributes and directives is now preserved.
commons
The order of attributes and directives is now preserved. Jeremias could
you please test if this works for you (I don't have access to a windows
system atm)?
Thanks
Carsten
Carsten Ziegeler wrote:
Felix Meschberger wrote:
Hi,
Without reading code, this sounds like depending on the order
[
https://issues.apache.org/jira/browse/SLING-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-414:
--
Assignee: Carsten Ziegeler
Environment properties like sling.id, or sling.home
[
https://issues.apache.org/jira/browse/SLING-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-460.
--
commons/osgi testAttributes() and testDirectives() fail under Windows
[
https://issues.apache.org/jira/browse/SLING-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597406#action_12597406
]
Carsten Ziegeler commented on SLING-414:
The sling.home variable makes only sense
[
https://issues.apache.org/jira/browse/SLING-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-460:
--
Assignee: Carsten Ziegeler
commons/osgi testAttributes() and testDirectives() fail
[
https://issues.apache.org/jira/browse/SLING-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-414.
--
Resolution: Fixed
Added new SlingSettingsService in the engine module which creates
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-365:
---
Fix Version/s: 2.0.0
This should be fixed for the first release.
Checkin versionable nodes
: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: 2.0.0
We need to parse manifest entries at several places, therefore it makes sense
to have a parser at a common place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
[
https://issues.apache.org/jira/browse/SLING-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-441:
--
Assignee: Carsten Ziegeler
Windows Users receiving java.lang.NoClassDefFoundError
in the jcr/contentloader) and a static method to create a
collection of such entry instances from a header string would be best.
I just added a new ManifestHeader class to the commons osgi module.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Hi,
as we are through with all the refactorings (hopefully) I just added all
projects to continuum again. So let's wait for the mails...
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597055#action_12597055
]
Carsten Ziegeler commented on SLING-441:
I just tested the latest from svn on vista
of the prefixes will be stored
* Parameters prefixed with the colon (:) will never be stored as they are
intended as processing parameters
--
Carsten Ziegeler
[EMAIL PROTECTED]
Ok, no answer so far :(
I looked at the config admin and I think that we perhaps could achieve a
simpler solution by providing a ConfigurationPlugin which adds the
sling.id to the configuration.
WDYT?
Carsten
Carsten Ziegeler wrote:
Hi,
I'm wondering how we solve this issue. Currently
a little bit with the
interface
during development to see what's best.
I think we should postpone this until after the release.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-446:
--
Assignee: Carsten Ziegeler
Move Scheduling to commons
[
https://issues.apache.org/jira/browse/SLING-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-450:
--
Assignee: Carsten Ziegeler
Move bundles from sling to extensions
[
https://issues.apache.org/jira/browse/SLING-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-450.
--
Resolution: Fixed
Moved all bundles to extensions
Move bundles from sling to extensions
[
https://issues.apache.org/jira/browse/SLING-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-446.
--
Resolution: Fixed
Moved and refactored to commons package.
Move Scheduling to commons
Felix Meschberger wrote:
Hi,
Am Mittwoch, den 14.05.2008, 10:23 +0200 schrieb Carsten Ziegeler:
Hi,
should we also rename the package from core to engine (and everything
else)? I think so, but I just wanted to check before doing :)
Yes, I would say so, too.
In addtion: the core (or engine
[
https://issues.apache.org/jira/browse/SLING-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-449.
--
Resolution: Fixed
Move core to engine and renamed the packages, the artifact id
[
https://issues.apache.org/jira/browse/SLING-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-451:
--
Assignee: Carsten Ziegeler
Rename current sling directory to servlets
[
https://issues.apache.org/jira/browse/SLING-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-451.
--
Resolution: Fixed
Directory has been renamed.
servlets-get has been renamed to servlets/get
the same syntax for the various
additional information.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Issue Type: Task
Components: Core
Reporter: Carsten Ziegeler
Fix For: 2.0.0
We should check all poms for accurancy before the release as due to the
refactoring some poms might not be correct anymore.
--
This message is automatically generated by JIRA.
-
You
from Sling. As the testing stuff is about
jcr testing, we could move it to the jcr modules?
(This one is not that important though)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SLING-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-439.
--
Resolution: Fixed
Removed selector node type together with object handling stuff from core
501 - 600 of 1029 matches
Mail list logo
