That did the trick. Thanks
Sent from my iPhone
> On May 27, 2018, at 8:09 PM, bill lam wrote:
>
> Perhaps, when you merged commits, the version inside
> manifest.ijs did not increment in the correct. Try
> $ git pull --rebase
> and then increment VERSION again and push again.
>
> Вс, 27 мая 20
Perhaps, when you merged commits, the version inside
manifest.ijs did not increment in the correct. Try
$ git pull --rebase
and then increment VERSION again and push again.
Вс, 27 мая 2018, John Baker написал(а):
> Chris, Bill ...
>
> I just pushed another JOD update to the new github repos. The
Chris, Bill ...
I just pushed another JOD update to the new github repos. The version
incremented for all three parts of JOD but no build was triggered. This may
have
been due to resolving a conflict on manifest.ijs.
The new version is 0.9.994.
Eventually I will get the recipe right for updates
I was looking for an reason to stop testing older versions and a minimum of
8.04 is as good as any.
Thanks
Sent from my iPhone
> On May 22, 2018, at 11:19 AM, chris burke wrote:
>
> The current code has a minimum release for builds of 804, see the Changes
> section on page http://code.jsoftw
The current code has a minimum release for builds of 804, see the Changes
section on page http://code.jsoftware.com/wiki/Addons/GitHub .
On Tue, May 22, 2018 at 10:01 AM, bill lam wrote:
> From JAL Build Log
>
> 2018 5 22 15 4 35 addons
> built: general/joddocument0.9.993 j804
> general/joddocu
From JAL Build Log
2018 5 22 15 4 35 addons
built: general/joddocument0.9.993 j804
general/joddocument0.9.993 j805 general/joddocument0...
If you want to continue support j602, then RELEASE needed
to be set to that version. Otherwise, from jwiki it said,
RELEASE earliest J release supported, e.
After adding the required FOLDER and resetting the minimum RELEASE I managed to
trigger a JAL update from the new GitHub repos. Incrementing the VERSION for
commits is critical.
The move to GitHub will expose J code to a much wider audience and foster
better collaboration. I’d urge all addon
Thanks Bill.
I will adjust the manifests.
Sent from my iPhone
> On May 21, 2018, at 9:22 PM, bill lam wrote:
>
> rebuild should be automatical without any delay.
>
> In your manifest.ijs you had reverse something that
> are needed/changed since recently.
>
> -RELEASE=: ''
> -
> -FOLDER=: 'ge
rebuild should be automatical without any delay.
In your manifest.ijs you had reverse something that
are needed/changed since recently.
-RELEASE=: ''
-
-FOLDER=: 'general/jod'
-
+RELEASE=:'j602 j701 j801 j802 j803 j804 j805 j806 j807'
At least, the FOLDER is mandatory. and RELEASE is the
minimu
I pushed a test JOD update to the jsoftware git repos. The commits show but it
didn’t trigger a JAL build.
Are the builds scheduled or is there a manual step on your end?
Sent from my iPhone
> On May 21, 2018, at 12:45 PM, chris burke wrote:
>
> Each addon repo has a webhook that is used to u
Thanks Chris,
I will try an update and test the JAL build.
For now I will leave the release addons under jsoftware.
I maintain a second development set that contains everything in the release
plus much additional stuff that is useful for development but is just bloat for
normal use.
Sent fro
Each addon repo has a webhook that is used to update the J server addons.
It sends a "commit" event to the J server so it can update the addon if the
manifest version has been incremented. This is essentially the same as the
old SVN commit event.
Also, if you wish you can transfer your repos to yo
In the next few days I will be committing a minor JOD update to the new GitHub
addon repos.
I see I am a contributor to the JOD addons and I have set up local git versions
of them. I haven’t tried committing anything yet because I not sure if there is
anything else that needs to done to trigger
13 matches
Mail list logo
