I will give it a try this weekend.
musachy
On Fri, Oct 2, 2009 at 12:41 PM, Lukasz Lenart
wrote:
> Hi,
>
> Ready for test, Google App Engine enabled
> mvn archetype:generate -DarchetypeCatalog=http://www.lenart.org.pl/maven
>
>
> Regards
> --
> Lukasz
> http://www.lenart.org.pl/
> http://dailylo
Hi,
Ready for test, Google App Engine enabled
mvn archetype:generate -DarchetypeCatalog=http://www.lenart.org.pl/maven
Regards
--
Lukasz
http://www.lenart.org.pl/
http://dailylog.lenart.org.pl/
-
To unsubscribe, e-mail: dev-un
If we can't get the help from people in the user list, then I would
say we do what you are suggesting, but we take it to the "extreme" a
bit, meaning, that when we think the code is ready to be frozen for a
release, we cut a build(with tag, staging repo and all) and let people
in dev@ know about it
On Thu, Oct 1, 2009 at 10:50 PM, Wes Wannemacher wrote:
> On Fri, Oct 2, 2009 at 1:25 AM, Martin Cooper wrote:
>> On Thu, Oct 1, 2009 at 10:00 PM, Musachy Barroso wrote:
>>> I still don't understand why we don't let users know that there is a
>>> build that we are testing so we get more eyes on
I have always liked that option better, I don't see the point of
calling GA something that has been tested for 3(+/-) days, instead of
voting on something that has been in use for a couple of months and is
known to be good for sure. When you say it is a "policy", do you mean
an Apache policy? or a
I'm on Windows, and I did test it after you reported the failure. I
tested it on Win with 7-zip, and didn't notice any errors...
Nils-H
> Well, I did notice that the zips were malfunctioning (see my previous
> email), but I assumed it was a local problem (bad harddrive with many
> corrupted secto
