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
Bertrand Delacretaz wrote:
Here the goal is to check that the contents match what's tagged with
the same release number under
http://svn.apache.org/repos/asf/incubator/sling/tags/, right?
Yes, and to make sure that everything is correct from a legal pov.
However, org.apache.sling.launchpad.we
Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 11:39 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
...Whoa, you are running almost 50 release votes in parallel?!? I'm all
for modularity, but isn't this a bit extreme?...
Ah - didn't see this message before writing my "how to check the
releas
On Wed, Jun 4, 2008 at 11:39 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> ...Whoa, you are running almost 50 release votes in parallel?!? I'm all
> for modularity, but isn't this a bit extreme?...
Ah - didn't see this message before writing my "how to check the
release" one ;-)
I'll probably c
Hi,
Thanks Carsten for preparing the release!
On Wed, Jun 4, 2008 at 7:51 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ...I've put all release artifacts here:
That's a lot, and I'm wondering how to check all that - comments below.
> ...The releases (source archives) are in
> http://people.
On Thu, Jun 5, 2008 at 7:55 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Alexander Klimetschek wrote:
>> ...I have some suggestions for changes to the i18n/message bundle node
>> types (although not finalized).
>>
>> Could this artifact be released later?...
Would your changes be backwards-i
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 no
Jukka Zitting wrote:
Hi,
Whoa, you are running almost 50 release votes in parallel?!? I'm all
for modularity, but isn't this a bit extreme?
What's wrong with just tagging the entire trunk and having the release
candidate be the packaged svn export of that tag?
Hmm, don't know - noone came up
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]
Alexander Klimetschek wrote:
Have you built Sling from the root directory before
(X:\java\labs\osgi-sling\svn\sling\> mvn install)? Looks like the
Sling root pom is not yet in your local maven 2 repository (and since
there is no release yet, it is not on any public repositories yet).
Ups, you'r
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 no other code in Sling
depends on
Have you built Sling from the root directory before
(X:\java\labs\osgi-sling\svn\sling\> mvn install)? Looks like the
Sling root pom is not yet in your local maven 2 repository (and since
there is no release yet, it is not on any public repositories yet).
Regards,
Alex
On Wed, Jun 4, 2008 at 10:5
[
https://issues.apache.org/jira/browse/SLING-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Trieloff updated SLING-511:
Attachment: SLING-511.patch
updated dojo version and checksum to 1.1.1
> Update Dojo dependency to
Update Dojo dependency to 1.1.1
---
Key: SLING-511
URL: https://issues.apache.org/jira/browse/SLING-511
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: 2.0.1
Good point, I will create an issue+patch.
On Jun 3, 2008, at 23:42 , Craig L. Ching wrote:
Hi Lars,
We resolved the issue this morning, so no need to look into
anything ;-)
The fix was pretty trivial.
One thing I would like to point out, though, dojo recently released
1.1.1, might consider
Hi,
On Wed, Jun 4, 2008 at 8:51 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> This time we are releasing a lot of artifacts - after this first release
> we will release one or two artifacts at a time in different intervals. As
> always the initial release is the hardest one.
>
> Although we re
Hi All
I am trying to get started, however
( Am I missing a repository setting ? )
X:\java\labs\osgi-sling\svn\sling\maven\maven-sling-plugin>mvn -Papache
install
[INFO] Scanning for projects...
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/sling/sling/1-incubator/
Hi,
I'm trying to use some of the JCR bundles and I'm having problems
caused by unresolved dependencies. this problem occurs both in Equinox
and Felix. I'm using the current version from trunk.
Not sure if it's related but I tried to see which dependencies are
missing and I found the following:
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
On Jun 4, 2008, at 5:41 AM, Carsten Ziegeler wrote:
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.
NOTICE is only for attributions that are required by their corresponding
copyright license or r
Hello everyone,
after some struggling we finally managed to built the release candidates
(hurray); thanks for everyone helping in getting this done.
I've put all release artifacts here:
http://people.apache.org/~cziegeler/releases/sling/
The releases (source archives) are in
http://people.ap
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
Hi Bertrand,
I have created a jira issue to submit my code untill I'm able commit to the
google project. Hope it's fine for the moment.
janandith.
Hi Felix,
I've created a jira issue and attached the code as scala.tar.gz till I'm
able to commit to the google project.
Please have a look at it.
janandith.
Hi ,
I cannot commit my code to http://code.google.com/p/sling-scala although I
tried several times. I think I need access rights.
Therefore I created a jira issue to submit my code and experiments
related to the project.
This is the first time I've created a jira issue so please correct me i
[
https://issues.apache.org/jira/browse/SLING-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janandith Uditha Jayawardena updated SLING-510:
---
Attachment: scala-standalone.tar.gz
This is the experiment java proje
[
https://issues.apache.org/jira/browse/SLING-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janandith Uditha Jayawardena updated SLING-510:
---
Attachment: scala.tar.gz
This is the code I've written under sling/sc
This Is the current code for google summer of code sling/scala.
---
Key: SLING-510
URL: https://issues.apache.org/jira/browse/SLING-510
Project: Sling
Issue Type: New Feature
BTW, who determines what version of Jetty you distribute? Is it Sling
or is it Felix? More curious than anything, but Jetty is on 6.1.11 and
it's including more and more features around it's cometd implementation
that I'd like to use. I'm assuming I could probably roll my own
distribution that u
[
https://issues.apache.org/jira/browse/SLING-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-509:
--
Attachment: rat.txt
RAT report from revision 663156 - fixed license headers since the la
[
https://issues.apache.org/jira/browse/SLING-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-509.
---
Resolution: Fixed
> Run RAT and add missing license headers
>
[
https://issues.apache.org/jira/browse/SLING-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-509:
--
Fix Version/s: 2.0.0
> Run RAT and add missing license headers
> ---
[
https://issues.apache.org/jira/browse/SLING-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-509:
--
Attachment: rat.txt
RAT report for revision 663126
> Run RAT and add missing license he
Run RAT and add missing license headers
---
Key: SLING-509
URL: https://issues.apache.org/jira/browse/SLING-509
Project: Sling
Issue Type: Test
Reporter: Bertrand Delacretaz
We should run RAT
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]
[
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
On Wed, Jun 4, 2008 at 3:33 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ...For instance maven thinks that there is a mx4j inclusion in the scheduler.
> But it is definitly not, mx4j is used by quartz at compile time, but it's
> neither used at runtime nor is it distributed by us
I'm fin
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 i
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 is copyright ASF.
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 reflec
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
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 is copyright ASF.
Hmm, ok, might make sense.
...Another issue is that now all notices files have
[
https://issues.apache.org/jira/browse/SLING-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602279#action_12602279
]
Bertrand Delacretaz commented on SLING-493:
---
See the mknotice script for info abou
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 reflects Roy's changes.
>... I r
On Wed, Jun 4, 2008 at 2:41 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ...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?
I don't t
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602275#action_12602275
]
Bertrand Delacretaz commented on SLING-495:
---
A number of those notices were remove
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
Hi,
I just started to look at the new notice files and found several
problems, so I reopened the bug and added the info there.
I really think we should go back to hand written notice files, let's use
the now generated once as a starting point.
In addition I think we can remove the first bla
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602268#action_12602268
]
Carsten Ziegeler commented on SLING-495:
commons/scheduler: This product includes so
[
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://json.or
Parameter decoding uses wrong default charset
-
Key: SLING-508
URL: https://issues.apache.org/jira/browse/SLING-508
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions:
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]
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]
[
https://issues.apache.org/jira/browse/SLING-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Tucker closed SLING-500.
---
> The Dojo Toolkit bundle doesn't include the Dojo source files
>
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz closed SLING-495.
-
Resolution: Fixed
NOTICE files regenerated in revision 663025
> Complete our NOTICE files
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
[
https://issues.apache.org/jira/browse/SLING-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reopened SLING-495:
---
Reopening to account for fielding's changes in revisions 662927
> Complete our NOTICE fil
Hi,
Am Dienstag, den 03.06.2008, 23:56 + schrieb [EMAIL PROTECTED]:
> Note: we cannot redistribute Jetty under the terms here. If we
> are only going to redistribute a portion of Jetty, then remove
> the other parts from the Jetty notice file.
We only redistribute the jetty-6.1.6.jar and jet
62 matches
Mail list logo
