Re: [VOTE] geronimo-jpa_2.0_spec first early access release
+1 Jacek On Wed, Jan 28, 2009 at 11:25 PM, David Jencks wrote: > I've been working with the OpenJPA project to develop the jpa 2.0 spec jar > in our spec repository. They are ready for their first early access > milestone release. > > I've staged the release here: > > http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ > > The svn location is here: > https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 > > I haven't staged the site. I don't think its necessary for a early access > release, but will reconsider on request. > > I ran rat on the project, and the autochecking thinks the legal files are > ok. > > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > thanks > david jencks > > -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
[jira] Resolved: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4518. --- Resolution: Fixed Committed a fix to trunk (revision 738734) and branches/2.1 (revision 738735) that sets the 'java.rmi.server.hostname' property in RMIRegistryService GBean. As I mentioned before this should make things work if ServerHostname is set to 127.0.0.1 or any other address. If ServerHostname is set to 0.0.0.0 the machine network configuration needs to be set correctly to return the right (public) ip address. > Can't shutdown the server when host was set to 127.0.0.1 in > config-substitutions.properties > --- > > Key: GERONIMO-4518 > URL: https://issues.apache.org/jira/browse/GERONIMO-4518 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.1.4, 2.2 > Environment: Windows XP + Sun JDK 1.5 >Reporter: Shawn Jiang >Assignee: Jarek Gawor > Fix For: 2.1.4, 2.2 > > Attachments: G4518_Shawn.patch > > > 1, change the host in config-substitutions.properties to 127.0.0.1 > 2, start the server. > 3, shutdown the server. > *expected result*: the server could be shutdown. > *actual result*: the sever can't be shutdown with exception: > java.net.ConnectException: Connection refused: connect > -- > C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1 > Using GERONIMO_HOME: C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT > Using GERONIMO_TMPDIR: var\temp > Using JRE_HOME:D:\dev\JDKs\sun_jdk1.5.0_15\jre > log4j:WARN No appenders could be found for logger > (org.apache.geronimo.kernel.basic.BasicKernel). > log4j:WARN Please initialize the log4j system properly. > Username: system > Password: *** > Locating server on 127.0.0.1:1099... > Could not communicate with the server. The server may not be running or the > port number may be inco > rrect (Connection refused to host: 6.153.277.58; nested exception is: > java.net.ConnectException: Connection refused: connect) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668308#action_12668308 ] Jarek Gawor commented on GERONIMO-4518: --- I looked at this a bit more and here's what I think is going on. The client connects to the address returned by InetAddress.getLocalHost() of the remote server. The address returned by InetAddress.getLocalHost() is really based on the machine's network configuration. The network configuration should be set properly to return the appropriate address (the public ip address or the local loopback address that matches the ServerHostname substitution property). It's the RMI code somewhere that calls InetAddress.getLocalHost() by default. However, we can force the RMI code to use a specific hostname by setting the "java.rmi.server.hostname" system property. We can set that system property to the ServerHostname substitution property. This should make things work better if ServerHostname is set to something else then 0.0.0.0. But if ServerHostname is set to 0.0.0.0 (which is set by default) machine's network configuration must still be set correctly so that InetAddress.getLocalHost() returns the right ip address. > Can't shutdown the server when host was set to 127.0.0.1 in > config-substitutions.properties > --- > > Key: GERONIMO-4518 > URL: https://issues.apache.org/jira/browse/GERONIMO-4518 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.1.4, 2.2 > Environment: Windows XP + Sun JDK 1.5 >Reporter: Shawn Jiang >Assignee: Jarek Gawor > Fix For: 2.1.4, 2.2 > > Attachments: G4518_Shawn.patch > > > 1, change the host in config-substitutions.properties to 127.0.0.1 > 2, start the server. > 3, shutdown the server. > *expected result*: the server could be shutdown. > *actual result*: the sever can't be shutdown with exception: > java.net.ConnectException: Connection refused: connect > -- > C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1 > Using GERONIMO_HOME: C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT > Using GERONIMO_TMPDIR: var\temp > Using JRE_HOME:D:\dev\JDKs\sun_jdk1.5.0_15\jre > log4j:WARN No appenders could be found for logger > (org.apache.geronimo.kernel.basic.BasicKernel). > log4j:WARN Please initialize the log4j system properly. > Username: system > Password: *** > Locating server on 127.0.0.1:1099... > Could not communicate with the server. The server may not be running or the > port number may be inco > rrect (Connection refused to host: 6.153.277.58; nested exception is: > java.net.ConnectException: Connection refused: connect) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 738693
Geronimo Revision: 738693 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090128/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090128
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 11 seconds
[INFO] Finished at: Wed Jan 28 21:42:29 EST 2009
[INFO] Final Memory: 633M/955M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090128/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.978
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.710)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.615)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.689)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.702)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:21.458)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:19.584)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:43.186)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.656)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:50.271)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.778)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:29.432)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.552)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:31.594)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.234)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.258)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:04.442)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.666)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.647)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.042) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.703)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4507: Fix Version/s: 2.1.4 > Admin console should honor the priority of user agent's language setting > > > Key: GERONIMO-4507 > URL: https://issues.apache.org/jira/browse/GERONIMO-4507 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3, 2.2 > Environment: All >Reporter: Jack Cai >Assignee: Donald Woods >Priority: Minor > Fix For: 2.1.4, 2.2 > > Attachments: locale-priority.patch, locale-priority_fix.patch, > locale-priority_V21.patch > > > See discussion: > http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa reopened GERONIMO-4507: - > Admin console should honor the priority of user agent's language setting > > > Key: GERONIMO-4507 > URL: https://issues.apache.org/jira/browse/GERONIMO-4507 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3, 2.2 > Environment: All >Reporter: Jack Cai >Assignee: Donald Woods >Priority: Minor > Fix For: 2.1.4, 2.2 > > Attachments: locale-priority.patch, locale-priority_fix.patch, > locale-priority_V21.patch > > > See discussion: > http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4507: Attachment: locale-priority_V21.patch Donald, I ported the patch for 2.1 version. This patch is the almost same as 2.2 version. > Admin console should honor the priority of user agent's language setting > > > Key: GERONIMO-4507 > URL: https://issues.apache.org/jira/browse/GERONIMO-4507 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3, 2.2 > Environment: All >Reporter: Jack Cai >Assignee: Donald Woods >Priority: Minor > Fix For: 2.2 > > Attachments: locale-priority.patch, locale-priority_fix.patch, > locale-priority_V21.patch > > > See discussion: > http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] geronimo-jpa_2.0_spec first early access release
My +1 david jencks On Jan 28, 2009, at 2:25 PM, David Jencks wrote: I've been working with the OpenJPA project to develop the jpa 2.0 spec jar in our spec repository. They are ready for their first early access milestone release. I've staged the release here: http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 I haven't staged the site. I don't think its necessary for a early access release, but will reconsider on request. I ran rat on the project, and the autochecking thinks the legal files are ok. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks
[VOTE] geronimo-jpa_2.0_spec first early access release
I've been working with the OpenJPA project to develop the jpa 2.0 spec jar in our spec repository. They are ready for their first early access milestone release. I've staged the release here: http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 I haven't staged the site. I don't think its necessary for a early access release, but will reconsider on request. I ran rat on the project, and the autochecking thinks the legal files are ok. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks
[jira] Assigned: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-4518: - Assignee: Jarek Gawor (was: Donald Woods) > Can't shutdown the server when host was set to 127.0.0.1 in > config-substitutions.properties > --- > > Key: GERONIMO-4518 > URL: https://issues.apache.org/jira/browse/GERONIMO-4518 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.1.4, 2.2 > Environment: Windows XP + Sun JDK 1.5 >Reporter: Shawn Jiang >Assignee: Jarek Gawor > Fix For: 2.1.4, 2.2 > > Attachments: G4518_Shawn.patch > > > 1, change the host in config-substitutions.properties to 127.0.0.1 > 2, start the server. > 3, shutdown the server. > *expected result*: the server could be shutdown. > *actual result*: the sever can't be shutdown with exception: > java.net.ConnectException: Connection refused: connect > -- > C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1 > Using GERONIMO_HOME: C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT > Using GERONIMO_TMPDIR: var\temp > Using JRE_HOME:D:\dev\JDKs\sun_jdk1.5.0_15\jre > log4j:WARN No appenders could be found for logger > (org.apache.geronimo.kernel.basic.BasicKernel). > log4j:WARN Please initialize the log4j system properly. > Username: system > Password: *** > Locating server on 127.0.0.1:1099... > Could not communicate with the server. The server may not be running or the > port number may be inco > rrect (Connection refused to host: 6.153.277.58; nested exception is: > java.net.ConnectException: Connection refused: connect) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
NullPointerException throws out when starting Geronimo 2.2 snapshot in GEP
NullPointerException throws out when starting Geronimo 2.2 snapshot in GEP
It is in
plugins\activemq\geronimo-activemq\src\main\java\org\apache\geronimo\activemq\BrokerServiceGBeanImpl.java
Line 84: System.setProperty("activemq.geronimo.home.url", new
File(serverInfo.getBaseDirectory()).toURI().toURL().toString());
It seems serverInfo.getBaseDirectory() returns null
Re: OpenJPA trunk is open for business
David, I can work on releasing the artifact if you're time would be better spent on resolving ActiveMQ and TCK problems for our upcoming Geronimo releases. -Donald David Jencks wrote: If you guys are happy with the current state of the 2.0 persistence api jar I'll see about starting a release vote tomorrow. My reading of the spec leads me to think we're supposed to make it very clear anything based on it is early access so I plan to use a version number of 1.0-EA-1. Suggestions welcomed :-) Do you read the spec labeling requirements differently? thanks david jencks On Jan 27, 2009, at 1:42 PM, Michael Dick wrote: Hi all, There are two (AFAIK) outstanding questions regarding the new release. 1. Do we want / need a formal JIRA release for 2.0.0-M1. Jeremy and I created one earlier today, but we'd have to manually reassign each JIRA issue to the new release. Bulk updates overwrite the "fixed in" and "afftects" attributes but we might be able to get by with just a few bulk changes. Pros : * Incoming bugs can be reported against 2.0.0-M1 (and M2, M3 in the future) making it a bit easier for users to see when an issue was fixed or introduced. * Change logs can be generated for specific milestone releases. Cons : * Some overhead populating the release, and general noise in JIRA (we'll need to do the same for M2 etc). At the moment we're leaning towards just having a single 2.0.0 release in JIRA. 2. Trunk currently has a dependency on a SNAPSHOT release of the geronimo persistence APIs. This raises a red flag with the maven release plugin. To resolve the problem we can do the release manually (which is mildly painful) or ask Geronimo to publish a M1 release of the APIs. I'm inclined to get a M1 release from Geronimo. I don't like the idea of releasing source code which compiles against a moving target (SNAPSHOT releases). I'm open to ideas on either item. If no one's bothered either way we'll go with a single 2.0.0 release and try to get an M1 version of the API from Geronimo. Thanks, -mike On Tue, Jan 27, 2009 at 3:26 PM, Jeremy Bauer wrote: OpenJPA committers, An 2.0.0-M1 branch has been created (Thanks, Mike!) for the M1 release. Commits can now resume on trunk. Happy committing, -Jeremy On Mon, Jan 26, 2009 at 2:15 PM, Jeremy Bauer wrote: OpenJPA committers, OpenJPA 2.0 iteration 2 is wrapping up and preparations are beginning for a milestone 1 snapshot release. Please refrain from committing any new code to trunk while the release is being created. Another posting will go out when trunk is available for commits - hopefully soon. Thanks and sorry for the inconvenience, -Jeremy
[BUILD] trunk: Failed for Revision: 738475
Geronimo Revision: 738475 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090128/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090128/unit-test-reports [INFO] [INFO] Building Geronimo Plugins, CXF :: CXF [INFO]task-segment: [install] [INFO] [WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:provided' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception of classes directly in package org.xmlpull.v1 )
Re: [jira] Closed: (GERONIMO-4522) history dependencies.xml file should support property substitutions. Plan processing should use maven filtering, not velocity
On Tue, Jan 27, 2009 at 6:32 PM, David Jencks wrote:
> Hi Trygve,
> Maybe I broke stuff its a bit hard to tell from your description.
> There are two things going on in your build:
>
> 1. car-maven-plugin "car" packaging which for each plugin project builds a
> plugin and puts it in the local maven repo. It's plausible that the changes
> here broke this step.
> 2. car-maven-plugin assembly packaging which assembles a server out of the
> plugins from the maven repo. I don't see how this could have broken but you
> never know...
>
> To clarify the situation... IIUC (1) is actually generating artifacts that
> get into the local maven repo?? Are these artifacts copied into the
> geronimo server repository in (2)? If not, something else must have changed
> so these plugins aren't dependencies of the server assembly project.
>
Thanks for the clarification, it matches my understanding.
>
> back to (1)...
> in each plugin project, there should be a target/fliteredplan/plan.xml file
> that should be your plan with the property substitutions done (but not the
> environment element inserted). Is it there and did the property
> substitution work?
>
The file is not there.
> Furthermore, there should be target/resources/META-INF/plan.xml which
> should be your completed plan file with the dependencies etc included and
> target/resources/META-INF/geronimo-;plugin.xml which should have the
> dependencies and the category. Finally both these files should be in the
> completed car file.
>
The plan.xml file is missing as well, but geronimo-plan.xml is present. The
content of geronimo-plan.xml from the broken setup is identical to that of
geronimo-plan.xml in the working setup.
>
> I'd also like to make two suggestions about your build... is a very bad
> idea to have projects reference into each others directories or into other
> file system locations. I'm not sure why you have a lot of individual db
> pools...
>
The reason we have multiple DB pools is that we (try to...) scale our
application horizontally by using many databases. These databases are
identical to each other, hence the shared plan.xml file.
> - if the db pools are all used in one application, note that you can set
> up as many db pools in one plan as you need, as
> connectiondefinitiony-instance elements.
>
The pools are used by many applications (or many different modules of the
same application). The idea behind making each pool a separate plugin was
that some pools would not be used at some server setups, but in practice
either all or none of them are used. I created a plugingroup for all the
pools but it would be better to use a single plan.xml file with multiple
pool definitions as you suggest.
> - if you actually need separate plugins for each db pool so they can be
> used independently, I strongly advise packing the common plan into a jar
> file as a resource (in its own project) and then using the
> maven-dependency-plugin to unpack it into target/rawplan or similar
> location.
>
Yes that sounds reasonable.
>
> Please let us know what is wrong.
>
I did a couple of quick tests today and it seems to me like the
"planFileName" and "sourceDir" configuration variables are ignored by the
car-maven-plugin. At least I am unable to pick up any other file than
/src/main/plan/plan.xml. Tried both with different directory as well as
filename:
org.apache.geronimo.buildsupport
car-maven-plugin
test-plan.xml
${project.basedir}/src/main/hobo
${connectorDeployer}
${productName}
org.tranql
tranql-connector-mysql-local
rar
This still uses /src/main/plan/plan.xml if present, or ignores plan.xml if
not found on the standard location:
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] No plan found, plugin will have no classloader
>From you recommendations I won't really need to use a custom plan.xml
location any more, but I'm 90% sure this used to work and was broken
sometime between last week and yesterday.
Many thanks for your quick help! Much appreciated.
Trygve
> On Jan 27, 2009, at 6:15 AM, Trygve Hardersen wrote:
>
> Hi
>
> I hit a problem today with our custom Geronimo assembly that I think is
> related to this:
>
> We have many MySQL DB pools, each represented as a Geronimo plugin. The
> plan.xml file for these plugins is very simmilar, so I'm sharing a common
> file between the plugins:
>
> db-plugin/pom.xml -->
>
>
>
> org.apache.geronimo.buildsupport
> car-maven-plugin
> true
>
>
> mysql-pool-plan.xml
> ${project.parent.basedir}/src/main/plan
>
>
>
>
> db-plugin/src/main/plan/mysql-pool-plan.xml -->
>
>
>
> http://geronimo.apache.org/xml/ns/j2ee/connec
