Hi,
> We would have to bundle the source with the SDK and vote on a new SDK release.
Wouldn't that also be in violation? And actually force the component to be non
optional, unless you count having it installed but not using it as non optional?
Justin
There's a key question to be answered on legal-discuss, which is whether
we are in violation of the guidelines by releasing a package that doesn't
bundle or download Category X and just telling folks where to get the
Category X data. Henri said Yes, Greg implied no (with the
runtime-dependency ans
Hi,
You may ant to cc / forward to Curtis as he may not be reading the dev list.
Justin
OK, so should I ask Infra for flex-radii8 or do we want to try this idea
on it?
If I understand, I would create a radii8 branch and check the code in
there?
-Alex
On 8/30/14 10:05 PM, "Harbs" wrote:
>I like it.
>
>On Aug 30, 2014, at 6:13 PM, Christofer Dutz
>wrote:
>
>> Hi,
>>
>> while work
Hi,
One (minor) down side is that work will not show up in git hub default ranch
(develop?) until changes are merged into it. This makes the project look less
active than it is.
Justin
I like it.
On Aug 30, 2014, at 6:13 PM, Christofer Dutz wrote:
> Hi,
>
> while working on Squiggly, FlexPMD and the Mavenizer I too realized that the
> way we are currently doing things here is far from ideal as merging stuff
> back to master is allmost impossible.
>
> How about not having a
Hi Alex,
Given legal advice currently is:
1. If I cannot run Apache Flex without acquiring that (L)GPL data, then it
violates the guidelines.
2. making it an optional feature is a great and perfectly acceptable solution
3. Flex's ActionScript spellchecker would not include the LGPL/GPL dictionari
Hi,
> Glad that it's now working :-)
Well making a snapshop and the snapshop and 100% working may be two different
things. Mind checking the contents for me?
> When running on the Apache Jenkins this automatically works.
Good to know, but making a release is still a manual process right via
h
Glad that it's now working :-)
When running on the Apache Jenkins this automatically works.
That's why I wanted to run the nightly builds on that machine to allow
auto-deploying of SNAPSHOT versions.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Hi,
> ant -f maven.xml
Works for me now - thanks.
> Would start to deploy the SNAPSHOT artifacts to Apaches Snapshot repo.
I have given that a try:
https://repository.apache.org/content/repositories/snapshots/org/apache/flex/squiggly/
Want to confirm everything looks good in there?
Given you
+1
The first workable sounding solution.
Thanks Chris!
EdB
On Saturday, August 30, 2014, Christofer Dutz
wrote:
> Hi,
>
> while working on Squiggly, FlexPMD and the Mavenizer I too realized that
> the way we are currently doing things here is far from ideal as merging
> stuff back to master
Yeah! Welcome ... yet another Chris on board ;-)
Chris
-Ursprüngliche Nachricht-
Von: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Gesendet: Freitag, 29. August 2014 19:08
An: dev@flex.apache.org
Betreff: RE: Please welcome Chris Martin as an Apache Flex committer
Welcome on b
Hi,
while working on Squiggly, FlexPMD and the Mavenizer I too realized that the
way we are currently doing things here is far from ideal as merging stuff back
to master is allmost impossible.
How about not having a "develop" branch, but one for each sub-project. So when
I start working on the
Gee ... I sort of hate Ant ;-)
Well I did notice an error in the code for preparing the poms. I fixed this. It
must have worked, because I didn't use the root of Squiggly as root of the
project, but the main directory. On my machine executing
ant -f maven.xml
inside the main directory correct
On 8/30/14 1:51 AM, "Justin Mclean" wrote:
>Hi,
>
>> From folks who have been in the ipmc longer and advise on whether this
>>is a category x dependency.
>
>Looks like the question has already been answered, and it probably legal
>rather than incubator who would need to answer if we think it is
Hi,
> That was exactly what I was looking for ... thanks :-)
I'm currently getting:
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project
[unknown-group-id]:[unknown-artifact-id]:[unknown-version]
(/Users/justinmclean/Documents/A
Hi,
+1 binding
- artefact names good
- signatures and hash good
- NOTICE and LICENCE good
- README and RELEASE_NOTES fine
- all source files have correct header
- no binary files in source release
- can compile from source package
- can create example that works
Possible minor issues:
Generated
Hi,
> From folks who have been in the ipmc longer and advise on whether this is a
> category x dependency.
Looks like the question has already been answered, and it probably legal rather
than incubator who would need to answer if we think it is an issue.
1. https://code.google.com/p/lucene-hun
18 matches
Mail list logo
