I'm at the end of my day and will try it tomorrow.
-Alex
On 6/19/17, 11:27 PM, "piotrz" wrote:
>Hi Alex,
>
>I also got some info from Chris that it can be done by: “mvn clean deploy
>–Papache-release”. Please do this - if not I can try it today.
>
>Let me know.
>
>Piotr
>
>
>
>-
>Apache Fl
Hi Alex,
I also got some info from Chris that it can be done by: “mvn clean deploy
–Papache-release”. Please do this - if not I can try it today.
Let me know.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nab
In reading more about Maven, it appears that we might be able to run "mvn
deploy" against the current Git release0.8.0 branch. I might try that
tomorrow to see what it does.
Thoughts?
-Alex
On 6/19/17, 4:21 PM, "Alex Harui" wrote:
>Hi Piotr,
>
>I noticed that there appears to be an option to c
Hi Piotr,
I noticed that there appears to be an option to create a release from an
SCM tag. So that might be another option that needs researching.
-Alex
On 6/19/17, 4:02 PM, "piotrz" wrote:
>Hi Alex,
>
>I will study it tomorrow and try something. I think I will try to revert
>my
>changes in
Hi Alex,
I will study it tomorrow and try something. I think I will try to revert my
changes in poms, but still waiting for some idea from others.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCU
I found that I can login with my Apache credentials here:
https://repository.apache.org/
And this:
http://www.apache.org/dev/publishing-maven-artifacts.html
HTH,
-Alex
On 6/19/17, 5:19 AM, "piotrz" wrote:
>While I'm waiting for some feedback from others I would like to ask how
>actuall
While I'm waiting for some feedback from others I would like to ask how
actually login to nexus where Apache releases are holds ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-
Alex,
Ok since I finally understand it - Let's wait a bit what others think.
I think option with reverting will not be so painful. Changing everything
from 0.8.0 to 0.8.0-SNAPSHOT is almost automatic doing that:
mvn versions:set -DnewVersion=0.8.0-SNAPSHOT
As for the copy manually I think that
Hi Piotr,
No, I just meant to copy the KEYS file out to
https://dist.apache.org/repos/dist/dev/flex/sdk
I just went and did it and synced up our KEYS files. There is also one at:
https://dist.apache.org/repos/dist/release/flex
Thanks,
-Alex
On 6/18/17, 2:31 AM, "piotrz" wrote:
>Alex,
>
>I ju
Yep, that's what I've been warning about. Maven expects things a certain
way and it isn't clear you can/should alter the sequence.
Option 3 is to alter the Ant scripts to work from what Maven produces
Option 4 is to upgrade the Maven steps to produce everything Ant would
produce (including someho
I have assumption after digging into that farther that we will not be able to
make the rest of steps from the instruction.
Release plugin used in maven build is assuming that on startup you have
1) Branch with Snapshot
2) You are creating from that branch another one - This one is for release
(in
If I correct understand Chris's instruction [1] in order to cut next RC I
need to do "mvn release:perform".
Anyone is understand it differently ?
Steps from 1-4 are done on our branch.
I just tried it on falcon repository and got fail [2]. There is also
following file which seems to be genera
I will try to play with steps from Chris to see what Maven will ask me during
that. I hope I will not break anything.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJ
Alex,
I just update KEYS file in flex-sdk repo.
By this "And then use that file to update the KEYS file on
dist.apache.org/release/flex/KEYS" you mean that I need to do signing
something like that [1] ?
[1] https://www.apache.org/dev/release-signing.html#sign-release
Piotr
-
Apache Fl
I think all you need to do now is append the key to the KEYS file in
flex-sdk repo. And then use that file to update the KEYS file on
dist.apache.org/release/flex/KEYS.
IMO it is optional to update id.apache.org.
Thanks,
-Alex
On 6/17/17, 9:34 AM, "piotrz" wrote:
>It look like I'm stuck with
I just dig into old BlazeDS release [1] and I see that Chris put it into some
folder. I think if I run Maven "apache-release" profile I think I may be
able to put them into some folder here [2].
We will see if someone help me with this keys for signing process.
[1]
http://apache-flex-development.
It look like I'm stuck with this one. :/
I did generate key and push it to the public serever [1], but if I correct
understand you I still need to push it on my private space id.apache.org.
Maybe it's enough to sign artifacts ?
[1]
http://p80.pool.sks-keyservers.net/pks/lookup?op=get&search=0x6B
Hi Alex,
This instruction [1] is saying:
"To use key-based login, you need to generate the key on your local desktop
(do not use a publicly accessible server for this) and then add your public
key to LDAP using the self-service app at https://id.apache.org";
Is this the key which I've generated
Hi Piotr,
SFTP is used to access home.apache.org. Search for "home.apache.org" on
this page: https://www.apache.org/dev/committers.html
I'm not sure I did all of those steps. The one remaining thing I think
you need to do is add your key to our KEYS file as described later in [2].
HTH,
-Alex
Hi,
I'm going through instruction of keys generation and last thing which I need
to do is publish myfile.asc to home.apache.org. In order to have something
like that [1]. I have instruction [2], but do not understand how can I
connect and upload to public_home this as file - Any idea ?
[1] http:/
If you look up past BlazeDS releases, which are Maven driven, I'm pretty
sure the artifacts are put in a staging repository for examination.
Somehow, testers will pull the artifacts from this place instead of the
final home on Maven Central.
At least, that's how I understood it, but I could certai
Alex,
What do you mean by "staging" repository ? Let's wait for opinion from other
PMC. I will try to go over signing instruction from Josh.
Let's make this release finally happen!
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-deve
And Nexus isn't an Apache thing AFAICT. You might have to read up on how
it integrates with Maven.
Thanks for offering to help out on the Maven side. I'm concerned that you
can't just take manually/locally built artifacts and follow the steps to
publish those artifacts. I think those steps migh
You're going to want to get your signing key ready:
https://www.apache.org/dev/release-signing.html
- Josh
On Fri, Jun 16, 2017 at 11:40 AM, piotrz wrote:
> Hi Alex,
>
> I think option 3 is almost what I think we should do.
>
> - Ant - examining should be same as it was by Approval script - No
Hi Alex,
I think option 3 is almost what I think we should do.
- Ant - examining should be same as it was by Approval script - No change
here.
- Maven:
1) Build Maven from sources downloaded by Approval script (I think it should
be possible to build FlexJS and Falcon) or checkout release branch
I still don't think we have clarity on how to complete this release.
AIUI, nobody has run any of the Maven commands in [1]. Instead, versions
in POM files have been manually updated?
If I run my Ant scripts to produce another set of artifacts, who is going
to run what steps in order to produce m
Ok build finished successfully.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp62274p62426.html
Sent from the Apache Flex Development mailing list arch
Hi,
I just tested and pushed the changes to release branch, additionally fixed
one small bug. Once build [1] pass I think we are ready to go.
Fix for patching problem was also committed by Justin.
[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/release0.8.0/37/
Piotr
Hi,
> I did the changes, but need to do more test whether I didn't forget about
> something. I will push everything tomorrow - if there will not be any veto.
Just a friendly reminder that a -1 on a release vote is not a veto. You need 3
+1’s and more +1’s than -1’s for a release vote to pass.
H
I did the changes, but need to do more test whether I didn't forget about
something. I will push everything tomorrow - if there will not be any veto.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISC
Ahh! Ok so I will change the poms later today.
Once Vote pass we will be able to deploy it to the apache maven central by
Chris instruction.
Got it!
Thanks Josh once again!
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.
As I understand it, we need the pom.xml versions to be updated to 0.8.0
before we cut the RC. That was the biggest issue. The RC can't have
0.8.0-SNAPSHOT in it.
- Josh
On Thu, Jun 15, 2017 at 3:02 AM, piotrz wrote:
> Hi,
>
> Here is my understanding what need to be done in this release.
> 1) F
Hi,
Here is my understanding what need to be done in this release.
1) Fix issue with patching typedefs
2) Cut next RC, if vote pass I will try to execute Chris's steps starting
from p. 4 [1] (Josh help me to understand it.) in order to deploy released
artifacts and change branch from 0.8.0-SNAPSH
I forgot to post link, from pipeline [1]
[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/develop/75/console
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Re
I think I did update develop branch to 0.9.-SNAPSHOT. Build of compiler and
typedefs went fine, but FlexJS is failing and I'm not sure why.
It's searching this some swc [1] but with version + date:
Could not find artifact
org.apache.flex.flexjs.typedefs:flexjs-typedefs-parent:pom:0.9.0-20170614.1
Hi Christofer,
Does the RM execute these steps locally or on builds.a.o?
Do we need logins to Nexus?
Does "mvn release:perform" checkout from a tag, or head or something else?
Could it checkout from a tag?
Thanks,
-Alex
On 6/13/17, 1:34 AM, "Christofer Dutz" wrote:
>I just wrote down the proc
Hi Olaf,
I think we need to go through the steps which Chris provided and then we can
cut another RC.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Discuss-Release-Apache-FlexJS-0-8-0-RC1-tp6
Hi guys,
>It seems to me there is some interest in the extended community to see a
release out
It's still hard for me to understand the technical details but it seems to
me that the discussion Maven over Ant has reached a new climax which is not
very helpful at least.
Maybe I got something wrong
I just wrote down the process:
https://cwiki.apache.org/confluence/display/FLEX/Releasing+FlexJS+with+Maven
Chris
Am 13.06.17, 10:08 schrieb "piotrz" :
Chris,
If you are not going to do this, I can try but probably I will have a lot of
questions and it's not going to happen soon
Chris,
If you are not going to do this, I can try but probably I will have a lot of
questions and it's not going to happen soon. I will have time on maybe today
(but cannot promise) and on wednesday.
Just let me know. Even if you will do this I will pay attention to each of
your commits in order
If we want to do a release of Maven artifacts, yes.
It’s quite easy with Maven, it’s only difficult doing Maven releases with Ant.
Chris
Am 13.06.17, 09:19 schrieb "piotrz" :
Hi Chris,
I'm not sure from that point whether we can cut next RC or not. It seems
that we have to st
Hi Chris,
I'm not sure from that point whether we can cut next RC or not. It seems
that we have to still make your steps which you described earlier? Am I
right?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.
All Flex project repos are prefixed with flex-
> On Jun 13, 2017, at 9:59 AM, Christofer Dutz
> wrote:
>
> By the way … why is this directory called “flex-typedefs” and not
> “flexjs-typedefs”?
>
> Chris
>
> Am 13.06.17, 08:55 schrieb "Christofer Dutz" :
>
>Hi all,
>
>Please don’t
By the way … why is this directory called “flex-typedefs” and not
“flexjs-typedefs”?
Chris
Am 13.06.17, 08:55 schrieb "Christofer Dutz" :
Hi all,
Please don’t let this become another license discussion … I thought that
had been settled. I intentionally added that this was a techni
Hi all,
Please don’t let this become another license discussion … I thought that had
been settled. I intentionally added that this was a technical issue in my
report.
If the flexjs-typedefs directory is going to be included in the compiler
package, the compiler packages pom needs an exclusion
Hi -
> On Jun 12, 2017, at 12:41 PM, Alex Harui wrote:
>
> I'm confused. Can I get a summary?
>
> Are there some files that are being caught by RAT? If so, what are they?
>
> Are we sure the process should be that the RM should switch away from
> SNAPSHOT before the vote? If a major problem
Hi,
> Justin - you did state that you consider this acceptable for this release and
> that we can clean it up for the next.
Yes I stated that in my vote and that would be acceptable.
Thanks,
Justin
Hi -
> On Jun 12, 2017, at 3:34 PM, Justin Mclean wrote:
>
> Hi,
>
>> Are there some files that are being caught by RAT? If so, what are they?
>
> I mentioned them in my vote email. [1] 3 patch files don’t have ASF headers.
We may need to revisit the project’s preferred way of doing this. Fr
Hi,
> Are there some files that are being caught by RAT? If so, what are they?
I mentioned them in my vote email. [1] 3 patch files don’t have ASF headers.
> IMO, the main thing folks want from Maven are the JARs which aren't an
> official ASF release anyway. Seems like we should vote on a sou
Replying to Yishay and Alex:
Last time I took the release source bundle, changed the versions and ran a
release build. Even if this worked, it was just a hack and technically we
published release artifacts that are different than the version we voted on.
So, someone who downloads the release ar
I'm confused. Can I get a summary?
Are there some files that are being caught by RAT? If so, what are they?
Are we sure the process should be that the RM should switch away from
SNAPSHOT before the vote? If a major problem is found in that RC,
wouldn't we have deployed bad artifacts under the
Doesn't this logic mean that all the releases up to now have been invalid?
It seems to me there is some interest in the extended community to see a
release out. Looking at the RELEASE_NOTES I see lots of nice new features
and bug fixes, which would be beneficial to people who want to start using
Hi Piotr,
No … all good (
I’d be happy to document things that help someone that wants to dig into Maven.
Right now, most of my free dev-time is going to other Apache projects so my
time is limited, but documenting this a little should be ok.
Chris
Am 12.06.17, 13:25 schrieb "piotrz" :
Chris,
I hope I didn't offend you or something. I would like to understand it
clearly in order to do this if you will not be available in the next release
cause of other tasks.
Do we have your steps on confluence ? If not will you have some time to put
there as part of release process ?
Thanks,
It should be between the Last call and opening the vote. It is equal to
“cutting the release candidate”.
So, the LAST CALL thread is finished and the RM writes that he’s going to cut a
release … AFTER THAT he does these steps and THEN he opens the vote thread. I
never said anything else than th
Chris,
I'm a bit confused. You have said that I shouldn't do this as part of
VOTING, LAST CALL:
"No,
The removing the SNAPSHOT, tagging and setting the new version should be,
more or less, one step.
"
Now you are saying just opposite. So again when I should do this (Last Call,
Voting) step ?
Samsung Galaxy Smartphone gesendet.
Ursprüngliche Nachricht
Von: piotrz
Datum: 12.06.17 11:56 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Discuss Release Apache FlexJS 0.8.0 RC1
Ok. So all your steps are required for post VOTING.
I didn't have problems when
Ok. So all your steps are required for post VOTING.
I didn't have problems when I was building sources downloaded by
ApproveFlexJS script, but I will try again at home to make sure that I
didn't have -Dskip.rat.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in cont
No,
The removing the SNAPSHOT, tagging and setting the new version should be, more
or less, one step.
The maven-release-plugin handles almost all of this in one step. So if your do
a release:prepare all of this should happen. You can then have others checkout
the tag and if all give their go,
Chris,
I still didn't get clear answer to my question. I would like to understand
it in order to do this in the next release. I will try to clarify my
questions:
1) Once release manager make "Last Call" - Should I remove SNAPSHOT from all
poms on release branch ?
2) Should I do 1 during VOTING ?
Actually not by removing the credentials … by using an empty settings.xml or
none at all and having a default. My settings-test.xml only contains the
location of the maven local repo and no other settings therefore Maven defaults
to its built-in defaults (I did manually provide the artifacts the
Hi,
> mvn clean install -Drat.skip=true -s ~/.m2/settings-test.xml
>
> (My settings-test.xml simply excludes the Apache snapshot repo)
So by just removing this right?
apache.snapshots.https
jmclean
X
If so I’m still getting this:
error: patch failed: js/target/downloads/svg.js:
2017-06-12 11:03 GMT+02:00 Christofer Dutz :
>
> But not being able to release stuff to Maven-Central is reason enough for
> a -1 … sorry for that … next RC should also handle the version numbers of
> the maven pom as I described them in my last post to this thread.
>
>
Total agree since the main
Ok … so I setup a build that doesn’t accidentally pull in SNAPSHOTS from the
Apache repo:
mvn clean install -Drat.skip=true -s ~/.m2/settings-test.xml
(My settings-test.xml simply excludes the Apache snapshot repo)
One thing I found (no this is not going to be a legal thing … I am reporting
t
Hi,
Locally I have been using Maven for 4 months or so to build Falcon / FlexJS and
haven’t run into any major issues expect when the dual branch was first merged
and in the last couple of days so obviously something has changed recently that
stops this from working.
Thanks,
Justin
Carlos,
We had pretty long discussion on ApacheCon about that. I hope we will get
the point where Maven will be the main builder for the framework.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCU
Hi Piotrz,
sorry, but I almost sure we decided to put maven as main way of building. I
know how to build with ant with the approve xml, and did it other times for
other releases, but I think is totally wrong with what we agreed in this
list.
Maybe I'm wrong but if not, It's almost strange to me n
Hi,
> Flex-typedefs code should be packaged in the -falconjx packages.
I can see in that in the falcon source release when when I try to compile it I
get the following error:
error: patch failed: js/target/downloads/svg.js:401
error: js/target/downloads/svg.js: patch does not apply
Thanks,
Jus
Hi Chris,
But you are saying what should happened once we are after release, not
during Release Cut and Voting ? During that time we should still use
SNAPSHOT ?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.24
You were probably getting the SNAPSHOTS from the Apache SNAPSHOT repo.
Ok … I promised not to invest any more of my time in issues related to the
double-build-system, guess I’ll make an exception …
1) In order to have a proper Maven release, the versions of the maven build
should be changed to
Hi,
Here’s the link to the latest failure onto build server and you can see it’s
typedef related.
https://builds.apache.org/job/FlexJS%20Framework%20(maven)/953/console
Thanks,
Justin
Hi,
> I didn't get it and I was building by Maven straight from the sources
> downloaded by ApproveFlexJS script.
Are these the same sources that are in the release? Perhaps there’s an issue
there
BTW I’m also see the issue on develop branch and so is the apache build server.
Thanks,
Justi
Hi Justin,
I didn't get it and I was building by Maven straight from the sources
downloaded by ApproveFlexJS script. Can you try build typedefs and later SDK
- what will happen ?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-
Hi,
Currently the RC1 fails to compile with maven with this error:
[ERROR] org.apache.flex.flexjs.typedefs:flexjs-typedefs-js:swc:0.8.0-SNAPSHOT
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] apache-release
(https://repository.apache.org/content/repositories/releases, releases=t
Hi,
> I did not see anything that would preclude a release, but the readme does not
> have anything that mentions Maven. The prerequisites only mention ANT and
> environment variables.
Falcon has this [1] should be easy enough to do similar.
Thanks,
Justin
1. https://github.com/apache/flex-fa
I did not see anything that would preclude a release, but the readme does not
have anything that mentions Maven. The prerequisites only mention ANT and
environment variables.
It would be a good idea that for the next release, we should add installation
instructions for Maven as well. (and proba
Hi Carlos,
Unfortunately Maven is not the main way of building of FlexJS.
- Flex installer still serves Ant build of FlexJS for the user.
- Maven distribution package of FlexJS has some missing thing and it is not
usable by IDE - jira has been raised.
As for the tests:
I did all tests as you m
Hi,
in the vote thread the instructions are for ANT, but no mention for MAVEN.
I thought we set maven as the default way to build, so shouldn't be
mentioned?
apart from that. Is right If I:
a) check rc1 branch
b) pass maven in that branch
c) test is all right
thanks
2017-06-10 17:25 GMT+02:0
Flex-typedefs code should be packaged in the -falconjx packages.
-Alex
On 6/10/17, 1:49 AM, "Justin Mclean" wrote:
>Hi,
>
>Perhaps a silly question but does there need to be a release of the
>typedef project as well? Even if only for Maven?
>
>Thanks,
>Justin
Hi,
Perhaps a silly question but does there need to be a release of the typedef
project as well? Even if only for Maven?
Thanks,
Justin
Please note that I will be traveling for the next few days. In any case I
will be waiting for the artifacts to be propagated through the mirrors
before pushing a FlexJS npm release.
Hopefully the timelines will coincide. Worst case, there will be a bit of
a lag for the npm release.
Thanks,
Om
81 matches
Mail list logo
