[jira] Created: (MNG-5145) Optional compile dependencies being resolved by test dependencies
Optional compile dependencies being resolved by test dependencies - Key: MNG-5145 URL: https://jira.codehaus.org/browse/MNG-5145 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.3 Reporter: Robert Watkins Priority: Critical Attachments: pom.xml Optional compile-time dependencies are being resolved (in WAR projects, at least) into the packaged artifact. There has been a regression since Maven 2.2.1 in regards to resolving optional dependencies. In the attached pom (which builds a WAR), there are two dependencies: * org.springframework:spring-core:2.5.6 - at compile scope * org.dbunit:dbunit:2.3.0 - at test scope. The dependency tree looks like this: net.twasink:webapp:war:1.0 +- org.springframework:spring-core:jar:2.5.6:compile | \- commons-logging:commons-logging:jar:1.1.1:compile \- org.dbunit:dbunit:jar:2.3.0:test +- junit:junit:jar:3.8.2:test +- junit-addons:junit-addons:jar:1.4:test | +- xerces:xercesImpl:jar:2.6.2:test | \- xerces:xmlParserAPIs:jar:2.6.2:test +- org.apache.poi:poi:jar:3.1-FINAL:test | \- log4j:log4j:jar:1.2.13:test +- commons-collections:commons-collections:jar:3.1:test +- commons-lang:commons-lang:jar:2.1:test +- org.slf4j:slf4j-api:jar:1.4.3:test \- org.slf4j:slf4j-nop:jar:1.4.3:test Note that log4j:log4j:1.2.13 is a test dependency. However, when you do 'mvn package', and inspect the resulting WAR file, it includes log4j! The problem appears to be that commons-logging (a compile dependency brought in by spring-core) declares log4j as an _optional_ compile dependency. This is clashing with the test dependency brought in transitively by dbunit. To make it worse, this is still brought in if you add an explicit exclusion of log4j to spring-core. Maven 2.2.1 did not bring in the log4j JAR - this is a regression under Maven 3.0.3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5144) Maven should warn on an always wrong reporting.outputDirectory
Maven should warn on an always wrong reporting.outputDirectory
--
Key: MNG-5144
URL: https://jira.codehaus.org/browse/MNG-5144
Project: Maven 2 & 3
Issue Type: Improvement
Components: POM
Affects Versions: 3.0.3
Reporter: jieryn
Priority: Minor
It would be nice if Maven would warn users of a bad configuration when they
code {code}{code} style. This will
cause deletion of the project when clean phase is requested.
See
http://maven.40175.n5.nabble.com/Upgraded-to-Maven-3-now-the-quot-clean-quot-goal-deletes-entire-module-directories-td4652053.html
for the full thread.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-342) wagon-scp should remove target area prior to uploading/unzipping new content
[
https://jira.codehaus.org/browse/WAGON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed WAGON-342.
-
Resolution: Duplicate
Duplicates WAGON-343.
> wagon-scp should remove target area prior to uploading/unzipping new content
>
>
> Key: WAGON-342
> URL: https://jira.codehaus.org/browse/WAGON-342
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh-external
>Affects Versions: 1.0
> Environment: Maven 3.0.3
> maven-site-plugin:3.0-beta-3
>Reporter: Jamal
>Priority: Minor
> Attachments: ScpHelper.java
>
>
> Similiar to the request captured in this issue
> (https://jira.codehaus.org/browse/MSITE-250), my problem is that our target
> area gets out of sync when we upload our site generated content frequently
> using CI. When files are moved/deleted, our site deployment target area
> becomes a hassle to keep correct because when noticed, we have to manually
> delete either old files, or the entire folder (because it's easier :)) prior
> to deploying the site. I'd like it if the wagon-scp code could remove the
> files/subfolders in the target area prior to uploading.
> I looked at the code, and a easy fix, which I tested, is to update the
> ScpHelper.putDirectory() method (in wagon-ssh-common) to remove the contents
> of the folder prior to uploading/unzipping the new files:
> ...
> try
> {
> executor.executeCommand( "cd " + path + "; rm -rf * ");
>
> wagon.put( zipFile, getPath( destDir, zipFile.getName() ) );
>
> executor.executeCommand( "cd " + path + "; unzip -q -o " +
> zipFile.getName() + "; rm -f " + zipFile.getName() );
> zipFile.delete();
> ...
> I have attached the version of the file which I updated and tested, and below
> is what the output looks like with my simple test project.
> Password for dev@localhost: XX
> scp://localhost/tmp/site-deploy - Session: Opened
> Executing command: mkdir -p /tmp/site-deploy/.
> Executing command: cd /tmp/site-deploy/.; rm -rf *
> Executing command: mkdir -p /tmp/site-deploy/.
> Executing command: scp -t "/tmp/site-deploy/./wagon3163598898345372687.zip"
> Uploading: ./wagon3163598898345372687.zip to scp://localhost/tmp/site-deploy
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-343) wagon-scp should remove target area prior to uploading/unzipping new content
wagon-scp should remove target area prior to uploading/unzipping new content
Key: WAGON-343
URL: https://jira.codehaus.org/browse/WAGON-343
Project: Maven Wagon
Issue Type: Bug
Components: wagon-ssh-external
Affects Versions: 1.0
Environment: Maven 3.0.3
maven-site-plugin:3.0-beta-3
Reporter: Jamal
Priority: Minor
Attachments: ScpHelper.java
Similiar to the request captured in this issue
(https://jira.codehaus.org/browse/MSITE-250), my problem is that our target
area gets out of sync when we upload our site generated content frequently
using CI. When files are moved/deleted, our site deployment target area
becomes a hassle to keep correct because when noticed, we have to manually
delete either old files, or the entire folder (because it's easier :)) prior to
deploying the site. I'd like it if the wagon-scp code could remove the
files/subfolders in the target area prior to uploading.
I looked at the code, and a easy fix, which I tested, is to update the
ScpHelper.putDirectory() method (in wagon-ssh-common) to remove the contents of
the folder prior to uploading/unzipping the new files:
...
try
{
executor.executeCommand( "cd " + path + "; rm -rf * ");
wagon.put( zipFile, getPath( destDir, zipFile.getName() ) );
executor.executeCommand( "cd " + path + "; unzip -q -o " +
zipFile.getName() + "; rm -f " + zipFile.getName() );
zipFile.delete();
...
I have attached the version of the file which I updated and tested, and below
is what the output looks like with my simple test project.
Password for dev@localhost: XX
scp://localhost/tmp/site-deploy - Session: Opened
Executing command: mkdir -p /tmp/site-deploy/.
Executing command: cd /tmp/site-deploy/.; rm -rf *
Executing command: mkdir -p /tmp/site-deploy/.
Executing command: scp -t "/tmp/site-deploy/./wagon3163598898345372687.zip"
Uploading: ./wagon3163598898345372687.zip to scp://localhost/tmp/site-deploy
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-342) wagon-scp should remove target area prior to uploading/unzipping new content
wagon-scp should remove target area prior to uploading/unzipping new content
Key: WAGON-342
URL: https://jira.codehaus.org/browse/WAGON-342
Project: Maven Wagon
Issue Type: Bug
Components: wagon-ssh-external
Affects Versions: 1.0
Environment: Maven 3.0.3
maven-site-plugin:3.0-beta-3
Reporter: Jamal
Priority: Minor
Attachments: ScpHelper.java
Similiar to the request captured in this issue
(https://jira.codehaus.org/browse/MSITE-250), my problem is that our target
area gets out of sync when we upload our site generated content frequently
using CI. When files are moved/deleted, our site deployment target area
becomes a hassle to keep correct because when noticed, we have to manually
delete either old files, or the entire folder (because it's easier :)) prior to
deploying the site. I'd like it if the wagon-scp code could remove the
files/subfolders in the target area prior to uploading.
I looked at the code, and a easy fix, which I tested, is to update the
ScpHelper.putDirectory() method (in wagon-ssh-common) to remove the contents of
the folder prior to uploading/unzipping the new files:
...
try
{
executor.executeCommand( "cd " + path + "; rm -rf * ");
wagon.put( zipFile, getPath( destDir, zipFile.getName() ) );
executor.executeCommand( "cd " + path + "; unzip -q -o " +
zipFile.getName() + "; rm -f " + zipFile.getName() );
zipFile.delete();
...
I have attached the version of the file which I updated and tested, and below
is what the output looks like with my simple test project.
Password for dev@localhost: XX
scp://localhost/tmp/site-deploy - Session: Opened
Executing command: mkdir -p /tmp/site-deploy/.
Executing command: cd /tmp/site-deploy/.; rm -rf *
Executing command: mkdir -p /tmp/site-deploy/.
Executing command: scp -t "/tmp/site-deploy/./wagon3163598898345372687.zip"
Uploading: ./wagon3163598898345372687.zip to scp://localhost/tmp/site-deploy
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-228) HTML code detection in license content too precise: doesn't detect EPL at http://www.eclipse.org/legal/epl-v10.html is HTML
[ https://jira.codehaus.org/browse/MPIR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-228. -- Resolution: Fixed Fix Version/s: 2.4.1 Assignee: Herve Boutemy relaxed algorithm in [r1152589|http://svn.apache.org/viewvc?rev=1152589&view=rev] > HTML code detection in license content too precise: doesn't detect EPL at > http://www.eclipse.org/legal/epl-v10.html is HTML > --- > > Key: MPIR-228 > URL: https://jira.codehaus.org/browse/MPIR-228 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: license >Affects Versions: 2.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.4.1 > > > EPL license is not detected as HTML, then included as text -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-87) Compiler errors display as INFO level messages
[ https://jira.codehaus.org/browse/MCOMPILER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274703#comment-274703 ] Robin Vobruba commented on MCOMPILER-87: i use "mvn --quiet", and if i understand the description from "mvn --help" correctly: " -q,--quiet Quiet output - only show errors" , compilation errors would still not show if they are WARNINGs, when using the --quiet switch. therefore, i would prefer them to be ERRORs, except if there is a way to make mvn output WARNING+ instead of ERROR+, like with --quiet. sorry for not having though about this earlier (when we talked in chat). > Compiler errors display as INFO level messages > -- > > Key: MCOMPILER-87 > URL: https://jira.codehaus.org/browse/MCOMPILER-87 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug > Environment: Ubuntu 8.04 64-bit, Maven version: 2.0.8, Java version: > 1.6.0_10 > OS name: "linux" version: "2.6.21.7-2.fc8xen" arch: "amd64" Family: "unix" >Reporter: Dang Nguyen >Assignee: Mark Struberg > > When a compile failure occurs, the exception(s) that causes the compile > failure is displayed as an INFO level message. Only the final message that > reads "BUILD FAILURE" is displayed as an ERROR level message. The exception > stack should also be ERROR level messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPIR-228) HTML code detection in license content too precise: doesn't detect EPL at http://www.eclipse.org/legal/epl-v10.html is HTML
HTML code detection in license content too precise: doesn't detect EPL at http://www.eclipse.org/legal/epl-v10.html is HTML --- Key: MPIR-228 URL: https://jira.codehaus.org/browse/MPIR-228 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: license Affects Versions: 2.4 Reporter: Herve Boutemy EPL license is not detected as HTML, then included as text -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-228) HTML code detection in license content too precise: doesn't detect EPL at http://www.eclipse.org/legal/epl-v10.html is HTML
[ https://jira.codehaus.org/browse/MPIR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274701#comment-274701 ] Herve Boutemy commented on MPIR-228: XML prolog in http://www.eclipse.org/legal/epl-v10.html makes the detection fail > HTML code detection in license content too precise: doesn't detect EPL at > http://www.eclipse.org/legal/epl-v10.html is HTML > --- > > Key: MPIR-228 > URL: https://jira.codehaus.org/browse/MPIR-228 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: license >Affects Versions: 2.4 >Reporter: Herve Boutemy > > EPL license is not detected as HTML, then included as text -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274696#comment-274696
]
Anthony Whitford commented on MSITE-443:
I like Sven's idea. Ultimately, I am looking for a way to say, "Use javadoc
2.8" _once_ -- this should affect both the and sections,
otherwise my pom violates the DRY principle.
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: https://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
>
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the
> {{}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{}} section doesn't use the {{}}
> section at all.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-227) add an index listing all licenses at page start
[ https://jira.codehaus.org/browse/MPIR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-227. -- Resolution: Fixed Fix Version/s: 2.4.1 patch applied with minor formatting fixes in [r1152565|http://svn.apache.org/viewvc?rev=1152565&view=rev] added an IT before in [r1152562|http://svn.apache.org/viewvc?rev=1152562&view=rev], then removed raw HTML in favour of Doxia events in [r1152571|http://svn.apache.org/viewvc?rev=1152571&view=rev] and added an introduction in [r1152572|http://svn.apache.org/viewvc?rev=1152572&view=rev] thanks for the help > add an index listing all licenses at page start > --- > > Key: MPIR-227 > URL: https://jira.codehaus.org/browse/MPIR-227 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature > Components: license >Reporter: Robin Vobruba >Assignee: Herve Boutemy >Priority: Minor > Fix For: 2.4.1 > > Attachments: addSimpleLicensesIndex.diff > > > issue: > When a project uses multiple licenses, and they are their content is rendered, > it is difficult to even notice that there are multiple ones, because one > possibly > has to scroll down multiple screens to see the start of the second one. > proposed solution: > When a project uses multiple licenses, and license rendering is not set to > linkOnly, > then render an index at the start of the page, containing links to the section > anchors of the licenses. > patch: > implements the proposed solution, though it may have to be heavily altered, > as i never wrote something for a maven (report) plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
