:-) well unless you are doing Android dev there really isn't any need to
know what the AAR structure is.
An AAR contains the following:
- assets folder - Contains any number of text or binary assets.
- res folder - Contains zero or more other folders which contains text
or binary resourc
Hervé,
Can you explain what confusion this causes?
--
Regards,
Igor
On 2/6/2014, 16:47, Hervé BOUTEMY wrote:
Hi,
You'd better not use the @Component annotation but @Parameter instead: this is
a feature that will be deprecated in future version:
http://jira.codehaus.org/browse/MPLUGIN-257
Re
yes, the change was intentional, to fix
http://jira.codehaus.org/browse/MSCMPUB-10 you issued :)
Adding a note on the website and announce is a good idea.
Too late this time for announce, but I'll modify site
And perhaps add something in the announce template
Regards,
Hervé
Le mercredi 5 févr
Hi Hervé,
Hi,
You'd better not use the @Component annotation but @Parameter instead: this is
a feature that will be deprecated in future version:
http://jira.codehaus.org/browse/MPLUGIN-257
Thanks for the hint learnt already (via IRC) the right way via
@Parameter ...
But according to the
Hi,
You'd better not use the @Component annotation but @Parameter instead: this is
a feature that will be deprecated in future version:
http://jira.codehaus.org/browse/MPLUGIN-257
Regards,
Hervé
Le jeudi 6 février 2014 22:04:57 Karl Heinz Marbaise a écrit :
> Hi,
>
> in the meantime i found
I can remove the implementation as it's all fairly self-contained, but you
probably know best which classes like Schedule, Scheduling, ProjectIndex,
PhaseRecorder and possibly other classes that were weave specific that we can
remove from the lifecycle executor code. If that's done it will help
Hi,
in the meantime i found a better way (thanks to Robert Scholte):
@Component
private MojoExecution mojoExecution;
mojoExecution.getExecutionId();
mojoExecution.getConfiguration();
Kind regards
Karl Heinz Marbaise
If you're not running in parallel mode you will be fine. If you are then right
now you can use the new method introduced in the
AbstractMavenLifecycleParticipant:
https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/AbstractMavenLifecycleParticipant.java#L68
Thi
Jason,
a bit off topic, but you mention that "if last reactorProject" type logic
breaks badly in parallel mode.
Any pointers how to fix/replace it?
Thanks,
~t~
On Thu, Feb 6, 2014 at 4:05 PM, Jason van Zyl wrote:
> Hi,
>
> I made a first pass at coalescing the logic for a specific way to b
Hi Baptiste,
first thanks for the links and answers...
> Here's the thread:
http://maven.40175.n5.nabble.com/Maven2-Maven3-plugin-development-Ensuring-only-the-available-parameters-are-allowed-tp5780854p5780948.html
Maybe I'd try something along those lines:
Plugin plugin = lookupThePluginYo
I can fremover weave mode entirely this weekend. It wasnt worth it.
K
6. feb. 2014 16:06 skrev "Jason van Zyl" følgende:
> Hi,
>
> I made a first pass at coalescing the logic for a specific way to build
> (single threaded, multi threaded, weave) into its own implementation but
> there is still m
Hi,
I made a first pass at coalescing the logic for a specific way to build (single
threaded, multi threaded, weave) into its own implementation but there is still
much cleanup to be done. This was pure refactoring and there isn't much
functional change aside from adding a command line paramete
12 matches
Mail list logo