[
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904219#action_12904219
]
Karl Wright commented on CONNECTORS-92:
---------------------------------------
bq. I am still thinking about why this is so hard. Would be nice to have
something like a servlet or filter that initializes everything that you do in
your special runner now.
The issues have to do with these facts:
- Embedded derby is single-process. You cannot run more than one process
against a given database at a given time.
- ACF supports both single-process and multi-process models, but IF you're
going to use single-process, you need to have a main class that starts up all
the threads that would otherwise be different processes. That's what
jetty-runner does, in part.
So, obviously, something like jetty-runner needs to exist if you are going to
use derby. I don't think maven magic will suffice to replace the code that
does that.
Furthermore, I think trying to get maven to do this for us is overkill. I'm
open to suggestions, but I still don't think you need to solve this problem in
order to have ACF be built effectively by maven.
What I think we need to build at the framework level are all the jars and wars
(which it looks like you have pretty well specified), PLUS a start.jar (which I
didn't see anywhere - did I miss it?). Then your example execution will not be
a "jetty instance" per se, but will simply fire off the equivalent of "java
-jar start.jar". I can't believe there isn't a maven plugin for that. This,
of course, must happen at the modules level, because no connectors will be
available at the framework level.
> Move from ant to maven or other build system with decent library management
> ---------------------------------------------------------------------------
>
> Key: CONNECTORS-92
> URL: https://issues.apache.org/jira/browse/CONNECTORS-92
> Project: Apache Connectors Framework
> Issue Type: Wish
> Components: Build
> Reporter: Jettro Coenradie
> Attachments: maven-poms-problem-starting-jetty-and-derby.patch,
> move-to-maven-acf-framework.patch, Screen shot 2010-08-23 at 16.31.07.png
>
>
> I am looking at the current project structure. If we want to make another
> build tool available I think we need to change the directory structure. I
> tried to place a suggestion in an image. Can you please have a look at it. If
> we agree that this is a good way to go, than I will continue to work on a
> patch. Which might be a bit hard with all these changing directories, but
> I'll do my best to at least get an idea whether it would be working.
> So I have three questions:
> - Do you want to move to maven or put maven next to ant?
> - Do you prefer another build mechanism [ant with ivy, gradle, maven3]
> - Do you have an idea about the amount of scripts that need to be changed if
> we change the project structure
> The image of a possible project layout (that is based on the maven standards)
> is attached to the issue
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
