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 2014/07/31 09:37:50 UTC
Missing BlazeDS repo on the sources page
Hi,
I just noticed that we are missing the BlazeDS repo on the Apache Flex Sources Page ...
Chris
AW: Missing BlazeDS repo on the sources page
Posted by Christofer Dutz <ch...@c-ware.de>.
Geee ... I already thought I might have mis-expressed myself.
I didn't setup the build to "release" anything in a software release manner. I have setup the job to publish SNAPSHOT versions of BlazeDS (I did manage to deploy a first set of snapshots manually, but now it's happening automatically).
This ist he usual way software is developed using maven. Noone would use SNAPSHOT versions in public (Acutally you can't even release anything that relys on SNAPSHOT verisons). This is the way a work in progress is shipped to early adopters and I think it's a very good approach. And it's an approach allmost all other Apache projects go.
If we took this even further and we published snapshot versions for all Flex sub-projects. People could start working with 4.14 while it is being developed and report back problems way before we have released a new version, just by changing 1.13.0 to 1.14-SNAPSHOT.
Chris
-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]
Gesendet: Donnerstag, 31. Juli 2014 13:10
An: dev@flex.apache.org
Betreff: Re: Missing BlazeDS repo on the sources page
Hi,
> It seems to be a work in progress, not a release.
Agreed - that's why we shouldn't be making publicly available in the Apache repo.
> You raise valid points that certainly need to be addressed before a
> release is cut. But for now, we should be glad somebody is doing
> actual work that helps us get closer to a version that is NOT Adobe;
> we should help, rather than obstruct, his efforts.
With my PMC hat on. Legal issues are important. it looks like we may be publishing 3rd party jars and all sort of other things that could get up into trouble, like for instance not having a LICENSE file. Please let hold off publishing it for now until we can give it a good looking over.
There's no need to publicly publish this to work out and fix what those issues are, none of the issues I raised are a hinderance or obstruction to currently development.
> Maybe you can have a look at the LICENSE and NOTICE files that would
> be required, as that has become something of a specialty of yours?
Currently I don't have the spare time, but other people are welcome to do so. In fact I'd prefer if someone else does it so they can gain experience at this task. I'm happy to help out and review when I can.
Thanks,
Justin
Re: Missing BlazeDS repo on the sources page
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> It seems to be a work in progress, not a release.
Agreed - that's why we shouldn't be making publicly available in the Apache repo.
> You raise valid points that certainly need to be addressed before a release
> is cut. But for now, we should be glad somebody is doing actual work that
> helps us get closer to a version that is NOT Adobe; we should help, rather
> than obstruct, his efforts.
With my PMC hat on. Legal issues are important. it looks like we may be publishing 3rd party jars and all sort of other things that could get up into trouble, like for instance not having a LICENSE file. Please let hold off publishing it for now until we can give it a good looking over.
There's no need to publicly publish this to work out and fix what those issues are, none of the issues I raised are a hinderance or obstruction to currently development.
> Maybe you can have a look at the LICENSE and NOTICE files that would be
> required, as that has become something of a specialty of yours?
Currently I don't have the spare time, but other people are welcome to do so. In fact I'd prefer if someone else does it so they can gain experience at this task. I'm happy to help out and review when I can.
Thanks,
Justin
Re: Missing BlazeDS repo on the sources page
Posted by Erik de Bruin <er...@ixsoftware.nl>.
It seems to be a work in progress, not a release.
You raise valid points that certainly need to be addressed before a release
is cut. But for now, we should be glad somebody is doing actual work that
helps us get closer to a version that is NOT Adobe; we should help, rather
than obstruct, his efforts.
Maybe you can have a look at the LICENSE and NOTICE files that would be
required, as that has become something of a specialty of yours?
EdB
On Thu, Jul 31, 2014 at 10:45 AM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > What exactly is the problem with it? I have actually just setup a
> jenkins build for this to auto-publish the snapshot versions to Apache
> Maven Repo.
>
> You may want to stop that - see below.
>
> While it "compiles" I get a lot of warning like "bootstrap class path not
> set" and "x.java uses unchecked or unsafe operations", look like some of
> the files are not UTF8 ("unmappable character for encoding UTF8") and
> that's also causing issues. Also while it say it compiles it actuall has
> several fatal errors along the way - for example (and this happens several
> times)
> [MergeXML] [Fatal Error] remoting-config.aftermods.xml:1:1: Premature end
> of file.
> [MergeXML] ** Parsing error, line 1, uri
> file:/Users/justinmclean/Documents/flex-blazeds/qa/apps/qa-manual/WEB-INF/flex/mergeGenerated/remoting-config.aftermods.xml
> [MergeXML] Premature end of file.
>
> Also ant checkintests fails.
>
> It also concerns me we have a large number of jars checked into Git, some
> may or may not be Apache licensed.
>
> And I also think it needs a bit of an IP scrub, from a glance at the
> images these all need to be checked:
> AIR icon issue, blazeDS logo, servidium logo?, Apache camel missing TM,
> log4J book cover, cyberlab logo, duke logo, java world award, hsqldb,
> spring java application framework, jakarta common HTTP client, icons_ ???
> where did these come from?, Apache Jakarta (no longer a project)?,
> logfactor5 logo, apache XML logo missing trademark?, commons logging
> missing trademark?, maven logos (including a maven sucks logo!), build by
> ant logo, open JMS logo, Flex metadata logo, old (tiny) pdf logo,
> Callabnet logo, SourceCast logo, sharp1.jpg, source forge logo, tomcat
> logo, Zaurus logo.
>
> (Most of these may not be in the source package but they probably
> shouldn't be in an Apache repo)
>
> Rather importantly It's missing LICENCE and NOTICE files.
>
> And there probably quite a few other things, for instance I've not done a
> rat check on it.
>
> IMO we should not be making it available as a snapshot until at least some
> of the above is addressed.
>
> Thanks,
> Justin
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Missing BlazeDS repo on the sources page
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> What exactly is the problem with it? I have actually just setup a jenkins build for this to auto-publish the snapshot versions to Apache Maven Repo.
You may want to stop that - see below.
While it "compiles" I get a lot of warning like "bootstrap class path not set" and "x.java uses unchecked or unsafe operations", look like some of the files are not UTF8 ("unmappable character for encoding UTF8") and that's also causing issues. Also while it say it compiles it actuall has several fatal errors along the way - for example (and this happens several times)
[MergeXML] [Fatal Error] remoting-config.aftermods.xml:1:1: Premature end of file.
[MergeXML] ** Parsing error, line 1, uri file:/Users/justinmclean/Documents/flex-blazeds/qa/apps/qa-manual/WEB-INF/flex/mergeGenerated/remoting-config.aftermods.xml
[MergeXML] Premature end of file.
Also ant checkintests fails.
It also concerns me we have a large number of jars checked into Git, some may or may not be Apache licensed.
And I also think it needs a bit of an IP scrub, from a glance at the images these all need to be checked:
AIR icon issue, blazeDS logo, servidium logo?, Apache camel missing TM, log4J book cover, cyberlab logo, duke logo, java world award, hsqldb, spring java application framework, jakarta common HTTP client, icons_ ??? where did these come from?, Apache Jakarta (no longer a project)?, logfactor5 logo, apache XML logo missing trademark?, commons logging missing trademark?, maven logos (including a maven sucks logo!), build by ant logo, open JMS logo, Flex metadata logo, old (tiny) pdf logo, Callabnet logo, SourceCast logo, sharp1.jpg, source forge logo, tomcat logo, Zaurus logo.
(Most of these may not be in the source package but they probably shouldn't be in an Apache repo)
Rather importantly It's missing LICENCE and NOTICE files.
And there probably quite a few other things, for instance I've not done a rat check on it.
IMO we should not be making it available as a snapshot until at least some of the above is addressed.
Thanks,
Justin
AW: Missing BlazeDS repo on the sources page
Posted by Christofer Dutz <ch...@c-ware.de>.
What exactly is the problem with it? I have actually just setup a jenkins build for this to auto-publish the snapshot versions to Apache Maven Repo.
The maven build inside modules seems to be running niceley and to me it looks as if this was the thing tha Adobe guys were using. The Ant construct around the maven build looks completeley outdated to me.
Chris
-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]
Gesendet: Donnerstag, 31. Juli 2014 09:51
An: dev@flex.apache.org
Betreff: Re: Missing BlazeDS repo on the sources page
Hi,
> I just noticed that we are missing the BlazeDS repo on the Apache Flex Sources Page ...
We could put it up but we con't actually compile it and/or make a release - that needs someone to work on it and from a quick glance a few weeks ago it needs a fair amount of work.
Justin
Re: Missing BlazeDS repo on the sources page
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I just noticed that we are missing the BlazeDS repo on the Apache Flex Sources Page ...
We could put it up but we con't actually compile it and/or make a release - that needs someone to work on it and from a quick glance a few weeks ago it needs a fair amount of work.
Justin