Ok, I'm finally in. My desktop machine was down all week due to the
inclusion of a RAID card and an attempt at converting the boot drive
to a RAID 0 backed by solid state disks. I had to abort, a certain
vendor of SSDs (who will remain nameless for the time being) isn't
spec compliant to SATA. It was kind of a major timesink!
I was surprised to find that the build actually builds. Nice work!
My plan is to just start at the bottom of the dependency tree and work
upwards with cleaning up the bundle plugin calls. That will renew my
experience there and get some of that work out of the way.
As a pattern, I see that you've put an osgi.bnd in every build. My
past experience was to avoid this file and have the bundle plugin work
from scratch. It can be more work that way, but I liked that the
manifest instructions were completely contained in the POM. Any
thoughts there?
Cheers, Brian
On Dec 9, 2009, at 1:57 PM, Toni Menzel wrote:
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 [email protected]
have fun,
Toni
On Wed, Dec 9, 2009 at 7:41 PM, Brian Topping <[email protected]>
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
[email protected]
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
