You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by Toni Menzel <to...@okidokiteam.com> on 2009/06/03 15:40:10 UTC
trunk code arrival and changes/patches
Hi guys,
i just want to ask when the source will arrive in trunk svn ?
Also, does it make sense
- to create jira items and
- attach patches based on the initial code donation zips (ace-17 in
jira as far as i know) right now ?
Mostly those changes deal with:
Organisational Changes:
- additional build tasks for maven deployment/integration (sure, we
keep ant here, just for deploy the stuff)
- change of artifact names net.luminis.liq --> org.apache.ace and
version 1.0.0 --> 0.1.0-SNAPSHOT
- deployment target cleanup: some scripts lists non-donated artifacts
(graphical UI bundles)
- remove empty packages (probably left overs from cleanup before donating)
Functional Changes:
- Cleanup bnd directives
- Made it java 5 compatible (some committed dependencies are java
class version 50.0, not 49.0)
wdyt ?
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
Re: trunk code arrival and changes/patches
Posted by Toni Menzel <to...@okidokiteam.com>.
This is the regular *ping* for ace in svn.
On Fri, Jun 5, 2009 at 11:36 PM, Marcel
Offermans<ma...@luminis.nl> wrote:
> On Jun 3, 2009, at 13:31 , Bram de Kruijff wrote:
>
>>>> Maven Support: Its currently a 5/6 line addition to build.xml pushing
>>>> the bundles from deploy/bundles to local maven incl. minimal pom.
>>>> Its suprisingly simple, builds are blazing fast (ant, local dependency
>>>> resolution), so practically i would be find with keeping the ant based
>>>> build.
>>>> You really "forget" how fast and simple builds can be after years of
>>>> maven ;)
>>>
>>> Maven support sounds great, Toni!
>>
>> Loving maven too but not religious about it and when it comes to faster
>> builds
>> your are probably right.. although I think the diff is marginal
>> considering most
>> is going into code checking and java doc generation anyway.
>
> Compiling the whole codebase at once instead of bundle by bundle makes a big
> difference in larger projects.
>
>> The simple tweak to support deployment sound nice. Truely mavenizing
>> this codebase would involve some work and IMHO it doesn't make sense
>> to maintain two build frameworks. You can wrap both ways so I guess it
>> should go either way based on consensus.
>
> I agree, I don't want to maintain two build systems. Adding some commands to
> the Ant based build system to deploy (snapshot) artifacts into a maven
> repository sounds like a good solution.
>
> Greetings, Marcel
>
>
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
Re: trunk code arrival and changes/patches
Posted by Marcel Offermans <ma...@luminis.nl>.
On Jun 3, 2009, at 13:31 , Bram de Kruijff wrote:
>>> Maven Support: Its currently a 5/6 line addition to build.xml
>>> pushing
>>> the bundles from deploy/bundles to local maven incl. minimal pom.
>>> Its suprisingly simple, builds are blazing fast (ant, local
>>> dependency
>>> resolution), so practically i would be find with keeping the ant
>>> based
>>> build.
>>> You really "forget" how fast and simple builds can be after years of
>>> maven ;)
>>
>> Maven support sounds great, Toni!
>
> Loving maven too but not religious about it and when it comes to
> faster builds
> your are probably right.. although I think the diff is marginal
> considering most
> is going into code checking and java doc generation anyway.
Compiling the whole codebase at once instead of bundle by bundle makes
a big difference in larger projects.
> The simple tweak to support deployment sound nice. Truely mavenizing
> this codebase would involve some work and IMHO it doesn't make sense
> to maintain two build frameworks. You can wrap both ways so I guess it
> should go either way based on consensus.
I agree, I don't want to maintain two build systems. Adding some
commands to the Ant based build system to deploy (snapshot) artifacts
into a maven repository sounds like a good solution.
Greetings, Marcel
RE: trunk code arrival and changes/patches
Posted by Bram de Kruijff <Br...@gxwebmanager.com>.
> From: Marcel Offermans [marcel.offermans@luminis.nl]
> Sent: Wednesday, June 03, 2009 5:43 PM
> To: ace-dev@incubator.apache.org
> Subject: Re: trunk code arrival and changes/patches
>
>
> On Jun 3, 2009, at 7:29 , Toni Menzel wrote:
>
> > Thanks to Git its not too bad to live without public svn for a while
> > but now time passed by.. @incubator: what are you checking ??
Loving Git concepts but not actually using it yet in real life. Are there any
plans in the Apache community on migrating? It seems there is a proper
svn bridge too.
> > Maven Support: Its currently a 5/6 line addition to build.xml pushing
> > the bundles from deploy/bundles to local maven incl. minimal pom.
> > Its suprisingly simple, builds are blazing fast (ant, local dependency
> > resolution), so practically i would be find with keeping the ant based
> > build.
> > You really "forget" how fast and simple builds can be after years of
> > maven ;)
>
> Maven support sounds great, Toni!
Loving maven too but not religious about it and when it comes to faster builds
your are probably right.. although I think the diff is marginal considering most
is going into code checking and java doc generation anyway.
The simple tweak to support deployment sound nice. Truely mavenizing
this codebase would involve some work and IMHO it doesn't make sense
to maintain two build frameworks. You can wrap both ways so I guess it
should go either way based on consensus.
> > On Wed, Jun 3, 2009 at 3:54 PM, Bram de Kruijff
> > <Br...@gxwebmanager.com> wrote:
> >> +1 for getting it in SVN! I had a look at the zip files but was
> >> also hesitant to start spamming the list/jira before we have a
> >> common codebase. I'd like to help out, so let me know if there is
> >> something I can do to help speed up the process.
>
> Nothing but pinging us right now! :)
/ping ace
/me hitting snooze
/away
Re: trunk code arrival and changes/patches
Posted by Marcel Offermans <ma...@luminis.nl>.
We are currently waiting on the Software Grant to be processed. I
resent it a couple of days because it seemed to be lost the first
time. I need one of the mentors to monitor the process, as I do not
have the karma to check. Perhaps either of them can check what the
current status is.
On Jun 3, 2009, at 7:29 , Toni Menzel wrote:
> Thanks to Git its not too bad to live without public svn for a while
> but now time passed by.. @incubator: what are you checking ??
>
> Maven Support: Its currently a 5/6 line addition to build.xml pushing
> the bundles from deploy/bundles to local maven incl. minimal pom.
> Its suprisingly simple, builds are blazing fast (ant, local dependency
> resolution), so practically i would be find with keeping the ant based
> build.
> You really "forget" how fast and simple builds can be after years of
> maven ;)
Maven support sounds great, Toni!
> Also i am think of sharing some concepts and documentation fragments i
> observed in the codebase. But its not clear too me how close the final
> svn arrival is, actually.
I hope very close. :)
> We are not allowed to share git repositories with ongoing changes
> right now, are we ?
Not sure to be honest.
> I mean, initial donation was done by marcel with zip upload.
> Everything else now would be a legal "fork" under ASL, isn't it ?
Probably, I'm not legal expert.
> On Wed, Jun 3, 2009 at 3:54 PM, Bram de Kruijff
> <Br...@gxwebmanager.com> wrote:
>> +1 for getting it in SVN! I had a look at the zip files but was
>> also hesitant to start spamming the list/jira before we have a
>> common codebase. I'd like to help out, so let me know if there is
>> something I can do to help speed up the process.
Nothing but pinging us right now! :)
Greetings, Marcel
Re: trunk code arrival and changes/patches
Posted by Toni Menzel <to...@okidokiteam.com>.
Thanks to Git its not too bad to live without public svn for a while
but now time passed by.. @incubator: what are you checking ??
Maven Support: Its currently a 5/6 line addition to build.xml pushing
the bundles from deploy/bundles to local maven incl. minimal pom.
Its suprisingly simple, builds are blazing fast (ant, local dependency
resolution), so practically i would be find with keeping the ant based
build.
You really "forget" how fast and simple builds can be after years of maven ;)
Also i am think of sharing some concepts and documentation fragments i
observed in the codebase. But its not clear too me how close the final
svn arrival is, actually.
We are not allowed to share git repositories with ongoing changes
right now, are we ?
I mean, initial donation was done by marcel with zip upload.
Everything else now would be a legal "fork" under ASL, isn't it ?
Toni
On Wed, Jun 3, 2009 at 3:54 PM, Bram de Kruijff
<Br...@gxwebmanager.com> wrote:
> +1 for getting it in SVN! I had a look at the zip files but was also hesitant to start spamming the list/jira before we have a common codebase. I'd like to help out, so let me know if there is something I can do to help speed up the process.
>
> Regards,
> Bram
>
> Ps Looking forward to have maven support ;)
>
> --
> Bram de Kruijff
> Product Architect
>
> GX
> open for business
>
> t: +31(0)24 - 388 82 61
> f: +31(0)24 - 388 86 21
> e: Bram.deKruijff@gxwebmanager.com
>
> www.gxwebmanager.com
>
>
> -----Original Message-----
> From: tonit.com@googlemail.com [mailto:tonit.com@googlemail.com] On Behalf Of Toni Menzel
> Sent: Wednesday, June 03, 2009 3:40 PM
> To: ace-dev@incubator.apache.org
> Subject: trunk code arrival and changes/patches
>
> Hi guys,
>
> i just want to ask when the source will arrive in trunk svn ?
>
> Also, does it make sense
> - to create jira items and
> - attach patches based on the initial code donation zips (ace-17 in
> jira as far as i know) right now ?
>
> Mostly those changes deal with:
> Organisational Changes:
> - additional build tasks for maven deployment/integration (sure, we
> keep ant here, just for deploy the stuff)
> - change of artifact names net.luminis.liq --> org.apache.ace and
> version 1.0.0 --> 0.1.0-SNAPSHOT
> - deployment target cleanup: some scripts lists non-donated artifacts
> (graphical UI bundles)
> - remove empty packages (probably left overs from cleanup before donating)
>
> Functional Changes:
> - Cleanup bnd directives
> - Made it java 5 compatible (some committed dependencies are java
> class version 50.0, not 49.0)
>
> wdyt ?
>
>
> --
> Toni Menzel
> Independent Software Developer
> Professional Profile: http://okidokiteam.com
> toni@okidokiteam.com
> http://www.ops4j.org - New Energy for OSS Communities - Open
> Participation Software.
>
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
RE: trunk code arrival and changes/patches
Posted by Bram de Kruijff <Br...@gxwebmanager.com>.
+1 for getting it in SVN! I had a look at the zip files but was also hesitant to start spamming the list/jira before we have a common codebase. I'd like to help out, so let me know if there is something I can do to help speed up the process.
Regards,
Bram
Ps Looking forward to have maven support ;)
--
Bram de Kruijff
Product Architect
GX
open for business
t: +31(0)24 - 388 82 61
f: +31(0)24 - 388 86 21
e: Bram.deKruijff@gxwebmanager.com
www.gxwebmanager.com
-----Original Message-----
From: tonit.com@googlemail.com [mailto:tonit.com@googlemail.com] On Behalf Of Toni Menzel
Sent: Wednesday, June 03, 2009 3:40 PM
To: ace-dev@incubator.apache.org
Subject: trunk code arrival and changes/patches
Hi guys,
i just want to ask when the source will arrive in trunk svn ?
Also, does it make sense
- to create jira items and
- attach patches based on the initial code donation zips (ace-17 in
jira as far as i know) right now ?
Mostly those changes deal with:
Organisational Changes:
- additional build tasks for maven deployment/integration (sure, we
keep ant here, just for deploy the stuff)
- change of artifact names net.luminis.liq --> org.apache.ace and
version 1.0.0 --> 0.1.0-SNAPSHOT
- deployment target cleanup: some scripts lists non-donated artifacts
(graphical UI bundles)
- remove empty packages (probably left overs from cleanup before donating)
Functional Changes:
- Cleanup bnd directives
- Made it java 5 compatible (some committed dependencies are java
class version 50.0, not 49.0)
wdyt ?
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.