Hi Jason,
I can help in the analysis. I recently written some annotation
checking tool in japa (javaparser) and ASM :) Do you want to analyze
the source code or the class files?
Regards,
g
On Wed, Feb 27, 2013 at 1:56 AM, Hervé BOUTEMY wrote:
> Did you finally tried "full graph analysis on C
Hi Hervé,
I'm sorry for the late reply
> introducing new status, with pseudo-pom property and so on seems irrealistic,
> at least to me: the concept is interesting, but I doubt it can fit into the
> actual code
Do you think it is feasible to add such status info as some plugin config?
> Perhap
gt;
>> Promotion is handled completely by the apache-ivy. It allows you not
>> only to reference snapshot as maven do, but you can specify
>> "latest.integration" or "latest.release" as version. We use standard
>> Ivy statuses, but custom statuses can be d
ard
Ivy statuses, but custom statuses can be defined too.
Regards, Gabor
> (notice I won't be here for 1 week, so won't be able to continue the
> discussion for the moment, but the topic is worth more discussion)
>
> Regards,
>
> Hervé
>
> Le jeudi 20 décembre
re the end of the day...)
>
> Regards,
>
> Hervé
>
> Le jeudi 20 décembre 2012 07:51:08 Gábor Guta a écrit :
>> We make the promotion of the already built artifact and we update the
>> metadata. e.g.: if the corresponding integration tests are fine, the
>> status of t
to rebuild the artifact at each promotion, or
> make promotion of the already built artifact (then without rebuilding it),
> only changing its status metatada?
>
> Regards,
>
> Hervé
>
> Le mercredi 19 décembre 2012 15:37:18 Gábor Guta a écrit :
>> Can you give me feedback fe
Can you give me feedback feedback / recommendation about how can I
write extensions for Maven to support a build pipeline and artifact
promotion in a "standard" way. As far as understand these issues are
common problems, because I have found many blogs describing hacks and
workarounds. I also have
