[jira] Created: (MEV-313) publish seperate spring POM's for seperate dependencies
publish seperate spring POM's for seperate dependencies --- Key: MEV-313 URL: http://jira.codehaus.org/browse/MEV-313 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Ryan Sonnek instead of one massive POM that forces developers to use excludes like crazy, there should be seperate POM's for seperate dependencies. Ideally, there would be no need for the whole exclude concept. For starters, spring-orm-hibernate should be fairly easy to extract from the current POM. http://jroller.com/page/wireframe/?anchor=seperate_artifacts_for_seperate_dependencies -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJDEVELOPER-2) incorrect use of source paths for jdeveloper 10g
[ http://jira.codehaus.org/browse/MPJDEVELOPER-2?page=all ] Ryan Sonnek closed MPJDEVELOPER-2: -- Resolution: Fixed noone in their right mind would use JDeveloper, so i would suggest this maven plugin to be nuked as well. incorrect use of source paths for jdeveloper 10g Key: MPJDEVELOPER-2 URL: http://jira.codehaus.org/browse/MPJDEVELOPER-2 Project: maven-jdeveloper-plugin Type: Bug Versions: 1.3 Environment: maven-1.0-rc2, maven-jdeveloper-plugin-1.3 Reporter: Ryan Sonnek Attachments: plugin.jelly the jdeveloper plugin does not produce a valid project file for jdeveloper 10g. attached is a modified plugin.jelly that solves some of the problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-221) transitive dependencies not being picked up
[ http://jira.codehaus.org/browse/MEV-221?page=comments#action_51533 ] Ryan Sonnek commented on MEV-221: - I deleted my local repository and tried to only use the spring-hibernate dependency, but I get these compilation errors: cannot access org.springframework.dao.support.DaoSupport file org\springframework\dao\support\DaoSupport.class not found I still need the spring-dao and spring-beans dependencies to build my project. transitive dependencies not being picked up --- Key: MEV-221 URL: http://jira.codehaus.org/browse/MEV-221 Project: Maven Evangelism Type: Bug Reporter: Ryan Sonnek According to the POM for spring-hibernate-1.2.5, the spring-dao and spring-beans packages should be picked up by transitive dependencies. I can not compile my application without explicitly adding these to my POM in addition to spring-hibernate. dependency groupIdorg.springframework/groupId artifactIdspring-beans/artifactId version1.2.5/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-dao/artifactId version1.2.5/version exclusions exclusion groupIdjavax.transaction/groupId artifactIdjta/artifactId /exclusion /exclusions /dependency dependency groupIdorg.springframework/groupId artifactIdspring-hibernate/artifactId version1.2.5/version /dependency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1608) assembling dependencies uses timestamp instead of snapshot jars
[ http://jira.codehaus.org/browse/MNG-1608?page=all ] Ryan Sonnek closed MNG-1608: Resolution: Fixed my local snapshots must have been out of date, because rerunning the assembly after rebuilding my projects put the right jars in the assembly. assembling dependencies uses timestamp instead of snapshot jars --- Key: MNG-1608 URL: http://jira.codehaus.org/browse/MNG-1608 Project: Maven 2 Type: Bug Components: maven-jar-plugin, maven-assembly-plugin Versions: 2.0 Reporter: Ryan Sonnek I'm using the jar plugin to add my dependencies to the manifest. I'm also using the assembly plugin to package all dependencies into one archive. The problem is that the jar manifest adds my dependencies as foo-SNAPHOT and the archiver adds them as foo-20041113.jar. This causes my snapshot classes to not be found at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-218) spring 1.2.5 pointing to invalid 1.2.6 poms
spring 1.2.5 pointing to invalid 1.2.6 poms --- Key: MEV-218 URL: http://jira.codehaus.org/browse/MEV-218 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Ryan Sonnek during the recent deployment of the spring 1.2.6 artifacts, someone has updated the 1.2.5 poms to point users to the 1.2.6 jars. The problem with this is that the old 1.2.5 poms had *excellent* transitive dependencies so that my application could be built just by depending on spring. the new 1.2.6 poms have *no* dependencies setup, so now my app can't build after cleaning out my local repo! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1626) transitive dependencies not being picked up
transitive dependencies not being picked up --- Key: MNG-1626 URL: http://jira.codehaus.org/browse/MNG-1626 Project: Maven 2 Type: Bug Versions: 2.0 Reporter: Ryan Sonnek According to the POM for spring-hibernate-1.2.5, the spring-dao and spring-beans packages should be picked up by transitive dependencies. I can not compile my application without explicitly adding these to my POM in addition to spring-hibernate. dependency groupIdorg.springframework/groupId artifactIdspring-beans/artifactId version1.2.5/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-dao/artifactId version1.2.5/version exclusions exclusion groupIdjavax.transaction/groupId artifactIdjta/artifactId /exclusion /exclusions /dependency dependency groupIdorg.springframework/groupId artifactIdspring-hibernate/artifactId version1.2.5/version /dependency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1608) assembling dependencies uses timestamp instead of snapshot jars
assembling dependencies uses timestamp instead of snapshot jars --- Key: MNG-1608 URL: http://jira.codehaus.org/browse/MNG-1608 Project: Maven 2 Type: Bug Components: maven-jar-plugin, maven-assembly-plugin Versions: 2.0 Reporter: Ryan Sonnek I'm using the jar plugin to add my dependencies to the manifest. I'm also using the assembly plugin to package all dependencies into one archive. The problem is that the jar manifest adds my dependencies as foo-SNAPHOT and the archiver adds them as foo-20041113.jar. This causes my snapshot classes to not be found at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1348) includes attribute not allows on resource tag
includes attribute not allows on resource tag - Key: MNG-1348 URL: http://jira.codehaus.org/browse/MNG-1348 Project: Maven 2 Type: Bug Components: maven-model Versions: 2.0 Reporter: Ryan Sonnek according to the product documentation at http://maven.apache.org/maven2/maven-model/maven.html each resource should be able to specify includes. maven errors out unless the inclues is moved out of resource and into the resources tag. example model: resources resource directorysrc/main/wsdd/directory includes*.wsdl/includes /resource /resources exception: [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parse error reading POM at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) 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.project.InvalidProjectModelException: Parse error re ading POM at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1097) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1057) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi le(DefaultMavenProjectBuilder.java:291) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:276) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:509) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:441) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:345) ... 11 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected ST ART_TAG or END_TAG not TEXT (position: TEXT seen .../directory\r\ninc ludes*.wsdl/... @71:27) at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1080 ) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseResource(MavenXpp 3Reader.java:3825) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Re ader.java:621) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Re ader.java:2131) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.j ava:4255) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1093) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-370) cvs tag ignored
cvs tag ignored --- Key: CONTINUUM-370 URL: http://jira.codehaus.org/browse/CONTINUUM-370 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0 Environment: maven-2.0.0, contiuum-1.0 Reporter: Ryan Sonnek Continuum ignores the CVS tag attribute set on a maven2 project. You can configure the branch/version for the build using the edit project page, but it should respect the tag in the pom.xml example pom.xml: scm connectionscm:cvs:pserver:[EMAIL PROTECTED]:/cvs:project//connection developerConnectionscm:cvs:pserver:[EMAIL PROTECTED]:/cvs:project//developerConnection tagVERSION_1_0/tag /scm Continuum output: 2005-10-26 13:13:15,015 [Thread-1] DEBUG ScmManager - Command line: cvs -f -d :pserver:[EMAIL PROTECTED]:2401/cvs -q checkout -d 2 project I could be misunderstanding the purpose of the scm tag. Any clarification on this would be appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (CONTINUUM-176) adding parent pom create duplicate continuum projects for all children
[ http://jira.codehaus.org/browse/CONTINUUM-176?page=all ] Ryan Sonnek reopened CONTINUUM-176: --- Thanks, this worked, but now when I add the parent POM to continuum, ONLY the child projects are added. This is an issue because if the parent POM is changed, the child projects won't know about the change and they will be built incorrectly. adding parent pom create duplicate continuum projects for all children -- Key: CONTINUUM-176 URL: http://jira.codehaus.org/browse/CONTINUUM-176 Project: Continuum Type: Bug Versions: 1.0-alpha-2 Reporter: Ryan Sonnek adding my parent maven2 project to continuum creates a continuum project for each of my subprojects. the continuum project's start off with the label of my subprojects, but once the build run's they all revert to the label of the parent projects. the build process for each of the subproject's is the same as well. they don't actually just build the subproject. continuum builds the entire project. try using my project's pom at https://shard.dev.java.net/source/browse/*checkout*/shard/pom.xml for an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-176) adding parent pom create duplicate continuum projects for all children
adding parent pom create duplicate continuum projects for all children -- Key: CONTINUUM-176 URL: http://jira.codehaus.org/browse/CONTINUUM-176 Project: Continuum Type: Bug Versions: 1.0-alpha-2 Reporter: Ryan Sonnek adding my parent maven2 project to continuum creates a continuum project for each of my subprojects. the continuum project's start off with the label of my subprojects, but once the build run's they all revert to the label of the parent projects. the build process for each of the subproject's is the same as well. they don't actually just build the subproject. continuum builds the entire project. try using my project's pom at https://shard.dev.java.net/source/browse/*checkout*/shard/pom.xml for an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-387) pom changes for basic hibernate project
pom changes for basic hibernate project --- Key: MNG-387 URL: http://jira.codehaus.org/browse/MNG-387 Project: m2 Type: Bug Components: repository-tools Reporter: Ryan Sonnek it seems as if the current m2 repository has some invalid poms. I'm assuming this is because the m2 pom's were automatically generated from the m1 pom's. Here is a list of changes that were required in my local repository to get a very basic hibernate project up and going. change dom4j-1.6.pom stax dependencies to these: dependency groupIdstax/groupId artifactIdstax-api/artifactId version1.0/version /dependency dependency groupIdstax/groupId artifactIdstax/artifactId version1.1-dev/version /dependency remove this dependency from stax-1.1-dev.pom: dependency groupIdxmlbeans-jsr173-api/groupId artifactIdxmlbeans-jsr173-api/artifactId version2.0-dev/version /dependency manually install geronimo servlet-api as servlet api remove two dependencies from xom-1.0b3.pom: dependency groupIdicu4j/groupId artifactIdicu4j/artifactId version2.6.1/version /dependency dependency groupIdtagsoup/groupId artifactIdtagsoup/artifactId version0.9.7/version /dependency manually install empty jdbc-2.0.jar can these pom's be scrubbed, or move these dependencies to the m2 repository? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-387) pom changes for basic hibernate project
[ http://jira.codehaus.org/browse/MNG-387?page=comments#action_39006 ] Ryan Sonnek commented on MNG-387: - I also had to add the following dependencies which are not provided in the hibernate POM: dependency groupIdodmg/groupId artifactIdodmg/artifactId version3.0/version scoperuntime/scope /dependency dependency groupIdehcache/groupId artifactIdehcache/artifactId version1.1/version scoperuntime/scope /dependency dependency groupIdcglib/groupId artifactIdcglib/artifactId version2.0.2/version /dependency dependency groupIdasm/groupId artifactIdasm/artifactId version1.4.3/version /dependency dependency groupIdgeronimo-spec/groupId artifactIdgeronimo-spec-jta/artifactId version1.0-M1/version /dependency pom changes for basic hibernate project --- Key: MNG-387 URL: http://jira.codehaus.org/browse/MNG-387 Project: m2 Type: Bug Components: repository-tools Reporter: Ryan Sonnek it seems as if the current m2 repository has some invalid poms. I'm assuming this is because the m2 pom's were automatically generated from the m1 pom's. Here is a list of changes that were required in my local repository to get a very basic hibernate project up and going. change dom4j-1.6.pom stax dependencies to these: dependency groupIdstax/groupId artifactIdstax-api/artifactId version1.0/version /dependency dependency groupIdstax/groupId artifactIdstax/artifactId version1.1-dev/version /dependency remove this dependency from stax-1.1-dev.pom: dependency groupIdxmlbeans-jsr173-api/groupId artifactIdxmlbeans-jsr173-api/artifactId version2.0-dev/version /dependency manually install geronimo servlet-api as servlet api remove two dependencies from xom-1.0b3.pom: dependency groupIdicu4j/groupId artifactIdicu4j/artifactId version2.6.1/version /dependency dependency groupIdtagsoup/groupId artifactIdtagsoup/artifactId version0.9.7/version /dependency manually install empty jdbc-2.0.jar can these pom's be scrubbed, or move these dependencies to the m2 repository? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-359) support project inheritence with flat project layout
support project inheritence with flat project layout Key: MNG-359 URL: http://jira.codehaus.org/browse/MNG-359 Project: m2 Type: Bug Components: maven-core Versions: 2.0-alpha-1 Reporter: Ryan Sonnek Priority: Critical the project inheritence does not currently support projects that are laid out with a flat directory structure. ex: --/my-project-root/ pom.xml (base pom) --/my-subproject-one/ pom.xml (child pom) original thread on mailing list: http://marc.theaimsgroup.com/?l=turbine-maven-userm=111442037703037w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
