What GroupId for BlazeDS Maven Artifacts?

[Christofer Dutz <ch...@c-ware.de>]

While I'm at it, I thought I'd give BlazeDS a try.

Had to fix one or two things, but I noticed that the pom.xml files provided in the project all reference com.adobe.blazeds ... I guess we should change this. But what to?

org.apache.flex.blazeds

or

org.aoache.blazeds

First GroupId would make it more obvious that BlazeDS has something to do with Flex. But on the other side, could give the impression that you can only use it with Flex.
After all even Adobe didn't tie it to Flex.

I would suggest to use "org.apache.flex.blazeds" ... but that's just my opinion.
What do you think?

Chris

RE: What GroupId for BlazeDS Maven Artifacts?

[Frédéric THOMAS <we...@hotmail.com>]

If we really want to seems independant, which I'm not sure, it could be "org.apache.blazeds" but maybe it was what you meant as "org.apache.flex.blazeds" is reapeted in the first and last proposal.

Frédéric THOMAS

> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: What GroupId for BlazeDS Maven Artifacts?
> Date: Sat, 26 Apr 2014 18:01:30 +0000
> 
> While I'm at it, I thought I'd give BlazeDS a try.
> 
> Had to fix one or two things, but I noticed that the pom.xml files provided in the project all reference com.adobe.blazeds ... I guess we should change this. But what to?
> 
> org.apache.flex.blazeds
> 
> or
> 
> org.aoache.blazeds
> 
> First GroupId would make it more obvious that BlazeDS has something to do with Flex. But on the other side, could give the impression that you can only use it with Flex.
> After all even Adobe didn't tie it to Flex.
> 
> I would suggest to use "org.apache.flex.blazeds" ... but that's just my opinion.
> What do you think?
> 
> Chris
 		 	   		  

Re: What GroupId for BlazeDS Maven Artifacts?

[Nicholas Kwiatkowski <ni...@spoon.as>]

org.apache.flex.blazeds  is what I would recommend.  BlazeDS is not a TLP.

-nick


On Sat, Apr 26, 2014 at 2:01 PM, Christofer Dutz
<ch...@c-ware.de>wrote:

> While I'm at it, I thought I'd give BlazeDS a try.
>
> Had to fix one or two things, but I noticed that the pom.xml files
> provided in the project all reference com.adobe.blazeds ... I guess we
> should change this. But what to?
>
> org.apache.flex.blazeds
>
> or
>
> org.aoache.blazeds
>
> First GroupId would make it more obvious that BlazeDS has something to do
> with Flex. But on the other side, could give the impression that you can
> only use it with Flex.
> After all even Adobe didn't tie it to Flex.
>
> I would suggest to use "org.apache.flex.blazeds" ... but that's just my
> opinion.
> What do you think?
>
> Chris
>