[jira] Commented: (CONTINUUM-621) Company logo does not appear
[ http://jira.codehaus.org/browse/CONTINUUM-621?page=comments#action_60497
]
Dan Tran commented on CONTINUUM-621:
due to security concern, firefox does not like file protocol and ignore
Company logo does not appear
Key: CONTINUUM-621
URL: http://jira.codehaus.org/browse/CONTINUUM-621
Project: Continuum
Type: Bug
Components: Web interface, Core system
Versions: 1.0.3, 1.0.2
Environment: Mozilla Firefox 1.5.0.1
Windows XP SP2
Reporter: Mang Lau
Priority: Minor
Fix For: 1.0.3
The company logo does not appear on the Continuum web interface. The logo
shows in IE but in Firefox, nothing shows up. It works if you use http
protocol but doesn't work with the file protocol. I've tried with and
without specifying the file protocol.
Snippet of page source here:
{code:html}
a href=http://www.otpp.com/;
img src=file://C:\logo.jpg alt=Ontario Teachers' Pension Plan
title=Ontario Teachers' Pension Plan border=0
/a
{code}
--
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: (MNG-2136) Active profile in profiles.xml prevents active profile in pom.xml to be triggered automatically
[ http://jira.codehaus.org/browse/MNG-2136?page=comments#action_60499 ] John Casey commented on MNG-2136: - The above example is working as designed. The activeByDefault/ element is meant to specify that this profile will be activated if no other profiles are active in the build. Therefore, specific activation of any profile will cause this one to be deactivated. The issue with using the logic that the profile should always be applied is this: 1. If it's always applied, why not put it in the POM? 2. If it's active-unless-deactivated, how do you deactivate it? Changing this feature right now might not make a huge impact on the user community, but it would break backwards compatibility in the strictest sense. Also, it requires defining some mechanism for deactivating profiles. We have one undocumented feature for this, which is: -P -jboss4x which would explicitly deactivate the jboss4x profileId, but this is not well tested, and IMO is pretty specific...I'd say that we would need something akin to: deactivation !-- stuff similar to the activation section -- /deactivation where the user can specify conditions that will deactivate the profile. Alternately, we could add an element to simply invert the activation logic...meaning the profile is active by default if this element is set, but anything triggered in the activation section will DEACTIVATE the profile... I dunno which way we should go with this, but my feeling is that it might have to wait for 2.1. Active profile in profiles.xml prevents active profile in pom.xml to be triggered automatically --- Key: MNG-2136 URL: http://jira.codehaus.org/browse/MNG-2136 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.3 Reporter: Vincent Massol Priority: Blocker Fix For: 2.0.3 If there's a profiles.xml with an active profile in it, then the active profile defined in the pom.xml is ignored and not triggered. -- 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: (MNG-2127) mvn.bat always exits 0 on Windows 2000 and higher
[ http://jira.codehaus.org/browse/MNG-2127?page=comments#action_60505 ]
Dan Fabulich commented on MNG-2127:
---
Wow... I'm definitely surprised to see that ant.bat suffers from this same
problem. Let that teach me a valuable lesson. :-)
I'm definitely surprised to hear that we don't support Win9x, because there's a
bunch of code in this batch script designed to handle Win9x, including a batch
label called :Win9xApp, which only triggers when %OS% is not equal to
Windows_NT, which is always true on Windows_NT, Windows 2000, Windows XP, and
Windows 2003. Is any of that code necessary?
Anyway, using the current latest mvn.bat from SVN (384215) helps quite a bit.
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-core/src/bin/mvn.bat?rev=384215view=markup
With that said, on line 154, it says exit /b %ERROR_CODE%. This breaks on
Windows NT... the batch script always returns 1, because that's an invalid
command on NT. Does Maven support Windows NT?
Interestingly, since the latest SVN mvn.bat uses exit /b, but includes the if
errorlevel 1 goto error fix, it works properly in Ant on Windows 2003 even
without the MAVEN_TERMINATE_CMD environment variable. Here's my test, which
works on Windows 2003, but not on Windows XP:
property name=maven.executable location=mvnfixed.bat /
exec executable=${maven.executable} failonerror=false resultproperty=x
/exec
echo message=x = ${x} /
condition property=should.have.failed
equals arg1=0 arg2=${x} /
/condition
fail if=should.have.failed message=should have failed/
exec executable=${maven.executable} failonerror=true
arg value=--help /
/exec
Anyway, I think I can live with this.
mvn.bat always exits 0 on Windows 2000 and higher
-
Key: MNG-2127
URL: http://jira.codehaus.org/browse/MNG-2127
Project: Maven 2
Type: Bug
Components: Command Line
Versions: 2.0, 2.0.1, 2.0.2
Environment: I'm on Windows 2003 Server, but this will affect any OS for
which the %OS% environment variable is Windows_NT, including Windows XP and
Windows 2000.
Reporter: Dan Fabulich
Assignee: Brett Porter
Priority: Blocker
Attachments: mvnfixed.bat, mvnfixed.bat
Write the following ant script and run it on Windows 2000 or higher:
project default=maintarget name=mainexec executable=mvn.bat
failonerror=true //target/project
This will run mvn with no arguments, which will always fail. But the ant
script will claim build successful, because the exit value of mvn.bat was
0. It is absolutely critical that this work correctly, or else I can't
integrate Maven into any other automated system.
This is happening because mvn.bat is improperly abusing local scoping. On
line 130 of mvn.bat, we execute maven, but we don't do anything with its exit
value... we just always goto end. The fix for this is to add a line 131 that
says if errorlevel 1 goto error, which will behave correctly.
(I marked this as having a test case because I've included a test ant script,
but technically this isn't a JUnit test case, so it may be an inappropriate
use of the testcase included marker.)
--
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: (MAVENUPLOAD-771) Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23
[ http://jira.codehaus.org/browse/MAVENUPLOAD-771?page=all ] Ceki Gulcu updated MAVENUPLOAD-771: --- Attachment: slf4j-log4j12-1.0-bundle.jar Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23 -- Key: MAVENUPLOAD-771 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-771 Project: maven-upload-requests Type: Task Reporter: Ceki Gulcu Attachments: jcl104-over-slf4j-1.0-bundle.jar, slf4j-jcl-1.0-bundle.jar, slf4j-jdk14-1.0-bundle.jar, slf4j-log4j12-1.0-bundle.jar, slf4j-log4j13-1.0-bundle.jar, slf4j-nop-1.0-bundle.jar, slf4j-simple-1.0-bundle.jar The SLF4J project recently released version 1.0 of the SLF4J API and NLOG4J 1.2.23. Please kindly add the attached files to ibiblio's maven 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
[jira] Updated: (MAVENUPLOAD-771) Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23
[ http://jira.codehaus.org/browse/MAVENUPLOAD-771?page=all ] Ceki Gulcu updated MAVENUPLOAD-771: --- Attachment: slf4j-simple-1.0-bundle.jar slf4j-nop-1.0-bundle.jar slf4j-log4j13-1.0-bundle.jar Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23 -- Key: MAVENUPLOAD-771 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-771 Project: maven-upload-requests Type: Task Reporter: Ceki Gulcu Attachments: jcl104-over-slf4j-1.0-bundle.jar, slf4j-jcl-1.0-bundle.jar, slf4j-jdk14-1.0-bundle.jar, slf4j-log4j12-1.0-bundle.jar, slf4j-log4j13-1.0-bundle.jar, slf4j-nop-1.0-bundle.jar, slf4j-simple-1.0-bundle.jar The SLF4J project recently released version 1.0 of the SLF4J API and NLOG4J 1.2.23. Please kindly add the attached files to ibiblio's maven 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
[jira] Commented: (MAVENUPLOAD-771) Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23
[ http://jira.codehaus.org/browse/MAVENUPLOAD-771?page=comments#action_60506 ] Ceki Gulcu commented on MAVENUPLOAD-771: As URLS: http://jira.codehaus.org/secure/attachment/19504/jcl104-over-slf4j-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19511/nlog4j-1.2.23-bundle.jar http://jira.codehaus.org/secure/attachment/19505/slf4j-jcl-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19506/slf4j-jdk14-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19507/slf4j-log4j12-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19508/slf4j-log4j13-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19509/slf4j-nop-1.0-bundle.jar http://jira.codehaus.org/secure/attachment/19510/slf4j-simple-1.0-bundle.jar Upload request for SLF4J 1.0 (final) and NLOG4J 1.2.23 -- Key: MAVENUPLOAD-771 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-771 Project: maven-upload-requests Type: Task Reporter: Ceki Gulcu Attachments: jcl104-over-slf4j-1.0-bundle.jar, nlog4j-1.2.23-bundle.jar, slf4j-jcl-1.0-bundle.jar, slf4j-jdk14-1.0-bundle.jar, slf4j-log4j12-1.0-bundle.jar, slf4j-log4j13-1.0-bundle.jar, slf4j-nop-1.0-bundle.jar, slf4j-simple-1.0-bundle.jar The SLF4J project recently released version 1.0 of the SLF4J API and NLOG4J 1.2.23. Please kindly add the attached files to ibiblio's maven 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
[jira] Created: (MPLUGIN-13) Provide Automated Documentation for a Plugin That Provides a Report
Provide Automated Documentation for a Plugin That Provides a Report --- Key: MPLUGIN-13 URL: http://jira.codehaus.org/browse/MPLUGIN-13 Project: Maven 2.x Plugin Plugin Type: Improvement Reporter: Stephen Duncan Jr Provide some automated, consistent indication and documentation that a plugin can be used in reporting. -- 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: (MASSEMBLY-1) assembly jar-with-dependencies does not utilize or provide for manifest configuration
[ http://jira.codehaus.org/browse/MASSEMBLY-1?page=all ] Brett Porter updated MASSEMBLY-1: - Fix Version: (was: 2.0.1) 2.1 assembly jar-with-dependencies does not utilize or provide for manifest configuration - Key: MASSEMBLY-1 URL: http://jira.codehaus.org/browse/MASSEMBLY-1 Project: Maven 2.x Assembly Plugin Type: Bug Environment: $ uname -a Darwin xxx 8.2.0 Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC Power Macintosh powerpc $ java -version java version 1.5.0_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-72) Java HotSpot(TM) Client VM (build 1.5.0_05-44, mixed mode, sharing) $ mvn -version Maven version: 2.0 maven-assembly-plugin version 2.0 Reporter: Michael Heuer Assignee: Brett Porter Priority: Minor Fix For: 2.1 Attachments: mng-1380-src.tar.gz Original Estimate: 1 hour Time Spent: 30 minutes Remaining: 0 minutes Date: Mon, 31 Oct 2005 17:04:21 +1100 From: Brett Porter [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Subject: Re: [m2] manifest for assembly jar-with-dependencies Yes, that's an issue with the assembly plugin. If there is no corresponding JIRA issue, please file one. - Brett On 10/28/05, Michael Heuer [EMAIL PROTECTED] wrote: Hello, I followed the guide at http://maven.apache.org/guides/mini/guide-manifest.html to add entries to my MANIFEST.MF, and that works fine with $ mvn package However, it seems that the assembly plugin does not reuse the configuration information when building the jar-with-dependencies jar, so I'm left with a default manifest in that jar. michael -- 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-30) Wrong classpath separator
[ http://jira.codehaus.org/browse/SUREFIRE-30?page=comments#action_60513 ]
Brett Porter commented on SUREFIRE-30:
--
that's what I used in the 2.0 version. As you can see, it is already marked
fixed.
Wrong classpath separator
-
Key: SUREFIRE-30
URL: http://jira.codehaus.org/browse/SUREFIRE-30
Project: surefire
Type: Bug
Versions: 1.5.2, 1.5.3
Environment: Only Windows
Reporter: Marcin Cetnarski
Assignee: Brett Porter
Fix For: 2.0
Attachments: SurefireBooter.patch
In SurefireBooter when use fork mode elements of classpath are separated by
colon. This works on Linux but not on Windows. I sugest to use semicolon.
private static ClassLoader createForkingClassLoader( String basedir )
throws Exception
{
Properties p = loadProperties( basedir, CLASSLOADER_PROPERTIES );
String cp = p.getProperty( classpath );
boolean childDelegation = true.equals( p.getProperty(
childDelegation, false ) );
List urls = Arrays.asList( cp.split( ; ) ); // was List urls =
Arrays.asList( cp.split( : ) );
return createClassLoader( urls, childDelegation );
}
and
private void getForkArgs( String batteryConfig )
throws Exception
{
.
else
{
if ( cp.length() == 0 )
cp = url;
else
cp += ; + url; // was cp += : + url;
}
--
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-2139) Maven Tasks for Ant should provide an Ant task to launch Maven
Maven Tasks for Ant should provide an Ant task to launch Maven -- Key: MNG-2139 URL: http://jira.codehaus.org/browse/MNG-2139 Project: Maven 2 Type: Wish Components: Ant tasks Versions: 2.0.3, 2.0, 2.0.1, 2.0.2 Environment: Windows makes this especially troublesome Reporter: Dan Fabulich Due to bug MNG-2127, it can be tricky to launch Maven from within Ant correctly and extract the correct exit value on all operating systems. A great solution would be to implement a maven task in the Maven Tasks for Ant. This code would be able to correctly and simply construct Maven's classpath (using the classes already baked into maven-artifact-ant-*-dep.jar) and execute arbitrary goals on arbitrary POMs. -- 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: (MNG-2139) Maven Tasks for Ant should provide an Ant task to launch Maven
[ http://jira.codehaus.org/browse/MNG-2139?page=all ] Brett Porter closed MNG-2139: - Assign To: Brett Porter Resolution: Duplicate Maven Tasks for Ant should provide an Ant task to launch Maven -- Key: MNG-2139 URL: http://jira.codehaus.org/browse/MNG-2139 Project: Maven 2 Type: Wish Components: Ant tasks Versions: 2.0.3, 2.0, 2.0.1, 2.0.2 Environment: Windows makes this especially troublesome Reporter: Dan Fabulich Assignee: Brett Porter Due to bug MNG-2127, it can be tricky to launch Maven from within Ant correctly and extract the correct exit value on all operating systems. A great solution would be to implement a maven task in the Maven Tasks for Ant. This code would be able to correctly and simply construct Maven's classpath (using the classes already baked into maven-artifact-ant-*-dep.jar) and execute arbitrary goals on arbitrary POMs. -- 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: (MJAVADOC-36) Would like a way to get default javadoc behavior
[ http://jira.codehaus.org/browse/MJAVADOC-36?page=comments#action_60526 ] Martin Desruisseaux commented on MJAVADOC-36: - Thanks for doing all this javadoc work. Would like a way to get default javadoc behavior Key: MJAVADOC-36 URL: http://jira.codehaus.org/browse/MJAVADOC-36 Project: Maven 2.x Javadoc Plugin Type: Wish Environment: Windows XP Reporter: Martin Desruisseaux Assignee: Maria Odea Ching Priority: Minor Fix For: 2.0-beta-4 Attachments: MJAVADOC-36-maven-javadoc-plugin.patch, no_default_stylesheet.diff Time Spent: 2 hours, 30 minutes Remaining: 0 minutes The javadoc plugin overrides some Sun's javadoc default options with its own default. This is quite nice for options like -bottom, since Maven has informations that Sun's javadoc doesn't have. The -package option (which default to 'true' in maven-javadoc-plugin, while the default was 'false' in Sun's javadoc) sound a little bit more surprising to me, since it lead us to a situation where we have two set of default values to keep in mind: the Sun's ones, and the Maven ones. It is not a real problem for options like -package and -use. It is a little bit more disturbing for -stylesheet, since it seems hard to tell to Maven to not use the Maven's stylesheet, but to keep the Sun's default stylesheet instead. I understand that we can provide our own stylesheet with the stylesheet parameter, but in this case I have no file to point; I would just like to keep Sun's default stylesheet. I would like a way to disable completly the -stylesheet option in the javadoc plugin. Or alternatively, the plugin may use the Maven's stylesheet only when explicitly required. -- 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: (MASSEMBLY-68) Need method to exclude all child dependencies when creating a jar
[ http://jira.codehaus.org/browse/MASSEMBLY-68?page=comments#action_60535 ] Allan Ramirez commented on MASSEMBLY-68: So it would only assemble the jars of your modules? Need method to exclude all child dependencies when creating a jar - Key: MASSEMBLY-68 URL: http://jira.codehaus.org/browse/MASSEMBLY-68 Project: Maven 2.x Assembly Plugin Type: Improvement Reporter: Dan Diephouse Fix For: 2.1 With xfire, we have 10 different modules. We want to create an xfire-all jar that has all the xfire modules bundled. We can do this with the assembly plugin right now by creating a pom with all our modules in it. However, when it includes all the child dependencies. To exclude child dependencies you have to listen them individually. XFire probably has around 50+ dependencies spread out over the build. Maintaining this exclude list would be too much work, so we'd like a way to simply say - build a jar composed of these 10 jars, but none of their deps. -- 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: (MIDEA-32) Changed Xpp3Dom in favor of dom4j
[ http://jira.codehaus.org/browse/MIDEA-32?page=all ] Brett Porter updated MIDEA-32: -- Fix Version: 2.0 Changed Xpp3Dom in favor of dom4j - Key: MIDEA-32 URL: http://jira.codehaus.org/browse/MIDEA-32 Project: Maven 2.x Idea Plugin Type: Improvement Reporter: Johann Reyes Fix For: 2.0 Attachments: MIDEA-32.patch As per @todo changed from Xpp3Dom to dom4j so it can cope properly with entities. -- 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: (MNGECLIPSE-59) Allow artifact resolution from workspace projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_60540 ] Eugene Kuleshov commented on MNGECLIPSE-59: --- The plan is to always use code from Workspace if version matches. It won't be necessary to have anything special in pom. Though I can't give you any estimate on this, because most of the work is actually in the Maven ebedder component. Allow artifact resolution from workspace projects - Key: MNGECLIPSE-59 URL: http://jira.codehaus.org/browse/MNGECLIPSE-59 Project: Maven 2.x Extension for Eclipse Type: New Feature Components: Dependency Resolver Versions: 0.0.4 Reporter: Leonardo Quijano Vincenzi Assignee: Eugene Kuleshov Fix For: 1.0.0 Provide artifact resolution from workspace projects, which override the same artifact from the local or remote repositories. This would allow to work with dependant Eclipse projects without specifying the Eclipse dependency manually. The workspace artifact resolution would have to be specified manually, since several Maven-Enabled projects in the same workspace could have the same artifact and version Id. Or at least automatic resolution with an optional override would be nice. More comments here: http://jira.codehaus.org/browse/MNGECLIPSE-58 -- 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
