On 1/7/19, 1:20 AM, "Christofer Dutz" <[email protected]> wrote:
Just adding my thoughts to the problem:
Whenever I did a Maven training in the past, the core mantra I tried my
students to understand was:
"If it's hard to do with Maven, you're probably doing it wrong."
Ok ... if you're working on builds for non-java, things do get quite a lot
trickier, but still solvable.
Even if this sounds pretty blunt, in the past about 10 years of doing a lot
of projects with Maven, in the end it has proven to be very true.
I would suggest to get someone involved, who's a Maven expert, to help you
diagnose and fix the issues you are having instead of adding a patch that works
around the core problem.
I doubt Maven is actively preventing only the Royale project from doing
releases from outside the US, so I guess it's a configuration problem.
So I would suggest to get some of the Maven folks on one of the Maven lists
to help you.
This sounds like a tangential topic to me. There is more to the story than I
have so far described in order to try to reduce the amount of stuff folks have
to read. Maybe it is a configuration issue, but I did not mention that I was
able to reproduce upload issues to Nexus by also trying to stream video over
Roku on my home network when uploading. And also I did not mention the amount
of time spent helping new RMs get configured to even run both Ant and Maven and
the tests. Clearly, the default configurations didn't make others successful.
A busy network seems to increase the chance of failure. Having it all set up
on a single computer that all RM's could share that is known to work would help
solve this problem.
Having a single shared computer for RM's doesn't appear to violate any ASF
policy. I don't see any security risks, but maybe someone will come up with
one. But to share this computer, we need the computer to be able to commit
stuff, either with a special account, or by swapping in credentials.
Thanks,
-Alex
