I also can't log in - I think the login is for the admins only.
Re set-up: I found this:
https://issues.apache.org/jira/browse/INFRA-3486
You might try making a similar Jira, but I would also suggest saying something
about not finding any links to the correct process to get set up... That shou
Nice, I cannot log in with my Apache LDAP account. What is necessary
to set this up for uimaFIT?
Cheers,
-- Richard
On 15.09.2013, at 13:38, Marshall Schor wrote:
> You might be interested also in this report, or in setting up other "projects"
> to get a report like this:
>
> https://analysis
You might be interested also in this report, or in setting up other "projects"
to get a report like this:
https://analysis.apache.org/dashboard/index/50467
Currently, only the UIMA SDK is set up, I think.
-Marshall
On 9/5/2013 4:56 PM, Richard Eckart de Castilho wrote:
> Yep, that someone was m
On 9/5/2013 6:37 PM, Richard Eckart de Castilho wrote:
> Sigh. You are right.
>
> I wonder why Maven so effectively defies doing anything even remotely
> sensible or creative with profile activation.
>
> - Profiles cannot activate other profiles by any command.
> - Profiles cannot declare properti
It would be possible to activate profiles by properties instead of explicitly.
E.g. we could build a "rat" profile which is activated by two properties
"apache.release" and "jenkins.build".
mvn -Dapache.release
vs.
mvn -Papache.release
If multiple conditions are specified on a profile,
On 9/5/2013 5:15 PM, Richard Eckart de Castilho wrote:
> It would be possible to activate profiles by properties instead of explicitly.
>
> E.g. we could build a "rat" profile which is activated by two properties
> "apache.release" and "jenkins.build".
>
> mvn -Dapache.release
>
> vs.
>
>
On 9/5/2013 2:50 PM, Richard Eckart de Castilho wrote:
> Did you look at the Jenkins build of the SDK recently? ;)
>
> https://builds.apache.org/job/UIMA-SDK/
no, I hadn't looked. Looks like someone added additional code running checks
and other reports; maybe these can inspire some other volunte
Sigh. You are right.
I wonder why Maven so effectively defies doing anything even remotely
sensible or creative with profile activation.
- Profiles cannot activate other profiles by any command.
- Profiles cannot declare properties that trigger other profiles.
- Profiles *can* be activated by pro
On 9/5/2013 4:53 PM, Richard Eckart de Castilho wrote:
> Wouldn't we have to duplicate significant parts of the configurations?
I guess that would depend on what we wanted to include in the Jenkins build
that's not already there. I don't think there's too much worthwhile. The only
thing I see of
Yep, that someone was me. When the JavaDoc is built, we should
see those warnings as well. From time to time I may tackle some
of these warnings, but it can also be a general motivation to
tackle some things here and there while working on related code.
-- Richard
On 05.09.2013, at 22:53, Marsha
Wouldn't we have to duplicate significant parts of the configurations?
-- Richard
On 05.09.2013, at 22:50, Marshall Schor wrote:
> how about having a jenkins-build profile, set for jenkins builds? Then we
> could
> put anything we wanted into that.
>
> I think that might be more "direct" and
how about having a jenkins-build profile, set for jenkins builds? Then we could
put anything we wanted into that.
I think that might be more "direct" and maintainable than turning on
apache-release, and then somehow turning off some parts of that.
-Marshall
On 9/5/2013 2:50 PM, Richard Eckart de
So I suppose this means that we should create JavaDoc artifacts in the
future:
2x +1 (Richard, Peter)
1x +0 (Marschall)
No other votes ;)
-- Richard
On 30.08.2013, at 10:46, Peter Klügl wrote:
> On 29.08.2013 23:40, Marshall Schor wrote:
>> We have our multi-module builds set up so that
>>
>
Did you look at the Jenkins build of the SDK recently? ;)
https://builds.apache.org/job/UIMA-SDK/
Btw. I'd like to turn on apache-release on the Jenkins build
and just skip the gpg signing, so that we get immediate failures
on missing license headers and the like. Any objections?
-- Richard
On
OK. I've updated the build process to produce javadocs (but only under
-Papache-release, to keep development builds going faster).
Running this for the 1st time on uimaj-core produced >400 warnings... (the
Javadocs on internals haven't been invested in ...)
-Marshall
On 9/5/2013 6:50 AM, Richard
On 29.08.2013 23:40, Marshall Schor wrote:
> We have our multi-module builds set up so that
>
> a) Javadocs are run just for the publicly-viewable apis
> b) not run for individual sub-modules (e.g., not for uimaj-core).
>
> Many releases ago, we did not even publish modules (other than maven plugin
16 matches
Mail list logo
