No worries, man.
You can feel lucky, cause it was a more messy work organizing the mass of
resources into single artifacts than anything else.
;)

Now, i you could check things out and try to make a dev-server  or
dev-gateway target (use pax runner to easily grab the maven artifacts using
 the mvn:<groupId>:<artifactId>:<version>).
Not sure, are you aware of Pax Runner ?

When trying, you will see really fast that things don't work out because the
bundles are (mostly) default bnd settings.
You should compare the contents+manifest of the maven build artifacts and
the ones from core/deploy/bundles (built by ant).
Then, i think its enough for most of the cases to tweak the osgi.bnd file
(bnd files, used by maven-bundle-plugin) in the right direction to get the
desired shape.
Changing Export-Package, Private-Package and and adding Embed-Dependency
where appropriate.
(we call the ANT build the reference)

So, i think you just start over when you have some time and look at those
things and don't hesitate to commit the changes.

If you want, we can skype/gmailchat tomorrow ?
My skype is tonitcom, gmail is tonit.com@gmail.com

have fun,
Toni

On Wed, Dec 9, 2009 at 7:41 PM, Brian Topping <topping@codehaus.org> wrote:

> Hi Toni,
>
> I was starting to feel like I had missed the boat for helping out, so I'm
> glad you asked.
>
> What can I do here? Would you like to take the lead on task delegation or
> should we just jump in?
>
> Cheers, Brian
>
>
> On Dec 9, 2009, at 1:17 PM, Toni Menzel wrote:
>
>  Hi guys,
>>
>> at [1] we now have not less than 50 maven artifacts, made of what i found
>> in
>> build.xml (project-bundle calls).
>> All bundles are pre-configured with the standard maven-bundle-plugin (2.0)
>> behavior.
>>
>> Exceptions are:
>> - multigatewaybootstrap
>> - Webstart Management Agent
>> Both are pretty much distributions and should be not ported 1:1 but using
>> the maven way (assembly plugin for example). Saved that for later, once
>> things work.
>> - webui
>> Done as ACE-69.
>>
>> Having that said, they are not identical to the bundles produced by the
>> ant
>> build yet.
>> This is going to be the next step (see
>> https://issues.apache.org/jira/browse/ACE-62 for a complete list)
>>
>> As a third step, the webui is going to be ported using the
>> maven-gwt-plugin.
>> I found that an extra library is required (dnd-gwt). Unfortunately the
>> author has not been pushed it to a maven repo. Have already contacted the
>> author about it.
>> As last resort we always can push it ourselves to any repo.
>>
>> Just you know the state of affairs. At this stage, work could be split up
>> pretty nicely. So if one wants to step up ?
>>
>> cheers,
>> Toni
>>
>> [1] https://svn.apache.org/repos/asf/incubator/ace/trunk
>>
>
>


-- 
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.

Hi Toni,

thanks a lot for the update.

Regards
JB

Toni Menzel wrote:
> Hi guys,
> 
> at [1] we now have not less than 50 maven artifacts, made of what i found in
> build.xml (project-bundle calls).
> All bundles are pre-configured with the standard maven-bundle-plugin (2.0)
> behavior.
> 
> Exceptions are:
> - multigatewaybootstrap
> - Webstart Management Agent
> Both are pretty much distributions and should be not ported 1:1 but using
> the maven way (assembly plugin for example). Saved that for later, once
> things work.
> - webui
> Done as ACE-69.
> 
> Having that said, they are not identical to the bundles produced by the ant
> build yet.
> This is going to be the next step (see
> https://issues.apache.org/jira/browse/ACE-62 for a complete list)
> 
> As a third step, the webui is going to be ported using the maven-gwt-plugin.
> I found that an extra library is required (dnd-gwt). Unfortunately the
> author has not been pushed it to a maven repo. Have already contacted the
> author about it.
> As last resort we always can push it ourselves to any repo.
> 
> Just you know the state of affairs. At this stage, work could be split up
> pretty nicely. So if one wants to step up ?
> 
> cheers,
> Toni
> 
> [1] https://svn.apache.org/repos/asf/incubator/ace/trunk
> 

-- 
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086

    [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788222#action_12788222
] 

Toni Menzel commented on ACE-65:
--------------------------------

most (all?) commits went under the commit message "ACE-62 .." because the task splitting has
been done after initial ace-62 work. 

> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)
> This step does not necessary align with the exact bundle structure you get from the ant
build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hi Toni,

I was starting to feel like I had missed the boat for helping out, so  
I'm glad you asked.

What can I do here? Would you like to take the lead on task delegation  
or should we just jump in?

Cheers, Brian

On Dec 9, 2009, at 1:17 PM, Toni Menzel wrote:

> Hi guys,
>
> at [1] we now have not less than 50 maven artifacts, made of what i  
> found in
> build.xml (project-bundle calls).
> All bundles are pre-configured with the standard maven-bundle-plugin  
> (2.0)
> behavior.
>
> Exceptions are:
> - multigatewaybootstrap
> - Webstart Management Agent
> Both are pretty much distributions and should be not ported 1:1 but  
> using
> the maven way (assembly plugin for example). Saved that for later,  
> once
> things work.
> - webui
> Done as ACE-69.
>
> Having that said, they are not identical to the bundles produced by  
> the ant
> build yet.
> This is going to be the next step (see
> https://issues.apache.org/jira/browse/ACE-62 for a complete list)
>
> As a third step, the webui is going to be ported using the maven-gwt- 
> plugin.
> I found that an extra library is required (dnd-gwt). Unfortunately the
> author has not been pushed it to a maven repo. Have already  
> contacted the
> author about it.
> As last resort we always can push it ourselves to any repo.
>
> Just you know the state of affairs. At this stage, work could be  
> split up
> pretty nicely. So if one wants to step up ?
>
> cheers,
> Toni
>
> [1] https://svn.apache.org/repos/asf/incubator/ace/trunk

Hi guys,

at [1] we now have not less than 50 maven artifacts, made of what i found in
build.xml (project-bundle calls).
All bundles are pre-configured with the standard maven-bundle-plugin (2.0)
behavior.

Exceptions are:
- multigatewaybootstrap
- Webstart Management Agent
Both are pretty much distributions and should be not ported 1:1 but using
the maven way (assembly plugin for example). Saved that for later, once
things work.
- webui
Done as ACE-69.

Having that said, they are not identical to the bundles produced by the ant
build yet.
This is going to be the next step (see
https://issues.apache.org/jira/browse/ACE-62 for a complete list)

As a third step, the webui is going to be ported using the maven-gwt-plugin.
I found that an extra library is required (dnd-gwt). Unfortunately the
author has not been pushed it to a maven repo. Have already contacted the
author about it.
As last resort we always can push it ourselves to any repo.

Just you know the state of affairs. At this stage, work could be split up
pretty nicely. So if one wants to step up ?

cheers,
Toni

[1] https://svn.apache.org/repos/asf/incubator/ace/trunk

     [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toni Menzel resolved ACE-65.
----------------------------

    Resolution: Fixed

> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)
> This step does not necessary align with the exact bundle structure you get from the ant
build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Port WebUI to clean Maven build
-------------------------------

                 Key: ACE-69
                 URL: https://issues.apache.org/jira/browse/ACE-69
             Project: Ace
          Issue Type: Sub-task
            Reporter: Toni Menzel


This is separated from the other (normal bundles) because it includes the use of maven-gwt-plugin
and additional proper packaging.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toni Menzel updated ACE-65:
---------------------------

    Description: 
A a result, we need to get all relevant bundles for currently used targets from the maven
build.
So this involves splitting core/gateway/server resources into pretty small artifacts. By default
they are all bundles (maven-bundle-plugin), with the exception of commonly used libraries
(embedded into different bundles)

This step does not necessary align with the exact bundle structure you get from the ant build.

  was:
A a result, we need to get all relevant bundles for currently used targets from the maven
build.
So this involves splitting core/gateway/server resources into pretty small artifacts. By default
they are all bundles (maven-bundle-plugin), with the exception of commonly used libraries
(embedded into different bundles)



> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)
> This step does not necessary align with the exact bundle structure you get from the ant
build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/ACE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toni Menzel reassigned ACE-68:
------------------------------

    Assignee: Toni Menzel

> Align bundle partitioning with ant build
> ----------------------------------------
>
>                 Key: ACE-68
>                 URL: https://issues.apache.org/jira/browse/ACE-68
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> this makes the maven build actually a drop in replacement for the ant based artifacts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Align bundle partitioning with ant build
----------------------------------------

                 Key: ACE-68
                 URL: https://issues.apache.org/jira/browse/ACE-68
             Project: Ace
          Issue Type: Sub-task
            Reporter: Toni Menzel


this makes the maven build actually a drop in replacement for the ant based artifacts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786991#action_12786991
] 

Toni Menzel edited comment on ACE-65 at 12/7/09 5:20 PM:
---------------------------------------------------------

Current mvn build looks like this
{code}
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache ACE - POM .................................. SUCCESS [2.061s]
[INFO] Apache ACE - Util (library) ....................... SUCCESS [2.713s]
[INFO] Apache ACE - Repository ........................... SUCCESS [2.353s]
[INFO] Apache ACE - Repository Impl ...................... SUCCESS [1.528s]
[INFO] Apache ACE - ConsoleLogger ........................ SUCCESS [1.326s]
[INFO] Apache ACE - Log .................................. SUCCESS [1.948s]
[INFO] Apache ACE - Discovery API ........................ SUCCESS [1.123s]
[INFO] Apache ACE - Discovery Property based ............. SUCCESS [1.649s]
[INFO] Apache ACE - Identification Property .............. SUCCESS [1.080s]
[INFO] Apache ACE - Identification API ................... SUCCESS [2.219s]
[INFO] Apache ACE - Scheduler API ........................ SUCCESS [0.831s]
[INFO] Apache ACE - Deployment Provider API .............. SUCCESS [0.847s]
[INFO] Apache ACE - Client Repository (library) .......... SUCCESS [2.226s]
[INFO] Apache ACE - Deployment Streamgenerator ........... SUCCESS [0.851s]
[INFO] Apache ACE - Deployment Servlet ................... SUCCESS [1.065s]
[INFO] Apache ACE - Deployment Provider Base (library) ... SUCCESS [0.931s]
[INFO] Apache ACE - Deployment Provider Filebased ........ SUCCESS [1.087s]
[INFO] Apache ACE - Deployment Provider Repositorybased .. SUCCESS [1.586s]
[INFO] Apache ACE - HttpListener ......................... SUCCESS [1.231s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31.057s
[INFO] Finished at: Mon Dec 07 18:11:10 CET 2009
[INFO] Final Memory: 21M/506M
[INFO] ------------------------------------------------------------------------
{code}
Though not 100% complete and functional but in deep progress.

      was (Author: tonit):
    Current mvn build looks like this
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache ACE - POM .................................. SUCCESS [2.061s]
[INFO] Apache ACE - Util (library) ....................... SUCCESS [2.713s]
[INFO] Apache ACE - Repository ........................... SUCCESS [2.353s]
[INFO] Apache ACE - Repository Impl ...................... SUCCESS [1.528s]
[INFO] Apache ACE - ConsoleLogger ........................ SUCCESS [1.326s]
[INFO] Apache ACE - Log .................................. SUCCESS [1.948s]
[INFO] Apache ACE - Discovery API ........................ SUCCESS [1.123s]
[INFO] Apache ACE - Discovery Property based ............. SUCCESS [1.649s]
[INFO] Apache ACE - Identification Property .............. SUCCESS [1.080s]
[INFO] Apache ACE - Identification API ................... SUCCESS [2.219s]
[INFO] Apache ACE - Scheduler API ........................ SUCCESS [0.831s]
[INFO] Apache ACE - Deployment Provider API .............. SUCCESS [0.847s]
[INFO] Apache ACE - Client Repository (library) .......... SUCCESS [2.226s]
[INFO] Apache ACE - Deployment Streamgenerator ........... SUCCESS [0.851s]
[INFO] Apache ACE - Deployment Servlet ................... SUCCESS [1.065s]
[INFO] Apache ACE - Deployment Provider Base (library) ... SUCCESS [0.931s]
[INFO] Apache ACE - Deployment Provider Filebased ........ SUCCESS [1.087s]
[INFO] Apache ACE - Deployment Provider Repositorybased .. SUCCESS [1.586s]
[INFO] Apache ACE - HttpListener ......................... SUCCESS [1.231s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31.057s
[INFO] Finished at: Mon Dec 07 18:11:10 CET 2009
[INFO] Final Memory: 21M/506M
[INFO] ------------------------------------------------------------------------

Though not 100% complete and functional but in deep progress.
  
> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786991#action_12786991
] 

Toni Menzel commented on ACE-65:
--------------------------------

Current mvn build looks like this
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache ACE - POM .................................. SUCCESS [2.061s]
[INFO] Apache ACE - Util (library) ....................... SUCCESS [2.713s]
[INFO] Apache ACE - Repository ........................... SUCCESS [2.353s]
[INFO] Apache ACE - Repository Impl ...................... SUCCESS [1.528s]
[INFO] Apache ACE - ConsoleLogger ........................ SUCCESS [1.326s]
[INFO] Apache ACE - Log .................................. SUCCESS [1.948s]
[INFO] Apache ACE - Discovery API ........................ SUCCESS [1.123s]
[INFO] Apache ACE - Discovery Property based ............. SUCCESS [1.649s]
[INFO] Apache ACE - Identification Property .............. SUCCESS [1.080s]
[INFO] Apache ACE - Identification API ................... SUCCESS [2.219s]
[INFO] Apache ACE - Scheduler API ........................ SUCCESS [0.831s]
[INFO] Apache ACE - Deployment Provider API .............. SUCCESS [0.847s]
[INFO] Apache ACE - Client Repository (library) .......... SUCCESS [2.226s]
[INFO] Apache ACE - Deployment Streamgenerator ........... SUCCESS [0.851s]
[INFO] Apache ACE - Deployment Servlet ................... SUCCESS [1.065s]
[INFO] Apache ACE - Deployment Provider Base (library) ... SUCCESS [0.931s]
[INFO] Apache ACE - Deployment Provider Filebased ........ SUCCESS [1.087s]
[INFO] Apache ACE - Deployment Provider Repositorybased .. SUCCESS [1.586s]
[INFO] Apache ACE - HttpListener ......................... SUCCESS [1.231s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31.057s
[INFO] Finished at: Mon Dec 07 18:11:10 CET 2009
[INFO] Final Memory: 21M/506M
[INFO] ------------------------------------------------------------------------

Though not 100% complete and functional but in deep progress.

> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Create Pax Runner Profiles for targets
--------------------------------------

                 Key: ACE-67
                 URL: https://issues.apache.org/jira/browse/ACE-67
             Project: Ace
          Issue Type: Sub-task
            Reporter: Toni Menzel


the old "development" targets can now be standard pax runner profile. So that you could start
a gateway like pax-runner.sh --profles="org.apache.ace.gateway"
Confiiguration needs to be done by:
- either a new bundle that creates the necessary configuration structure on disk
- other

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Create deployment assemblies that resemble current targets
----------------------------------------------------------

                 Key: ACE-66
                 URL: https://issues.apache.org/jira/browse/ACE-66
             Project: Ace
          Issue Type: Sub-task
            Reporter: Toni Menzel


we'll need extra assembly project (using maven-assembly-plugin) to create fixed deployment
outputs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Copy all resources into maven artifacts
---------------------------------------

                 Key: ACE-65
                 URL: https://issues.apache.org/jira/browse/ACE-65
             Project: Ace
          Issue Type: Sub-task
            Reporter: Toni Menzel


A a result, we need to get all relevant bundles for currently used targets from the maven
build.
So this involves splitting core/gateway/server resources into pretty small artifacts. By default
they are all bundles (maven-bundle-plugin), with the exception of commonly used libraries
(embedded into different bundles)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/ACE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toni Menzel reassigned ACE-65:
------------------------------

    Assignee: Toni Menzel

> Copy all resources into maven artifacts
> ---------------------------------------
>
>                 Key: ACE-65
>                 URL: https://issues.apache.org/jira/browse/ACE-65
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Toni Menzel
>            Assignee: Toni Menzel
>
> A a result, we need to get all relevant bundles for currently used targets from the maven
build.
> So this involves splitting core/gateway/server resources into pretty small artifacts.
By default they are all bundles (maven-bundle-plugin), with the exception of commonly used
libraries (embedded into different bundles)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

On Dec 7, 2009, at 10:52 , Jean-Baptiste Onofré wrote:

> Agreed, for now, we can disable unit tests to focus on the build itself. The tests/itests
scope could come later.

Order wise, I agree that we should first get the build going up to the point where we can
produce the right artifacts and group them into "runnable targets".

Next step then is to port the tests.

Greetings, Marcel

Agreed, for now, we can disable unit tests to focus on the build itself. 
The tests/itests scope could come later.

Regards
JB

Toni Menzel wrote:
> its pretty unrelated to the ACE-62 work, but having failing builds does not
> sound good - so we should disable them.
> 
> On Mon, Dec 7, 2009 at 10:40 AM, Marcel Offermans <
> marcel.offermans@luminis.nl> wrote:
> 
>> Technically, yes, we can mark such tests with an annotation to indicate
>> they're broken. That will exclude them from being run.
>>
>> For now I'm fine with doing that, so if that helps you with the
>> mavenization, feel free to do so. It's documented here (right at the
>> bottom):
>>
>> http://incubator.apache.org/ace/testing.html
>>
>> Greetings, Marcel
>>
>>
>> On Dec 7, 2009, at 10:26 , Toni Menzel wrote:
>>
>>> can we disable this build / or disable the test then ? Just to get the
>> good
>>> green back.
>>>
>>> On Sun, Dec 6, 2009 at 11:22 PM, Marcel Offermans <
>>> marcel.offermans@luminis.nl> wrote:
>>>
>>>> To clarify, there are indeed a couple of integration tests that fail on
>>>> this Bamboo server. On my local machine, I have not yet been able to
>> make
>>>> them fail, nor have they failed in the past. This probably means there
>> are a
>>>> few race conditions in there somewhere.
>>>>
>>>> Greetings, Marcel
>>>>
>>>>
>>>> On Dec 6, 2009, at 23:00 , Toni Menzel wrote:
>>>>
>>>>> Test failures in ant build (default) are somewhat "not reproducable "
?
>>>>> http://opensource.bamboo.atlassian.com/browse/ACE-DEF
>>>>>
>>>>> On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
>>>>> marcel.offermans@luminis.nl> wrote:
>>>>>
>>>>>> I just had the same thought, and added the build to the existing
>> Bamboo
>>>>>> build (that was donated by Atlassian and is used by different (Apache)
>>>>>> projects). That way we have both the Ant and Maven builds in the
same
>>>>>> location. See ACE-64 for progress.
>>>>>>
>>>>>> Greetings, Marcel
>>>>>>
>>>>>> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
>>>>>>
>>>>>>> Thanks Marcel,
>>>>>>>
>>>>>>> I have a question concerning continuous integration.
>>>>>>>
>>>>>>> I propose to create a continuous integration chain. At Apache
we can
>>>> use
>>>>>> Continuum (that I currently use for AutoDeploy
>>>>>> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
>>>>>>> What do you think ?
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> 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.
>>
> 
> 

On Dec 7, 2009, at 10:48 , Toni Menzel wrote:

> its pretty unrelated to the ACE-62 work, but having failing builds does not
> sound good - so we should disable them.


I agree that we should not have failing builds. Disabling the tests is a bit like tricking
ourselves though. But since we have not hunted down these issues yet, we can disable them
and make sure we have an issue in JIRA to remind ourselves.

Greetings, Marcel

its pretty unrelated to the ACE-62 work, but having failing builds does not
sound good - so we should disable them.

On Mon, Dec 7, 2009 at 10:40 AM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:

> Technically, yes, we can mark such tests with an annotation to indicate
> they're broken. That will exclude them from being run.
>
> For now I'm fine with doing that, so if that helps you with the
> mavenization, feel free to do so. It's documented here (right at the
> bottom):
>
> http://incubator.apache.org/ace/testing.html
>
> Greetings, Marcel
>
>
> On Dec 7, 2009, at 10:26 , Toni Menzel wrote:
>
> > can we disable this build / or disable the test then ? Just to get the
> good
> > green back.
> >
> > On Sun, Dec 6, 2009 at 11:22 PM, Marcel Offermans <
> > marcel.offermans@luminis.nl> wrote:
> >
> >> To clarify, there are indeed a couple of integration tests that fail on
> >> this Bamboo server. On my local machine, I have not yet been able to
> make
> >> them fail, nor have they failed in the past. This probably means there
> are a
> >> few race conditions in there somewhere.
> >>
> >> Greetings, Marcel
> >>
> >>
> >> On Dec 6, 2009, at 23:00 , Toni Menzel wrote:
> >>
> >>> Test failures in ant build (default) are somewhat "not reproducable " ?
> >>> http://opensource.bamboo.atlassian.com/browse/ACE-DEF
> >>>
> >>> On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
> >>> marcel.offermans@luminis.nl> wrote:
> >>>
> >>>> I just had the same thought, and added the build to the existing
> Bamboo
> >>>> build (that was donated by Atlassian and is used by different (Apache)
> >>>> projects). That way we have both the Ant and Maven builds in the same
> >>>> location. See ACE-64 for progress.
> >>>>
> >>>> Greetings, Marcel
> >>>>
> >>>> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
> >>>>
> >>>>> Thanks Marcel,
> >>>>>
> >>>>> I have a question concerning continuous integration.
> >>>>>
> >>>>> I propose to create a continuous integration chain. At Apache we
can
> >> use
> >>>> Continuum (that I currently use for AutoDeploy
> >>>> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
> >>>>>
> >>>>> What do you think ?
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> 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.
>
>


-- 
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.

Technically, yes, we can mark such tests with an annotation to indicate they're broken. That
will exclude them from being run.

For now I'm fine with doing that, so if that helps you with the mavenization, feel free to
do so. It's documented here (right at the bottom):

http://incubator.apache.org/ace/testing.html

Greetings, Marcel


On Dec 7, 2009, at 10:26 , Toni Menzel wrote:

> can we disable this build / or disable the test then ? Just to get the good
> green back.
> 
> On Sun, Dec 6, 2009 at 11:22 PM, Marcel Offermans <
> marcel.offermans@luminis.nl> wrote:
> 
>> To clarify, there are indeed a couple of integration tests that fail on
>> this Bamboo server. On my local machine, I have not yet been able to make
>> them fail, nor have they failed in the past. This probably means there are a
>> few race conditions in there somewhere.
>> 
>> Greetings, Marcel
>> 
>> 
>> On Dec 6, 2009, at 23:00 , Toni Menzel wrote:
>> 
>>> Test failures in ant build (default) are somewhat "not reproducable " ?
>>> http://opensource.bamboo.atlassian.com/browse/ACE-DEF
>>> 
>>> On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
>>> marcel.offermans@luminis.nl> wrote:
>>> 
>>>> I just had the same thought, and added the build to the existing Bamboo
>>>> build (that was donated by Atlassian and is used by different (Apache)
>>>> projects). That way we have both the Ant and Maven builds in the same
>>>> location. See ACE-64 for progress.
>>>> 
>>>> Greetings, Marcel
>>>> 
>>>> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
>>>> 
>>>>> Thanks Marcel,
>>>>> 
>>>>> I have a question concerning continuous integration.
>>>>> 
>>>>> I propose to create a continuous integration chain. At Apache we can
>> use
>>>> Continuum (that I currently use for AutoDeploy
>>>> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
>>>>> 
>>>>> What do you think ?
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> 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.

Hello Toni,

On Dec 7, 2009, at 10:25 , Toni Menzel wrote:

> maybe i am missing something, but how do i unit test Services that have
> dependencies which are injected (usually) by the DependencyManager ?
> Is there anything else than injecting those mocks via manual reflection ?

We have a utility class (called TestUtils) that has various methods to inject instances. It
allows you to inject an arbitrary instance, a null object or even an adapter that allows you
to "partially" implement any instance (and have the rest of the methods handled like a null
object).

> On the other hand, usually the approach is to support constructor injection
> instead of field injection. Any thought in this direction at
> DependencyManager ?

Constructor injection is a static injection, so it is currently not explicitly supported (most
instances will have their members injected at runtime, not just once when constructed). Then
again, there is nothing preventing you from adding a constructor with parameters either. With
the utilities above, I don't think it's really necessary though.

> Even if not, i would propose giving those services a catch-all constructor
> which can be used in out of container scenarios (testing).
> (would be great if dependencymanager could live with that alone).

What exactly do you mean by a "catch-all constructor"?

Greetings, Marcel

can we disable this build / or disable the test then ? Just to get the good
green back.

On Sun, Dec 6, 2009 at 11:22 PM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:

> To clarify, there are indeed a couple of integration tests that fail on
> this Bamboo server. On my local machine, I have not yet been able to make
> them fail, nor have they failed in the past. This probably means there are a
> few race conditions in there somewhere.
>
> Greetings, Marcel
>
>
> On Dec 6, 2009, at 23:00 , Toni Menzel wrote:
>
> > Test failures in ant build (default) are somewhat "not reproducable " ?
> > http://opensource.bamboo.atlassian.com/browse/ACE-DEF
> >
> > On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
> > marcel.offermans@luminis.nl> wrote:
> >
> >> I just had the same thought, and added the build to the existing Bamboo
> >> build (that was donated by Atlassian and is used by different (Apache)
> >> projects). That way we have both the Ant and Maven builds in the same
> >> location. See ACE-64 for progress.
> >>
> >> Greetings, Marcel
> >>
> >> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
> >>
> >>> Thanks Marcel,
> >>>
> >>> I have a question concerning continuous integration.
> >>>
> >>> I propose to create a continuous integration chain. At Apache we can
> use
> >> Continuum (that I currently use for AutoDeploy
> >> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
> >>>
> >>> What do you think ?
> >>
> >>
> >>
> >
> >
> > --
> > 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.

Hi,

maybe i am missing something, but how do i unit test Services that have
dependencies which are injected (usually) by the DependencyManager ?
Is there anything else than injecting those mocks via manual reflection ?

On the other hand, usually the approach is to support constructor injection
instead of field injection. Any thought in this direction at
DependencyManager ?
Even if not, i would propose giving those services a catch-all constructor
which can be used in out of container scenarios (testing).
(would be great if dependencymanager could live with that alone).

Toni

-- 
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.

Hi guys,

Sorry I'm coming late on this, had a network emergency locally.

I agree that the github repo should be disregarded moving out.  We  
didn't do anything with it and changes are hard.

I might differ that we should be working on a branch, unless all  
committers are prepared to do a clean checkout and build until we are  
done.  Leftover artifacts in source and build directories can be  
troublesome, and it may be easier to not take chances with the Ant  
build as we get things moved around for Maven.

I'm okay in any event, just wanted to add $0.02...

Cheers, Brian

On Dec 6, 2009, at 3:10 PM, Jean-Baptiste Onofré wrote:

> Hi Toni,
>
> Totally agree to work directly on the asf repo and we should  
> consider the github repo as deprecated.
>
> I propose:
> 1/ to commit the ace-pom containing all informations shared between  
> ace sub-projects and branches
> 2/ begin to create sub-projects per module. For example, I think  
> that the current ace current is too large. We should consider to  
> split into several maven sub-project (modularize).
>
> Regards
> JB
>
> Toni Menzel wrote:
>> Hi,
>> Because
>> - Brian, Jean-Babtiste, and me are now full committers
>> - Changes on github fork are small, i would go for keeping the  
>> mavenization
>> work at the apache repo and commit stuff right away in either:
>> a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
>> b.) directly in trunk, but keeping the current structure alive in  
>> parallel.
>> (doable because changes are either new (poms, folders) or copies
>> (resources/sources).
>> c.) history is preserved and no git/svn bridging work is required  
>> when
>> merging back.
>> whats the way to go for ? Would then try to keep this in sync (for  
>> everyone
>> to collaborate) and done as soon as possible.
>> wdyt ?
>> Toni
>
> -- 
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
>

To clarify, there are indeed a couple of integration tests that fail on this Bamboo server.
On my local machine, I have not yet been able to make them fail, nor have they failed in the
past. This probably means there are a few race conditions in there somewhere.

Greetings, Marcel


On Dec 6, 2009, at 23:00 , Toni Menzel wrote:

> Test failures in ant build (default) are somewhat "not reproducable " ?
> http://opensource.bamboo.atlassian.com/browse/ACE-DEF
> 
> On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
> marcel.offermans@luminis.nl> wrote:
> 
>> I just had the same thought, and added the build to the existing Bamboo
>> build (that was donated by Atlassian and is used by different (Apache)
>> projects). That way we have both the Ant and Maven builds in the same
>> location. See ACE-64 for progress.
>> 
>> Greetings, Marcel
>> 
>> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
>> 
>>> Thanks Marcel,
>>> 
>>> I have a question concerning continuous integration.
>>> 
>>> I propose to create a continuous integration chain. At Apache we can use
>> Continuum (that I currently use for AutoDeploy
>> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
>>> 
>>> What do you think ?
>> 
>> 
>> 
> 
> 
> -- 
> 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.

    [ https://issues.apache.org/jira/browse/ACE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786718#action_12786718
] 

Toni Menzel commented on ACE-62:
--------------------------------

svn.apache.org/repos/asf/incubator/ace/trunk contains now the first maven artifacts. Marcel
wired it already with the CI build (http://opensource.bamboo.atlassian.com/browse/ACE-CORE).

Will continue tomorrow - just wanted to get things started, today.
Feel free to continue, comment, complain .. ;)
Toni

> Convert Ace build to Maven
> --------------------------
>
>                 Key: ACE-62
>                 URL: https://issues.apache.org/jira/browse/ACE-62
>             Project: Ace
>          Issue Type: Task
>            Reporter: Brian Topping
>            Assignee: Toni Menzel
>
> Some discussion has occurred after ACUS about converting the ACE build to Maven.  This
has some unique challenges, mostly regarding build speed.  The build is currently a highly-optimized
set of Ant tasks, which is not necessarily compatible speed-wise with a set of naturally decomposed
Maven POMs.  
> Three people have expressed interest in working on this: Toni Menzel, Jean-Baptiste Onofré,
and Brian Topping.  Toni suggested that we start a Github project so the three of us (currently
not committers) could start work on this immediately, which is a great idea.  So if http://github.com/topping/Apache-Ace-Mavenization
doesn't work, let's use something better suited somewhere else!
> Shall we focus the discussion here?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Test failures in ant build (default) are somewhat "not reproducable " ?
http://opensource.bamboo.atlassian.com/browse/ACE-DEF

On Sun, Dec 6, 2009 at 9:35 PM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:

> I just had the same thought, and added the build to the existing Bamboo
> build (that was donated by Atlassian and is used by different (Apache)
> projects). That way we have both the Ant and Maven builds in the same
> location. See ACE-64 for progress.
>
> Greetings, Marcel
>
> On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:
>
> > Thanks Marcel,
> >
> > I have a question concerning continuous integration.
> >
> > I propose to create a continuous integration chain. At Apache we can use
> Continuum (that I currently use for AutoDeploy
> http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
> >
> > What do you think ?
>
>
>


-- 
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.

I just had the same thought, and added the build to the existing Bamboo build (that was donated
by Atlassian and is used by different (Apache) projects). That way we have both the Ant and
Maven builds in the same location. See ACE-64 for progress.

Greetings, Marcel

On Dec 6, 2009, at 21:12 , Jean-Baptiste Onofré wrote:

> Thanks Marcel,
> 
> I have a question concerning continuous integration.
> 
> I propose to create a continuous integration chain. At Apache we can use Continuum (that
I currently use for AutoDeploy http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).
> 
> What do you think ?

    [ https://issues.apache.org/jira/browse/ACE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786691#action_12786691
] 

Marcel Offermans commented on ACE-64:
-------------------------------------

Setup an ACE-CORE build that reports to the ace-commits mailing list. It now runs mvn clean
install on Java 6, using Maven 2.2.1.

> Create a Bamboo continuous build for the new Maven build.
> ---------------------------------------------------------
>
>                 Key: ACE-64
>                 URL: https://issues.apache.org/jira/browse/ACE-64
>             Project: Ace
>          Issue Type: New Feature
>          Components: Maven Build
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Now that we're converting the build to Maven, it makes sense to add a continuous build
next to the existing one to validate this build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

It sounds good Toni.

I committed a short ACE POM on the github, but not yet time to commit 
the complete one.

I will be able to commit tomorrow morning.

Regards
JB

Toni Menzel wrote:
> okay, then i will add the master pom to trunk (directly). And start adding
> (new) sub folders that represent the new maven artifacts (like
> "ace-identification-property" and alike).
> 
> So in the end, we will (hopefully) have functional identical components. -
> easy to compare.
> 
> 
> 
> On Sun, Dec 6, 2009 at 8:39 PM, Marcel Offermans <
> marcel.offermans@luminis.nl> wrote:
> 
>> On Dec 6, 2009, at 19:59 , Toni Menzel wrote:
>>
>>> Because
>>> - Brian, Jean-Babtiste, and me are now full committers
>>> - Changes on github fork are small, i would go for keeping the
>> mavenization
>>> work at the apache repo and commit stuff right away in either:
>>> a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
>>> b.) directly in trunk, but keeping the current structure alive in
>> parallel.
>>> (doable because changes are either new (poms, folders) or copies
>>> (resources/sources).
>>> c.) history is preserved and no git/svn bridging work is required when
>>> merging back.
>>>
>>> whats the way to go for ? Would then try to keep this in sync (for
>> everyone
>>> to collaborate) and done as soon as possible.
>> Whatever variation we choose, I think it would be good if we can quickly
>> compare the Ant and Maven builds until we're sure that everything works.
>>
>> I think we can create a new folder in trunk (option b) and start copying
>> things over.
>>
>> Also, no doubt we'll run into issues when doing the conversion, so I've
>> added a "Maven Build" component to JIRA, so we can easily keep track of
>> them.
>>
>> Greetings, Marcel
>>
>>
> 
> 

-- 
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086

Thanks Marcel,

I have a question concerning continuous integration.

I propose to create a continuous integration chain. At Apache we can use 
Continuum (that I currently use for AutoDeploy 
http://continuum.nanthrax.net) or Hudson (that we use on ServiceMix).

What do you think ?

Regards
JB

Marcel Offermans wrote:
> On Dec 6, 2009, at 19:59 , Toni Menzel wrote:
> 
>> Because
>> - Brian, Jean-Babtiste, and me are now full committers
>> - Changes on github fork are small, i would go for keeping the mavenization
>> work at the apache repo and commit stuff right away in either:
>> a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
>> b.) directly in trunk, but keeping the current structure alive in parallel.
>> (doable because changes are either new (poms, folders) or copies
>> (resources/sources).
>> c.) history is preserved and no git/svn bridging work is required when
>> merging back.
>>
>> whats the way to go for ? Would then try to keep this in sync (for everyone
>> to collaborate) and done as soon as possible.
> 
> Whatever variation we choose, I think it would be good if we can quickly compare the
Ant and Maven builds until we're sure that everything works.
> 
> I think we can create a new folder in trunk (option b) and start copying things over.
> 
> Also, no doubt we'll run into issues when doing the conversion, so I've added a "Maven
Build" component to JIRA, so we can easily keep track of them.
> 
> Greetings, Marcel
> 

-- 
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086

Hi Toni,

Totally agree to work directly on the asf repo and we should consider 
the github repo as deprecated.

I propose:
1/ to commit the ace-pom containing all informations shared between ace 
sub-projects and branches
2/ begin to create sub-projects per module. For example, I think that 
the current ace current is too large. We should consider to split into 
several maven sub-project (modularize).

Regards
JB

Toni Menzel wrote:
> Hi,
> Because
> - Brian, Jean-Babtiste, and me are now full committers
> - Changes on github fork are small, i would go for keeping the mavenization
> work at the apache repo and commit stuff right away in either:
> a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
> b.) directly in trunk, but keeping the current structure alive in parallel.
> (doable because changes are either new (poms, folders) or copies
> (resources/sources).
> c.) history is preserved and no git/svn bridging work is required when
> merging back.
> 
> whats the way to go for ? Would then try to keep this in sync (for everyone
> to collaborate) and done as soon as possible.
> 
> wdyt ?
> Toni
> 

-- 
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086

Create a Bamboo continuous build for the new Maven build.
---------------------------------------------------------

                 Key: ACE-64
                 URL: https://issues.apache.org/jira/browse/ACE-64
             Project: Ace
          Issue Type: New Feature
          Components: Maven Build
            Reporter: Marcel Offermans
            Assignee: Marcel Offermans


Now that we're converting the build to Maven, it makes sense to add a continuous build next
to the existing one to validate this build.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hello Toni,

On Dec 6, 2009, at 20:46 , Toni Menzel wrote:

> okay, then i will add the master pom to trunk (directly). And start adding
> (new) sub folders that represent the new maven artifacts (like
> "ace-identification-property" and alike).

Sounds good!

> So in the end, we will (hopefully) have functional identical components. -
> easy to compare.

Yes, for starters, let's try to keep the components identical. If we identify any issues with
the componentization, we can try to solve those in a second pass. Same probably goes for the
refactoring we have to do because we agreed on new terminology.

Greetings, Marcel

okay, then i will add the master pom to trunk (directly). And start adding
(new) sub folders that represent the new maven artifacts (like
"ace-identification-property" and alike).

So in the end, we will (hopefully) have functional identical components. -
easy to compare.



On Sun, Dec 6, 2009 at 8:39 PM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:

> On Dec 6, 2009, at 19:59 , Toni Menzel wrote:
>
> > Because
> > - Brian, Jean-Babtiste, and me are now full committers
> > - Changes on github fork are small, i would go for keeping the
> mavenization
> > work at the apache repo and commit stuff right away in either:
> > a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
> > b.) directly in trunk, but keeping the current structure alive in
> parallel.
> > (doable because changes are either new (poms, folders) or copies
> > (resources/sources).
> > c.) history is preserved and no git/svn bridging work is required when
> > merging back.
> >
> > whats the way to go for ? Would then try to keep this in sync (for
> everyone
> > to collaborate) and done as soon as possible.
>
> Whatever variation we choose, I think it would be good if we can quickly
> compare the Ant and Maven builds until we're sure that everything works.
>
> I think we can create a new folder in trunk (option b) and start copying
> things over.
>
> Also, no doubt we'll run into issues when doing the conversion, so I've
> added a "Maven Build" component to JIRA, so we can easily keep track of
> them.
>
> 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.

On Dec 6, 2009, at 19:59 , Toni Menzel wrote:

> Because
> - Brian, Jean-Babtiste, and me are now full committers
> - Changes on github fork are small, i would go for keeping the mavenization
> work at the apache repo and commit stuff right away in either:
> a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
> b.) directly in trunk, but keeping the current structure alive in parallel.
> (doable because changes are either new (poms, folders) or copies
> (resources/sources).
> c.) history is preserved and no git/svn bridging work is required when
> merging back.
> 
> whats the way to go for ? Would then try to keep this in sync (for everyone
> to collaborate) and done as soon as possible.

Whatever variation we choose, I think it would be good if we can quickly compare the Ant and
Maven builds until we're sure that everything works.

I think we can create a new folder in trunk (option b) and start copying things over.

Also, no doubt we'll run into issues when doing the conversion, so I've added a "Maven Build"
component to JIRA, so we can easily keep track of them.

Greetings, Marcel

Hi,
Because
- Brian, Jean-Babtiste, and me are now full committers
- Changes on github fork are small, i would go for keeping the mavenization
work at the apache repo and commit stuff right away in either:
a.) a branch svn.apache.org/repos/asf/incubator/ace/[ant2maven]
b.) directly in trunk, but keeping the current structure alive in parallel.
(doable because changes are either new (poms, folders) or copies
(resources/sources).
c.) history is preserved and no git/svn bridging work is required when
merging back.

whats the way to go for ? Would then try to keep this in sync (for everyone
to collaborate) and done as soon as possible.

wdyt ?
Toni

-- 
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.

Thanks all for the warm welcome ;)
@Angelo: i think you know what you are talking about. Feels a bit strange
walking through your own patches in order to integrate them.

Now to my favorite topic: me. ;)
27years old, living and working in Hannover, Germany as a freelance
consultant in the Java/OSGi space.
Lived my OSS life so far in the OPS4J community (so with Apache it's like
joining the devil..;)
Mostly - any tribute to Alin Dreghiciu here - spent time and effort on Pax
projects that should be pretty well known in the OSGi world.

As of Apache ACE, i think it can become the solution to true OSGi
provisioning.
Practically i see short term work in integrating it into the Pax Exam test
container scenario, where you can "deploy" your tests to the cloud and
gather results. All using ACE as infrastructure. And Pax Exam in the ACE
Client role.

Anyhow, there's a lot more, hope we discuss and see some of those in the
future on this list.

Have fun.
Toni

On Thu, Dec 3, 2009 at 12:29 PM, Angelo vd Sijpt <angelovds@gmail.com>wrote:

> Toni, welcome! Now you can start working through your own patches :)
>
> Angelo
>
>
> On Thu, Dec 3, 2009 at 12:24 PM, Bertrand Delacretaz <
> bdelacretaz@apache.org
> > wrote:
>
> > On Thu, Dec 3, 2009 at 12:03 PM, Marcel Offermans
> > <marcel.offermans@luminis.nl> wrote:
> > > ...Welcome to the team, and thanks for all past and future
> > contributions!...
> >
> > Welcome Toni!
> >
> > I'd love to hear some words of introduction (or a link) from you here
> > it you don't mind ;-)
> >
> > -Bertrand
> >
>



-- 
Toni Menzel
Independent Software Developer
Professional Profile: http://tonimenzel.com
toni@okidokiteam.com
http://www.ops4j.org     - New Energy for OSS Communities - Open
Participation Software.

Excellent ! Welcome guys and have fun !

Regards
Felix

Marcel Offermans schrieb:
> Hi all,
> 
> Today surely is a great day for the ACE community, as I have the privilege to welcome
two new committers to the Apache ACE project: Brian Topping and Jean-Baptiste Onofré. Your
accounts should have received the right karma for Subversion, Jira and Confluence (thanks
for lending a hand Carsten). 
> 
> I will let Brian and Jean-Baptiste introduce themselves. Welcome to the team, and thanks
for your contributions!
> 
> Greetings, Marcel
> 
>