Hi Om,
If make_branches succeeds, then you shouldn't need to go back and delete
branches and tags and run make_branches again if the "maven" step fails.
You might need to revert any changes to the release branch that the "maven"
step did, but then you should be able to delete the local copy of
On Thu, Oct 4, 2018 at 1:48 AM Alex Harui wrote:
> Om, it looks like you are still deleting and recreating the branches.
> Does this mean you have never completed the make_branches step?
Yes, I delete the tags, branches (remote) each time something fails. Then
I do a global search for 0.9.5
On Thu, Oct 4, 2018 at 9:33 AM Alex Harui wrote:
> Om,
>
> What version of Java are you using? Maven uses Java and maybe there is an
> incompatibility in the server communication layer of Java.
>
OmPrakashs-MacBook-Pro:release om$ java -version
java version "1.8.0_181"
Java(TM) SE Runtime
It seems that releases are overly automated.
Seems like once everything is built and tests are passed a set of scripts in a
runbook can be manually run by the RM.
Regards,
Dave
Sent from my iPhone
> On Oct 4, 2018, at 9:23 AM, Alex Harui wrote:
>
> I don't know for sure, but I believe much
Om,
What version of Java are you using? Maven uses Java and maybe there is an
incompatibility in the server communication layer of Java.
-Alex
On 10/4/18, 1:14 AM, "OmPrakash Muppirala" wrote:
DSL via AT :-)
Although this morning was a different connection (at work)
I don't know for sure, but I believe much of it is part of Maven's default
release process. We "must" prove that the example sources pass all standard
release requirements (pass the RAT check and compiles without error). I think
by default after those tests, Maven packages up the sources for
I am curious about why we are uploading example swcs to maven central.
What is the usecase?
Thanks,
Om
On Thu, Oct 4, 2018, 2:26 AM Alex Harui wrote:
> We are using both Maven and Ant to create releases. Some of our users
> prefer Maven others prefer Ant. Best way to make sure both work is
We are using both Maven and Ant to create releases. Some of our users prefer
Maven others prefer Ant. Best way to make sure both work is to use Maven for
Maven and Ant for Ant.
I don't know if is really Maven that is failing or just something wrong with
Om's internet connection.
-Alex
On
Hi Harbs,
for me Maven is not easier, seems as difficult as ANT. For me the points
for maven is the reliability and robustness of the build process and the
management of dependencies. ANT was the first step for me, and I always
liked, but the problems was that it was more a way to script than
Om, it looks like you are still deleting and recreating the branches. Does
this mean you have never completed the make_branches step? Is make_branches
failing trying to run a build in the develop branch and uploading
0.9.5-SNAPSHOT artifacts? I supposed we could try to find a way to skip
DSL via AT :-)
Although this morning was a different connection (at work)
On Thu, Oct 4, 2018 at 1:09 AM Piotr Zarzycki
wrote:
> Neverending story ;) What's your internet connection actually?
>
> On Thu, Oct 4, 2018, 10:04 AM OmPrakash Muppirala
> wrote:
>
> > Hmm, failed again at a different
Neverending story ;) What's your internet connection actually?
On Thu, Oct 4, 2018, 10:04 AM OmPrakash Muppirala
wrote:
> Hmm, failed again at a different spot:
>
> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]
>
>
Hmm, failed again at a different spot:
[exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]
[exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Topaz-Theme SUCCESS [ 18.741 s]
On Wed, Oct 3, 2018 at 2:02 PM Alex Harui wrote:
> Hi Om,
>
> Does anything deploy, or is that the first thing that is attempted to
> deploy? I found this article that might help:
>
> https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html
It
Hi Om,
Does anything deploy, or is that the first thing that is attempted to deploy?
I found this article that might help:
https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html
I would be concerned about restarting from the middle of a Maven call.
It would be hard to make this happen. I think all artefacts are spread
across target folders and local caches. When artefacts is build I'm not
sure from where Maven is taking it - Cache or Targets folder.
You are almost done with that. If you won't succeed till Monday maybe I
will try to find
Another suggestion I have is - can we do all the pushes to remote after
everything is done locally? That way, if something goes wrong halfway, we
can just delete the royale-* dirs locally and rerun the releasecandiate ant
script?
Not sure if this is an easy change?
Thanks,
Om
On Wed, Oct 3,
Okay, I tried a couple of times and I have started getting `SSL peer shut
down incorrectly errors`
[exec] [INFO] [INFO]
[exec] [INFO] [INFO] BUILD FAILURE
[exec] [INFO] [INFO]
Looks like it was a missing [
MXRoyale and SparkRoyale built for me.
HTH,
-Alex
On 10/3/18, 12:43 AM, "OmPrakash Muppirala" wrote:
Thanks!
I reverted everything back to previous state. I can give it a shot
tomorrow evening.
Regards,
Om
On Wed, Oct 3,
Thanks!
I reverted everything back to previous state. I can give it a shot
tomorrow evening.
Regards,
Om
On Wed, Oct 3, 2018 at 12:41 AM Alex Harui wrote:
> It was in a releasable state. TourDeFlex was running on it.
>
> I'm trying to track down the change that broke it.
>
> -Alex
>
> On
It was in a releasable state. TourDeFlex was running on it.
I'm trying to track down the change that broke it.
-Alex
On 10/3/18, 12:32 AM, "OmPrakash Muppirala" wrote:
A bit more progress. Now we are failing on the MXRoyale project:
[exec] [INFO] [INFO]
A bit more progress. Now we are failing on the MXRoyale project:
[exec] [INFO] [INFO]
[exec] [INFO] [INFO] BUILD FAILURE
[exec] [INFO] [INFO]
I'm going to give this another shot in a couple of hours, unless there are
any objections.
Thanks,
Om
On Mon, Oct 1, 2018, 2:04 PM Alex Harui wrote:
> Jewel is mentioned in there. I added mention of the migration components
> and tour de flex. Not sure if I got the formatting right. I think
Jewel is mentioned in there. I added mention of the migration components and
tour de flex. Not sure if I got the formatting right. I think it is good
enough.
-Alex
On 10/1/18, 12:13 PM, "OmPrakash Muppirala" wrote:
I updated it, although it looks a bit sparse now. Can we list a few
I updated it, although it looks a bit sparse now. Can we list a few major
highlights here, that I can go add to the release notes?
Jewel should at least have several updates.
Thanks,
Om
On Mon, Oct 1, 2018 at 12:09 PM Alex Harui wrote:
> Hey, I just noticed that nobody put a 0.9.4 section in
Hey, I just noticed that nobody put a 0.9.4 section in the RELEASE_NOTES.
Maybe just rename the 0.9.3 section?
-Alex
On 10/1/18, 12:07 PM, "OmPrakash Muppirala" wrote:
Good catch! I just pushed a fix for that.
Thanks,
Om
On Mon, Oct 1, 2018 at 11:04 AM Alex Harui
Good catch! I just pushed a fix for that.
Thanks,
Om
On Mon, Oct 1, 2018 at 11:04 AM Alex Harui wrote:
> Om,
>
> I think the release/0.9.4 in royale-asjs/pom.xml needs to be
> reverted back to 0.9.3.
>
> Everything else looks ok from my quick examination.
>
> Thanks and good luck,
> -Alex
>
>
Om,
I think the release/0.9.4 in royale-asjs/pom.xml needs to be
reverted back to 0.9.3.
Everything else looks ok from my quick examination.
Thanks and good luck,
-Alex
On 10/1/18, 10:29 AM, "Piotr Zarzycki" wrote:
I saw your commit and I think you should be ok.
pon., 1 paź
I saw your commit and I think you should be ok.
pon., 1 paź 2018 o 19:21 OmPrakash Muppirala
napisał(a):
> Okay, I did the following to reset:
>
> For all three repos:
> * Reverted all references of 0.9.5 to 0.9.4
> * Deleted 0.9.4-rc1 tag
> * Deleted branch: release/0.9.4
>
> Can someone
Okay, I did the following to reset:
For all three repos:
* Reverted all references of 0.9.5 to 0.9.4
* Deleted 0.9.4-rc1 tag
* Deleted branch: release/0.9.4
Can someone please make sure that we are good before starting work?
Thanks,
Om
On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira
wrote:
> Hi
Hi Om,
is related to flash player debugger not launched? are you on Mac?
I think on Mac I have to make *.swf files be always opened by Flash Player
debugger.
In the other hand, I need to commit during the day some fixes, one on
typedefs and expect more on compiler. So if you plan to try again
I provided path to Chrome via -Dbrowser, but I got an error that ant was
not able to access the application.
So, I tried installing firefox and that seemed to work.
On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki
wrote:
> Hi Om,
>
> You did use Firefox for that purpose ? I had to specify
Hi Om,
You did use Firefox for that purpose ? I had to specify -Dbrowser=path to
firefox.exe
Thanks,
Piotr
pon., 1 paź 2018 o 10:22 OmPrakash Muppirala
napisał(a):
> Okay, I made several attempts through the day, making progress each time.
> The last run failed because the browser could not
Okay, I made several attempts through the day, making progress each time.
The last run failed because the browser could not be launched.
I am going to pause on this and try again tomorrow (or later) . If someone
else wants to give this a go in the meantimne, they are welcome :-)
Thanks,
Om
On
Hi Om,
no, I Thought this was due to different tries of the release process but
most of the poms are in 0.9.6-SNAPSHOT.
You can search the entire repo for "0.9.X-SNAPSHOT" string to see that now
X is 6.
thanks
El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala ()
escribió:
> On Sun, Sep 30,
On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira wrote:
> Hi Om,
> just saw that some poms was not changed to 0.9.6-SNAPSHOT.
>
Do you mean 0.9.4-SNAPSHOT?
Thanks,
Om
I think that should be fixed and get a prepare maven release process that
> could finaly gets all poms updated to new version.
>
Hi Om,
just saw that some poms was not changed to 0.9.6-SNAPSHOT.
I think that should be fixed and get a prepare maven release process that
could finaly gets all poms updated to new version.
Don't know if that could be the problem. Can you try again?
thanks
El dom., 30 sept. 2018 a las 21:32,
Made a bit more progress, but the build is failing here now:
[exec] [INFO] [INFO] Apache Royale: Examples: Royale:
DataBindingExample_as SUCCESS [ 2.469 s]
[exec] [INFO] [INFO] Apache Royale: Examples: Royale:
DataBindingExample_Flat FAILURE [ 1.756 s]
[exec] [INFO] [INFO]
Thanks for the quick fix! Will pull develop and try again. Will report in
a while.
Regards,
Om
On Sun, Sep 30, 2018, 8:47 AM Carlos Rovira wrote:
> Hi Om,
>
> error is now fixed. Can you try to release again?
> thanks
>
> Carlos
>
>
>
>
>
> El dom., 30 sept. 2018 a las 17:27, Carlos Rovira
Side note...I searched for javadoc or maven-javadoc-pluign and didn't find
anything
So it's a completely mystery to me how release process is triggering the
creation of javadocs. :?
El dom., 30 sept. 2018 a las 17:47, Carlos Rovira ()
escribió:
> Hi Om,
>
> error is now fixed. Can you try to
Hi,
just reverted the two generated commits for release, I left to you remove
new branches generated.
About the fail, I was wrong, since I saw this very quickly. It's not about
JDK, I'm using as well 1.8. I was confused for other thing I had some weeks
ago, and was trying to use another JDK, but
Hi, since I'm going to work now on some compiler changes, I'll revert those
2 commits in each repo. I'll try to pass as well maven with java 1.8 in amp
and see if I get the same error
El dom., 30 sept. 2018 a las 15:16, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Om,
>
> I think if
Om,
I think if you got fail during the process you should right after that.
1) Remove created release tags
2) Revert all changes which Maven did in develop branches to the previous
state
Thanks,
Piotr
niedz., 30 wrz 2018 o 12:40 Carlos Rovira
napisał(a):
> Hi Om,
> don't have many time now,
Hi Om,
don't have many time now, but seems you are using JDK 1.8 and that project
needs to be 1.7 or will fail
I'll connect some hours later to see if you could use that sdk
good luck! :)
El dom., 30 sept. 2018 a las 11:34, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Om,
>
>
Hi Om,
Have you tried build that example on their own? Is it failing with the same
stack trace?
Thanks,
Piotr
On Sun, Sep 30, 2018, 9:31 AM OmPrakash Muppirala
wrote:
> So, I made a lot of progress (much more than last time), but unfortunately
> the build failed at this stage. Looks like an
So, I made a lot of progress (much more than last time), but unfortunately
the build failed at this stage. Looks like an issue with the
SampleAmfWebApp. Anyone else seeing this error or am I doing something
wrong?
[exec] [INFO] [INFO] Apache Royale: Examples: Native: USStatesMap
...
Okay, trying now.
On Tue, Sep 25, 2018 at 9:52 AM Piotr Zarzycki
wrote:
> Om,
>
> I think if you first try to build Royale framework with Maven all the
> dependencies will be downloaded. During framework build you should get
> question about license related to player global etc. Once you do
Om,
I think if you first try to build Royale framework with Maven all the
dependencies will be downloaded. During framework build you should get
question about license related to player global etc. Once you do successful
build you could try to go and play with script for release. - That way to
According to the archives, try running:
mvn -s settings-template.xml clean install
Thanks,
-Alex
On 9/23/18, 3:48 PM, "OmPrakash Muppirala" wrote:
On Sun, Sep 23, 2018 at 3:43 PM OmPrakash Muppirala
wrote:
> Thanks. I decided to stick with 1.8 :-)
>
>
BTW,
Thanks. I decided to stick with 1.8 :-)
I am seeing this error:
[ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
(default-compile-as) on project Core: Could not resolve dependencies for
project
Hi Om,
I have Java 8 and 10 installed, and I think I was able to compile three
repos, but I find AMF java example doesn't work, since BlazeDS needs a
Lower version I need to go with 8 for this example. Maybe other part needs
as well 7 or 8.
I think trying another SDK should be left to some time
Okay trying this out now.
First question: The release doc [1] says we need Java 1.7 or higher. Has
anyone tried Java 10? That is the default version available through all
installation channels.
Any pitfalls I should consider?
Thanks,
Om
On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira
wrote:
I think we are ready to go, so let's go! ;-)
Good luck Om! :)
El vie., 21 sept. 2018 a las 18:19, Alex Harui ()
escribió:
> Yes, I think they are ready. I removed the release/0.9.4 branches so the
> scripts should be able to make a new one.
>
> -Alex
>
> On 9/21/18, 8:58 AM, "OmPrakash
Yes, I think they are ready. I removed the release/0.9.4 branches so the
scripts should be able to make a new one.
-Alex
On 9/21/18, 8:58 AM, "OmPrakash Muppirala" wrote:
Alex said in his last email that the repos are ready. Will try in a few
minutes.
Thanks,
Om
Alex said in his last email that the repos are ready. Will try in a few
minutes.
Thanks,
Om
On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki
wrote:
> Om,
>
> In my opinion you have everything ready to go! Since develop is ready
> probably you will start doing steps from the beginning, so in the
Om,
In my opinion you have everything ready to go! Since develop is ready
probably you will start doing steps from the beginning, so in the results
we will get branches release/0.9.4. However they already exists, because of
my previous attempt.
Maybe before you even start they need to be
So am I clear to try and release? Or should I wait for any other feature
or bug?
Thanks,
Om
On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira wrote:
> Hi Alex
>
> El vie., 21 sept. 2018 a las 3:06, Alex Harui ()
> escribió:
>
> > I made some adjustments to the repos so that they "should" be ready
Hi Alex
El vie., 21 sept. 2018 a las 3:06, Alex Harui ()
escribió:
> I made some adjustments to the repos so that they "should" be ready to run
> the scripts and produce the 0.9.4 release. Of course, I could be wrong.
> We'll see how Om fares.
>
>
so cool :)
> I also put in a change that
Hey Om,
If you have capacity please finish that release. Users of VSCode and
Moonshine will be happy!
Thanks,
Piotr
On Thu, Sep 20, 2018, 5:08 PM OmPrakash Muppirala
wrote:
> The last time I tried to release, it was on Windows PC. Some tweaks were
> required. Also, I would say that the
I made some adjustments to the repos so that they "should" be ready to run the
scripts and produce the 0.9.4 release. Of course, I could be wrong. We'll see
how Om fares.
I also put in a change that should fix the dependencies issue. So the
remaining questions are around the AMF problem.
Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)
Thanks!
Carlos
El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> The last time I tried to release, it was on Windows PC. Some tweaks were
> required. Also,
The last time I tried to release, it was on Windows PC. Some tweaks were
required. Also, I would say that the release process was too automated
As a result I was not able to figure out what exaxtly broke, etc.
FWIW, I have a Mac now. I can try again if Piotr wants to take a break.
Getting
Hi Alex,
thanks you see it in the list of unread messages and will go to say that I
found it.
I'll take a look now
El jue., 20 sept. 2018 a las 9:44, Alex Harui ()
escribió:
>
>
> On 9/19/18, 11:49 PM, "Carlos Rovira" wrote:
>
> Hi Alex,
>
> what Zend-AMF issue you refer? can you
On 9/19/18, 11:49 PM, "Carlos Rovira" wrote:
Hi Alex,
what Zend-AMF issue you refer? can you post the link to that issue?
thanks
https://lists.apache.org/list.html?us...@royale.apache.org
PD: about your preoccupation, we'll have issues for many months to come. I
Hi Alex,
what Zend-AMF issue you refer? can you post the link to that issue?
thanks
PD: about your preoccupation, we'll have issues for many months to come. I
see each day in Jewel as I go here and there fixing or completing issues I
find, so I think is ok release with that issues so people can
Jewel is another reason.
Carlos wrote a lot of blog posts which can’t be run until we release.
(Plus lots of little things that were fixed…)
> On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki
> wrote:
>
> I personally express important reason. Releasing can help community around
> VSCode and
I personally express important reason. Releasing can help community around
VSCode and Moonshine.
Piotr
On Wed, Sep 19, 2018, 9:41 PM Alex Harui wrote:
> What do you see as the important reasons? I know the Apache mantra is to
> release early and often, but if it were up to me, we would
What do you see as the important reasons? I know the Apache mantra is to
release early and often, but if it were up to me, we would release after we hit
some interesting milestone, like getting Alina's app to compile completely, or
someone else says they are ready to go to production and need
I’m happy to try and be a release manager, but I don’t have time for at least a
month. I think it’s pretty important to get this release out sooner rather than
later.
If you can help Piotr finish this release, I’ll try to do the 0.9.5 release.
Thanks,
Harbs
> On Sep 19, 2018, at 6:54 PM, Alex
Process is definitely automated. If we would not skip version we would have
RC1 two days ago from me. I got dedicated time for making that release,
cause it can help improve Josh's plugin - which is using Royale compiler.
As you know that plugin is used in VSCode and Moonshine, so Framework part
IMO, speculating things to be worse than they are without being informed is not
good for the community.
Piotr ran into problems because we were forced to try to skip a version.
Again, there is nobody whose job it is to make releasing simple, and who will
take the time to try to anticipate
Hi Alex,
don't think each comment is negative only because is not positive! I
already said some words recognizing the huge effort behind that task. I
know how hard it is.
But as I said the great work done, I want to expose the only point I think
is problematic, the difficult of the process. And I
Hi Piotr,
sorry to hear that, I think we're out of resources. I'm concentrating in
make Jewel as stable as possible since in few days we can start a new
project with Royale-Jewel, so I still don't know how I'll be doing to
continuer Jewel, make that project and continue with my other tasks that
Btw. The process is quite automatic, but skipping the version wasn't
something considered before.
On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki
wrote:
> Carlos,
>
> Unfortunately I'm giving up doing that. I have spent on this too much time
> and money. Someone else can continue from my point.
>
Carlos,
Unfortunately I'm giving up doing that. I have spent on this too much time
and money. Someone else can continue from my point.
Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction from
Alex I don't know what to do next.
Details are in previous email.
Good Luck!
Piotr
Hi Piotr,
I encourage you and Alex to try to refine more the process so we can
release more easily. I think right now the process is very dependent of
many manual tasks, and that impact in all: huge effort to do the release,
many time involved, impossible to reproduce in next release,..
I think
We are releasing from specific commit. The problem is laying out on setup
appropriate values for ANT build and Maven build. This is where all
failing.
All the problem is happening because we need omit one version, cause npm
was updated with 0.9.3 - Not sure why.
Update of version should happen
Hi Olaf,
hehe, I think we overlap and mostly said the same ;-)
for me that's the right way.
Thanks
El mié., 19 sept. 2018 a las 10:57, Olaf Krueger ()
escribió:
> > I think there should be some rules where during release process
> committing
> > to develop is stopped.
>
> What do you think
Hi Piotr,
I still doesn't have knowledge of the release process, but hope to be the
next release manager. In the meanwhile, I'm following things, and what I
think, (of course without know to much about the real process and
implications in this concrete project), is that we should do the same as
> I think there should be some rules where during release process committing
> to develop is stopped.
What do you think about creating a "release/v0.9.x" branch which has to be
merged back to master and dev after the release is done instead of doing the
release from dev?
Thanks for doing all
I think everything is messed up right now. Before I got your response I was
in a state where I run:
ant -f releasecandidate.xml -Drelease.version=0.9.4 -Drc=1 make_branches
It pushes to the develop 0.9.4-SNAPSHOT
It pushes release branch called 0.9.4 where there is 0.9.3-SNAPSHOT - Not
sure why.
81 matches
Mail list logo
