You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2015/03/28 14:42:36 UTC

Publish Maven artifacts for released versions of FlexUnit4?

Hi,

I just noticed that we never published any maven artifacts for FlexUnit4 ... would it be ok, to do that post-release? I would checkout the revision we released and stage these in the Apache Repo.

What do you think?

Chris


Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Erik de Bruin <er...@ixsoftware.nl>.
A volunteer?

[Everyone takes one step back]

Mr. Dutz, you're it!

;-)

EdB



On Mon, Mar 30, 2015 at 12:22 PM, Christofer Dutz
<ch...@c-ware.de> wrote:
> Do we have a RM for FlexUnit? Otherwise I'd volunteer to step up to do that :-)
>
> Chris
>
> ________________________________________
> Von: Justin Mclean <ju...@classsoftware.com>
> Gesendet: Montag, 30. März 2015 08:18
> An: dev@flex.apache.org
> Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?
>
> Hi,
>
>> What do you think is this a 4.2.1 or 4.3.0?
>
>
> Up to the RM I'd say, either is fine by me.
>
> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Do we have a RM for FlexUnit? Otherwise I'd volunteer to step up to do that :-)

Chris

________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Montag, 30. März 2015 08:18
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi,

> What do you think is this a 4.2.1 or 4.3.0?


Up to the RM I'd say, either is fine by me.

Justin

Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> What do you think is this a 4.2.1 or 4.3.0?


Up to the RM I'd say, either is fine by me.

Justin

AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Yeah,

think we'll stick to the new release. I saw some bugfixes being in there since 4.2 and this way a lot less can go wrong.

Even if it's just some bugs being fixed, i think 4.3 might be the better way as this way the 4.3 will be the first version deployed as Maven, which I like to think as a major improvement. 

What do you think is this a 4.2.1 or 4.3.0?

Chris

-----Ursprüngliche Nachricht-----
Von: piotrz [mailto:piotrzarzycki21@gmail.com] 
Gesendet: Montag, 30. März 2015 07:28
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi Chris,

I think we should release 4.2.1. I have provided small fix some time ago to flex unit - would be great to have it there. If look into the history log in you will see.

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Publish-Maven-artifacts-for-released-versions-of-FlexUnit4-tp45842p45861.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by piotrz <pi...@gmail.com>.
Hi Chris,

I think we should release 4.2.1. I have provided small fix some time ago to
flex unit - would be great to have it there. If look into the history log in
you will see.

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Publish-Maven-artifacts-for-released-versions-of-FlexUnit4-tp45842p45861.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> As I added the release stuff to the build to the develop branch after the 4.2 release, I doubt I could actually safely release 4.2 revision with this. I would much more think that eventually releasing a 4.2.1 with maven artifacts instead and pack in the changes you and Alex provided since the release.


If we're got fixes that need to be there in order to make a working mavin release then we should make a 4.2.1 (or 4.3) release at some point.

Re publishing the 4.2 jars as they are now, IMO it would be counter productive to publish stuff that's (slightly) broken.

Given the changes since 4.2 are minimal and easily reviewed why not just go with a new release sooner rather than later?

Thanks,
Justin

Re: AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Alex Harui <ah...@adobe.com>.
Either way is fine with me. Is the issue that it is easier to build from the head? I think you can branch from a tag or hash?


Sent from my LG G3, an AT&T 4G LTE smartphone


------ Original message------

From: Christofer Dutz

Date: Sun, Mar 29, 2015 3:15 AM

To: dev@flex.apache.org;

Subject:AW: Publish Maven artifacts for released versions of FlexUnit4?


Hi Justin ... but I just noticed something else.

As I added the release stuff to the build to the develop branch after the 4.2 release, I doubt I could actually safely release 4.2 revision with this. I would much more think that eventually releasing a 4.2.1 with maven artifacts instead and pack in the changes you and Alex provided since the release.

What do you think? Think it would be the safer way.

Chris

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Sonntag, 29. März 2015 12:03
An: dev@flex.apache.org
Betreff: AW: Publish Maven artifacts for released versions of FlexUnit4?

Hi Justin,

investigating it a little more ... ok now this is really strange. I do generate the poms to pom.xml and sign them, but they are renamed when uploading ... will change this ... thanks for reporting this :-)

Chris



[ C h r i s t o f e r  D u t z ]

C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Alleestraße 23, 64367 Mühltal

fon:  0 61 54 / 5779991
mobil:  0171 / 7 444 2 33
email:  christofer.dutz@c-ware.de
http://www.c-ware.de

FA Darmstadt: 07 813 60581

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Sonntag, 29. März 2015 11:30
An: dev@flex.apache.org
Betreff: AW: Publish Maven artifacts for released versions of FlexUnit4?

Oh ... thanks for that hint Justin.
I added the signature stuff to the Ant scripts quite some time ago. For this I had to manually sign all artifacts. Will double-check to make sure the poms are signed too.

Chris




-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]
Gesendet: Sonntag, 29. März 2015 00:27
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi,

> Could you guys please double check the artifacts ...

I guess the main question is how do we confirm what source code this was compiled from?

> I know this is not an official release, but I still thing the signatures need verification.

May be the way it been deployed? but the the jar sigs and md5 hashes are ok (and using an Apache email). but the pom file signature isn't.

for file in *.asc; do echo $file; gpg --verify $file; done

flexUnitTasks-4.2.0-javadoc.jar.asc
gpg: Signature made Sun 29 Mar 04:03:33 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0-sources.jar.asc
gpg: Signature made Sun 29 Mar 04:03:27 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.jar.asc
gpg: Signature made Sun 29 Mar 04:03:13 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.pom.asc
gpg: no signed data
gpg: can't hash datafile: No data

Thanks,
Justin




AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Justin ... but I just noticed something else.

As I added the release stuff to the build to the develop branch after the 4.2 release, I doubt I could actually safely release 4.2 revision with this. I would much more think that eventually releasing a 4.2.1 with maven artifacts instead and pack in the changes you and Alex provided since the release.

What do you think? Think it would be the safer way.

Chris

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de] 
Gesendet: Sonntag, 29. März 2015 12:03
An: dev@flex.apache.org
Betreff: AW: Publish Maven artifacts for released versions of FlexUnit4?

Hi Justin,

investigating it a little more ... ok now this is really strange. I do generate the poms to pom.xml and sign them, but they are renamed when uploading ... will change this ... thanks for reporting this :-)

Chris



[ C h r i s t o f e r  D u t z ]

C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Alleestraße 23, 64367 Mühltal

fon:  0 61 54 / 5779991
mobil:  0171 / 7 444 2 33
email:  christofer.dutz@c-ware.de
http://www.c-ware.de

FA Darmstadt: 07 813 60581

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de] 
Gesendet: Sonntag, 29. März 2015 11:30
An: dev@flex.apache.org
Betreff: AW: Publish Maven artifacts for released versions of FlexUnit4?

Oh ... thanks for that hint Justin.
I added the signature stuff to the Ant scripts quite some time ago. For this I had to manually sign all artifacts. Will double-check to make sure the poms are signed too.

Chris




-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com] 
Gesendet: Sonntag, 29. März 2015 00:27
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi,

> Could you guys please double check the artifacts ...

I guess the main question is how do we confirm what source code this was compiled from?

> I know this is not an official release, but I still thing the signatures need verification. 

May be the way it been deployed? but the the jar sigs and md5 hashes are ok (and using an Apache email). but the pom file signature isn't.

for file in *.asc; do echo $file; gpg --verify $file; done

flexUnitTasks-4.2.0-javadoc.jar.asc
gpg: Signature made Sun 29 Mar 04:03:33 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0-sources.jar.asc
gpg: Signature made Sun 29 Mar 04:03:27 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.jar.asc
gpg: Signature made Sun 29 Mar 04:03:13 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.pom.asc
gpg: no signed data
gpg: can't hash datafile: No data

Thanks,
Justin




AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Justin,

investigating it a little more ... ok now this is really strange. I do generate the poms to pom.xml and sign them, but they are renamed when uploading ... will change this ... thanks for reporting this :-)

Chris



[ C h r i s t o f e r  D u t z ]

C-Ware IT-Service
Inhaber
Dipl. Inf. Christofer Dutz
Alleestraße 23, 64367 Mühltal

fon:  0 61 54 / 5779991
mobil:  0171 / 7 444 2 33
email:  christofer.dutz@c-ware.de
http://www.c-ware.de

FA Darmstadt: 07 813 60581

-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de] 
Gesendet: Sonntag, 29. März 2015 11:30
An: dev@flex.apache.org
Betreff: AW: Publish Maven artifacts for released versions of FlexUnit4?

Oh ... thanks for that hint Justin.
I added the signature stuff to the Ant scripts quite some time ago. For this I had to manually sign all artifacts. Will double-check to make sure the poms are signed too.

Chris




-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com] 
Gesendet: Sonntag, 29. März 2015 00:27
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi,

> Could you guys please double check the artifacts ...

I guess the main question is how do we confirm what source code this was compiled from?

> I know this is not an official release, but I still thing the signatures need verification. 

May be the way it been deployed? but the the jar sigs and md5 hashes are ok (and using an Apache email). but the pom file signature isn't.

for file in *.asc; do echo $file; gpg --verify $file; done

flexUnitTasks-4.2.0-javadoc.jar.asc
gpg: Signature made Sun 29 Mar 04:03:33 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0-sources.jar.asc
gpg: Signature made Sun 29 Mar 04:03:27 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.jar.asc
gpg: Signature made Sun 29 Mar 04:03:13 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.pom.asc
gpg: no signed data
gpg: can't hash datafile: No data

Thanks,
Justin




AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Oh ... thanks for that hint Justin.
I added the signature stuff to the Ant scripts quite some time ago. For this I had to manually sign all artifacts. Will double-check to make sure the poms are signed too.

Chris




-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com] 
Gesendet: Sonntag, 29. März 2015 00:27
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Hi,

> Could you guys please double check the artifacts ...

I guess the main question is how do we confirm what source code this was compiled from?

> I know this is not an official release, but I still thing the signatures need verification. 

May be the way it been deployed? but the the jar sigs and md5 hashes are ok (and using an Apache email). but the pom file signature isn't.

for file in *.asc; do echo $file; gpg --verify $file; done

flexUnitTasks-4.2.0-javadoc.jar.asc
gpg: Signature made Sun 29 Mar 04:03:33 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0-sources.jar.asc
gpg: Signature made Sun 29 Mar 04:03:27 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.jar.asc
gpg: Signature made Sun 29 Mar 04:03:13 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.pom.asc
gpg: no signed data
gpg: can't hash datafile: No data

Thanks,
Justin




Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

May be that the pom's asc file needs to be named flexUnitTasks-4.2.0.pom.xml.asc not flexUnitTasks-4.2.0.pom.asc?

Justin

Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> Could you guys please double check the artifacts ...

I guess the main question is how do we confirm what source code this was compiled from?

> I know this is not an official release, but I still thing the signatures need verification. 

May be the way it been deployed? but the the jar sigs and md5 hashes are ok (and using an Apache email). but the pom file signature isn't.

for file in *.asc; do echo $file; gpg --verify $file; done

flexUnitTasks-4.2.0-javadoc.jar.asc
gpg: Signature made Sun 29 Mar 04:03:33 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0-sources.jar.asc
gpg: Signature made Sun 29 Mar 04:03:27 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.jar.asc
gpg: Signature made Sun 29 Mar 04:03:13 2015 AEDT using RSA key ID 5C60D6B9
gpg: Good signature from "Christofer Dutz (Apache Comitter) <cd...@apache.org>"
flexUnitTasks-4.2.0.pom.asc
gpg: no signed data
gpg: can't hash datafile: No data

Thanks,
Justin




AW: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Christofer Dutz <ch...@c-ware.de>.
Hi,

Ok well I staged the 4.2.0 version in the Apache Staging Repo at:
https://repository.apache.org/content/repositories/orgapacheflex-1008

Could you guys please double check the artifacts ... I know this is not an official release, but I still thing the signatures need verification. So if someone here could do so, it would be great. If there are no objections I would switch the repo to release in two or three days.

So now I would start making sure the 4.3.0-SNAPSHOT versions get deployed automatically.

Chris

________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Samstag, 28. März 2015 15:14
An: dev@flex.apache.org
Betreff: Re: Publish Maven artifacts for released versions of FlexUnit4?

Ok by me.

On 3/28/15, 6:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>I just noticed that we never published any maven artifacts for FlexUnit4
>... would it be ok, to do that post-release? I would checkout the
>revision we released and stage these in the Apache Repo.
>
>What do you think?
>
>Chris
>

Re: Publish Maven artifacts for released versions of FlexUnit4?

Posted by Alex Harui <ah...@adobe.com>.
Ok by me.

On 3/28/15, 6:42 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>I just noticed that we never published any maven artifacts for FlexUnit4
>... would it be ok, to do that post-release? I would checkout the
>revision we released and stage these in the Apache Repo.
>
>What do you think?
>
>Chris
>