date:20100330

[ 
https://issues.apache.org/jira/browse/GERONIMO-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851737#action_12851737
 ] 

Shawn Jiang commented on GERONIMO-5219:
---

On Mar 29, 2010, at 7:02 PM, Shawn Jiang wrote:

I'd like to work on this.  Is there a JIRA opened for this ?

Not yet.  Feel free to create as many subtasks as you need under this jira:

 http://issues.apache.org/jira/browse/GERONIMO-5080

Maybe a good title for this one would be something like "Java EE Injection 
annotation scanning for 299 beans"

And basically the goal is to give Geronimo a list of 299 bean classes so that 
it can scan them for these annotations:

 @Resource
 @EJB
 @PersistenceContext
 @PersistenceUnit
 @WebServiceRef

The code to do the scanning is there in the naming builders, but the code to 
get a list of bean classes is not there.

Bare in mind this task is way bigger than it appears as we currently have no 
code to really bootstrap OpenWebBeans into Geronimo and kick of any of the work 
it needs to do to actually generate that list of 299 beans.

There's also a requirement which we might want to just ignore initially as it 
might be way too against the Geronimo architecture.  The trick is that new 
beans can be added at startup via the BeanManager events and Geronimo does not 
do *any* annotation scanning at startup, only at deploy which could be in a 
completely different java process.  I think we might just need to turn a blind 
eye to that detail or it might be too hard to get started as essentially it 
might mean have re-architect Geronimo at a very fundamental level.  Getting 
anything running would be a great step forward.

Anyway, get ready for a challenge :)

> Java EE Injection annotation scanning for 299 beans
> ---
>
> Key: GERONIMO-5219
> URL: https://issues.apache.org/jira/browse/GERONIMO-5219
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>

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

[jira] Created: (GERONIMO-5219) Java EE Injection annotation scanning for 299 beans

Java EE Injection annotation scanning for 299 beans
---

 Key: GERONIMO-5219
 URL: https://issues.apache.org/jira/browse/GERONIMO-5219
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
Reporter: Shawn Jiang
Assignee: Shawn Jiang




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

Re: Publish with GEP takes minutes, while deploy takes 10 seconds

2010-03-30 Thread Delos

Hi Boes,

Could you open a JIRA for it? It would be appreciated if you could upload
the two applications as attachments.

2010/3/30 boes 

> Hello Delos,
>
> I created two EAR projects. Both having three WAR's in the EAR. The WAR's
> are created in Eclipse as 'Dynamic Web Project'.
>
> The only difference between the two projects is in the HiThereSlow
> projectthat I changed geronimo-application.xml. I added dependencies to
> some libraries that do exist in the Geronimo repository. The libs are in
> the repository after a fresh installation of
> geronimo-tomcat6-javaee5-2.1.4.
>
> Although I added the depency tags, the libraries are not used by the
> application. Publishing the two projects shows that the project with the
> depencies (HiThereSlow) takes much more time to publish than the one
> without (HiThere). On my old laptop it takes 15 seconds to publish
> HiThereSlow, where HiThere is published in a second. Adding more empty
> WAR's to the HiThereSlow EAR will increase the publishing times almost
> linear with the number of WAR's.
>
> I can't see why the publishing process should do anything with the
> dependencies in geronimo-application.xml. Maybe it does some verification,
> but it should not do so. Deploying HiThereSlow using the Geronimo console
> on the running Geronimo server is going very fast.
>
> Please let me know if this information is of any use. If you have some
> more questions or don't understand my English (I'm Dutch) please let me
> know.
>
>
> Gert-Jan Boesschen Hospers (Boes)
>
>
>
>
>
>
>
> >
> >
> >
> > Hi Boes,
> >
> > I also found with eclipse 3.5+, the deployment seems slower than before.
> > I'm
> > still investigating the root cause.
> >
> > In deployment process, GEP will pass all artifacts(EAR,WAR,JAR) to WTP.
> As
> > I
> > know, WTP will analyze these artifacts, generate many objects,
> > package&extract them. I've ever tried a big EAR and found most time is
> > consumed by WTP.  But I haven't further investigated the process in WTP.
> >
> > If possible, could you provide your app for me to double check the
> > problem?
> >
> > Although we haven't found the root cause, there may be some workaround
> for
> > you
> > 1) To speed up the deployment of JSP,  you can select "No re-deployment
> > when
> > only JSP files are updated" in "Test environment" section of server
> > "Overview" page. You may find the page after double click server instance
>
> > in
> > "Servers" view.
> > 2) Put all lib you will never change as shared library in Geronimo server
>
> > 3) Avoid automatic publishing. If automatic publishing is enabled, any
> > save
> > action on an deployed artifact will trigger publishing. It's inconvenient
>
> > for a big artifact. I suggest you disable it and manually publish it when
>
> > all your changes have been completed. You can select "Never publish
> > automatically" in "Publishing" section of server "Overview" page.
> >
> > Hope it helps!
> >
> > 2010/3/30 boes <[hidden 
> > email]>
>
> >
> >>
> >> Hi,
> >>
> >> I have an Enterprise Application (EAR) that I develop in Eclipse
> >> (galileo-SR1). When I publish my EAR to the started local Geronimo
> >> V2.1.4
> >> server, it takes more then 3 minutes to finish. I use GEP version 2.2.
> >> During the process 1 CPU is constantly running at 100%, so it looks like
>
> >> the
> >> system is very busy. The status bar shows 'Publishing to Apache Geronimo
>
> >> V2.1 at localhost (0%)' and it stays on 0% almost to the end of the
> >> publishing process.
> >>
> >> When I export the application as an .ear file to the file system and
> >> then
> >> deploy the application to the same Geronimo server using the Geronimo
> >> console, I found that writing the EAR to the filesystem takes 2 seconds
> >> to
> >> complete, and the deployment of the EAR to Geronimo takes about 8
> >> seconds.
> >>
> >> My EAR consists of 8 web applications (WAR) and one utility project
> >> (JAR).
> >> Deployment to the production environment also takes less then 10
> >> seconds.
> >> The application itself is extensively used and stable.
> >>
> >> Is there a logical reason why publishing takes much more time then
> >> deployment? Are they two different things that can't be compared?
> >>
> >> I tried to get some more info on what the publishing process is actually
>
> >> doing in those three minutes. In the server settings in Eclipse I set
> >> the
> >> console output to 'Debug', but I did not get any output from GEP. Is
> >> there
> >> an option to make GEP verbose and let it print what it is doing?
> >>
> >> I found that adding dependencies to a project slows down the publishing
> >> process. I started with a new EAR project with one WAR, which had only
> >> one
> >> html page. It takes a second to publish this EAR to Geronimo. Then I
> >> extended the geronimo-application.xml deployment despriptor by adding
> >> some
> >> dependencies to existing libraries in the Geronimo repo

[jira] Created: (GERONIMO-5218) The portlets page in iframe height is limited in debug view, so that some content is not visible when expanding the tree in debug view.

The portlets page in iframe height is limited in debug view, so that some 
content is not visible when expanding the tree in debug view.
---

 Key: GERONIMO-5218
 URL: https://issues.apache.org/jira/browse/GERONIMO-5218
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
Reporter: Shawn Jiang




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

[jira] Created: (GERONIMO-5217) History.back and History.forward is not working correctly after change the console navigation to ajax.

History.back and History.forward is not working correctly after change the 
console navigation to ajax.
--

 Key: GERONIMO-5217
 URL: https://issues.apache.org/jira/browse/GERONIMO-5217
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
Reporter: Shawn Jiang




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

Re: Deploying Aries Blog sample & AriesTrader on Geronimo

2010-03-30 Thread Rex Wang

Great! Thanks

2010/3/30 Jarek Gawor 

> Hi all,
>
> I recently integrated the JTA and JPA pieces from Aries in Geronimo
> and exposed connection factories in OSGi service registry. With these
> changes we now have all the main pieces in place to deploy unmodified
> Aries Blog sample & AriesTrader on Geronimo. Here's how to do it:
>
> 1) Make sure you have the latest trunk build. I used tomcat ee 6
> assembly but things should also work with the jetty assembly.
>
> 2) Deploy the attached aries-datasource connector. It will create the
> data sources & database tables for both samples. To deploy the
> connector do:
>
> ./bin/deploy -u system -p manager deploy
>
> ~/.m2/repository/org/tranql/tranql-connector-derby-embed-xa/1.5/tranql-connector-derby-embed-xa-1.5.rar
> aries-datasource.xml
>
> 3) Build "samples" module in Aries trunk.
>
> To deploy the Blog sample do:
>
> ./bin/deploy -u system -p manager deploy 
> trunk>/samples/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.1-incubating-SNAPSHOT.eba
>
> or to deploy AriesTrader do:
>
> ./bin/deploy -u system -p manager deploy 
> trunk>/samples/ariestrader-sample/assemblies/ariestrader-all-eba/target/org.apache.aries.samples.ariestrader.all-0.1-incubating-SNAPSHOT.eba
>
> If all goes well the Blog sample should be available under
> http://localhost:8080/blog and AriesTrader under
> http://localhost:8080/ariestrader.
>
> Btw, when running the deploy command you might see some "Address
> already in use" exceptions. They can be ignored.
>
> Let me know if you have any problems,
>
> Jarek
>



-- 
Lei Wang (Rex)
rwonly AT apache.org

[jira] Closed: (GERONIMO-4994) To support multiple level navigation tree in geronimo web console.


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

Shawn Jiang closed GERONIMO-4994.
-


Closing it.

> To support multiple level navigation tree in geronimo web console.
> --
>
> Key: GERONIMO-4994
> URL: https://issues.apache.org/jira/browse/GERONIMO-4994
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2.1, 3.0
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
> Fix For: 2.2.1, 3.0
>
> Attachments: demo.swf, G4994.patch
>
>
> We need to re-org the navigation tree to improve the usability.  So that web 
> console needs to support:
> 1, more than 2 level menu.
> 2, easy menu item sequence definition.
> Nice to have:
> 1, ajax like style navigation system, that means the banner and the 
> navigation tree will be separated from the portlets content.   
> 2, a quick launcher box in the top of the navigation section so that the user 
> can quickly launch a function in seconds without finding the function in the 
> tree.

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

[jira] Resolved: (GERONIMO-4933) Some optimization for loaded bundle checking

2010-03-30 Thread Ivan (JIRA)


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

Ivan resolved GERONIMO-4933.


Resolution: Fixed

Commit changes to trunk At revision: 929357.

> Some optimization for loaded bundle checking
> 
>
> Key: GERONIMO-4933
> URL: https://issues.apache.org/jira/browse/GERONIMO-4933
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: kernel, osgi
>Affects Versions: 3.0
>Reporter: Ivan
>Priority: Minor
> Fix For: 3.0
>
> Attachments: GERONIMO-4933.patch
>
>
> The full loop checking whether the bundle is loaded is less efficient. Seems 
> that OSGI will maintaine a location-bundle map inside, if the bundle of the 
> same location is installed, the existing bundle will return immediently.

-- 
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: 929353

Geronimo Revision: 929353 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

[jira] Commented: (GERONIMO-5040) PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows

2010-03-30 Thread Johannes Weberhofer (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851644#action_12851644
 ] 

Johannes Weberhofer commented on GERONIMO-5040:
---

In the meantime commons-daemon-1.0.2 was released fixing DAEMON-112 and several 
other bugs

> PermGenSpace Problems and shut-down issues when using the "Apache Commons 
> Daemon" under Windows
> ---
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Plugins
>Affects Versions: 2.1.4, 2.2
>Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and 
> the currently used exe-Mode) it is necessary to add all important options 
> directly into the "startup"-"arguments" fields before the "-jar" line, which 
> should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode 
> and set a timeout (30 seconds or so); otherwise the geronimo server will 
> simply be killed without any chance to terminate gracefully.

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

[jira] Commented: (GERONIMO-4963) Environment variables settings are invalid on geronimosrv.

2010-03-30 Thread Johannes Weberhofer (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851640#action_12851640
 ] 

Johannes Weberhofer commented on GERONIMO-4963:
---

This issue could be marked as a duplicate of GERONIMO-4537

> Environment variables settings are invalid on geronimosrv.
> --
>
> Key: GERONIMO-4963
> URL: https://issues.apache.org/jira/browse/GERONIMO-4963
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: startup/shutdown
>Affects Versions: 2.1.4
> Environment: Windows
>Reporter: Julia Chang
>
> Geronimo-2.1.4 can run as windows service by using geronimosrv (apache 
> commons deamon).
> But, environment variables settings are invalid on geronimosrv,
> I can set environment variable like that on tomcat.exe
> --Environment key1=value1#key2=value2
> or
> set PR_ENVIRONMENT=key1=value1#key2=value2

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

[jira] Assigned: (GERONIMO-5113) Add naming builder support for processing DataSourceDefinition annotations.


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

Jarek Gawor reassigned GERONIMO-5113:
-

Assignee: Jarek Gawor

> Add naming builder support for processing DataSourceDefinition annotations. 
> 
>
> Key: GERONIMO-5113
> URL: https://issues.apache.org/jira/browse/GERONIMO-5113
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Reporter: Rick McGuire
>Assignee: Jarek Gawor
>


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

[jira] Commented: (GERONIMO-5216) CLONE -getContextRoot() returns forward slash rather than empty string for apps deployed to root context

2010-03-30 Thread Matthias Koch (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851573#action_12851573
 ] 

Matthias Koch commented on GERONIMO-5216:
-

Hi Jay,

yes the problem can be fixed when changing all jstl libs to prevent //
in jakarta taglibs 1.1.2 they will do this, if you enter a context value in the 
tag. but they won't check for // if context value is not defined in tag.
for this i already build have a patch, but this is not the only jstl lib who 
did this way. as for me i also use the spring taglibs which will produce the 
same problem.

the problem is that tomcat only returns a empty string when webapp dir is 
called ROOT
but for geronimo ROOT is not possible 
i have tried to look into the code of tomcat and geronimo to find the place 
where this could be fixed, but i haven't found it yet (first look into those 
source code)

maybe its possible to patch the Request class from tomcat
in method: setContextPath
there is a check if path is null, this can be extended to also check if its 
only / 
but i think this would be a ugly hack.

kr Matthias 

> CLONE -getContextRoot() returns forward slash rather than empty string for 
> apps deployed to root context
> 
>
> Key: GERONIMO-5216
> URL: https://issues.apache.org/jira/browse/GERONIMO-5216
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.2
>Reporter: Matthias Koch
>Assignee: Jay D. McHugh
>
> An app deployed to the root context should have "" returned by 
> getContextRoot() - On Tomcat, we are returning "/".
> dcherk wrote:
> > I am deploying my war file into the root context with the following
> > deployment plan:
> > --
> > http://geronimo.apache.org/xml/ns/j2ee/web-2.0";
> > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";
> > xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2";
> > xmlns:security="http://geronimo.apache.org/xml/ns/security-1.2";>
> >   ...
> >   
> >   ...
> > 
> > --
> > 
> > The application starts up properly, and responds on http://localhost, as
> > expected.
> > 
> > However, when I examine request.getContextPath(), I get a forward slash:
> > "/".
> > 
> > This is incorrect, as far as I can tell.  According to the API
> > (http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletRequest.html#getContextPath()):
> > --
> > For servlets in the default (root) context, this method
> > [HttpServletRequest.html.getContextPath()] returns "".
> > --
> > 

-- 
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: 929229

Geronimo Revision: 929229 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

[BUILD] branches/2.2: Failed for Revision: 929198

Geronimo Revision: 929198 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100330/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100330/unit-test-reports
 
from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


  org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.1-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be 
found - check that the goal name is correct: Unable to download the artifact 
from any repository

Try downloading the file manually from the project website.

Then, install it using the command: 
mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport 
-DartifactId=car-maven-plugin -Dversion=2.2.1-SNAPSHOT -Dpackaging=maven-plugin 
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there: 
mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport 
-DartifactId=car-maven-plugin -Dversion=2.2.1-SNAPSHOT -Dpackaging=maven-plugin 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.1-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


  org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.1-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be 
found - check that the goal name is correct: Unable to download the artifact 
from any repository

Try downloading the file manually from the project website.

Then, install it using the command: 
mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport 
-DartifactId=car-maven-plugin -Dversion=2.2.1-SNAPSHOT -Dpackaging=maven-plugin 
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there: 
mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport 
-DartifactId=car-maven-plugin -Dversion=2.2.1-SNAPSHOT -Dpackaging=maven-plugin 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.1-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


  org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.1-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:241)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin

[jira] Resolved: (GERONIMO-5151) JSTL sql tags do not work


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

Jarek Gawor resolved GERONIMO-5151.
---

   Resolution: Fixed
Fix Version/s: 3.0

Resolving as the Geronimo JSTL bundle contains the fix for the problem. Once/if 
the patch gets applied to the JSTL library we can switch back to the JSTL 
bundle.



> JSTL sql tags do not work
> -
>
> Key: GERONIMO-5151
> URL: https://issues.apache.org/jira/browse/GERONIMO-5151
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: javaee6, osgi, Web Profile
>Affects Versions: 3.0
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> The JSTL sql tags use DriverManager API to connect to the database. There are 
> well-known problems with DriverManager API and classloaders and that is 
> exactly what is causing the sql tags not work in OSGi environment.  The core 
> of the problem is that the DriverManager uses the caller's classloader (in 
> this case the JSTL bundle classloader) to find a driver for the given url. 
> Since JSTL bundle does not import any database drivers, the DriverManager 
> does not "see" any drivers and so fails to connect to the database.
> I opened https://issues.apache.org/bugzilla/show_bug.cgi?id=48773 bug report 
> (with a patch) in the taglibs project for this issue.

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

Re: Publish with GEP takes minutes, while deploy takes 10 seconds

2010-03-30 Thread boes


Hello Delos,

I created two EAR projects. Both having three WAR's in the EAR. The WAR's
are created in Eclipse as 'Dynamic Web Project'.

The only difference between the two projects is in the HiThereSlow
projectthat I changed geronimo-application.xml. I added dependencies to
some libraries that do exist in the Geronimo repository. The libs are in
the repository after a fresh installation of
geronimo-tomcat6-javaee5-2.1.4.

Although I added the depency tags, the libraries are not used by the
application. Publishing the two projects shows that the project with the
depencies (HiThereSlow) takes much more time to publish than the one
without (HiThere). On my old laptop it takes 15 seconds to publish
HiThereSlow, where HiThere is published in a second. Adding more empty
WAR's to the HiThereSlow EAR will increase the publishing times almost
linear with the number of WAR's.

I can't see why the publishing process should do anything with the
dependencies in geronimo-application.xml. Maybe it does some verification,
but it should not do so. Deploying HiThereSlow using the Geronimo console
on the running Geronimo server is going very fast.

Please let me know if this information is of any use. If you have some
more questions or don't understand my English (I'm Dutch) please let me
know.


Gert-Jan Boesschen Hospers (Boes)







>
>
>
> Hi Boes,
>
> I also found with eclipse 3.5+, the deployment seems slower than before.
> I'm
> still investigating the root cause.
>
> In deployment process, GEP will pass all artifacts(EAR,WAR,JAR) to WTP. As
> I
> know, WTP will analyze these artifacts, generate many objects,
> package&extract them. I've ever tried a big EAR and found most time is
> consumed by WTP.  But I haven't further investigated the process in WTP.
>
> If possible, could you provide your app for me to double check the
> problem?
>
> Although we haven't found the root cause, there may be some workaround for
> you
> 1) To speed up the deployment of JSP,  you can select "No re-deployment
> when
> only JSP files are updated" in "Test environment" section of server
> "Overview" page. You may find the page after double click server instance
> in
> "Servers" view.
> 2) Put all lib you will never change as shared library in Geronimo server
> 3) Avoid automatic publishing. If automatic publishing is enabled, any
> save
> action on an deployed artifact will trigger publishing. It's inconvenient
> for a big artifact. I suggest you disable it and manually publish it when
> all your changes have been completed. You can select "Never publish
> automatically" in "Publishing" section of server "Overview" page.
>
> Hope it helps!
>
> 2010/3/30 boes 
>
>>
>> Hi,
>>
>> I have an Enterprise Application (EAR) that I develop in Eclipse
>> (galileo-SR1). When I publish my EAR to the started local Geronimo
>> V2.1.4
>> server, it takes more then 3 minutes to finish. I use GEP version 2.2.
>> During the process 1 CPU is constantly running at 100%, so it looks like
>> the
>> system is very busy. The status bar shows 'Publishing to Apache Geronimo
>> V2.1 at localhost (0%)' and it stays on 0% almost to the end of the
>> publishing process.
>>
>> When I export the application as an .ear file to the file system and
>> then
>> deploy the application to the same Geronimo server using the Geronimo
>> console, I found that writing the EAR to the filesystem takes 2 seconds
>> to
>> complete, and the deployment of the EAR to Geronimo takes about 8
>> seconds.
>>
>> My EAR consists of 8 web applications (WAR) and one utility project
>> (JAR).
>> Deployment to the production environment also takes less then 10
>> seconds.
>> The application itself is extensively used and stable.
>>
>> Is there a logical reason why publishing takes much more time then
>> deployment? Are they two different things that can't be compared?
>>
>> I tried to get some more info on what the publishing process is actually
>> doing in those three minutes. In the server settings in Eclipse I set
>> the
>> console output to 'Debug', but I did not get any output from GEP. Is
>> there
>> an option to make GEP verbose and let it print what it is doing?
>>
>> I found that adding dependencies to a project slows down the publishing
>> process. I started with a new EAR project with one WAR, which had only
>> one
>> html page. It takes a second to publish this EAR to Geronimo. Then I
>> extended the geronimo-application.xml deployment despriptor by adding
>> some
>> dependencies to existing libraries in the Geronimo repository. This
>> increases the publish time to 30 seconds. How can that be explained?
>>
>> Is there any more info on GEP? What is it doing when it publishes an EAR
>> to
>> Geronimo? What can I do to speed up publishing?
>>
>> Thanks for any help and information on this subject.
>>
>> Boes
>>
>>
>> --
>> View this message in context:
>> http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-tp684484p684484.html
>> Sent from the Development

[jira] Commented: (GERONIMO-5216) CLONE -getContextRoot() returns forward slash rather than empty string for apps deployed to root context

2010-03-30 Thread Jay D. McHugh (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851427#action_12851427
 ] 

Jay D. McHugh commented on GERONIMO-5216:
-

Hey Matthias,

It looks like this must be a problem with how the tag library is processing the 
 tag.

I will try to take a look as soon as I have some time.

Jay

> CLONE -getContextRoot() returns forward slash rather than empty string for 
> apps deployed to root context
> 
>
> Key: GERONIMO-5216
> URL: https://issues.apache.org/jira/browse/GERONIMO-5216
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.2
>Reporter: Matthias Koch
>Assignee: Jay D. McHugh
>
> An app deployed to the root context should have "" returned by 
> getContextRoot() - On Tomcat, we are returning "/".
> dcherk wrote:
> > I am deploying my war file into the root context with the following
> > deployment plan:
> > --
> > http://geronimo.apache.org/xml/ns/j2ee/web-2.0";
> > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";
> > xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2";
> > xmlns:security="http://geronimo.apache.org/xml/ns/security-1.2";>
> >   ...
> >   
> >   ...
> > 
> > --
> > 
> > The application starts up properly, and responds on http://localhost, as
> > expected.
> > 
> > However, when I examine request.getContextPath(), I get a forward slash:
> > "/".
> > 
> > This is incorrect, as far as I can tell.  According to the API
> > (http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletRequest.html#getContextPath()):
> > --
> > For servlets in the default (root) context, this method
> > [HttpServletRequest.html.getContextPath()] returns "".
> > --
> > 

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

[jira] Resolved: (GERONIMO-5094) Integrate the 2.2 version of the jaxb reference implementation.


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

Jarek Gawor resolved GERONIMO-5094.
---

   Resolution: Fixed
Fix Version/s: 3.0
 Assignee: Rick McGuire

This was taken care of by GERONIMO-5201 and GERONIMO-5202.


> Integrate the 2.2 version of the jaxb reference implementation. 
> 
>
> Key: GERONIMO-5094
> URL: https://issues.apache.org/jira/browse/GERONIMO-5094
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Reporter: Rick McGuire
>Assignee: Rick McGuire
> Fix For: 3.0
>
>


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

[jira] Resolved: (GERONIMO-5174) System bundle exports JAX-WS packages with wrong version


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

Jarek Gawor resolved GERONIMO-5174.
---

Resolution: Fixed
  Assignee: Rick McGuire  (was: Jarek Gawor)

This issue was resolved by GERONIMO-5207.


> System bundle exports JAX-WS packages with wrong version
> 
>
> Key: GERONIMO-5174
> URL: https://issues.apache.org/jira/browse/GERONIMO-5174
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: osgi, specs, webservices
>Affects Versions: 3.0
>Reporter: Jarek Gawor
>Assignee: Rick McGuire
> Fix For: 3.0
>
> Attachments: GERONIMO-5174.patch
>
>
> Right now we export the javax.xml.ws packages via system bundle with version 
> 2.2. That's incorrect since Java 6 does not support JAX-WS 2.2 and it 
> conflicts with Geronimo JAX-WS 2.2 spec bundle.

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

Re: Deploying Aries Blog sample & AriesTrader on Geronimo

2010-03-30 Thread Joe Bohn

That's terrific Jarek! I'm really happy to see AriesTrader running on
Geronimo ... "this is like deja vu all over again" :-)

Joe

Jarek Gawor wrote:

Hi all,

I recently integrated the JTA and JPA pieces from Aries in Geronimo
and exposed connection factories in OSGi service registry. With these
changes we now have all the main pieces in place to deploy unmodified
Aries Blog sample & AriesTrader on Geronimo. Here's how to do it:

1) Make sure you have the latest trunk build. I used tomcat ee 6
assembly but things should also work with the jetty assembly.

2) Deploy the attached aries-datasource connector. It will create the
data sources & database tables for both samples. To deploy the
connector do:

./bin/deploy -u system -p manager deploy
~/.m2/repository/org/tranql/tranql-connector-derby-embed-xa/1.5/tranql-connector-derby-embed-xa-1.5.rar
aries-datasource.xml

3) Build "samples" module in Aries trunk.

To deploy the Blog sample do:

./bin/deploy -u system -p manager deploy /samples/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.1-incubating-SNAPSHOT.eba

or to deploy AriesTrader do:

./bin/deploy -u system -p manager deploy /samples/ariestrader-sample/assemblies/ariestrader-all-eba/target/org.apache.aries.samples.ariestrader.all-0.1-incubating-SNAPSHOT.eba

If all goes well the Blog sample should be available under
http://localhost:8080/blog and AriesTrader under
http://localhost:8080/ariestrader.

Btw, when running the deploy command you might see some "Address
already in use" exceptions. They can be ignored.

Let me know if you have any problems,

Jarek

[jira] Updated: (GERONIMO-5216) CLONE -getContextRoot() returns forward slash rather than empty string for apps deployed to root context

2010-03-30 Thread Matthias Koch (JIRA)


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

Matthias Koch updated GERONIMO-5216:


Affects Version/s: (was: 2.1.1)
   (was: 2.0.2)
   (was: 2.0.1)
   (was: 2.1)
   (was: 2.0)
Fix Version/s: (was: 2.0.3)
   (was: 2.2)
   (was: 2.1.1)

Hi,

as for me this issue is not fixed in current geronimo version 2.2

either with 

or
/

i allways get the / 
when using  wich used getContextPath()

kr Matthias

> CLONE -getContextRoot() returns forward slash rather than empty string for 
> apps deployed to root context
> 
>
> Key: GERONIMO-5216
> URL: https://issues.apache.org/jira/browse/GERONIMO-5216
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.2
>Reporter: Matthias Koch
>Assignee: Jay D. McHugh
>
> An app deployed to the root context should have "" returned by 
> getContextRoot() - On Tomcat, we are returning "/".
> dcherk wrote:
> > I am deploying my war file into the root context with the following
> > deployment plan:
> > --
> > http://geronimo.apache.org/xml/ns/j2ee/web-2.0";
> > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";
> > xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2";
> > xmlns:security="http://geronimo.apache.org/xml/ns/security-1.2";>
> >   ...
> >   
> >   ...
> > 
> > --
> > 
> > The application starts up properly, and responds on http://localhost, as
> > expected.
> > 
> > However, when I examine request.getContextPath(), I get a forward slash:
> > "/".
> > 
> > This is incorrect, as far as I can tell.  According to the API
> > (http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletRequest.html#getContextPath()):
> > --
> > For servlets in the default (root) context, this method
> > [HttpServletRequest.html.getContextPath()] returns "".
> > --
> > 

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

[jira] Created: (GERONIMO-5216) CLONE -getContextRoot() returns forward slash rather than empty string for apps deployed to root context

2010-03-30 Thread Matthias Koch (JIRA)

CLONE -getContextRoot() returns forward slash rather than empty string for apps 
deployed to root context


 Key: GERONIMO-5216
 URL: https://issues.apache.org/jira/browse/GERONIMO-5216
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tomcat
Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.2
Reporter: Matthias Koch
Assignee: Jay D. McHugh
 Fix For: 2.0.3, 2.1.1, 2.2


An app deployed to the root context should have "" returned by getContextRoot() 
- On Tomcat, we are returning "/".

dcherk wrote:
> I am deploying my war file into the root context with the following
> deployment plan:
> --
> http://geronimo.apache.org/xml/ns/j2ee/web-2.0";
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";
> xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2";
> xmlns:security="http://geronimo.apache.org/xml/ns/security-1.2";>
>   ...
>   
>   ...
> 
> --
> 
> The application starts up properly, and responds on http://localhost, as
> expected.
> 
> However, when I examine request.getContextPath(), I get a forward slash:
> "/".
> 
> This is incorrect, as far as I can tell.  According to the API
> (http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletRequest.html#getContextPath()):
> --
> For servlets in the default (root) context, this method
> [HttpServletRequest.html.getContextPath()] returns "".
> --
> 

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

Re: Deploying Aries Blog sample & AriesTrader on Geronimo

2010-03-30 Thread Lin Sun

Great news.  Congrats!

Lin

On Mon, Mar 29, 2010 at 4:43 PM, Jarek Gawor  wrote:
> Hi all,
>
> I recently integrated the JTA and JPA pieces from Aries in Geronimo
> and exposed connection factories in OSGi service registry. With these
> changes we now have all the main pieces in place to deploy unmodified
> Aries Blog sample & AriesTrader on Geronimo. Here's how to do it:
>
> 1) Make sure you have the latest trunk build. I used tomcat ee 6
> assembly but things should also work with the jetty assembly.
>
> 2) Deploy the attached aries-datasource connector. It will create the
> data sources & database tables for both samples. To deploy the
> connector do:
>
> ./bin/deploy -u system -p manager deploy
> ~/.m2/repository/org/tranql/tranql-connector-derby-embed-xa/1.5/tranql-connector-derby-embed-xa-1.5.rar
> aries-datasource.xml
>
> 3) Build "samples" module in Aries trunk.
>
> To deploy the Blog sample do:
>
> ./bin/deploy -u system -p manager deploy  trunk>/samples/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.1-incubating-SNAPSHOT.eba
>
> or to deploy AriesTrader do:
>
> ./bin/deploy -u system -p manager deploy  trunk>/samples/ariestrader-sample/assemblies/ariestrader-all-eba/target/org.apache.aries.samples.ariestrader.all-0.1-incubating-SNAPSHOT.eba
>
> If all goes well the Blog sample should be available under
> http://localhost:8080/blog and AriesTrader under
> http://localhost:8080/ariestrader.
>
> Btw, when running the deploy command you might see some "Address
> already in use" exceptions. They can be ignored.
>
> Let me know if you have any problems,
>
> Jarek
>

[BUILD] trunk: Failed for Revision: 929125

Geronimo Revision: 929125 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100330/unit-test-reports
 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.aries 
-DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) 
org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT
2) 
org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT
3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots

[jira] Resolved: (GERONIMO-5095) Create JAX-RS spec jar

2010-03-30 Thread Rick McGuire (JIRA)


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

Rick McGuire resolved GERONIMO-5095.


Resolution: Fixed

Committed revision 929105.

Version created in the Geronimo specs project at 

https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jaxrs_1.1_spec

A couple of modifications were required:

1) packaging was changed to an OSGi bundle. 
2) The RuntimeDelegate class was modified to use the Geronimo ProviderLocator 
methods for service resolution. 
3) The order of the enums was changed to use the javadoc detail order, not the 
summary order to match the reference implementation. 
4) The serialVersionUID of WebApplicationException was changed to match the 
value specified in the spec javadocs. 


> Create JAX-RS spec jar 
> ---
>
> Key: GERONIMO-5095
> URL: https://issues.apache.org/jira/browse/GERONIMO-5095
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, specs
>Affects Versions: 3.0
>Reporter: Rick McGuire
>Assignee: Rick McGuire
> Fix For: 3.0
>
>


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

[jira] Assigned: (GERONIMO-5095) Create JAX-RS spec jar

2010-03-30 Thread Rick McGuire (JIRA)


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

Rick McGuire reassigned GERONIMO-5095:
--

Assignee: Rick McGuire  (was: Rex Wang)

> Create JAX-RS spec jar 
> ---
>
> Key: GERONIMO-5095
> URL: https://issues.apache.org/jira/browse/GERONIMO-5095
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, specs
>Affects Versions: 3.0
>Reporter: Rick McGuire
>Assignee: Rick McGuire
> Fix For: 3.0
>
>


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

[jira] Commented: (GERONIMO-5215) Cannot generate eclipse project config files for several modules


[ 
https://issues.apache.org/jira/browse/GERONIMO-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851328#action_12851328
 ] 

Forrest Xia commented on GERONIMO-5215:
---

commit patch 2 at revision 929049.

> Cannot generate eclipse project config files for several modules
> 
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch, GERONIMO-5215_2.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Closed: (GERONIMO-5215) Cannot generate eclipse project config files for several modules


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

Forrest Xia closed GERONIMO-5215.
-

Resolution: Fixed

> Cannot generate eclipse project config files for several modules
> 
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch, GERONIMO-5215_2.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Updated: (GERONIMO-5215) Cannot generate eclipse project config files for several modules


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

Forrest Xia updated GERONIMO-5215:
--

Attachment: GERONIMO-5215_2.patch

patch 2 is for plugins/tomcat/tomcat6/pom.xml

> Cannot generate eclipse project config files for several modules
> 
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch, GERONIMO-5215_2.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Updated: (GERONIMO-5215) Cannot generate eclipse project config files for several modules


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

Forrest Xia updated GERONIMO-5215:
--

Summary: Cannot generate eclipse project config files for several modules  
(was: Cannot generate eclipse project config files for geronimo-commands)

Update the title, since it's for several modules with the same issue when 
executing mvn eclipse:eclipse

> Cannot generate eclipse project config files for several modules
> 
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Reopened: (GERONIMO-5215) Cannot generate eclipse project config files for geronimo-commands


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

Forrest Xia reopened GERONIMO-5215:
---


Found more modules have similar problem, so reopen this jira.

> Cannot generate eclipse project config files for geronimo-commands
> --
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Closed: (GERONIMO-5215) Cannot generate eclipse project config files for geronimo-commands


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

Forrest Xia closed GERONIMO-5215.
-

Resolution: Fixed

> Cannot generate eclipse project config files for geronimo-commands
> --
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Commented: (GERONIMO-5215) Cannot generate eclipse project config files for geronimo-commands


[ 
https://issues.apache.org/jira/browse/GERONIMO-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851310#action_12851310
 ] 

Forrest Xia commented on GERONIMO-5215:
---

commit this patch at revision 929037.

> Cannot generate eclipse project config files for geronimo-commands
> --
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Updated: (GERONIMO-5215) Cannot generate eclipse project config files for geronimo-commands


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

Forrest Xia updated GERONIMO-5215:
--

Attachment: GERONIMO-5215.patch

This patch fix the mvn eclipse:eclipse issue.

> Cannot generate eclipse project config files for geronimo-commands
> --
>
> Key: GERONIMO-5215
> URL: https://issues.apache.org/jira/browse/GERONIMO-5215
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.1.5
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 2.1.5
>
> Attachments: GERONIMO-5215.patch
>
>
> When executing mvn eclipse:eclipse against 
> "framework/modules/geronimo-commands", an exception like this:
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, 
> include=[org/apache/geronimo/commands/version.properties], 
> exclude=[**/*.java], test=false, filtering=true
> Seems the maven eclipse plugin cannot merge two resource definitions 
> correctly as following:
>  
> 
> ${pom.basedir}/src/main/resources
> 
> **/*
> 
> 
> 
> ${pom.basedir}/src/main/resources
> true
> 
> 
> org/apache/geronimo/commands/version.properties
> 
> 
> 

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

[jira] Created: (GERONIMO-5215) Cannot generate eclipse project config files for geronimo-commands

Cannot generate eclipse project config files for geronimo-commands
--

 Key: GERONIMO-5215
 URL: https://issues.apache.org/jira/browse/GERONIMO-5215
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: buildsystem
Affects Versions: 2.1.5
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor
 Fix For: 2.1.5


When executing mvn eclipse:eclipse against 
"framework/modules/geronimo-commands", an exception like this:
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Request to merge when 'filtering' is not identical. Original=resource 
src/main/resources: output=target/classes, include=[**/*], exclude=[**/*.java], 
test=false, filtering=false, merging with=resource src/main/resources: 
output=target/classes, 
include=[org/apache/geronimo/commands/version.properties], exclude=[**/*.java], 
test=false, filtering=true

Seems the maven eclipse plugin cannot merge two resource definitions correctly 
as following:
 

${pom.basedir}/src/main/resources

**/*




${pom.basedir}/src/main/resources
true


org/apache/geronimo/commands/version.properties




-- 
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: 929021