Can be useful, if one comes across a source file in isolation from SVN.
What exactly can this person then do with a revision number, my
committer name and the date i have last commited if he does not know
about svn revisions, who else does commit and when last commit was?
For example, in
/
http://www.99soft.org/
On Sun, Oct 9, 2011 at 6:23 PM, Christian Grobmeier grobme...@gmail.com
wrote:
Hi
I'm honestly skeptical on removing stuff, no one knows who's using
that methods - I should to take care about checking on MyBatis code,
AFAIK Struts uses some of them...
What
Hello guys,
is this one resolved?
https://issues.apache.org/jira/browse/OGNL-13
Looks like it - if yes, please close :-)
Cheers
Christian
--
http://www.grobmeier.de
-
To unsubscribe, e-mail:
:58 AM, Christian Grobmeier
grobme...@gmail.com wrote:
Hello guys,
is this one resolved?
https://issues.apache.org/jira/browse/OGNL-13
Looks like it - if yes, please close :-)
Cheers
Christian
--
http://www.grobmeier.de
of 'Closed' and then move to 'Closed' only once the RC
has passed!
Thoughts?
best,
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 11:12 AM, Christian Grobmeier
grobme
This looks fixed too - can i set it to resolved?
https://issues.apache.org/jira/browse/OGNL-9
TO my knowledge i have runned all tests with v4
--
http://www.grobmeier.de
-
To unsubscribe, e-mail:
Hey guys,
i would like to suggest we make consequent use of changes.xml.
Whatever we do, we should open an issue, fix the stuff, and then add a
comment to changes.xml. We do this in log4php and I feel it is very
good: you always can find the changes per issues (via Fisheye- just
check in with the
mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 13.34, Christian Grobmeier grobme...@gmail.com ha
scritto:
Hey guys,
i would like to suggest we make consequent use of changes.xml.
Whatever we do, we should open an issue, fix the stuff, and then add
Of course, but automated changes are not guaranteed error-free.
I never had an error with Eclipse (use that since 2002 or so).
And it's easy to overlook some other change that was accidentally
committed at the same time.
As with every change. Actually with this argument we should stop
On Mon, Oct 10, 2011 at 10:42 AM, Olivier Lamy ol...@apache.org wrote:
Hello,
Looks nice ! I'd like to use for some other projects.
+1
I like too the idea about having this skin in the maven skins.
+1!!
Cheers
Christian
@Simone: feel free to commit in maven sandbox if you want. It's open
://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Oct 9, 2011 at 7:53 AM, Christian Grobmeier grobme...@gmail.com
wrote:
Hi all,
Checkstyle shows me more or less that we should go conform the Sun
standards. I would love this, but want to make sure we have agreed on
it. Because
Hi,
the code patch on ognl-21 does remove some public methods on
OgnlRuntime and SimpleNode. I don't think folks are usually caring on
those two classes, but how do we proceed with backwards compatility?
Daniel has remove a bunch of methods, which really look a bit outdated
or unused. As we are
/~simonetripodi/
http://www.99soft.org/
On Sun, Oct 9, 2011 at 3:56 PM, Christian Grobmeier grobme...@gmail.com
wrote:
Hi,
the code patch on ognl-21 does remove some public methods on
OgnlRuntime and SimpleNode. I don't think folks are usually caring on
those two classes, but how do we proceed
Hi all,
Checkstyle shows me more or less that we should go conform the Sun
standards. I would love this, but want to make sure we have agreed on
it. Because it would need a good bunch of bracket-moving
Cheers
Christian
-
To
for the site, and I would like to take advantage from a
discussion born in the incubator ML[1] to renew the discussion,
because our commons-fellow Christian Grobmeier came out with nice
(IMHO) improvements[2] just adopting a style provided from Twitter[3]
(ASL Licensed) called Bootstrap.
I just did a 5
Hi,
it seems the patches on the issue tracker are not straightforward to
apply. As Simone suggested, I would like to commit the changes
(basically a combination of my own ideas, work of Daniel Pitts and
some inspiration from JEXL) to the trunk. Then everybody can review it
and - if necessary -
/
On Thu, Oct 6, 2011 at 10:24 AM, Christian Grobmeier
grobme...@gmail.com wrote:
Hi,
it seems the patches on the issue tracker are not straightforward to
apply. As Simone suggested, I would like to commit the changes
(basically a combination of my own ideas, work of Daniel Pitts and
some
It's not clear whether the exception is expected, in which case the
output should be suppressed, or an error, in which case the test
should just be allowed to fail with the exception.
I was looking into the test cases but they are, well, pretty different from
what I am used so I thought I
Hi,
I just runned the test cases of ognl (first time I am afraid :-().
They all end up green, but throw console exceptions. Is this ok? I was
looking into the test cases but they are, well, pretty different from
what I am used so I thought I better ask. From what I understood I
would say
On Wed, Sep 14, 2011 at 8:56 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all guys,
there was an era when OGNL was totally dependencies-less, today relies
on Javassist - I never understood the reason of adopting it.
OGNL didn have dependencies? How cool is that!
I love libs which have
2011/8/25 Christian Grobmeier grobme...@gmail.com:
The vote has passed with 10 persons voting.
From Commons:
Gary Gregory
Henri Yandell
Sebastian Bazley
Oliver Heger
Christian Grobmeier
Simone Tripodi
Luc Maisonobe
Paul Benedict (non binding)
From OGNL:
Maurizio Cucchiara
Christian
Yes.
I just requested the karma for:
javadrewd
jkuhnert
leadpipe
lukaszlenart
mcucchiara
upayavira
Might take a few days - sorry if it comes to a delay
2011/8/31 Łukasz Lenart lukasz.len...@googlemail.com:
Do I need the same ?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
I've asked to import OGNL issues as well, any one to help mi with that
? Just ask Tony for a user.
What is your criteria do move the issues?
I have not really a deeper knowledge of OGNL. Why aren't we moving all
issues from the temp project to the real project at once and sort
them out there
on OGNL space on Jira, WDYT?
Good idea, I have done that and linked both issues together
Cheers
Many thanks in advance and thanks for notifying!!!
All the best, alles gute!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Aug 29, 2011 at 2:04 PM, Christian
Dear all,
this vote has passed with 6 +1, 4 of them binding:
Chris Mattmann
Martijn Dashorst
Christian Grobmeier
Robert Donkin
Craig Russel *
Maurizio Cucchiara *
Thanks to all who voted!
OGNL will perform the next steps:
http://incubator.apache.org/guides/graduation.html#subproject
Cheers
Hello;
https://issues.apache.org/jira/browse/OGNL-3
Last information in this issue was, opensymphony is down - it seems
they are back:
http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10090fixfor=-1
We should use
On Tue, Aug 30, 2011 at 2:57 PM, sebb seb...@gmail.com wrote:
On 30 August 2011 13:38, Christian Grobmeier grobme...@gmail.com wrote:
Dear all,
this vote has passed with 6 +1, 4 of them binding:
Chris Mattmann
Martijn Dashorst
Christian Grobmeier
Robert Donkin
Craig Russel *
I assume
On Tue, Aug 30, 2011 at 3:08 PM, Maurizio Cucchiara
mcucchi...@apache.org wrote:
Christian,
this is the INFRA issue http://issues.apache.org/jira/browse/INFRA-2577
Looks like Lukasz is taking care of.
Thanks Maurizio
Maurizio Cucchiara
On 30 August 2011 14:44, Christian Grobmeier grobme
Hello guys,
a discussion on the STruts list brought this to my attention:
https://issues.apache.org/jira/browse/WW-3580
As Struts is one of OGNL main consumers, maybe we make them a little
gift with OGNL 4.0.
What do you think?
Cheers
Christian
The vote has passed with 10 persons voting.
From Commons:
Gary Gregory
Henri Yandell
Sebastian Bazley
Oliver Heger
Christian Grobmeier
Simone Tripodi
Luc Maisonobe
Paul Benedict (non binding)
From OGNL:
Maurizio Cucchiara
Christian Grobmeier
Olivier Lamy
Simone Tripodi
I will now open
OGNL [1] has checked off all status items in the incubator.
Most of the OGNL developers are already commons developers and the
risk of failure is pretty small, even without having made a release.
As the Commons project is already very experienced with releasing
components, there is no need for
+1 to both votes
On Sat, Aug 13, 2011 at 2:13 AM, sebb seb...@gmail.com wrote:
BSF [1] needs to move out of Jakarta.
It's not really big enough to warrant its own TLP.
IMO Commons would be a good alternative home for BSF.
Can we please vote to:
1. Accept BSF as a Commons Component
2.
Thank you for posting this summary of the Apache way. Yes, it is damn
hard to track contributions, especially if one wishes to do it
accurately and fairly. However, it is possible and even easy to keep
*approximate* track of contributions, e.g. via commit points as
described in my
Another option is to try to work with Ceki to address some of the
concerns of the commons community with regards to using slf4j.
* There is a hassle with too many jars for dependencies with slf4j.
* Every time Ceki goes on vacation everything stops.
* Some have a preference for Apache driven
Paul,
BTW, in terms of swelling community development, if LOG4J+JCL were to
merge and just become JCL2, it could have the visibility of all
Commons committers. Isn't it much more of a common component than a
separate project? I think the logging project is dysfunctional anyway
-- make it a
+1
Thanks Mladen!
On Tue, Aug 2, 2011 at 7:06 AM, Mladen Turk mt...@apache.org wrote:
The proposed Apache Commons Daemon 1.0.7 release is now available for
voting.
It can be obtained from:
http://people.apache.org/~mturk/daemon-1.0.7/
The svn tag is:
(kindly provided on Christian
Grobmeier blog[1]) to check signatures and output is OK
Well done!!!
Have a nice day, all the best,
Simo
[1]
http://www.grobmeier.de/checking-md5-and-signatures-with-a-shell-script-29062011.html
$ ./verify.sh
Checking file: ./commons-daemon-1.0.7.jar
Using md5
Hi Simo,
thanks for doing that report again. Just wanted to submit, but have a
question (to all).
* A list of the three most important issues to address in the move
towards graduation.
- make at least a big release that shows to Commons PMC the
compliancy level of OGNL to Commons
, all the best!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Aug 1, 2011 at 4:39 PM, Christian Grobmeier grobme...@gmail.com
wrote:
Hi Simo,
thanks for doing that report again. Just wanted to submit, but have a
question (to all).
* A list of the three
+1
sigs, hashes are fine, site looks good and zip/gz etc unpack and run
on mac os x10.6.8 with java 1.6.0_26
Thanks Stefan!
On Thu, Jul 28, 2011 at 6:47 AM, Stefan Bodewig bode...@apache.org wrote:
Tag:
https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS_1.2_RC2/
Site:
Hi
I just signed off all status items on the incubation status page
(needs a while to sync to the latest version).
Anyway, I think OGNL is already fine to graduate. Most of the
community is already in commons, so I think ognl has a proven
community which will not go away after a while. If ognl
On Fri, Jul 29, 2011 at 10:33 AM, Torsten Curdt tcu...@vafer.org wrote:
At some stage I started to refactor commons logging into a multi
module maven project and got rid of the discovery part. So you would
have the commons-logging-api jar plus exactly one of the
implementation bridges. So you
/~simonetripodi/
http://www.99soft.org/
On Fri, Jul 29, 2011 at 11:58 AM, Luc Maisonobe luc.maison...@free.fr wrote:
Le 29/07/2011 10:53, Christian Grobmeier a écrit :
Hi
I just signed off all status items on the incubation status page
(needs a while to sync to the latest version).
Anyway
Guess the same - would like to see his desktop wallpaper, might
explain something ;-)
On Fri, Jul 29, 2011 at 12:40 PM, Maurizio Cucchiara
maurizio.cucchi...@gmail.com wrote:
Also I guess that Simone was not talking with Christina Aguilera :)
On 29 July 2011 12:27, Simone Tripodi
I guess Simo was talking about Luke Blanshard.
Oh yes.
So, Luke is missing from the OGNL list - we should fix that. Later we
must not forget to give him the commons group
On 29 July 2011 12:34, Christian Grobmeier grobme...@gmail.com wrote:
Agreed, thanks Christina for the follow-up.
BTW
[x] +1 release it
checked sigs, md5 and sha1 all well.
All package can be extracted
site looks ok
On Wed, Jul 27, 2011 at 7:03 AM, Stefan Bodewig bode...@apache.org wrote:
Tag:
https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS_1.2_RC1/
Site:
and LICENSE files. basedir will refer to the core subproject, not the project
root, which is where those files are located.
On Jul 24, 2011, at 12:14 PM, Ralph Goers wrote:
I need to revert this. It breaks the site build.
Ralph
On Jul 24, 2011, at 6:30 AM, Christian Grobmeier wrote:
Thanks
Hey all,
OpenSymphony has closed. Not sure if OSCache has survived.
This page recommends OSCache:
http://cayenne.apache.org/doc/query-result-caching.html
It looks like this project is the follow up:
java.net/projects/oscache
But it seems also to be rather dead (last commit 4 yrs)
Is it time
uh yes :-)
Sorry for the spam - time to have dinner and grab a beer!
On Mon, Jul 25, 2011 at 8:29 PM, Matt Benson gudnabr...@gmail.com wrote:
Wrong list? ;)
Matt
On Mon, Jul 25, 2011 at 1:18 PM, Christian Grobmeier
grobme...@gmail.com wrote:
Hey all,
OpenSymphony has closed. Not sure
Snappy looks pretty cool!
I created an issue for it:
https://issues.apache.org/jira/browse/COMPRESS-147
Without a fix version ;-)
Cheers
On Sat, Jul 23, 2011 at 1:49 PM, Stefan Bodewig bode...@apache.org wrote:
On 2011-07-23, Simone Tripodi wrote:
I think it would be nice having also s pure
might not work in M2.
Gary
On Jul 24, 2011, at 5:33, Christian Grobmeier grobme...@gmail.com wrote:
Just tried to build a eclipse project of vfs with mvn eclipse:eclipse
My mvn version is 3.0.3. I get a weird error, so I am wondering if
somebody has experienced it before (or something
Hello,
as I have not done anything before with vfs, i would like to ask
before I do bigger things with it.
I would like to
- upgrade from parent pom 19 to 21
- maven-assembly-plugin from 2.2 to 2.2.1
- maven-release-plugin from 2.2-SNAPSHOT to 2.2
Hope thats OK for everybody if commit some
I think that we should consider to include the incubating logo, but AFAIK
the incubation process is going to come to the end very soon.
I think the same, we should instead put some effort in the graduation
discussion :-)
Christian
I'd like to see other's comments
On 21 July 2011 15:39,
btw, did you update the incubator.apache.org website with your change
of the download section? it is still visible
On Sat, Jul 23, 2011 at 8:49 PM, Maurizio Cucchiara
maurizio.cucchi...@gmail.com wrote:
Hi Sebb,
thanks for your rigorous explanation.
I followed your guide lines and I moved to
We need to sign off the items listed on this page:
http://incubator.apache.org/projects/ognl.html
before we can graduate.
I think we can sign off all of this list.
I am just unsure on:
Check and make sure that the papers that transfer rights to the ASF
been received. It is only necessary to
sounds good :-)
On Fri, Jul 22, 2011 at 6:18 AM, Stefan Bodewig bode...@apache.org wrote:
Hi all,
From the responses in the Java5 thread I propose the following.
(1) Release current trunk minus a few lines of code I already added for
initial Zip64 support plus some minor changes ASAP as
On Thu, Jul 21, 2011 at 9:50 AM, Henri Yandell flame...@gmail.com wrote:
I think the argument is the other way. You should be explaining why
you wouldn't simply just move to Java 5.
+1 - Java 1.4 must die now.
+1 to JDK 1.5 minimum.
+1
If we lift up to 1.5 as a minimum what about lifting to
On Thu, Jul 21, 2011 at 10:44 AM, Stefan Bodewig bode...@apache.org wrote:
On 2011-07-21, Christian Grobmeier wrote:
If we lift up to 1.5 as a minimum what about lifting to compress 2.0?
Depends on what we want to do. If we want to break BWC by introducing
genrics, then let's do that. I am
I like the idea of many smaller consecutive releases (release early,
release often) instead of a big bang release.
For example:
- 1.2: Current trunk to gather bug fixes
- 1.3: Zip64 (Java 5)
- 2.0: Break compatibility, generics, and so on.
+1, i like that approach very much!
Guys,
we have missed the second ognl report. It would be good if we could
write it pretty fast to show the inc people that ognl is active and
well, even when we have forgotten that report.
Was there anything else besides: everything well, first discussion
about graduation raised?
Cheers
, for me it works as well! :P
Many thanks in advance, all the best!
PS not sure but IIUS that's the third report we submit...
[1] http://markmail.org/message/a6ntvg32s7fikqox
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Jul 19, 2011 at 10:05 AM, Christian
Reads great!
Love to see things like that
On Tue, Jul 12, 2011 at 7:43 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all guys,
just to share with you all a small interview I had with Jaxenter today
during lunch-time, I hope that my fellows appreciate how things have
been exposed!
http://incubator.apache.org/projects/ognl.html
In fact, I think we can resolve every item there. At which point I'd
argue we can be graduated by the next board report :)
+1
Was it the quickest incubation ever then? :-)
-
To
+1
On Sun, Jun 26, 2011 at 6:48 AM, Rahul Akolkar rahul.akol...@gmail.com wrote:
This is half a dozen related votes in one thread (for convenience), namely:
1. Accept BCEL [1] as Commons component
1a. Grant Commons karma to Dave Brosius (dbrosius)
2. Accept JCS [2] as Commons component
2a.
[X ] +1, accept Meiyo as a new component in Sandbox;
[ ] +/-0
[ ] -1, because (please provide a reason why)
Interesting project, but is a vote really necessary?
As far as I know you wrote it alone, so you could simply drop it into
the sandbox? I have asked the same b/c I wrote a JSON lib
Hey OGNLers,
the permissions for the incubator website has just been fixed - you
should now be able to update the website at your own. At people, you
should see the group incubator
Happy uploading ;-)
Cheers,
Christian
-
To
A good place for this question might be infra@a.o - they have done
that several times (guess)
On Fri, Jun 3, 2011 at 10:16 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all,
Coming back to the original topic of the email: the old OGNL JIRA is
still reachable on web.archive.org[1], does
Hello,
i have created the current website and deployed it to
http://incubator.apache.org/ognl/
It will take a while until it is synced.
Website has some problems, but I have uploaded it anyway.
Additionally, I have asked at infra if the other podling committers
can get write access with adding
What kind of problem you are talking about?
minor stuff, logo missing for example. Just wanted to express I didn't
check in detail and there is a few stuff we need to fix later
-
To unsubscribe, e-mail:
...@gmail.com wrote:
OK, it's a good starting point anyway.
On 3 June 2011 12:24, Christian Grobmeier grobme...@gmail.com wrote:
What kind of problem you are talking about?
minor stuff, logo missing for example. Just wanted to express I didn't
check in detail and there is a few stuff we need
2011 11:51, Christian Grobmeier grobme...@gmail.com wrote:
New website is synced:
http://incubator.apache.org/ognl/
Well, don't know about your aesthetic feelings but we could do it
ourselves with Gimp? It wil be ugly of course, but we change it later
if a designer wants to offer some spare time
ja...@carmanconsulting.com wrote:
Since my work life is changing, I may just have more cycles to devote
to my role as a PMC member. I would like to re-join the PMC. What is
the process?
Hopefully its just a case of asking, as you have done.
If not, we should change the way it is.
I have
I think its unnecessary.
If you want to find out who did something, use svn. If a user needs to
get a responsible person - we all are somehow. The right person will
come out from the mailinglist.
Adding yourself is ok if you have done some portions, feel well with
the code and responsible for
I like the new dormancy suggestion, plus:
I am OK with changing revival to require only
one ASF committer.
and:
If someone goes and
keeps on working stuff ... well ... then that status is nullified by
merit. (not through a single commit though) I don't see a reason to
forbid svn access
AM
+1
2011/5/2 Christian Grobmeier grobme...@gmail.com:
My issue (for the commons PMC I guess) is how
committer votes will
happen when OGNL graduates.
After graduation, how would one of the current
contributors propose a
new committer if they are not themselves on the
Commons PMC
Thanks Julien.
this is generated with Confluence... not a clue how to remove it. Will
ask at incubator list if somebody has rights/knowledge
Cheers
On Fri, Apr 29, 2011 at 10:52 PM, Julius Davies juliusdav...@gmail.com wrote:
Hi,
I accidentally ended up here:
.
Christian
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Thu, Apr 28, 2011 at 7:06 AM, Christian Grobmeier
grobme...@gmail.com wrote:
If the plan is to end up in Commons post-incubation, then I'd strongly
suggest you use the same mailing lists. Commons is relatively
If the plan is to end up in Commons post-incubation, then I'd strongly
suggest you use the same mailing lists. Commons is relatively unique
in that all the components share the same mailing list. OGNL should
get used to that from the beginning, plus it will bring more interest
in on the
BTW, why do I get this stuff? Am I missing something? Can we block
this? Its going to iss...@commons.apache.org
2011/4/18 XXL Webhosting BV sa...@xxlwebhosting.nl:
Tomofumi Kitano (JIRA),
Wij hebben uw bericht ontvangen. Een van onze medewerkers zal uw bericht zo
spoedig mogelijk behandelen
Hello infra,
can request like the below somehow be blocked from sending mail to:
iss...@commons.apache.org
Cheers,
Christian
2011/4/18 XXL Webhosting BV sa...@xxlwebhosting.nl:
Tomofumi Kitano (JIRA),
Wij hebben uw bericht ontvangen. Een van onze medewerkers zal uw bericht zo
spoedig
$id is not of interest for me. $id information can easily be found
with svn blame/history.
For me it can be nuked out - same for @version, i want @since instead
On Tue, Apr 5, 2011 at 10:28 AM, Stephen Colebourne
scolebou...@joda.org wrote:
How about no @Version tag or $Id ?
Stephen
On 5
I'd tend to remove that package and use commons-logging in the
traditional way, WDYT?
Probably we should get rid of commons-logging to. Its pretty outdated,
slf4j is more widely used.
If we want to stick within apache code, I would take log4j - slf4j has
a wrapper for it.
But commons logging
Probably we should get rid of commons-logging to. Its pretty outdated,
slf4j is more widely used.
It's not outdated, it is just very stable, so has not needed a release.
AIUI it's also very widely used as a dependency.
would you recommend anybody to use commons-logging? I wouldn't. It
seems
BTW I would be +1 for NO @version and putting only @since
+1
@version contains cruft
+1
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
But commons logging has no more sense meanwhile. Or did i miss something?
What gave you that impression?
No releases, no question, no discussion on commons-logging.
Lack of development on Log4J
Slf4J has a rising community and active development.
commons-logging imho is the wrapper for a
The only purpose of slf4j seems to be to cause unneeded fragmentation
and discussions like this, Christian, which you are stirring now for
the nth time (n 5, for sure).
Well, then lets close this discussion.
Just want to add I am not a huge fan of slf4j for the reason you
mentioned above.
On Tue, Apr 5, 2011 at 4:35 PM, Torsten Curdt tcu...@vafer.org wrote:
-1 to banning @version, as it can be useful
Since $Id$ contains the user ID we I would an @version that contains the
revision number.
-1 to that from me
-1 from me too
I never have seen a reason to include this
On Mon, Apr 4, 2011 at 11:22 PM, Phil Steitz phil.ste...@gmail.com wrote:
On 4/4/11 2:18 PM, Torsten Curdt wrote:
I thought we had settled on '@author Apache Software Foundation',
Did we? TBH I find that pretty pointless and nothing more than noise.
I'd be in favor of removing them all
+1
Two comments:
- At the site top left javadocs for 1.5.6 are not linked
- groupId is commons-pool. Shouldn't it change to org.apache or
something? Guess that one is for later
I have not checked sigs
On Wed, Mar 30, 2011 at 8:17 AM, Phil Steitz phil.ste...@gmail.com wrote:
The tag is here:
Hi,
it seems you have checked out and worked on source code from this location:
http://svn.apache.org/repos/asf/commons/proper/math/tags/
But you need to work on that one:
http://svn.apache.org/repos/asf/commons/proper/math/trunk
this is the main development path
You need to checkout the
Hello Damjan,
i think that the Sanselan developers will welcome your patches. Once
they arrived, somebody will have a little time to apply them, I would
guess. Before you continue, I would like to suggest you these links:
* http://www.apache.org/foundation/how-it-works.html
*
The Commons Compress team is pleased to announce the
commons-compress-1.1 release!
Commons Compress defines an API for working with compression and
archive formats.
These include: bzip2, gzip and ar, cpio, jar, tar, zip.
Source and binary distributions are available for download from the
And I would like to thank all who helped me with the Nexus tool and more! :-)
On Tue, Aug 24, 2010 at 6:57 AM, Christian Grobmeier
grobme...@apache.org wrote:
The Commons Compress team is pleased to announce the
commons-compress-1.1 release!
Commons Compress defines an API for working
delete the old 1.0 release files from
dist/*.
Will do, thanks Sebb
Christian
On Thu, Aug 19, 2010 at 8:17 AM, Christian Grobmeier
grobme...@gmail.com wrote:
Just have uploaded artifacts and released it from nexus.
http://www.apache.org/dist/commons/compress/
Site is already uploaded
Just have uploaded artifacts and released it from nexus.
http://www.apache.org/dist/commons/compress/
Site is already uploaded with mvn site:deploy
It looks strange - have checked the upload on people/3/c.a.o/compress
but it looks like it is still the old content, even when my mvn goal
was
Wow, looks wrong.
i would have expected the whole content of this:
https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-compress/1.1
Promotion should be complete (so the web interface said)
On Thu, Aug 19, 2010 at 9:30 AM, Stefan Bodewig bode...@apache.org
It seems it is now available:
http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.1/
I will do some checks, then send out the announce
double-checks welcome :-)
On Thu, Aug 19, 2010 at 10:13 AM, Christian Grobmeier
grobme...@gmail.com wrote:
Wow, looks wrong.
i would have
I will check and send announcement a little later
Mirrors have not synced up - I will some more time.
And a day or so after that, please delete the old 1.0 release files from
dist/*.
Will do, thanks Sebb
Christian
On Thu, Aug 19, 2010 at 8:17 AM, Christian Grobmeier
grobme
We should release the bits that we voted on and what goes to /dist
*is* the release. Therefore if we are going to vote on bits staged
somewhere other than people.apache.org, we need to do something like
what sebb describes above. If wget is used, RMs should re-verify
hashes on p.a.o before
Noone ever proposed using something different.
Huh?
Christian wrote:
Compress 1.0 has everything:
http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/
I like it, to be honest. Everything I need on one place.
which I take to mean that he would like to be able to
201 - 300 of 496 matches
Mail list logo
