[mojo-dev] [jira] (MJSPC-54) Support sourceVersion 1.6 or 1.7
Roman Cerny
created MJSPC-54
Support sourceVersion 1.6 or 1.7
Issue Type:
Improvement
Assignee:
Unassigned
Created:
21/May/12 6:43 AM
Description:
The latest release in the Maven repository (jspc-maven-plugin:2.0-alpha-3) does only support Java 1.5 (as newest version).
It uses the jspc-compiler-tomcat6:2.0-alpha-3 as dependency:
http://repo2.maven.org/maven2/org/codehaus/mojo/jspc/jspc-compiler-tomcat6/2.0-alpha-3/jspc-compiler-tomcat6-2.0-alpha-3.pom
Which uses 6.0.18.
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.18/src/apache-tomcat-6.0.18-src.zip
Where in the class JDTCompiler there is a check for the version in the method generateClass
// Source JVM
if(ctxt.getOptions().getCompilerSourceVM() != null) {
String opt = ctxt.getOptions().getCompilerSourceVM();
if(opt.equals("1.1")) {
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_1);
} else if(opt.equals("1.2")) {
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_2);
} else if(opt.equals("1.3")) {
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_3);
} else if(opt.equals("1.4")) {
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_4);
} else if(opt.equals("1.5")) {
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_5);
} else {
log.warn("Unknown source VM " + opt + " ignored.");
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_5);
}
} else {
// Default to 1.5
settings.put(CompilerOptions.OPTION_Source,
CompilerOptions.VERSION_1_5);
}
With newer Jasper versions, also 1.6 or 1.7 is supported.
It would be nice too have a new release, using the latest tomcatVersion, currently: 6.0.35
Environment:
2.0-alpha-3
Project:
Maven 2.x JSPC Plugin
Priority:
Critical
Reporter:
Roman Cerny
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MOJO-1821) maven-wagon-plugin requires apache commons-io
Alexander Goehring commented on MOJO-1821 maven-wagon-plugin requires apache commons-io this problem could be solved with ... org.apache.maven.wagon wagon-http 2.2 ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MOJO-1832) Maven3: java.lang.ClassNotFoundException: org.apache.commons.io.IOUtils
Alexander Goehring commented on MOJO-1832 Maven3: java.lang.ClassNotFoundException: org.apache.commons.io.IOUtils MOJO-1832 is a duplicate of MOJO-1821 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJSPC-55) module with other than war packaging not ignored properly
Roman Cerny created MJSPC-55 module with other than war packaging not ignored properly Issue Type: Bug Assignee: Unassigned Created: 21/May/12 8:10 AM Description: I have a module project with pom and some child-modules with war, some other child-modules with jar Altough it is stated in the documentation that other packaging types than war are excluded: http://mojo.codehaus.org/jspc/jspc-maven-plugin/usage.html I still get the following error when running the plugin on the parent project. The -uriroot option must specify a pre-existing directory. When running with -X option the uriroot argument uses: "-uriroot", "/src/main/webapp" Clearly there is no such path, since it is a module project. Execution is stopped. Running the plugin on each of the childs separately works fine for me. So either: provide a skip option: as stated in MJSPC-32 (in order to skip this module manually) or skip modules with pom packaging automatically. Note: this bug also occurrs for jar packaging. Environment: 2.0-alpha-3 Project: Maven 2.x JSPC Plugin Priority: Critical Reporter: Roman Cerny This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MOJO-1821) maven-wagon-plugin requires apache commons-io
Mats Karlsson closed MOJO-1821 as Fixed maven-wagon-plugin requires apache commons-io Alexander Goehrings solution works! Change By: Mats Karlsson (21/May/12 8:35 AM) Resolution: Fixed Status: Open Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MCLIRR-48) Add support for ignoring field or method breaking backward compatibility
Vincent Massol created MCLIRR-48 Add support for ignoring field or method breaking backward compatibility Issue Type: Improvement Assignee: Unassigned Created: 21/May/12 9:05 AM Description: Right now the exclude is done at the class level only. I'd like to be able to exclude at field or method level so that we can safely ignore some backward compatibilities while not ignoring others in the same class file. Project: Maven 2.x Clirr Plugin Priority: Major Reporter: Vincent Massol This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MWEBSTART-195) Support same artifactId for different groups
Tobias Schöneberg created MWEBSTART-195 Support same artifactId for different groups Issue Type: New Feature Affects Versions: 1.0-beta-3 Assignee: Unassigned Created: 21/May/12 10:44 AM Description: Imho there should be a way to handle artifacts that differ only in their groupId. From a user's side, the configuration could be done like described for the ear-plugin: http://maven.apache.org/plugins/maven-ear-plugin/examples/customize-file-name-mapping.html WDYT? Project: Maven 2.x Webstart Plugin Priority: Major Reporter: Tobias Schöneberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MJS-17) maven-javascript-plugin: Licences untouched in compressed javascript files
Alexander Dietrich commented on MJS-17 maven-_javascript_-plugin: Licences untouched in compressed _javascript_ files You need to start the comment like this: /** @license This seems to make both Closure Compiler and YUI Compressor happy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
RE: [mojo-dev] Need help from someone with karma to create MTRUEZIP Jira project ( https://jira.codehaus.org/browse/HAUS-2231 )
Hi Dan, Fixed by Stephen, but we can't close the issue.Component issues have been moved. You'll have to do some administration for the versions and you're good to go. -Robert > Date: Sat, 19 May 2012 09:59:11 -0700 > From: dant...@gmail.com > To: dev@mojo.codehaus.org > Subject: [mojo-dev] Need help from someone with karma to create MTRUEZIP Jira > project ( https://jira.codehaus.org/browse/HAUS-2231 ) > > So that I can release truezip-maven-plugin 1.0 currently under voting period > > Big thanks ahead > > -Dan > > - > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
Re: [mojo-dev] [VOTE] Releasing TrueZip Maven Plugin 1.0 - Take 2
Hello, We now have a separate project for truezip-maven-plugin ( Thanks Stephen and Robert) The votes also passed +1 from Tony Chemit, Kent Sølvsten, Anders Hammar, and me Will proceed to promote the plugin to Maven Central Thank you every one. -Dan On Thu, May 17, 2012 at 10:23 PM, Anders Hammar wrote: > Ok, good. But I'm still -1 until that project has been created. > > /Anders > > On Fri, May 18, 2012 at 7:10 AM, Dan Tran wrote: >> I directly fixed up the site to use MTRUEZIP jira project ( >> http://mojo.codehaus.org/truezip/truezip-maven-plugin/issue-tracking.html >> ) >> >> There is no need to respin the build. >> >> Thanks >> >> -D >> >> On Thu, May 17, 2012 at 2:23 PM, Dan Tran wrote: >>> request for separate JIRA project has been created >>> https://jira.codehaus.org/browse/HAUS-2231 >>> >>> Thanks >>> >>> On Thu, May 17, 2012 at 11:53 AM, Kent Sølvsten wrote: Hi Here is my conditional +1. I would suggest that You file a ticket for creation of a separate JIRA project (it might speed up the proces posting it here, since a few people on this list are able to create the project). Then change the issue management part of the pom and create a new release (since the issue management section on the site would otherwise be wrong). When that is done, I would be fine with creating the release announcement without a new vote. /Kent Den 17/05/2012 kl. 17.22 skrev Dan Tran: > Hi > > I would like to release the first 1.0 release of TrueZIP Maven Plugin > > > The changes are at > http://mojo.codehaus.org/truezip/truezip-maven-plugin/changes-report.html > > The new site is at > http://mojo.codehaus.org/truezip/truezip-maven-plugin/ > > Staging Repository > https://nexus.codehaus.org/content/repositories/orgcodehausmojo-084 > > General Staging is at > https://nexus.codehaus.org/content/groups/staging/ > > This vote will be open for 72 hours and will use lazy consensus. > > [+1] release it > [0] don't care > [-1] don't release! > > +1 from me > > Thanks, > > -Dan > > - > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email >> >> - >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > - > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[mojo-dev] [jira] (MEXEC-109) Fork patch
Robert Scholte commented on MEXEC-109 Fork patch I still consider exec:exec as a blocking thread. Maven should only continue when this thread is closed by itself. I compare the fork with cargo:start and cargo:stop for instance. There are much more equivalent plugins with a start and stop goal, so I'd prefer to follow that pattern. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
