Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060111.080001.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060111.10.txt
[ http://jira.codehaus.org/browse/CONTINUUM-555?page=comments#action_4
]
Emmanuel Venisse commented on CONTINUUM-555:
Not exactly.
Actually, Continuum run the *first* build definition found for the current
schedule.
I don't know for now if
[ http://jira.codehaus.org/browse/CONTINUUM-555?page=all ]
Emmanuel Venisse updated CONTINUUM-555:
---
Fix Version: 1.1
Continuum only executes default build-definition
Key: CONTINUUM-555
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.013000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.02.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.023000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.033000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.050001.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060112.053000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060112.053000.txt
I've been thinking of a good design for the MRM and maven-proxy
integration and got stuck with this issue:
(1) Should we setup the maven-proxy app and then allow it to use MRM
indexing and caching and other stuffs?
or
(2) can have an MRM app that can accept the same config that maven-proxy
[ http://jira.codehaus.org/browse/MNGECLIPSE-25?page=comments#action_55491
]
Roland Klein commented on MNGECLIPSE-25:
Hello,
this behavior results from a corrupt tarball i got from ViewCVS, some filenames
were changed in that way that the
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060111.080001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.080001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MNGECLIPSE-25?page=all ]
Roland Klein closed MNGECLIPSE-25:
--
Resolution: Fixed
Oh, i just entered some comment look above ;)
Enable Maven in project causes ClassCastException
[SNIP]
URL: http://svn.apache.org/viewcvs?rev=367861view=rev
Log:
PR: MPDASHBOARD-32
maven.dashboard.report.showempty property not honored.
[SNIP]
- j:if test=${notEmptyElems.isEmpty() == 'true'}
+ j:if test=${empty(notEmptyElems)}
[SNIP]
Lukas, did you test it with maven 1.1
Ability to deploy-file as classifier
Key: MDEPLOY-19
URL: http://jira.codehaus.org/browse/MDEPLOY-19
Project: Maven 2.x Deploy Plugin
Type: New Feature
Versions: 2.1
Environment: xp
Reporter: Dan Tran
deploy-file
+1
Emmanuel
Brett Porter a écrit :
This needs to get out there with the new name. Can we do a release of
the current code? There are 2 feature requests in JIRA that can wait
until 2.1.
Also, we should possibly rename the JIRA project and prefix.
[ ] +1
[ ] +0
[ ] -1
- Brett
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060111.081501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060111.081501.txt
-
To unsubscribe,
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060111.083000.txt
Give equal footing to all m2 plugins and add Cargo plugin to the list
-
Key: MNG-1952
URL: http://jira.codehaus.org/browse/MNG-1952
Project: Maven 2
Type: Improvement
Components: documentation -
[ http://jira.codehaus.org/browse/MNGECLIPSE-4?page=all ]
Mark Chesney updated MNGECLIPSE-4:
--
Attachment: MNGECLIPSE-4.jpg
Problems with dependencies other that jar and war (ie. par, ejb3)
[ http://jira.codehaus.org/browse/MNG-1952?page=all ]
Vincent Massol updated MNG-1952:
Attachment: (was: siteplugin.patch)
Give equal footing to all m2 plugins and add Cargo plugin to the list
[ http://jira.codehaus.org/browse/MNGECLIPSE-4?page=all ]
Mark Chesney updated MNGECLIPSE-4:
--
Attachment: test-projects-MNGECLIPSE-4.zip
Problems with dependencies other that jar and war (ie. par, ejb3)
[ http://jira.codehaus.org/browse/MNG-1952?page=all ]
Vincent Massol updated MNG-1952:
Attachment: siteplugin2.patch
Give equal footing to all m2 plugins and add Cargo plugin to the list
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060111.084501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060111.084501.txt
-
To unsubscribe,
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060111.09.txt
I wasn't looking for extra help posted here when I got no response
from users mailing list.
no worries
-Hassan
Brett Porter [EMAIL PROTECTED]
10/01/2006 23:48
Please respond to Maven Developers List
To: Maven Developers List dev@maven.apache.org
cc:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060111.09.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.09.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
copy-dependencies does not work for type ejb-client
---
Key: MPRELEASE-17
URL: http://jira.codehaus.org/browse/MPRELEASE-17
Project: maven-release-plugin
Type: Bug
Versions: 1.5
Environment: maven 1.1 beta 2
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060111.093000.txt
[ http://jira.codehaus.org/browse/MNGECLIPSE-19?page=all ]
Mark Chesney updated MNGECLIPSE-19:
---
Attachment: test-projects-MNGECLIPSE-19.zip
version can not be supplied in parent pom
-
Key:
[ http://jira.codehaus.org/browse/MNGECLIPSE-19?page=all ]
Mark Chesney updated MNGECLIPSE-19:
---
Attachment: MNGECLIPSE-19.jpg
version can not be supplied in parent pom
-
Key: MNGECLIPSE-19
[ http://jira.codehaus.org/browse/MNG-1952?page=comments#action_55500 ]
Brett Porter commented on MNG-1952:
---
Honestly, I think they should be separate. The other plugins are not part of
the Maven project. If you really want Cargo at the top, put that
Brian E. Fox wrote:
What would be nice is if you could define some list of groups and say
don't look here Or better, define a repo to be internal and say these
groups are internal.
I think this has been proposed as a pure Maven feature before, and its
best to keep it there. Can you file it in
Hi John,
I think we'd all agree with the sentiment. I think the default needs to
be less noisy, and -X should be targetted (debug artifact resolution,
debug pom, etc). We could name systems and log accordingly. This is all
in JIRA.
If you have any suggestions for implementation, please say so!
[ http://jira.codehaus.org/browse/MJAVADOC-42?page=comments#action_55502 ]
Alexander Hars commented on MJAVADOC-42:
You are right, you can achieve this with CDATA right now. For example:
bottom![CDATA[Copyright 2005, a href=[WWW]
Hi Bob,
We've been over the first case before. I think its dangerous to change
that now - better documentation/explanation (or maybe even alternative
naming), but I think we need to retain the compile - runtime - test
relationship.
I know we need to sort out that second use case. There's also
Hi Dennis,
Could you drop a test case into JIRA for this? Would like to get it
resolved before 2.0. Looks like a bug, because it should find stuff
inside the reactor. It may be related to the
non-inheritance/interpolation bugs which are already there.
Do you have relativePath/ set correctly in
The final result is 4 binding +1's
I will release tomorrow.
- Brett
Brett Porter wrote:
Hi,
There's been a bunch of changes for site 2.0, and the sink api now
includes some classes for backwards compatibility after the package
change that need to go into the Maven 2.0.2 release.
I'd
[ http://jira.codehaus.org/browse/MJAVADOC-42?page=comments#action_55503 ]
Alexander Hars commented on MJAVADOC-42:
My previous comment was thrown off because of JIRA markup.
Here is the correct (unformatted) version:
{noformat}
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Maven Wiki for change
notification.
The following page has been changed by AlexanderHars:
http://wiki.apache.org/maven/JavadocPlugin
--
* bottom
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 11:03 PM
To: Maven Developers List
Subject: [vote] release maven-help-plugin 2.0
This needs to get out there with the new name. Can we do a release of
the current code? There are 2
+1
arnaud
On 1/11/06, Mike Perham [EMAIL PROTECTED] wrote:
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 11:03 PM
To: Maven Developers List
Subject: [vote] release maven-help-plugin 2.0
This needs to get out there with the
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_55510 ]
Jesse Kuhnert commented on MSUREFIRE-23:
Ahh, I didn't know about this part. The runtime errors are the biggest reason I
did it, but perhaps there is an easy solution to the
I have been a big fan of domained logging...where the logging api call
contains whatever is necessary to earmark that log message as belonging to a
particular domain (domain being whatever you want to define it as, the
class, the package, the logical functionality of something..)
I have done this
[ http://jira.codehaus.org/browse/MNG-624?page=comments#action_55515 ]
Brian Fox commented on MNG-624:
---
here's my 2 cents: What if the parent version could take a tag like LATEST and
then the release plugin could resolve it like it does with SNAPSHOTS. IMO,
[ http://jira.codehaus.org/browse/MNG-179?page=comments#action_55517 ]
Brian Fox commented on MNG-179:
---
I recently added a resolve goal to the 1.1 version of dependency plugin on the
mojo project. This does effectively this except it doesn't get all plugins.
[ http://jira.codehaus.org/browse/MNG-1898?page=comments#action_55518 ]
Brian Fox commented on MNG-1898:
I was really hoping this could get fixed in 2.0.2, I can't proceed with my Kodo
plugin until it gets fixed. If there is something I can do to help let
+1
Vincent
2006/1/11, Brett Porter [EMAIL PROTECTED]:
This needs to get out there with the new name. Can we do a release of
the current code? There are 2 feature requests in JIRA that can wait
until 2.1.
Also, we should possibly rename the JIRA project and prefix.
[ ] +1
[ ] +0
[ ] -1
+1
Vincent
2006/1/9, Mike Perham [EMAIL PROTECTED]:
All outstanding JIRA issues have been closed so I'd like to suggest a
new release.
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hide
sorter/order=ASCsorter/field=prioritypid=11140fixfor=12176
Brett asks:
- How
Messed up maven.dependency.classpath when using maven-antrun-plugin-1.1
---
Key: MANTRUN-38
URL: http://jira.codehaus.org/browse/MANTRUN-38
Project: Maven 2.x Antrun Plugin
Type: Bug
Versions:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-660?page=all ]
Michael Böckling updated MAVENUPLOAD-660:
-
Attachment: proguard-3.4-bundle.jar
ProGuard
Key: MAVENUPLOAD-660
URL:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060111.153002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.153002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
that's it
On 1/11/06, Brett Porter [EMAIL PROTECTED] wrote:
Ok, I understand now what you mean by relocate.
We should put the relocation info in the POM, but still retain the JAR
in both locations.
- Brett
Carlos Sanchez wrote:
On 1/10/06, Brett Porter [EMAIL PROTECTED] wrote:
A
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060111.154501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060111.154501.txt
-
To unsubscribe,
[
http://jira.codehaus.org/browse/MAVENUPLOAD-660?page=comments#action_55524 ]
Carlos Sanchez commented on MAVENUPLOAD-660:
com.sun.j2me.wtk artifact doesn't exist. If it can't be redistributed at least
you have to provide a pom.
ant is
[ http://jira.codehaus.org/browse/MAVENUPLOAD-644?page=all ]
Carlos Sanchez closed MAVENUPLOAD-644:
--
Resolution: Fixed
Maven Jini Plug-in version 2.0
--
Key: MAVENUPLOAD-644
URL:
[ http://jira.codehaus.org/browse/MNG-1950?page=all ]
Chris Hagmann reopened MNG-1950:
Brett,
I reopened this issue, because:
As long as I cannot use a plugin with one configuration per goal, I still have
the need to have custom lifecycle phases.
[ http://jira.codehaus.org/browse/MEV-287?page=comments#action_55527 ]
Carlos Sanchez commented on MEV-287:
I don't see any problem , how can be reproduced?
Spring beans 1.2.5 jar is corrupted
---
Key:
[ http://jira.codehaus.org/browse/MEV-286?page=all ]
Carlos Sanchez closed MEV-286:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
Nothing is removed from ibiblio
you can provide relocation poms though
Erase top Spring package since the real
Jesse McConnell wrote:
I have been a big fan of domained logging...where the logging api call
contains whatever is necessary to earmark that log message as belonging to a
particular domain (domain being whatever you want to define it as, the
class, the package, the logical functionality of
[ http://jira.codehaus.org/browse/MEV-285?page=all ]
Carlos Sanchez closed MEV-285:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
Nothing is removed from ibiblio
you can provide relocation poms though
Erase JAXME package since it is now
[
http://jira.codehaus.org/browse/MAVENUPLOAD-660?page=comments#action_55531 ]
Michael Böckling commented on MAVENUPLOAD-660:
--
No, ANT and WTK are needed to compile proguard, but are not necessarily needed
when using proguard. Isn't that what
After building with sh build.sh i can create the root user.
Trying to login results allways in:
org.codehaus.plexus.action.ActionNotFoundException: Cannot find action:
login
at
org.codehaus.plexus.action.DefaultActionManager.lookup(DefaultActionMana
ger.java:61)
at
[
http://jira.codehaus.org/browse/MAVENUPLOAD-660?page=comments#action_55532 ]
Carlos Sanchez commented on MAVENUPLOAD-660:
not necessarily needed sounds like optional, and it should work
to know the naming i have to know what jar are you
On 1/11/06, Brett Porter [EMAIL PROTECTED] wrote:
I think we'd all agree with the sentiment. I think the default needs to
be less noisy
Well, a good start for removing LOTS of useless debug messages while
generating site or reports could be committing this patch to plexus:
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: testng-4.4.5-jdk14.jar
Support TestNG
--
Key: MSUREFIRE-23
URL: http://jira.codehaus.org/browse/MSUREFIRE-23
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: testng-4.4.5-jdk15.jar
Support TestNG
--
Key: MSUREFIRE-23
URL: http://jira.codehaus.org/browse/MSUREFIRE-23
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: surefire-patch.txt
maven-surefire-report-maven-plugin-patch.txt
maven-surefire-plugin-patch.txt
Support TestNG
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_55533 ]
Jesse Kuhnert commented on MSUREFIRE-23:
These patches should be enough for someone to play around with the patch work.
I'm going to create sub-tasks on this issue for the
Add relevant parameters for configuring testng
--
Key: MSUREFIRE-40
URL: http://jira.codehaus.org/browse/MSUREFIRE-40
Project: Maven 2.x Surefire Plugin
Type: Sub-task
Environment: any
Reporter: Jesse Kuhnert
Add
Enable show/hide on surefire report
---
Key: MSUREFIRE-41
URL: http://jira.codehaus.org/browse/MSUREFIRE-41
Project: Maven 2.x Surefire Plugin
Type: Sub-task
Environment: any
Reporter: Jesse Kuhnert
enable show/hide on
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=comments#action_55535 ]
Jesse Kuhnert commented on MSUREFIRE-23:
I still need to convert testng to use maven, at least for publishing to testng
but thought I'd save myself the trouble if everyone
cactus:cactus:13-1.7 relocation to cactus:cactus-13:1.7 incomplete
--
Key: MAVENUPLOAD-672
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-672
Project: maven-upload-requests
Type: Bug
Reporter:
I checked with m1.0.2 and m1.1b3-SNAPSHOT. Seems to work fine.
-Lukas
Arnaud HERITIER wrote:
[SNIP]
URL: http://svn.apache.org/viewcvs?rev=367861view=rev
Log:
PR: MPDASHBOARD-32
maven.dashboard.report.showempty property not honored.
[SNIP]
- j:if test=${notEmptyElems.isEmpty() ==
+1
Lukas
Brett Porter wrote:
This needs to get out there with the new name. Can we do a release of
the current code? There are 2 feature requests in JIRA that can wait
until 2.1.
Also, we should possibly rename the JIRA project and prefix.
[ ] +1
[ ] +0
[ ] -1
- Brett
Hi,
In 1.1, we have decided to rework all security features.
I tried to use osuser but this framework is crappy :
- UserManager is a final class that load a osuser config file, we can't set parameters with plexus
because all initialization phase are done in constuctor that read config file
-
[ http://jira.codehaus.org/browse/MANTRUN-38?page=all ]
Carlos Sanchez closed MANTRUN-38:
-
Assign To: Carlos Sanchez
Resolution: Fixed
Fix Version: 1.2
Reverted the changes, not it's equal to compile classpath as before, but will
be
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060111.181501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060111.181501.txt
-
To unsubscribe,
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060111.183001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.183001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MANTRUN-37?page=comments#action_55539 ]
Carlos Sanchez commented on MANTRUN-37:
---
I see in your logs maven-antrun-plugin:1.0 ???
I need more info to reproduce it
The it tests use multimodule and they work
Antrun
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060111.184501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060111.184501.txt
-
To unsubscribe,
Jason van Zyl wrote:
That would be cool! It would be far simpler for users to track down
specific problems and even if there are intersecting domains involved
you just turn on the logging for the appropriate domain. Very nice idea.
Agreed. So how do we go about this? We can probably match the
sure thing, might not get to it for a bit...kinda crushed under some other
things but definitely something interesting to look into.
I was just thinking, that perhaps instead of domaining by package, it might
be interesting to try and do it via artifact...I am not sure what kind of
overhead would
Spring-full doesn't have any jars and there is already a Spring artifact.
-
Key: MEV-289
URL: http://jira.codehaus.org/browse/MEV-289
Project: Maven Evangelism
Type: Bug
Reporter: Alexandre
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060111.190001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.190001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
specifying manifestFile does nothing
--
Key: MJAR-17
URL: http://jira.codehaus.org/browse/MJAR-17
Project: Maven 2.x Jar Plugin
Type: Bug
Reporter: darren hartford
Trying to set an existing MANIFEST.MF file as the JAR
[ http://jira.codehaus.org/browse/MJAR-17?page=all ]
darren hartford closed MJAR-17:
---
Resolution: Fixed
user.insufficient.Caffine error :-)
Just adds more data to the top of the specified Manifest file which is fine.
specifying manifestFile does
[ http://jira.codehaus.org/browse/MEV-286?page=comments#action_55541 ]
Alexandre Poitras commented on MEV-286:
---
Cool! What is a relocation pom or is there any documentation on the subject?
Erase top Spring package since the real ones are in
[ http://jira.codehaus.org/browse/MEV-286?page=comments#action_55543 ]
Carlos Sanchez commented on MEV-286:
Take a look at this
http://test.maven.codehaus.org/maven2/servletapi/servlet-api/2.4/servlet-api-2.4.pom
and
[ http://jira.codehaus.org/browse/MEV-289?page=all ]
Carlos Sanchez closed MEV-289:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
That pom was used to make easier poms for spring jars
Spring-full doesn't have any jars and there is already a
[ http://jira.codehaus.org/browse/MRESOURCES-8?page=comments#action_55545 ]
Leszek Gawron commented on MRESOURCES-8:
My discussion on irc with Kenney ended up with the conclusion that something is
wrong in plexus configurator because
Spring beans 1.2.5 jar is corrupted
---
Key: MEV-290
URL: http://jira.codehaus.org/browse/MEV-290
Project: Maven Evangelism
Type: Bug
Reporter: Alexandre Poitras
I get a jar bad header error whenever I attempt to use it.
--
[ http://jira.codehaus.org/browse/MNG-1898?page=all ]
Brian Fox updated MNG-1898:
---
Attachment: test-1.0.zip
Plugin classpath broken from 2.0 to 2.0.1
-
Key: MNG-1898
URL:
[ http://jira.codehaus.org/browse/MNG-1898?page=all ]
Brian Fox updated MNG-1898:
---
Attachment: test-case.zip
Plugin classpath broken from 2.0 to 2.0.1
-
Key: MNG-1898
URL:
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060111.21.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MEV-290?page=all ]
Carlos Sanchez closed MEV-290:
--
Assign To: Carlos Sanchez
Resolution: Duplicate
Why do you create duplicated issues?
Spring beans 1.2.5 jar is corrupted
---
Continuum only executes default build-definition
Key: CONTINUUM-555
URL: http://jira.codehaus.org/browse/CONTINUUM-555
Project: Continuum
Type: Bug
Components: Core system
Versions: 1.0.2
Reporter:
[ http://jira.codehaus.org/browse/MEV-290?page=comments#action_1 ]
Alexandre Poitras commented on MEV-290:
---
Sorry I didn't search before, my bad I taught if it was already reported it
would have been fixed by now. I'll search before creating any
[ http://jira.codehaus.org/browse/MEV-287?page=all ]
Carlos Sanchez closed MEV-287:
--
Assign To: Carlos Sanchez
Resolution: Cannot Reproduce
jar tf works fine and the jar is exactly the same as distibuted by spring
Spring beans 1.2.5 jar is
1 - 100 of 180 matches
Mail list logo
