Just for information. I followed Benedikt's suggestion and I opened a issue:
https://issues.apache.org/jira/browse/SANDBOX-481
Regards.
2014-07-23 15:45 GMT+02:00 Benedikt Ritter :
> Hello Luca,
>
> I haven't seen any activity in that component for a while. If you like to
> revive the project,
Le 10/09/2014 21:49, Konstantin Kolinko a écrit :
> 2014-09-10 20:32 GMT+04:00 Luc Maisonobe :
>> Le 10/09/2014 16:28, Evan Ward a écrit :
>>> Thanks Luc for volunteering to oversee this. What is the status of the
>>> switch? I have a couple documentation updates I'm waiting to commit
>>> because I
2014-09-10 20:32 GMT+04:00 Luc Maisonobe :
> Le 10/09/2014 16:28, Evan Ward a écrit :
>> Thanks Luc for volunteering to oversee this. What is the status of the
>> switch? I have a couple documentation updates I'm waiting to commit
>> because I thought this switch was imminent.
>
> I have looked at
Doesn't the compiler do this already?
Also please try not to mix in other changes like format changes in a single
commit.
Gary
Original message From: brentwor...@apache.org
Date:09/10/2014 13:28 (GMT-05:00) To:
comm...@commons.apache.org Subject: svn commit: r1624061 -
/
Hello Benedikt,
thanks for the feedback, no worries, take your time.
I already fixed the below mentioned wrong template-comments.
For the project id/url related stuff I did not take a deeper look as it
is I guess moslty getting familiar with the commons-parent structure.
However let me know if
On 9 September 2014 20:25, Benedikt Ritter wrote:
> you mean like
> http://docs.oracle.com/javase/${maven.compiler.source}/docs/api/
> ?
Yes.
Though it might be better to use an intermediate property as follows:
${maven.compiler.source}
http://docs.oracle.com/javase/${commons.javadoc.link.ve
Le 10/09/2014 16:28, Evan Ward a écrit :
> Thanks Luc for volunteering to oversee this. What is the status of the
> switch? I have a couple documentation updates I'm waiting to commit
> because I thought this switch was imminent.
I have looked at the ticket and saw I miseed a question from infra,
On 9 September 2014 22:02, Emmanuel Bourg wrote:
> I think I'll just upload the artifacts on people.apache.org and put the
> release to a vote. We can upload the release in Maven Central later.
The non-Maven archives should please be uploaded to
https://dist.apache.org/repos/dist/dev/commons/
r
On 10 September 2014 11:26, Gilles wrote:
> On Wed, 10 Sep 2014 12:00:12 +0200, Stefan Bodewig wrote:
>>
>> [on the original topic: I personally like git but would leave the
>> decision to move on to the components]
>>
>> On 2014-09-10, Gilles wrote:
>>
>>> [The advantages of "git" must be somewhe
Thanks Luc for volunteering to oversee this. What is the status of the
switch? I have a couple documentation updates I'm waiting to commit
because I thought this switch was imminent.
Best Regards,
Evan
On 08/25/2014 05:23 AM, Luc Maisonobe wrote:
> Hi all,
>
> Le 21/08/2014 11:07, Luc Maisonobe a
ah, I have HttpsEverywhere and it redirs my request to HTTPS which there is
none, plain HTTP works. Looks good.
Gary
On Wed, Sep 10, 2014 at 7:39 AM, Stefan Bodewig wrote:
> On 2014-09-10, Gary Gregory wrote:
>
> > Hm... "The requested URL /security.html was not found on this server."
>
> I cop
+1 for moving to git, and using Atlassian's stash and crucible.
Git branching is very different than subversion, and any feature or issue
can have it's own branch and merged into master through a pull request. We
can also have rules on code reviews before a branch is merged onto master
or say rules
On 2014-09-10, Gary Gregory wrote:
> Hm... "The requested URL /security.html was not found on this server."
I copy pasted the link from my browser. The page has been there for
almost two weeks now, so we can rule out stale caches.
Are you sure you are trying the URL that contains "staging" insi
Hm... "The requested URL /security.html was not found on this server."
Gary
On Wed, Sep 10, 2014 at 6:16 AM, Stefan Bodewig wrote:
> Hi
>
> I've just added a link to the security page inside the main navigation,
> see
>
> http://commons.staging.apache.org/security.html
>
> The page is insid
On Wed, 10 Sep 2014 12:00:12 +0200, Stefan Bodewig wrote:
[on the original topic: I personally like git but would leave the
decision to move on to the components]
On 2014-09-10, Gilles wrote:
[The advantages of "git" must be somewhere else.]
Not sure about "the advantage", but let me show yo
On Wed, 10 Sep 2014 11:55:52 +0200, Luc Maisonobe wrote:
Hi Gilles,
Le 10/09/2014 11:43, Gilles a écrit :
On Wed, 10 Sep 2014 07:49:13 +0300, Silviu Burcea wrote:
This is the killer feature for Git, because many of us, the
newcomers,
like
me, will want to experiment a little before submitting
Hi
I've just added a link to the security page inside the main navigation,
see
http://commons.staging.apache.org/security.html
The page is inside the staging area only, but I'd like to publish it
sooner rather than later - and update the commons parent to include the
same link.
Should the l
Le 10/09/2014 11:43, Gilles a écrit :
> This use case does not convince me at all: when working on a feature,
> you always do it locally (modifying code, preparing unit tests), and
> SVN certainly does not force you to experiment publicly; it's rather
> the project's policy that forbids you to com
[on the original topic: I personally like git but would leave the
decision to move on to the components]
On 2014-09-10, Gilles wrote:
> [The advantages of "git" must be somewhere else.]
Not sure about "the advantage", but let me show you an example where a
DVCS (any DVCS) would have been really
Hello Bernd,
I'm back from Portual and will try to have a look at your comments this
week :-)
Thanks!
Benedikt
2014-08-31 23:20 GMT+02:00 Bernd Eckenfels :
> Hello Benedikt,
>
> I finally had some time to look at this. I tried to integrate it into
> VFS. I did not (yet) change the commpons-pare
Hi Gilles,
Le 10/09/2014 11:43, Gilles a écrit :
> On Wed, 10 Sep 2014 07:49:13 +0300, Silviu Burcea wrote:
>> This is the killer feature for Git, because many of us, the newcomers,
>> like
>> me, will want to experiment a little before submitting a patch. This
>> way, I
>> can create a local bran
On Wed, 10 Sep 2014 07:49:13 +0300, Silviu Burcea wrote:
This is the killer feature for Git, because many of us, the
newcomers, like
me, will want to experiment a little before submitting a patch. This
way, I
can create a local branch and I'm free to do whatever I want. The SVN
branch is visibl
22 matches
Mail list logo
