[jira] Created: (MEAR-112) support for java ee 6 missing
support for java ee 6 missing - Key: MEAR-112 URL: http://jira.codehaus.org/browse/MEAR-112 Project: Maven 2.x Ear Plugin Issue Type: New Feature Affects Versions: 2.3.2 Reporter: Milos Kleint the version parameter only accepts 1.3, 1.4 and 5 as valid values. It needs to be extended to allow also 6 as a valid version. -- 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] Commented: (MEAR-112) support for java ee 6 missing
[ http://jira.codehaus.org/browse/MEAR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186527#action_186527 ] Milos Kleint commented on MEAR-112: --- basic work here, still needs some work - http://svn.apache.org/viewvc?rev=802682view=rev support for java ee 6 missing - Key: MEAR-112 URL: http://jira.codehaus.org/browse/MEAR-112 Project: Maven 2.x Ear Plugin Issue Type: New Feature Affects Versions: 2.3.2 Reporter: Milos Kleint Assignee: Milos Kleint the version parameter only accepts 1.3, 1.4 and 5 as valid values. It needs to be extended to allow also 6 as a valid version. -- 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] Commented: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run
[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186528#action_186528 ] Udai Gupta commented on SUREFIRE-377: - Thanks Pawel, I guess I might need a Junit 4 to Junit3 migration tool :P When JUnit and TestNG tests are in same project, only one set gets run -- Key: SUREFIRE-377 URL: http://jira.codehaus.org/browse/SUREFIRE-377 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.4 Reporter: Dan Fabulich Fix For: 2.4 Attachments: surefire377.patch, testng-junit-together.zip The attached Maven project has two tests: one JUnit test and one TestNG test. According to the documentation, in this case TestNG should run both tests. Run mvn test. Only the TestNG test will run. If you modify the pom to set the property junit=true, only the JUnit test will run. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.4-SNAPSHOT/version configuration properties property namejunit/name valuetrue/value /property /properties /plugin -- 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] Why Maven does not use local plugin?
Hi Maven is failing and reporting that it cant find maven-install plugin or a valid version in central repository. The install plugin version 2.2 and 2.3 are definately installed locally - I can see the pom and jar for each in the local m2 repository. The install plugin is not installed in the central repository and I know that Maven checks for updates there but why does Maven fail just because it cant download the fuile from central when it IS installed locally? Thanks Jon -- View this message in context: http://www.nabble.com/Why-Maven-does-not-use-local-plugin--tp24897721p24897721.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Commented: (MEAR-112) support for java ee 6 missing
[ http://jira.codehaus.org/browse/MEAR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186544#action_186544 ] Stephane Nicoll commented on MEAR-112: -- kudo :) support for java ee 6 missing - Key: MEAR-112 URL: http://jira.codehaus.org/browse/MEAR-112 Project: Maven 2.x Ear Plugin Issue Type: New Feature Affects Versions: 2.3.2 Reporter: Milos Kleint Assignee: Milos Kleint the version parameter only accepts 1.3, 1.4 and 5 as valid values. It needs to be extended to allow also 6 as a valid version. -- 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] Commented: (MPDF-26) Add report generation in PDF
[
http://jira.codehaus.org/browse/MPDF-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186545#action_186545
]
Vincent Siveton commented on MPDF-26:
-
With this issue, we will need to change the plugin prerequisites to Maven 2.1
due to Linkage error:
{noformat}
java.lang.LinkageError: loader constraints violated when linking
org/codehaus/doxia/sink/Sink class
{noformat}
Add report generation in PDF
Key: MPDF-26
URL: http://jira.codehaus.org/browse/MPDF-26
Project: Maven 2.x PDF Plugin
Issue Type: Improvement
Affects Versions: 1.0
Reporter: Vincent Siveton
Using MavenReport#generate(org.codehaus.doxia.sink.Sink, Locale)
--
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: (MRELEASE-470) release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false
release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false Key: MRELEASE-470 URL: http://jira.codehaus.org/browse/MRELEASE-470 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-7 Environment: OS : Windows XP SVN client : svn, version 1.4.4 (r25188) / compiled Jun 8 2007, 18:49:42 Reporter: Mareks Birkenfelds command : -- 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: (MRELEASE-471) release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false
release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false Key: MRELEASE-471 URL: http://jira.codehaus.org/browse/MRELEASE-471 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-7 Environment: OS : Windows XP SVN client : svn, version 1.4.4 (r25188) / compiled Jun 8 2007, 18:49:42 Reporter: Mareks Birkenfelds command : mvn release:branch -DbranchName=Branch10 -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false should not commit files to SVN trunk, but it does - all pom.xml files are not changed, but commited in SVN ( maven touches those files) -- 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] Closed: (MRELEASE-470) release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false
[ http://jira.codehaus.org/browse/MRELEASE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mareks Birkenfelds closed MRELEASE-470. --- Resolution: Duplicate accidently submited 2 times release:branch touch each file in trunk even when specified option -DupdateWorkingCopyVersions=false Key: MRELEASE-470 URL: http://jira.codehaus.org/browse/MRELEASE-470 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0-beta-7 Environment: OS : Windows XP SVN client : svn, version 1.4.4 (r25188) / compiled Jun 8 2007, 18:49:42 Reporter: Mareks Birkenfelds command : -- 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-4289) Bump to latest Modello
Bump to latest Modello -- Key: MNG-4289 URL: http://jira.codehaus.org/browse/MNG-4289 Project: Maven 2 Issue Type: Bug Affects Versions: 2.2.0, 2.1.0, 2.0.10 Reporter: Vincent Siveton Due to MODELLO-189, we will need to bump to latest release of Modello -- 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-4290) Update guide-http-settings to reflect the fact that sun-based http has been restored as the default for the http/s wagons.
Update guide-http-settings to reflect the fact that sun-based http has been restored as the default for the http/s wagons. -- Key: MNG-4290 URL: http://jira.codehaus.org/browse/MNG-4290 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Affects Versions: 2.2.1 Reporter: John Casey -- 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] Updated: (MNG-4290) Update guide-http-settings to reflect the fact that sun-based http has been restored as the default for the http/s wagons.
[ http://jira.codehaus.org/browse/MNG-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4290: Fix Version/s: 2.2.1 Update guide-http-settings to reflect the fact that sun-based http has been restored as the default for the http/s wagons. -- Key: MNG-4290 URL: http://jira.codehaus.org/browse/MNG-4290 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Affects Versions: 2.2.1 Reporter: John Casey Assignee: John Casey Fix For: 2.2.1 -- 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: (MAVENUPLOAD-2551) xslthl (net.sf.xslthl) upload
xslthl (net.sf.xslthl) upload - Key: MAVENUPLOAD-2551 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2551 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Pronzato Hello, I am developer in the xslthl project and I would like to have our repository synced with maven central repository. net.sf.xslthl,mavens...@web.sourceforge.net:/home/groups/x/xs/xslthl/htdocs/maven/repository,rsync_ssh,Cedric Pronzato,mi...@users.sourceforge.net,, Regards, Cedric, -- 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] Commented: (MAVENUPLOAD-2550) Please sync org.jamon
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186627#action_186627 ] Ian Robertson commented on MAVENUPLOAD-2550: Correction: the line should be: org.jamon,mvns...@jamon.org:/home/jamon/maven2,rsync_ssh,Ian Robertson,ian.b.robert...@gmail.com,, Please sync org.jamon - Key: MAVENUPLOAD-2550 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2550 Project: Maven Upload Requests Issue Type: Wish Reporter: Ian Robertson org.jamon,ja...@jamon.org:/home/jamon/maven2,rsync_ssh,Ian Robertson,ian.b.robert...@gmail.com,, -- 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: (MASSEMBLY-441) manifest is incorrectly 'overwritten' when using jar-with-dependencies
manifest is incorrectly 'overwritten' when using jar-with-dependencies -- Key: MASSEMBLY-441 URL: http://jira.codehaus.org/browse/MASSEMBLY-441 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-4 Environment: Maven 2.1 JDK 1.5 Reporter: Adrian Shum plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptorRefs descriptorRefjar-with-dependencies/descriptorRef /descriptorRefs archive manifest mainClassmy.fullly.qualified.MainClass/mainClass /manifest /archive /configuration executions execution idmake-assembly/id phasepackage/phase goals goaldirectory/goal!-- same case when using single -- /goals /execution /executions /plugin I used the plugin config above and tried to create a 'all-in-one executable jar'. However, I found the MANIFEST.MF is not really what I declared. It seems that MANIFEST.MF of certain dependencies JARs is put there instead (In my case, Oracle's JDBC driver JAR's MANIFEST.MF is presented) -- 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
