I would think it is related but I'm at a loss as to explaining what is
actually going on.
Sam
On Sunday, 16 December 2012 04:09:50 UTC, remiP wrote:
Hi Sam,
Could this be related to the workaround I found for
FLEXMOJOS-483https://flexmojos.atlassian.net/browse/FLEXMOJOS-483(cf. the
last
The plugin is being loaded in one context, but not necessarily the context
in which the resolution happens.
My understanding though *probably* wrong was that it was that the problems
were occurring in background maven instance which was causing the problems
mentioned
here:
Maven will not generate the effective pom if the flexmojos plugin is not
loaded by the pom in question or one of its parents. I've tripped up on
this a few times of late.
On Tuesday, 27 November 2012 11:15:20 UTC, Christofer Dutz wrote:
Yeah! This is my favourite issue ... think I was the one
Hmmm ... but how should you use the copy-resources goal without using the
plugin?
Chris
2012/12/12 Sam Barker sam.bar...@mahifx.com
Maven will not generate the effective pom if the flexmojos plugin is not
loaded by the pom in question or one of its parents. I've tripped up on
this a few
Yeah! This is my favourite issue ... think I was the one who created it (or
at least I posted one solution option).
It's a pretty tricky little bug. The problem is that the copy-resources
target asks Maven to get the final name of an artifact. Unfortunately Maven
produced some Error while
This response on FLEXMOJOS-483 thread, can contribute light on the subject that
occupies to us:
https://flexmojos.atlassian.net/browse/FLEXMOJOS-483?focusedCommentId=12900page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12900
--
Jose Barragan
Software Architect Chief
This response on FLEXMOJOS-483 thread, can contribute light on the subject that
occupies to us:
https://flexmojos.atlassian.net/browse/FLEXMOJOS-483?focusedCommentId=12900page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12900
--
Jose Barragan
Software Architect
Hi Chris,
I was looking forward into talking to him about it and writing this up for
all others.
it will be great! We can't really change until we get a robust workflow in
IntelliJ, since we have the responsability to make it work with all our
developments. So we are stuck until something like
It is deffinitely still in as I an strongly relying on it ;-)
Am 26.11.2012 23:43 schrieb Carlos Rovira carlos.rov...@codeoscopic.com:
Hi Chris,
I was looking forward into talking to him about it and writing this up
for all others.
it will be great! We can't really change until we get a
