How can I help...

I'm interested in helping out in whatever way that I can. I've been writing enterprise Java about 7 or 8 years now. I think that I could provide some value to the team. How do I get started? -- Barry Egbert [EMAIL PROTECTED]

Re: Antwort: SAXParser problem with Maven 2.0.4, Xalan 2.8.1, Xerces 2.8

Aaron, This is a great cvs reporting plug-in you've started for maven2, have you been succesful and would you be putting it for public use. thanks, -barry Aaron.Digulla wrote: > > Hello, > > I made some further progress. > > Apparently, the problem is in Sun's S

[jira] Commented: (MECLIPSE-47) Planning support for wtp 1.0

[ http://jira.codehaus.org/browse/MECLIPSE-47?page=comments#action_58873 ] Barry Kaplan commented on MECLIPSE-47: -- This bug is not quite fixed. See my comment at the end. > Planning support for wtp 1.0 > > >

[jira] Closed: (MNG-1695) Generated outputpath is outside the eclipse project

[ http://jira.codehaus.org/browse/MNG-1695?page=all ] Barry Kaplan closed MNG-1695: - Resolution: Fixed Fix Version: 2.0.1 Already fixed at the time this issue was reported by rev 349273. > Generated outputpath is outside the eclipse proj

[jira] Commented: (MNG-1695) Generated outputpath is outside the eclipse project

[ http://jira.codehaus.org/browse/MNG-1695?page=comments#action_52130 ] Barry Kaplan commented on MNG-1695: --- Ah, sorry. I just updated to 349273 the correct path is now created! (Wish I tried this before setting up this issue :-( I still get the

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52129 ] Barry Kaplan commented on MNG-1605: --- Ok, I created MNG-1695 and attached a sample project hierarchy that can be used to demostrate the problem. As for: >> A correct output path

[jira] Created: (MNG-1695) Generated outputpath is outside the eclipse project

: plugin revision 349173, windows xp, running from a partition mounted at 'R' Reporter: Barry Kaplan Attachments: eclipse-plugin-test-project.zip In the sample multi-project attached, the generated eclipse project outputpath will have the drive letter appended. In iris-env/pom.

[jira] Created: (MNG-1693) .wtpmodules does not use same output directory as compiler

Reporter: Barry Kaplan When the output path is overriden via the outputDirectory configuration property, the 'java-output-path' property in .wtpmodules does not use this value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact

[jira] Commented: (MNG-1693) .wtpmodules does not use same output directory as compiler

[ http://jira.codehaus.org/browse/MNG-1693?page=comments#action_52108 ] Barry Kaplan commented on MNG-1693: --- And I think this is causing some eclipse validators to scan surefire generated files (which I target to a different output directory than eclipse

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52107 ] Barry Kaplan commented on MNG-1605: --- BTW, only with the double slashes do I get the warning. But the double slash was the only thing I could find that worked. I tried all kinds other

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52106 ] Barry Kaplan commented on MNG-1605: --- Workaround: I changed the plugin config to: //${project.artifactId}/target/eclipse-classes This caused the

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52105 ] Barry Kaplan commented on MNG-1605: --- A correct output path would have the project prepended, eg: "iris-infra/target/eclipse-classes". This is indeed what is created when ru

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52104 ] Barry Kaplan commented on MNG-1605: --- Thanks Fabrizio. All works except the output path. I have the following defined

[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level

[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52072 ] Barry Kaplan commented on MNG-1605: --- If [in the non-broke state] the sources will be used if they exists even without the flag, then running with the flag once in a while should be

[jira] Commented: (MNG-1606) Allow for forcing the creation of direct project references for dependencies

[ http://jira.codehaus.org/browse/MNG-1606?page=comments#action_51494 ] Barry Kaplan commented on MNG-1606: --- Sorry Brett, I'm not following what the meaning of this snippet is. Are configuration filters implemented anywhere? Are there some con

[jira] Commented: (MNG-1606) Allow for forcing the creation of direct project references for dependencies

[ http://jira.codehaus.org/browse/MNG-1606?page=comments#action_51490 ] Barry Kaplan commented on MNG-1606: --- What is a configuration filter? I don't see this in the docs. And how does using a configuration filter relate to MNG-955? Should that also

[jira] Created: (MNG-1623) Generation of eclipse projects requires that reactor projects have installed jars

: maven-eclipse-plugin Versions: 2.0 Reporter: Barry Kaplan Most reactor actions work without requiring projects in the hierachy to have installed jars. eg, You can compile and test the hierarchy using only the project target directories. However, when generating eclipse projects

[jira] Created: (MNG-1607) Provide the ability to globally exclude a dependency

: Barry Kaplan Some dependencies you simply never want downloaded no matter what. For example, when using jdk 1.5 xml-apis.jar causes headaches. But many projects require this dependency. Therefore it would be nice to support a 'never' download sett

[jira] Created: (MNG-1606) Allow for forcing the creation of direct project references for dependencies

: maven-eclipse-plugin Versions: 2.0 Reporter: Barry Kaplan For some thirdparty dependencies, it is common (for me at least) that an eclipse project for that dependency does/will exist in the workspace. It would be nice if dependencies in eclipse projects can be forced to use a direct

[jira] Created: (MNG-1605) Allow eclipse source to be specified at the dependency level

: 2.0 Reporter: Barry Kaplan Many (most?) projects do not have sources uploaded. And in any case, most projects only need a small subset of the sources. Source downloading, even (especially?) for sources that don't exist, is very time consuming. Therefore, it would be nice to sp

[jira] Created: (SUREFIRE-17) ReporterManager stdOutLog variable not initialized if test fails in setup

Reporter: Barry Kaplan Assigned to: Jason van Zyl When a test fails during setup, or inside the suite method, org.codehaus.surefire.report.ReporterManager will throw a NPE in method testFailed(ReportEntry, String typeError) at line 344. This is because stdOutLog and stdErrLog are not

[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects

[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49853 ] Barry Kaplan commented on MNG-955: -- Wait, now I'm confused. This issue seems to imply that project references will always be used if version matches. If so, I can't get th

[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects

[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49852 ] Barry Kaplan commented on MNG-955: -- I agree with Rafal, direct project references is critical. And since eclipse already does not have any clean way to seperate dependency types then

[jira] Created: (MNG-1405) Missing version messages should indicate the dependency

Missing version messages should indicate the dependency --- Key: MNG-1405 URL: http://jira.codehaus.org/browse/MNG-1405 Project: Maven 2 Type: Improvement Versions: 2.0 Reporter: Barry Kaplan When a

[jira] Created: (MNG-1404) Provide informative messages when POM is invalid

Provide informative messages when POM is invalid Key: MNG-1404 URL: http://jira.codehaus.org/browse/MNG-1404 Project: Maven 2 Type: Improvement Versions: 2.0 Reporter: Barry Kaplan When a pom is invalid

[jira] Commented: (MNG-591) Integration tests lifecycle

[ http://jira.codehaus.org/browse/MNG-591?page=comments#action_49625 ] Barry Kaplan commented on MNG-591: -- After reading all this, I'm a bit confused. What is the recommended approach in maven2 v1.x for handling different test types? I pretty much

[jira] Commented: (MAVEN-1545) Specify target jdk per project in multibuild

[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38742 ] Barry Kaplan commented on MAVEN-1545: - Just to clarify what Mark said. We did not fork off a javac, we needed to fork off an entire maven process, since maven always uses the