[jira] Commented: (MNG-1683) type zip for packaging ?
[ http://jira.codehaus.org/browse/MNG-1683?page=comments#action_79261 ] Dan Tran commented on MNG-1683: --- Define your main artifact as pom, then use assembly:attached to create your zip. I had once atttempted to introduce a compression plugin but withdrew due to assembly can do the same work. There is no need to introduce 2 similar works. type zip for packaging ? Key: MNG-1683 URL: http://jira.codehaus.org/browse/MNG-1683 Project: Maven 2 Issue Type: Improvement Environment: not significant Reporter: Olivier Lamy Attachments: maven-war-plugin.tar.gz, maven-zip-plugin.tar.gz, MNG-1683.tar.gz Hi, I don't know if the artifact type zip exists (I think not after few test). But I want to separate the html content and the webapp content (classes, configuration files and so on). The use case is to separate this different works (html designer and java developpement) and production installation (one is to an http server and the other is on an app server) in two artifacts with separate versionning. But the packagingzip/packaging is not recognized. Then I would like to use it as an artifact with maven's features (snapshot, pom, version, goals : install, deploy release and all others). Add it to the webapp dependencies (needed only for developpment or unit tests). With this type of dependency the zip content could be unpacked to a directory in the exploded webapp. (certainly need hack on the maven-war-plugin). I have certainly the workaround to declare this as jar and using the assembly plugin to generate a zip. But I can't use install release deploy or something else to manage the generated zip which is not an artifact. Thanks for help or workaround. - Olivier -- 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-1683) type zip for packaging ?
[ http://jira.codehaus.org/browse/MNG-1683?page=comments#action_79288 ] Dan Tran commented on MNG-1683: --- then we end up with bunch life cycles to support mutliple packaking types . zip, tar, tgz, bz2, etc. :-) but it may not be a bad idea type zip for packaging ? Key: MNG-1683 URL: http://jira.codehaus.org/browse/MNG-1683 Project: Maven 2 Issue Type: Improvement Environment: not significant Reporter: Olivier Lamy Attachments: maven-war-plugin.tar.gz, maven-zip-plugin.tar.gz, MNG-1683.tar.gz Hi, I don't know if the artifact type zip exists (I think not after few test). But I want to separate the html content and the webapp content (classes, configuration files and so on). The use case is to separate this different works (html designer and java developpement) and production installation (one is to an http server and the other is on an app server) in two artifacts with separate versionning. But the packagingzip/packaging is not recognized. Then I would like to use it as an artifact with maven's features (snapshot, pom, version, goals : install, deploy release and all others). Add it to the webapp dependencies (needed only for developpment or unit tests). With this type of dependency the zip content could be unpacked to a directory in the exploded webapp. (certainly need hack on the maven-war-plugin). I have certainly the workaround to declare this as jar and using the assembly plugin to generate a zip. But I can't use install release deploy or something else to manage the generated zip which is not an artifact. Thanks for help or workaround. - Olivier -- 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-2612) antrun's exec task breaks in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2612?page=all ] Dan Tran updated MNG-2612: -- Affects Version/s: (was: 2.0.5) 2.0.4 Fix Version/s: 2.0.5 antrun's exec task breaks in 2.0.5-SNAPSHOT --- Key: MNG-2612 URL: http://jira.codehaus.org/browse/MNG-2612 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: windows Reporter: Dan Tran Fix For: 2.0.5 Attachments: pom.xml I have no problem run the below pom in 2.0.4, but in 2.0.5-SNAPSHOT. mvn package throws this [INFO] Error executing ant tasks Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn.bat --he lp error=5 Here is the pom project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.codehaus.mojo.pde/groupId artifactIdm2eclipse/artifactId version1.0-SNAPSHOT/version packagingpom/packaging nameAntRun break in 2.0.5-SNAPSHOT Build/name build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution idbuild/id phasecompile/phase goals goalrun/goal /goals configuration tasks exec executable=mvn.bat arg line=--help / /exec /tasks /configuration /execution /executions /plugin /plugins /build /project --- -- 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-2612) antrun's exec task breaks in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2612?page=comments#action_79207 ] Dan Tran commented on MNG-2612: --- Just tested with the latest 2.0.5-SNAPSHOT, the problem is no longer there But it is reproducable with the snapshot I picked up on 9/23/2006. Consider it not reproducable antrun's exec task breaks in 2.0.5-SNAPSHOT --- Key: MNG-2612 URL: http://jira.codehaus.org/browse/MNG-2612 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: windows Reporter: Dan Tran Fix For: 2.0.5 Attachments: pom.xml I have no problem run the below pom in 2.0.4, but in 2.0.5-SNAPSHOT. mvn package throws this [INFO] Error executing ant tasks Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn.bat --he lp error=5 Here is the pom project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.codehaus.mojo.pde/groupId artifactIdm2eclipse/artifactId version1.0-SNAPSHOT/version packagingpom/packaging nameAntRun break in 2.0.5-SNAPSHOT Build/name build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution idbuild/id phasecompile/phase goals goalrun/goal /goals configuration tasks exec executable=mvn.bat arg line=--help / /exec /tasks /configuration /execution /executions /plugin /plugins /build /project --- -- 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: (SCM-206) add starteam-settings.xml support
[ http://jira.codehaus.org/browse/SCM-206?page=comments#action_78650 ] Dan Tran commented on SCM-206: -- please file a JIRA for starteam doc, for now the template is starteam-settings keyvalue/key keyvalue/key ... /starteam-settings add starteam-settings.xml support - Key: SCM-206 URL: http://jira.codehaus.org/browse/SCM-206 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-starteam Affects Versions: 1.0-beta-3 Environment: XP starteam Reporter: Dan Tran Assigned To: Dan Tran Fix For: 1.0 -- 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-2612) antrun's exec task breaks in 2.0.5-SNAPSHOT
antrun's exec task breaks in 2.0.5-SNAPSHOT --- Key: MNG-2612 URL: http://jira.codehaus.org/browse/MNG-2612 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.5 Environment: windows Reporter: Dan Tran Attachments: pom.xml I have no problem run the below pom in 2.0.4, but in 2.0.5-SNAPSHOT. mvn package throws this [INFO] Error executing ant tasks Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn.bat --he lp error=5 Here is the pom project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.codehaus.mojo.pde/groupId artifactIdm2eclipse/artifactId version1.0-SNAPSHOT/version packagingpom/packaging nameAntRun break in 2.0.5-SNAPSHOT Build/name build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution idbuild/id phasecompile/phase goals goalrun/goal /goals configuration tasks exec executable=mvn.bat arg line=--help / /exec /tasks /configuration /execution /executions /plugin /plugins /build /project --- -- 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] Moved: (MWAR-80) Classifier in jar file name is removed once assembled into war file
[ http://jira.codehaus.org/browse/MWAR-80?page=all ] Dan Tran moved MPWAR-67 to MWAR-80: --- Workflow: Maven New (was: jira) Key: MWAR-80 (was: MPWAR-67) Project: Maven 2.x War Plugin (was: maven-war-plugin) Classifier in jar file name is removed once assembled into war file --- Key: MWAR-80 URL: http://jira.codehaus.org/browse/MWAR-80 Project: Maven 2.x War Plugin Issue Type: Bug Environment: Maven 2.0.4, JDK 1.5, maven-war-plugin version 2.0 Reporter: Andreas Guther We use the Maven classifier to distinguish between different jar files of the same version build for different purposes. An example would be the classifier used for TestNG to distinguish between jdk15 and jdk14 jar files. I noticed that the jar file (for example test-1.0-classifier.jar) ends up in the WEB-INF/lib folder with the classifier removed (i.e. following the example test.1.0.jar). This is unexpected and confusing. Since there is very little documentation about the expected behavior while using classifiers, it is not clear if this is intenionally or a bug. If intenionally, it should be mentioned in the maven-war-plugin documentation. Maybe in that case it would be an enhancement to configure if the classifier should be preserved or removed. However, the current behavior is undocumented and unexpected. -- 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: (MECLIPSE-34) Goals to build eclipse plugin/feature and site
[ http://jira.codehaus.org/browse/MECLIPSE-34?page=comments#action_77218 ] Dan Tran commented on MECLIPSE-34: -- I just added pde-maven-plugin to mojo-sandbox. http://mojo.codehaus.org/pde-maven-plugin If there are enough interests and feedbacks, i can make alpha-1 release. Goals to build eclipse plugin/feature and site -- Key: MECLIPSE-34 URL: http://jira.codehaus.org/browse/MECLIPSE-34 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: PDE support Affects Versions: 2.0 Reporter: Eugene Kuleshov Please provide new goals to build eclipse plugin/feature and site using Eclipse's builder. See following articles on the topic: Build and Test Automation for plug-ins and features http://eclipse.org/articles/Article-PDE-Automation/automation.html Followup article - Building features and plugins with Ant http://eclipse.techforge.com/index.php/articles/188 So, plugin can issue command like this: set ECLIPSE_HOME=D:\eclipse\eclipse-3.0.2 java -cp %ECLIPSE_HOME%\startup.jar org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner -buildfile build.xml -Dcomponent=sdk.examples -Dconfigs=*,*,* -Dbaseos=win32 -Dbasews=win32 -Dbasearch=x86 -Djavacfailonerror=true -Dpde.build.scripts=%ECLIPSE_HOME%/plugins/org.eclipse.pde.build_3.0.1/scripts -DbaseLocation=%ECLIPSE_HOME% It will sort of run ant under the hood, but nobody will see it... -- 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: (MDEP-41) Display empty space instead of null for ArtifactItem
Display empty space instead of null for ArtifactItem -- Key: MDEP-41 URL: http://jira.codehaus.org/browse/MDEP-41 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Dan Tran Priority: Trivial My build log shows this Configured Artifact: com.borland.optimizeit.agent.win32:pri:null:1.0.0-SNAPSHOT:dll where null indicates no classifier. Please make it empty. Having null in the log make viewers nervous ;-). And I have to explaining it many times already ;-) The code is in ArtifactItem:toString method. Thanks -- 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_77046 ] Dan Tran commented on MSUREFIRE-121: It is Borland's Optimizeit memory and cpu profilers ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Issue Type: Bug Affects Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch, MSUREFIRE-121.plugin.patch2, MSUREFIRE-121.plugin.patch3 I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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: (SCM-241) scm:bootstrap does not propogate --settings or -s command line option
[ http://jira.codehaus.org/browse/SCM-241?page=comments#action_76819 ] Dan Tran commented on SCM-241: -- mvn -s settings-file scm:bootstrap works at first, but internally scm:bootstrap also invoke a shell to run the goal but it does not include the settings option. Work around is to include -s settings-file to your %BUILD_GOALLS% scm:bootstrap does not propogate --settings or -s command line option - Key: SCM-241 URL: http://jira.codehaus.org/browse/SCM-241 Project: Maven SCM Issue Type: Bug Components: maven-plugin Environment: Windows XP Professional, Maven 2.0.4, mvn.bat Reporter: L Northrop Priority: Minor Local override of settings file using either -s or --settings option on the DOS command line is not propogated to build. For example mvn --settings my_settings.xml scm:bootstrap -DcheckoutDirectory=%WKDIR% -DworkingDirectory=%WKDIR% -DconnectionUrl=scm:cvs:pserver:%CVS_USERNAME%:@%CVS_SERVER%:%CVS_ROOT%:%CVS_MODULE% -Dgoals=%BUILD_GOALS% -Dtag=%CVS_BRANCH% Following scm:bootstrap checkout the subsequent build is not picking up the settings from the specified settings file. -- 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: (MRELEASE-169) Provide a mechanism to undo the effects of prepare
[ http://jira.codehaus.org/browse/MRELEASE-169?page=comments#action_76752 ] Dan Tran commented on MRELEASE-169: --- One more usecase for this enhancement: I have about 70 modules to change from 1.0-beta-3-SNAPSHOT to 1.0-RC-1-SNAPSHOT since I'd like to skip beta-3 -Dan Provide a mechanism to undo the effects of prepare -- Key: MRELEASE-169 URL: http://jira.codehaus.org/browse/MRELEASE-169 Project: Maven 2.x Release Plugin Issue Type: New Feature Affects Versions: 2.0-beta-4 Environment: XP Reporter: David Hoffer Sometimes you don't know if your prepare will work until you try it. In these cases the dryRun option does not find the failures, examples are bad paths in the scm section. It would be nice if the release plugin could undo the changes that the prepare action caused. Currently, in a multi-module project there are a lot of files to manually fix if this happens. -- 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: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_76399 ] Dan Tran commented on MRELEASE-3: - John, Do you have any progress on this JIRA? I have a scenario where I need to do a release:prepare without the availablity of the snapshots. Let me know what I can do to help. release:prepare should not require multimodule artifacts to be in the local repository -- Key: MRELEASE-3 URL: http://jira.codehaus.org/browse/MRELEASE-3 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: John Casey Fix For: 2.0 Currently, if you try to run release:prepare on a multimodule project after removing any of that build's artifacts from the local repository, it will fail. Investigate why release:prepare needs the multimodule artifacts installed in the local repository before it can succeed. To reproduce, comment the following line in it2002/test.sh: mvn clean install NOTE: This may have to do with the version resolution code, which is used to resolve SNAPSHOT versions. -- 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: (MDEP-40) use Lowercase alpha
use Lowercase alpha - Key: MDEP-40 URL: http://jira.codehaus.org/browse/MDEP-40 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-ALPHA1 Environment: xp, unix Reporter: Dan Tran By convention, we use lower case. see http://svn.apache.org/viewvc/maven/plugins/tags/ -- 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: (SCM-241) scm:bootstrap does not propogate --settings or -s command line option
[ http://jira.codehaus.org/browse/SCM-241?page=comments#action_76328 ] Dan Tran commented on SCM-241: -- what kind of settings are you expecting scm:bootstrap to pickup? scm:bootstrap does not propogate --settings or -s command line option - Key: SCM-241 URL: http://jira.codehaus.org/browse/SCM-241 Project: Maven SCM Issue Type: Bug Components: maven-plugin Environment: Windows XP Professional, Maven 2.0.4, mvn.bat Reporter: L Northrop Priority: Minor Local override of settings file using either -s or --settings option on the DOS command line is not propogated to build. For example mvn --settings my_settings.xml scm:bootstrap -DcheckoutDirectory=%WKDIR% -DworkingDirectory=%WKDIR% -DconnectionUrl=scm:cvs:pserver:%CVS_USERNAME%:@%CVS_SERVER%:%CVS_ROOT%:%CVS_MODULE% -Dgoals=%BUILD_GOALS% -Dtag=%CVS_BRANCH% Following scm:bootstrap checkout the subsequent build is not picking up the settings from the specified settings file. -- 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: (MDEP-31) ERROR: Cannot override read-only parameter: scope in goal: dependency:copy-dependencies
[ http://jira.codehaus.org/browse/MDEP-31?page=comments#action_74298 ]
Dan Tran commented on MDEP-31:
--
Just deploy another snapshot, please do mvn -U to get the latest one.
-Dan
ERROR: Cannot override read-only parameter: scope in goal:
dependency:copy-dependencies
Key: MDEP-31
URL: http://jira.codehaus.org/browse/MDEP-31
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Reporter: David J. M. Karlsen
Assigned To: John Casey
Fix For: 1.1
Attachments: AbstractDependencyFilterMojo-MDEP-31.java
http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
states that scope is a valid (and writable) configuration element, but the
following configuration:
plugins
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0-SNAPSHOT/version
executions
execution
idcopy-dependencies/id
phasepackage/phase
goals
goalcopy-dependencies/goal
/goals
configuration
excludeTransitivetrue/excludeTransitive
scopecompile/scope
/configuration
/execution
/executions
/plugin
/plugins
will fail with:
[snip...]
Building index for all classes...
Generating
C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\allclasses-frame.html...
Generating
C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\allclasses-noframe.html...
Generating
C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\index.html...
Generating
C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\help-doc.html...
Generating
C:/dnbnorapi/kildekode/utvikling/dnbnorapi-client/target/site/apidocs\stylesheet.css...
[INFO] Building jar:
C:\dnbnorapi\kildekode\utvikling\dnbnorapi-client\target\dnbnorapi-client-1.0-SNAPSHOT-javadoc.jar
[INFO] [jar:test-jar {execution: default}]
[INFO] Building jar:
C:\dnbnorapi\kildekode\utvikling\dnbnorapi-client\target\dnbnorapi-client-1.0-SNAPSHOT-tests.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error configuring: org.apache.maven.plugins:maven-dependency-plugin.
Reason: ERROR: Cannot override read-only par
ameter: scope in goal: dependency:copy-dependencies
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 3 seconds
[INFO] Finished at: Wed Aug 02 13:09:21 CEST 2006
[INFO] Final Memory: 13M/27M
[INFO]
--
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: (MECLIPSE-127) Ability to add other workspace configuration similar to add-maven-repo goal
Ability to add other workspace configuration similar to add-maven-repo goal --- Key: MECLIPSE-127 URL: http://jira.codehaus.org/browse/MECLIPSE-127 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Affects Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 add ability to configure code slyle, jvm, warning,etc We can create a new goal like eclipse:configure-workspace and merge add-maven-repo into it. We will need to a complex class for injection. This complex class will have the following property String workspaceDirectory; // if given, will trigger add-maven-repo String styleFile; // if given, will trigger the settup of source format style file etc, This will allow us to preconfigure eclispe configuration in the parent pom, and there for developers in a team will have the same eclipse setup, rather manually configure it. WDYT? -- 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: (MEV-424) missing plexus-tools-1.0.5
missing plexus-tools-1.0.5 -- Key: MEV-424 URL: http://jira.codehaus.org/browse/MEV-424 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Dan Tran this is required to build maven-repository-manager -- 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: (MSITE-152) NPE in plugin site when a mojo has no configuration injection
NPE in plugin site when a mojo has no configuration injection - Key: MSITE-152 URL: http://jira.codehaus.org/browse/MSITE-152 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-5 Environment: xp Reporter: Dan Tran Fix For: 2.0 Attachments: site.log When a plugin has a mojo with no configuration injection like the one at https://svn.codehaus.org/mojo/tags/maven-native-1.0-alpha-1/native-maven-plugin/src/main/java/org/codehaus/mojo/natives/plugin/NativeInitializeMojo.java mvn site throws NPE. See attached log -- 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-118) assembly files uses maven parent relative path and not the modules relative path
[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_67776
]
Dan Tran commented on MASSEMBLY-118:
I am not sure if the fix in MASSEMBLY-100 solves your issue regarding having
spaces in the path thou
Best way is to fetch the source and test it your self
-D
assembly files uses maven parent relative path and not the modules relative
path
--
Key: MASSEMBLY-118
URL: http://jira.codehaus.org/browse/MASSEMBLY-118
Project: Maven 2.x Assembly Plugin
Type: Bug
Reporter: Baerrach bonDierne
Priority: Critical
Attachments: Maven Assembly Bug.zip
In mvn 2.0.4 if I have an assemly descriptor that has the following:
files
file
sourcesrc/site/apt/index.apt/source
outputDirectory/outputDirectory
destNameREADME.txt/destName
/file
/files
and a maven project that looks like:
Maven Assembly Bug
- pom.xml
- assembly-bug-module
- pom.xml
- src/site/apt/index.apt
with the assembly:assembly bound to the package phase inside
assembly-bug-module/pom.xml as
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
idpackage-assembly/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
descriptors
descriptor
src/main/assembly/bin.xml
/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
then when I run mvn install inside assembly-bug-module:
assembly-bug-module mvn install
the command works fine
When I run mvn install inside the Maven Assembly Bug directory the command
will fail
Maven Assembly Bug mvn install
[INFO] [assembly:assembly {execution: package-assembly}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error adding file to archive: path\Maven Assembly
Bug\src\site\apt\index.apt isn't a file.
Example project is attached as a zip file.
Trying to change the descriptor to use ${project.build.sourceDirectory} does
not work as this is not resoolved.
[INFO] Error adding file to archive: path\Maven Assembly
Bug\assembly-bug-module\${project.build.sourceDirectory}
\site\apt\index.apt isn't a file.
--
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-118) assembly files uses maven parent relative path and not the modules relative path
[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_67783
]
Dan Tran commented on MASSEMBLY-118:
sorry about the quick judgement, i thought you have spaces in your parent
directory name.
does ASSEMBLY-100 fixes your issues?
assembly files uses maven parent relative path and not the modules relative
path
--
Key: MASSEMBLY-118
URL: http://jira.codehaus.org/browse/MASSEMBLY-118
Project: Maven 2.x Assembly Plugin
Type: Bug
Reporter: Baerrach bonDierne
Priority: Critical
Attachments: Maven Assembly Bug.zip
In mvn 2.0.4 if I have an assemly descriptor that has the following:
files
file
sourcesrc/site/apt/index.apt/source
outputDirectory/outputDirectory
destNameREADME.txt/destName
/file
/files
and a maven project that looks like:
Maven Assembly Bug
- pom.xml
- assembly-bug-module
- pom.xml
- src/site/apt/index.apt
with the assembly:assembly bound to the package phase inside
assembly-bug-module/pom.xml as
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
idpackage-assembly/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
descriptors
descriptor
src/main/assembly/bin.xml
/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
then when I run mvn install inside assembly-bug-module:
assembly-bug-module mvn install
the command works fine
When I run mvn install inside the Maven Assembly Bug directory the command
will fail
Maven Assembly Bug mvn install
[INFO] [assembly:assembly {execution: package-assembly}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error adding file to archive: path\Maven Assembly
Bug\src\site\apt\index.apt isn't a file.
Example project is attached as a zip file.
Trying to change the descriptor to use ${project.build.sourceDirectory} does
not work as this is not resoolved.
[INFO] Error adding file to archive: path\Maven Assembly
Bug\assembly-bug-module\${project.build.sourceDirectory}
\site\apt\index.apt isn't a file.
--
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: (MSUREFIRE-133) Working directory is not setup correctly when running a unit test in the child subproject if run from the parent's directory
[ http://jira.codehaus.org/browse/MSUREFIRE-133?page=comments#action_67110 ] Dan Tran commented on MSUREFIRE-133: Please try maven-surefire-plugin-2.2. There are lots of bug fixes since 2.13-SNAPShOT Working directory is not setup correctly when running a unit test in the child subproject if run from the parent's directory Key: MSUREFIRE-133 URL: http://jira.codehaus.org/browse/MSUREFIRE-133 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.3 Environment: Windows XP with cygwin or Ubuntu Linux or MacOSX 10.4.6 Java 1.5, maven 2.0.4 Reporter: toli kuznets Attachments: pathBug.tar Current working directory is not setup correctly when you run all the unit tests of the child module from the parent directory. Create a maven parent project that only contains a child subproject with one unit test, which tries to open/create a file in the relative subdirectory of the current directory. When you run the test directly from the pathBugh/subproject/ directory, then the test passes just fine. If you run the test from the parent project directory, the test fails (cur. working directory is not setup correctly). If, however, the target directory already exists in child module, then everything works. Reproduction: 1. open the tarball 2. run 'mvn test' from the parent directory - unit test will fail 3. you can run 'mvn test' from child project it should pass. remember to delete the output directories after you successfully run the test in the child subdir. I've noticed that this bug only happens when the releases of Maven plugins is enabled in the parent POM (see the parent POM file for the truth table of what's necessary to get the test to fail). so it may be a failure that only happens in current plugin version. there's a mvn.out file in the attached tarball that has the debug information (-X) for the output of the maven test run. This only happens under maven. When you run the same unit test with ant or IntelliJ it works fine. See the attached tarball. note: the actual error may be in any other maven plugin, but i have a feeling it's in the surefire/unit test setup. -- 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: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=comments#action_66457 ] Dan Tran commented on MSUREFIRE-49: --- note that, insert any thing into environmentVariables breaks the invocation of jvm ( ie java ). It seems that cli processing of environment variables corrupt the system path environmentVariables does not work with windows --- Key: MSUREFIRE-49 URL: http://jira.codehaus.org/browse/MSUREFIRE-49 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: windows Reporter: Dan Tran Fix For: 2.1.3 Attachments: MSUREFIRE-49.log MSUREFIRE-44 added environmentVariables fields to all additional environment variables to be added to when forking the test It works on UNIX but not windows. Suspect it is platform specific problem for windows in plexus-util's cli library Here is the plugin configuration to reproduce the problem plugin artifactIdmaven-surefire-plugin/artifactId configuration environmentVariables keyvalue/key /environmentVariables forkModeonce/forkMode /configuration /plugin and the stack trace is [[DEBUG] Adding to surefire test classpath: c:\dev\maven\maven-2.0.2\core\plexus- utils-1.1.jar Environment: key=value added. java -classpath C:\Documents and Settings\dtran\.m2\repository\org\apache\maven \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar org.apache.maven.surefire.Surefi reBooter C:\dev\maven\src\surefire\surefire [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: There are some test fail ure. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) 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.plugin.MojoExecutionException: There are some test f ailure. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:531) ... 16 more [INFO] - --- [INFO] Total time: 4 seconds [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 [INFO] Final Memory: 3M/6M [INFO] - --- -- 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: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=comments#action_66487 ]
Dan Tran commented on MSUREFIRE-49:
---
a few more findings:
1. the work around is to explicitly set jvm param to ${java.home}/bin/java
2. environmentVariables does get set correctly in plexus' commandline and it
works
commandline with env settings are known to work since I use it
intensively in native-maven-plugin
So the root cause this issue lies some where in the surefire plugin itself, not
plexus
environmentVariables does not work with windows
---
Key: MSUREFIRE-49
URL: http://jira.codehaus.org/browse/MSUREFIRE-49
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.1.2
Environment: windows
Reporter: Dan Tran
Fix For: 2.1.3
Attachments: MSUREFIRE-49.log
MSUREFIRE-44 added environmentVariables fields to all additional environment
variables to be added to when forking the test
It works on UNIX but not windows. Suspect it is platform specific problem
for windows in plexus-util's cli library
Here is the plugin configuration to reproduce the problem
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
environmentVariables
keyvalue/key
/environmentVariables
forkModeonce/forkMode
/configuration
/plugin
and the stack trace is
[[DEBUG] Adding to surefire test classpath:
c:\dev\maven\maven-2.0.2\core\plexus-
utils-1.1.jar
Environment: key=value added.
java -classpath C:\Documents and
Settings\dtran\.m2\repository\org\apache\maven
\surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d
ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar
org.apache.maven.surefire.Surefi
reBooter C:\dev\maven\src\surefire\surefire
[INFO]
-
---
[ERROR] BUILD ERROR
[INFO]
-
---
[INFO] There are some test failure.
[INFO]
-
---
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: There are some test
fail
ure.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
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.plugin.MojoExecutionException: There are some
test f
ailure.
at
org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:531)
... 16 more
[INFO]
-
---
[INFO] Total time: 4 seconds
[INFO] Finished at: Sat Jan 21 10:18:59 PST 2006
[INFO] Final Memory: 3M/6M
[INFO]
-
---
--
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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=all ] Dan Tran updated MSUREFIRE-121: --- Attachment: MSUREFIRE-121.plugin.patch2 ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch, MSUREFIRE-121.plugin.patch2 I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=all ] Dan Tran updated MSUREFIRE-121: --- Attachment: MSUREFIRE-121.plugin.patch3 ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch, MSUREFIRE-121.plugin.patch2, MSUREFIRE-121.plugin.patch3 I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=all ] Dan Tran reopened MSUREFIRE-49: --- reproducable on windows. see attached log for detail [INFO] [surefire:test] [INFO] Surefire report directory: C:\dev\opti\dev\agent\it\pri\target\surefire-r eports 'java' is not recognized as an internal or external command, operable program or batch file. environmentVariables does not work with windows --- Key: MSUREFIRE-49 URL: http://jira.codehaus.org/browse/MSUREFIRE-49 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: windows Reporter: Dan Tran Fix For: 2.1.3 MSUREFIRE-44 added environmentVariables fields to all additional environment variables to be added to when forking the test It works on UNIX but not windows. Suspect it is platform specific problem for windows in plexus-util's cli library Here is the plugin configuration to reproduce the problem plugin artifactIdmaven-surefire-plugin/artifactId configuration environmentVariables keyvalue/key /environmentVariables forkModeonce/forkMode /configuration /plugin and the stack trace is [[DEBUG] Adding to surefire test classpath: c:\dev\maven\maven-2.0.2\core\plexus- utils-1.1.jar Environment: key=value added. java -classpath C:\Documents and Settings\dtran\.m2\repository\org\apache\maven \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar org.apache.maven.surefire.Surefi reBooter C:\dev\maven\src\surefire\surefire [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: There are some test fail ure. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) 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.plugin.MojoExecutionException: There are some test f ailure. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:531) ... 16 more [INFO] - --- [INFO] Total time: 4 seconds [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 [INFO] Final Memory: 3M/6M [INFO] - --- -- 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: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=all ] Dan Tran updated MSUREFIRE-49: -- Attachment: MSUREFIRE-49.log environmentVariables does not work with windows --- Key: MSUREFIRE-49 URL: http://jira.codehaus.org/browse/MSUREFIRE-49 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: windows Reporter: Dan Tran Fix For: 2.1.3 Attachments: MSUREFIRE-49.log MSUREFIRE-44 added environmentVariables fields to all additional environment variables to be added to when forking the test It works on UNIX but not windows. Suspect it is platform specific problem for windows in plexus-util's cli library Here is the plugin configuration to reproduce the problem plugin artifactIdmaven-surefire-plugin/artifactId configuration environmentVariables keyvalue/key /environmentVariables forkModeonce/forkMode /configuration /plugin and the stack trace is [[DEBUG] Adding to surefire test classpath: c:\dev\maven\maven-2.0.2\core\plexus- utils-1.1.jar Environment: key=value added. java -classpath C:\Documents and Settings\dtran\.m2\repository\org\apache\maven \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar org.apache.maven.surefire.Surefi reBooter C:\dev\maven\src\surefire\surefire [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: There are some test fail ure. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) 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.plugin.MojoExecutionException: There are some test f ailure. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:531) ... 16 more [INFO] - --- [INFO] Total time: 4 seconds [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 [INFO] Final Memory: 3M/6M [INFO] - --- -- 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66192
]
Dan Tran commented on MSUREFIRE-121:
Ok, let me try to rephase in details so see it makes sense.
In my fork mode sample configuration, myboot.jar must be loaded via
-Xbootclasspath/p:myboot.jar command line.
myboot.jar then references, at boot time, some other classes in my project
dependency and FAILS since my dependendencies
are not loaded yet. They are loaded only after the JVM is fully constructed (
see SureFireBooter's main method ).
The solution is to place my dependencies as part of java.exe 's -classpath
list which currently contain only the sure-fire's plugin dependencies
(ie surefire-api, surefire-booter, etc)
here is my jvm command line example
java.exe -Xrunpri:${basedir}/src/test/resources/optimizeit.xml
-Xbootclasspath/p:myboot.jar -classpath mydependencies ...
ability to add dependency to jvm's classpath rather in surefirebooter
classloader
-
Key: MSUREFIRE-121
URL: http://jira.codehaus.org/browse/MSUREFIRE-121
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.2
Environment: xp
Reporter: Dan Tran
Fix For: 2.3
Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch
I have a usecase where i have a jar file got loaded by -Xbootclasspath, that
jar file then loads classes from another jar ( my dependency)
expected in the classpath.
The problem is that surefire plugin does not add my dependencies at JVM
commanline thru -classpath option, but after the JVM starts
--
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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66205 ] Dan Tran commented on MSUREFIRE-121: Yes, classes in the bootstrap classloader really load stuff from the system classpath I am fine with the idea of allowing only a set of selected artifacts to add, it is a better solution to minimize the problem of long command line ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=comments#action_66070
]
Dan Tran commented on MSUREFIRE-121:
I am after placing the project dedendencies on the -classpath list of the fork
command
My surefire plugin would look like this
dependendcies
!-- need this on JVM -classpath list --
/dependencies
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModeonce/forkMode
workingDirectory${project.build.directory}/workingDirectory
argLine-Xrunpri:${basedir}/src/test/resources/optimizeit.xml
-Xbootclasspath/p:myboot.jar/argLine
allowClasspathElementsOnCommandlinetrue/allowClasspathElementsOnCommandline
/configuration
/plugin
myboot.jar after booting up needs to reference some other class in my project
dependencies expected on -classpath
ability to add dependency to jvm's classpath rather in surefirebooter
classloader
-
Key: MSUREFIRE-121
URL: http://jira.codehaus.org/browse/MSUREFIRE-121
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.2
Environment: xp
Reporter: Dan Tran
Fix For: 2.3
Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch
I have a usecase where i have a jar file got loaded by -Xbootclasspath, that
jar file then loads classes from another jar ( my dependency)
expected in the classpath.
The problem is that surefire plugin does not add my dependencies at JVM
commanline thru -classpath option, but after the JVM starts
--
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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/MSUREFIRE-121?page=all ] Dan Tran updated MSUREFIRE-121: --- Attachment: MSUREFIRE-121-booter.patch MSUREFIRE-121.plugin.patch ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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-107) DependencySet does not support classifier
DependencySet does not support classifier -- Key: MASSEMBLY-107 URL: http://jira.codehaus.org/browse/MASSEMBLY-107 Project: Maven 2.x Assembly Plugin Type: Bug Versions: 2.1 Environment: xp Reporter: Dan Tran dependencySet outputDirectory/outputDirectory unpacktrue/unpack includes includesomeGroupId:someArtifactid:someClassifier/include /includes /dependencySet Currently the depedencySetProcessing does not expect to handle classifier -- 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: (MSUREFIRE-121) ability to add dependency to jvm's classpath rather in surefirebooter classloader
ability to add dependency to jvm's classpath rather in surefirebooter classloader - Key: MSUREFIRE-121 URL: http://jira.codehaus.org/browse/MSUREFIRE-121 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.2 Environment: xp Reporter: Dan Tran Fix For: 2.3 I have a usecase where i have a jar file got loaded by -Xbootclasspath, that jar file then loads classes from another jar ( my dependency) expected in the classpath. The problem is that surefire plugin does not add my dependencies at JVM commanline thru -classpath option, but after the JVM starts -- 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: (SCM-203) The SCM starteam provider issue parameter
[ http://jira.codehaus.org/browse/SCM-203?page=comments#action_65577 ] Dan Tran commented on SCM-203: -- Emmanuel, we surely need a page discussing hidden properties/features in starteam provider, I will crank one up The SCM starteam provider issue parameter - Key: SCM-203 URL: http://jira.codehaus.org/browse/SCM-203 Project: Maven SCM Type: Improvement Components: maven-scm-provider-starteam Versions: 1.0-beta-3 Reporter: Antonio D'Errico Attachments: SCM-203.patch On starteam you can specify the issue to checkin the file. So the provider now have two hidden properties: - maven.scm.issue.type with admissible values cr, task, req, active to specify the issue type for checkin - maven.scm.issue.value that contains the complete path from the root folder of the StarTeam project view to the item if the issue.type is active this properties should have no value, and is ignored -- 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: (SCM-203) The SCM starteam provider issue parameter
[ http://jira.codehaus.org/browse/SCM-203?page=all ] Dan Tran closed SCM-203: Assign To: Dan Tran Resolution: Fixed Fix Version: 1.0 Applied the patch with some changes to generalize the issue types checkin handling + one more unit test. Thanks Antonio The SCM starteam provider issue parameter - Key: SCM-203 URL: http://jira.codehaus.org/browse/SCM-203 Project: Maven SCM Type: Improvement Components: maven-scm-provider-starteam Versions: 1.0-beta-3 Reporter: Antonio D'Errico Assignee: Dan Tran Fix For: 1.0 Attachments: SCM-203.patch On starteam you can specify the issue to checkin the file. So the provider now have two hidden properties: - maven.scm.issue.type with admissible values cr, task, req, active to specify the issue type for checkin - maven.scm.issue.value that contains the complete path from the root folder of the StarTeam project view to the item if the issue.type is active this properties should have no value, and is ignored -- 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: (SCM-204) Document Stateam provider hidden properties
Document Stateam provider hidden properties --- Key: SCM-204 URL: http://jira.codehaus.org/browse/SCM-204 Project: Maven SCM Type: Bug Components: documentation Versions: 1.0 Environment: xp starteam Reporter: Dan Tran -- 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: (SCM-205) Bad links in maven-scm-plugin site which refer back to scm root site
Bad links in maven-scm-plugin site which refer back to scm root site Key: SCM-205 URL: http://jira.codehaus.org/browse/SCM-205 Project: Maven SCM Type: Bug Components: maven-scm-site Reporter: Dan Tran -- 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: (SCM-204) Document Stateam provider hidden properties
[ http://jira.codehaus.org/browse/SCM-204?page=all ] Dan Tran closed SCM-204: Resolution: Fixed Fix Version: 1.0 added a new section in starteam.apt Document Stateam provider hidden properties --- Key: SCM-204 URL: http://jira.codehaus.org/browse/SCM-204 Project: Maven SCM Type: Bug Components: documentation Versions: 1.0 Environment: xp starteam Reporter: Dan Tran Assignee: Dan Tran Fix For: 1.0 -- 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: (SCM-206) add starteam-settings.xml support
[ http://jira.codehaus.org/browse/SCM-206?page=all ] Dan Tran closed SCM-206: Assign To: Dan Tran Resolution: Fixed Fix Version: 1.0 added, compession flag is moved form system properties to this settings. No backward compatibility issue here since we never publish compression feature yet. add starteam-settings.xml support - Key: SCM-206 URL: http://jira.codehaus.org/browse/SCM-206 Project: Maven SCM Type: New Feature Components: maven-scm-provider-starteam Versions: 1.0-beta-3 Environment: XP starteam Reporter: Dan Tran Assignee: Dan Tran Fix For: 1.0 -- 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-100) FileList processing fails in reactor build
[ http://jira.codehaus.org/browse/MASSEMBLY-100?page=all ]
Dan Tran updated MASSEMBLY-100:
---
Priority: Major (was: Blocker)
Description:
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou.
the work around is to prepend ${basedir} to the source in the descriptor. So
the fix for this issue must take care the scenario the case where user already
prepend $basedir in the assembly
was:
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou
Summary: FileList processing fails in reactor build (was: FileList
processing fail in reactor build)
FileList processing fails in reactor build
--
Key: MASSEMBLY-100
URL: http://jira.codehaus.org/browse/MASSEMBLY-100
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou.
the work around is to prepend ${basedir} to the source in the descriptor. So
the fix for this issue must take care the scenario the case where user
already prepend $basedir in the assembly
--
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-100) FileList processing fails in reactor build
[ http://jira.codehaus.org/browse/MASSEMBLY-100?page=comments#action_65523
]
Dan Tran commented on MASSEMBLY-100:
fixed
FileList processing fails in reactor build
--
Key: MASSEMBLY-100
URL: http://jira.codehaus.org/browse/MASSEMBLY-100
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Assignee: Dan Tran
Fix For: 2.2
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou.
the work around is to prepend ${basedir} to the source in the descriptor. So
the fix for this issue must take care the scenario the case where user
already prepend $basedir in the assembly
--
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-100) FileList processing fails in reactor build
[ http://jira.codehaus.org/browse/MASSEMBLY-100?page=all ]
Dan Tran updated MASSEMBLY-100:
---
Fix Version: 2.2
FileList processing fails in reactor build
--
Key: MASSEMBLY-100
URL: http://jira.codehaus.org/browse/MASSEMBLY-100
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Assignee: Dan Tran
Fix For: 2.2
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou.
the work around is to prepend ${basedir} to the source in the descriptor. So
the fix for this issue must take care the scenario the case where user
already prepend $basedir in the assembly
--
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-100) FileList processing fail in reactor build
FileList processing fail in reactor build
-
Key: MASSEMBLY-100
URL: http://jira.codehaus.org/browse/MASSEMBLY-100
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Priority: Blocker
${basedir} need to prepend to source file in the assembly, otherwise plexus
archiver will throw exception not able to locale the file.
This is not regression bug thou
--
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: (DOXIA-61) site-renderrer-alpha-8.pom contains respository
site-renderrer-alpha-8.pom contains respository Key: DOXIA-61 URL: http://jira.codehaus.org/browse/DOXIA-61 Project: doxia Type: Bug Components: Site Renderer Versions: 1.0-alpha-8 Environment: xp Reporter: Dan Tran Fix For: 1.0 Site renderer (alpha-8) 's pom.xml contains repository pointing to codehaus' snapshot. and mvn will attemp the fetch renderrer's parent pom from codehaus. -- 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: (SCM-201) Option to ignore checkout when checkoutDirectory exists
[ http://jira.codehaus.org/browse/SCM-201?page=all ] Dan Tran closed SCM-201: Assign To: Dan Tran Resolution: Fixed Fix Version: 1.0 fixed Option to ignore checkout when checkoutDirectory exists --- Key: SCM-201 URL: http://jira.codehaus.org/browse/SCM-201 Project: Maven SCM Type: New Feature Components: maven-plugin Versions: 1.0-beta-3 Environment: xp, starteam Reporter: Dan Tran Assignee: Dan Tran Fix For: 1.0 I have a need to pull mulitple legacy source trees from various scm:url into my local directory and invoke antrun to work on those trees. So I use multiple executions of maven-scm-plugin:checkout to fetch the source at initialize phase, then invoke antrun to do the rest. The annoy thing for every build is that scm:checkout remove my source tree and then fetch the source. This is the behavior we want for normal case. However for my case the checkout is a lengthy process. I would like to propose a new optiontion param skipCheckoutIfExists, with default to false to checkout mojo. WDYT? skipCheckoutIfExists name sound acceptable? -- 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: (SCM-201) Option to ignore checkout when checkoutDirectory exists
[ http://jira.codehaus.org/browse/SCM-201?page=comments#action_65346 ] Dan Tran commented on SCM-201: -- I rather not using a script to do that since maven can do that as well ( just almost there) I have multiple of this type of projects to be used solely for legacy to maven2 transitions. Option to ignore checkout when checkoutDirectory exists --- Key: SCM-201 URL: http://jira.codehaus.org/browse/SCM-201 Project: Maven SCM Type: New Feature Components: maven-plugin Versions: 1.0-beta-3 Environment: xp, starteam Reporter: Dan Tran I have a need to pull mulitple legacy source trees from various scm:url into my local directory and invoke antrun to work on those trees. So I use multiple executions of maven-scm-plugin:checkout to fetch the source at initialize phase, then invoke antrun to do the rest. The annoy thing for every build is that scm:checkout remove my source tree and then fetch the source. This is the behavior we want for normal case. However for my case the checkout is a lengthy process. I would like to propose a new optiontion param skipCheckoutIfExists, with default to false to checkout mojo. WDYT? skipCheckoutIfExists name sound acceptable? -- 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: (SCM-201) Option to ignore checkout when checkoutDirectory exists
Option to ignore checkout when checkoutDirectory exists --- Key: SCM-201 URL: http://jira.codehaus.org/browse/SCM-201 Project: Maven SCM Type: New Feature Components: maven-plugin Versions: 1.0-beta-3 Environment: xp, starteam Reporter: Dan Tran I have a need to pull mulitple legacy source trees from various scm:url into my local directory and invoke antrun to work on those trees. So I use multiple executions of maven-scm-plugin:checkout to fetch the source at initialize phase, then invoke antrun to do the rest. The annoy thing for every build is that scm:checkout remove my source tree and then fetch the source. This is the behavior we want for normal case. However for my case the checkout is a lengthy process. I would like to propose a new optiontion param skipCheckoutIfExists, with default to false to checkout mojo. WDYT? skipCheckoutIfExists name sound acceptable? -- 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: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build
[ http://jira.codehaus.org/browse/MDEP-2?page=comments#action_65204 ] Dan Tran commented on MDEP-2: - Kenney, i think you patch it to the wrong place. the plugin has been moved to maven-dependency-plugin at Apache Sibling Dependency Not Included in copy-dependencies output during multi-project build -- Key: MDEP-2 URL: http://jira.codehaus.org/browse/MDEP-2 Project: Maven 2.x Dependency Plugin Type: Bug Reporter: Stephen Duncan Jr Assignee: Kenney Westerhof Fix For: 1.1 Attachments: dependency-test.zip Using the following structure dependency-test - module1 - module2 I have the dependency-maven-plugin:copy-dependencies goal attached the package phase of the module2 module. module2 has a dependency on module1. When I run mvn package from the module2 folder, it correctly includes the module1 jar in the target/dependency folder. When I run mvn package from the dependency-test folder, the module1 jar is not included in the impl/target/dependency folder. A simple example of the problem is attached. -- 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: (SCM-117) Add parameters to scm configuration element
[ http://jira.codehaus.org/browse/SCM-117?page=comments#action_65038 ] Dan Tran commented on SCM-117: -- maven-scm-provider-starteam has a hidden system property that allow you to issue -cr path during checking 1. Create a CR using your starteam 2. pass -Dmaven.scm.issue=path to your CR Would this work? Add parameters to scm configuration element --- Key: SCM-117 URL: http://jira.codehaus.org/browse/SCM-117 Project: Maven SCM Type: Wish Components: maven-scm-provider-starteam Versions: 1.0-beta-2 Reporter: Aviran Mordo Assignee: Dan Tran It would be very nice to have the ability to add parameters to the scm element. For instance to add parameter to always force checkout. for instance in Starteam I would like to add -o so every time stcmd is called the parameters will be concatenated to the command line -- 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: (MASSEMBLY-95) Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers
[ http://jira.codehaus.org/browse/MASSEMBLY-95?page=all ] Dan Tran closed MASSEMBLY-95: - Assign To: Dan Tran Resolution: Fixed Fix Version: 2.1 fixed. Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers - Key: MASSEMBLY-95 URL: http://jira.codehaus.org/browse/MASSEMBLY-95 Project: Maven 2.x Assembly Plugin Type: New Feature Versions: 2.1 Environment: xp Reporter: Dan Tran Assignee: Dan Tran Fix For: 2.1 I submitted PLX-216's patch to support this issue. Once PLX-216 is committed, i will send in the patch for this issue -- 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: (MDEP-4) Add support of unpack types tar.gz, tgz
[ http://jira.codehaus.org/browse/MDEP-4?page=all ] Dan Tran closed MDEP-4: --- Assign To: Dan Tran Resolution: Fixed Fix Version: 1.1 fixed. Add support of unpack types tar.gz, tgz --- Key: MDEP-4 URL: http://jira.codehaus.org/browse/MDEP-4 Project: Maven 2.x Dependency Plugin Type: Improvement Environment: xp Reporter: Dan Tran Assignee: Dan Tran Fix For: 1.1 plexus-archiver supports these types, i little more work to do the unpack for these special types -- 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-95) Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers
Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers - Key: MASSEMBLY-95 URL: http://jira.codehaus.org/browse/MASSEMBLY-95 Project: Maven 2.x Assembly Plugin Type: New Feature Versions: 2.1 Environment: xp Reporter: Dan Tran I submitted PLX-216's patch to support this issue. Once PLX-216 is committed, i will send in the patch for this issue -- 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: (MDEP-4) Add support of unpack types tar.gz, tgz
[ http://jira.codehaus.org/browse/MDEP-4?page=all ] Dan Tran updated MDEP-4: Assign To: (was: Brian Fox) Description: plexus-archiver supports these types, i little more work to do the unpack for these special types (was: plexus-archiver supports these types, i little more work to do the unpack for these special type) Summary: Add support of unpack types tar.gz, tgz (was: [dependency-maven-plugin] Add support of unpack types tar.gz, tgz) Add support of unpack types tar.gz, tgz --- Key: MDEP-4 URL: http://jira.codehaus.org/browse/MDEP-4 Project: Maven 2.x Dependency Plugin Type: Improvement Environment: xp Reporter: Dan Tran plexus-archiver supports these types, i little more work to do the unpack for these special types -- 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: (MDEP-4) [dependency-maven-plugin] Add support of unpack types tar.gz, tgz
[ http://jira.codehaus.org/browse/MDEP-4?page=comments#action_64782 ] Dan Tran commented on MDEP-4: - patch submitted to PLX-216 to support this issue [dependency-maven-plugin] Add support of unpack types tar.gz, tgz - Key: MDEP-4 URL: http://jira.codehaus.org/browse/MDEP-4 Project: Maven 2.x Dependency Plugin Type: Improvement Environment: xp Reporter: Dan Tran Assignee: Brian Fox plexus-archiver supports these types, i little more work to do the unpack for these special type -- 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-93) DependencySet's include processing should error out when the include dependency is not available
DependencySet's include processing should error out when the include dependency is not available - Key: MASSEMBLY-93 URL: http://jira.codehaus.org/browse/MASSEMBLY-93 Project: Maven 2.x Assembly Plugin Type: Bug Versions: 2.1 Environment: xp Reporter: Dan Tran dependencySets dependencySet includes includesome-groupId:some-artifactId/include /includes /dependencySet I have a descriptor that use lots of include statements. assembly plugin should error out when the specified dependency is not in the dependency list. This will help to catch the error at packaging time rather eye balling the zip file. -- 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-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64510 ]
Dan Tran commented on MASSEMBLY-89:
---
There are 2 levels of interpolation in assembly files. The first time when the
xml file is read in, the interpolation is by MASSEMBLY-40 which
replace ${artifactId} with the actual artifactid of the pom.The second time
is by the outputFileNameMapping code which nolong see
${artifactId}.
However, Let me take a look the test case first. thanks for looking into it
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Assignee: John Casey
Priority: Critical
Fix For: 2.1
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
all dependency aritifacts into assembly without the version
Here is an exmple
dependencySets
dependencySet
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/dependencySet
/depenendencySets
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
a single file ${artifactId}.${extention}
--
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-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=all ]
Dan Tran updated MASSEMBLY-89:
--
Attachment: bin.xml
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Assignee: John Casey
Priority: Critical
Fix For: 2.1
Attachments: bin.xml, pom.xml
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
all dependency aritifacts into assembly without the version
Here is an exmple
dependencySets
dependencySet
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/dependencySet
/depenendencySets
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
a single file ${artifactId}.${extention}
--
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-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64513 ]
Dan Tran commented on MASSEMBLY-89:
---
Please place pom.xml and bin.xml on the same directory and run
mvn package.
both specified dependencies files are mapped into one file . test.jar
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Assignee: John Casey
Priority: Critical
Fix For: 2.1
Attachments: bin.xml, pom.xml
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
all dependency aritifacts into assembly without the version
Here is an exmple
dependencySets
dependencySet
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/dependencySet
/depenendencySets
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
a single file ${artifactId}.${extention}
--
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-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=all ]
Dan Tran updated MASSEMBLY-89:
--
Fix Version: 2.1
Environment: xp
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Environment: xp
Reporter: Dan Tran
Priority: Critical
Fix For: 2.1
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
all dependency aritifacts into assembly without the version
Here is an exmple
dependencySets
dependencySet
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/dependencySet
/depenendencySets
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
a single file ${artifactId}.${extention}
--
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-89) outputFileNameMapping broken
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Reporter: Dan Tran
Priority: Critical
Fix For: 2.1
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place all
dependency aritifacts into assembly without the version
Here is an exmple
dependencySets
dependencySet
outputFileNameMapping${artifactId}.${extension}/outputFileNameMapping
/dependencySet
/depenendencySets
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to a
single file ${artifactId}.${extention}
--
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: (MANTRUN-49) taskdef/ seems ignoring classpath
[ http://jira.codehaus.org/browse/MANTRUN-49?page=comments#action_64192 ]
Dan Tran commented on MANTRUN-49:
-
when set refid=maven.plugin.classpath in taskdef,
maven throws this error
Reference maven.plugin.classpath not found.
taskdef/ seems ignoring classpath
---
Key: MANTRUN-49
URL: http://jira.codehaus.org/browse/MANTRUN-49
Project: Maven 2.x Antrun Plugin
Type: Bug
Versions: 1.2
Environment: Fedora
Reporter: Jacek Gerbszt
Attachments: testcase.tar.gz
I'm trying to run xdoclet in ant build file called from antrun plugin. The
build file is very simple:
{code:xml}
project name=testcase default=run
property name=maven.repository value=set repository location
here!/
property name=destdir value=target/generated-sources/
path id=xdoclet.classpath
fileset dir=${maven.repository}
include
name=commons-collections/commons-collections/3.1/commons-collections-3.1.jar/
include
name=commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar/
include
name=jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar/
include name=xjavadoc/xjavadoc/1.1/xjavadoc-1.1.jar/
include
name=xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar/
include
name=xdoclet/xdoclet-ejb-module/1.2.3/xdoclet-ejb-module-1.2.3.jar/
/fileset
/path
target name=run
!-- print classplath --
property refid=xdoclet.classpath name=cp/
echo message=xdoclet.classpath: ${cp}/
!-- define ejbdoclet task --
taskdef classname=xdoclet.modules.ejb.EjbDocletTask
classpathref=xdoclet.classpath name=ejbdoclet/
!-- run ejbdoclet --
ejbdoclet destdir=${destdir}
fileset includes=**/*Bean.java
dir=${basedir}/src/main/java/
remoteinterface/
/ejbdoclet
/target
/project
{code}
When executed directly from command (ant
-Dmaven.repository=/home/javor/.m2/repository) it works fine. But fails when
embedded in antrun:
{code:xml}
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.2-SNAPSHOT/version
executions
execution
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
ant inheritRefs=true inheritall=true
antfile=build.xml
property name=maven.repository
value=${settings.localRepository}/
/ant
/tasks
/configuration
/execution
/executions
/plugin
{code}
Maven output:
{noformat}
...
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
run:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
/home/javor/workspace/testcase/build.xml:26: Can't create a remoteinterface
element under ejbdoclet. Make sure the jar file containing the corresponding
subtask class is on the classpath specified in the taskdef that defined {2}.
...
{noformat}
Could you show me any workaround or put a bit of light on that problem?
--
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: (MANTRUN-49) taskdef/ seems ignoring classpath
[ http://jira.codehaus.org/browse/MANTRUN-49?page=all ]
Dan Tran updated MANTRUN-49:
Priority: Blocker (was: Major)
taskdef/ seems ignoring classpath
---
Key: MANTRUN-49
URL: http://jira.codehaus.org/browse/MANTRUN-49
Project: Maven 2.x Antrun Plugin
Type: Bug
Versions: 1.2
Environment: Fedora
Reporter: Jacek Gerbszt
Priority: Blocker
Attachments: testcase.tar.gz
I'm trying to run xdoclet in ant build file called from antrun plugin. The
build file is very simple:
{code:xml}
project name=testcase default=run
property name=maven.repository value=set repository location
here!/
property name=destdir value=target/generated-sources/
path id=xdoclet.classpath
fileset dir=${maven.repository}
include
name=commons-collections/commons-collections/3.1/commons-collections-3.1.jar/
include
name=commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar/
include
name=jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar/
include name=xjavadoc/xjavadoc/1.1/xjavadoc-1.1.jar/
include
name=xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar/
include
name=xdoclet/xdoclet-ejb-module/1.2.3/xdoclet-ejb-module-1.2.3.jar/
/fileset
/path
target name=run
!-- print classplath --
property refid=xdoclet.classpath name=cp/
echo message=xdoclet.classpath: ${cp}/
!-- define ejbdoclet task --
taskdef classname=xdoclet.modules.ejb.EjbDocletTask
classpathref=xdoclet.classpath name=ejbdoclet/
!-- run ejbdoclet --
ejbdoclet destdir=${destdir}
fileset includes=**/*Bean.java
dir=${basedir}/src/main/java/
remoteinterface/
/ejbdoclet
/target
/project
{code}
When executed directly from command (ant
-Dmaven.repository=/home/javor/.m2/repository) it works fine. But fails when
embedded in antrun:
{code:xml}
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.2-SNAPSHOT/version
executions
execution
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
ant inheritRefs=true inheritall=true
antfile=build.xml
property name=maven.repository
value=${settings.localRepository}/
/ant
/tasks
/configuration
/execution
/executions
/plugin
{code}
Maven output:
{noformat}
...
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
run:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
/home/javor/workspace/testcase/build.xml:26: Can't create a remoteinterface
element under ejbdoclet. Make sure the jar file containing the corresponding
subtask class is on the classpath specified in the taskdef that defined {2}.
...
{noformat}
Could you show me any workaround or put a bit of light on that problem?
--
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: (MANTRUN-49) taskdef/ seems ignoring classpath
[ http://jira.codehaus.org/browse/MANTRUN-49?page=comments#action_64233 ]
Dan Tran commented on MANTRUN-49:
-
work around of refid. Here is the discussion on maven user list
think you have two problems - first, I don't think you can use the
reference directly in your ant script (though I don't know why).
Instead, you need to de-reference by setting it to a property value.
Something like this:
property name=cp1
refid=maven.dependency.classpath/
echo message=maven.dependency.classpath is ${cp1}/
echo message=/
property name=cp2 refid=maven.compile.classpath/
echo message=maven.compile.classpath is ${cp2}/
echo message=/
property name=cp3 refid=maven.runtime.classpath/
echo message=maven.runtime.classpath is ${cp3}/
echo message=/
property name=cp4 refid=maven.test.classpath/
echo message=maven.test.classpath is ${cp4}/
echo message=/
property name=cp5 refid=maven.plugin.classpath/
echo message=maven.plugin.classpath is ${cp5}/
echo message=/
Secondly, you appear to want a directory value (perhaps basedir?),
rather than a path-like structure like the classpath.
Hope this is helpful...
-Margaret
taskdef/ seems ignoring classpath
---
Key: MANTRUN-49
URL: http://jira.codehaus.org/browse/MANTRUN-49
Project: Maven 2.x Antrun Plugin
Type: Bug
Versions: 1.2
Environment: Fedora
Reporter: Jacek Gerbszt
Priority: Blocker
Attachments: testcase.tar.gz
I'm trying to run xdoclet in ant build file called from antrun plugin. The
build file is very simple:
{code:xml}
project name=testcase default=run
property name=maven.repository value=set repository location
here!/
property name=destdir value=target/generated-sources/
path id=xdoclet.classpath
fileset dir=${maven.repository}
include
name=commons-collections/commons-collections/3.1/commons-collections-3.1.jar/
include
name=commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar/
include
name=jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar/
include name=xjavadoc/xjavadoc/1.1/xjavadoc-1.1.jar/
include
name=xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar/
include
name=xdoclet/xdoclet-ejb-module/1.2.3/xdoclet-ejb-module-1.2.3.jar/
/fileset
/path
target name=run
!-- print classplath --
property refid=xdoclet.classpath name=cp/
echo message=xdoclet.classpath: ${cp}/
!-- define ejbdoclet task --
taskdef classname=xdoclet.modules.ejb.EjbDocletTask
classpathref=xdoclet.classpath name=ejbdoclet/
!-- run ejbdoclet --
ejbdoclet destdir=${destdir}
fileset includes=**/*Bean.java
dir=${basedir}/src/main/java/
remoteinterface/
/ejbdoclet
/target
/project
{code}
When executed directly from command (ant
-Dmaven.repository=/home/javor/.m2/repository) it works fine. But fails when
embedded in antrun:
{code:xml}
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.2-SNAPSHOT/version
executions
execution
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
ant inheritRefs=true inheritall=true
antfile=build.xml
property name=maven.repository
value=${settings.localRepository}/
/ant
/tasks
/configuration
/execution
/executions
/plugin
{code}
Maven output:
{noformat}
...
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
run:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
/home/javor/workspace/testcase/build.xml:26: Can't create a remoteinterface
element under ejbdoclet. Make sure the jar file containing the corresponding
subtask class is on the classpath specified in the taskdef that defined {2}.
...
{noformat}
Could you show me any workaround or put a bit of light on that problem?
--
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
-
[jira] Commented: (MRELEASE-61) Ability to pass all prompted information as parameters in release:prepare
[ http://jira.codehaus.org/browse/MRELEASE-61?page=comments#action_63981 ] Dan Tran commented on MRELEASE-61: -- Brett Porter has some time now to cleanup maven-release-plugin, he will put in a new mojo release:release a combinanion of prepare and perform. The new mojo also allows interactive mode. Search maven dev list for some details Ability to pass all prompted information as parameters in release:prepare - Key: MRELEASE-61 URL: http://jira.codehaus.org/browse/MRELEASE-61 Project: Maven 2.x Release Plugin Type: Bug Reporter: Yann Le Du Priority: Minor Fix For: 2.0-beta-4 In release:prepare, it would be nice that all prompted information can also be passed as parameters : * tag name (already available, -Dtag) * release version * new development version It would allow to call the plugin in real non-interactive mode - that is, without being forced to accept default values. -- 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: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=comments#action_63596 ] Dan Tran commented on MRELEASE-94: -- it seems the root pom.xml is not part of checkin list [INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/a01/proj/CVS -q comm it -R -F C:\DOCUME~1\ninet\LOCALS~1\Temp\scm-commit-message18612.txt loyaltyServ iceEJBRemote/pom.xml loyaltyService/pom.xml loyaltyCoreBusiness/pom.xml pom.xml loyaltyServiceEJB/pom.xml loyaltyCommon/pom.xml [INFO] Working directory: C:\workspace\ata\loyalty Modified Parent POM is not commited --- Key: MRELEASE-94 URL: http://jira.codehaus.org/browse/MRELEASE-94 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-3 Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant Reporter: Todd Nine Priority: Blocker I can successfully tag all sub projects of a parent pom (with the standard directory structure), but I'm unable complete the release:prepare operation since the parent POM is not checked in. As a result I am unable to perform a multi-project release. Each child pom has the scm repotisotries declared in the pom. Attached is verbose output of the command. mvn -Duser.name=c200506 -X clean release:prepare [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter-documenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime)[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-monitor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:mav en-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtim e) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim e (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-descriptor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected f or runtime) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for ru ntime) [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected f or runtime) [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven.reporting:maven-reporting::2.0 f or project: null:maven-reporting-api:jar:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven.reporting:maven-reporting:pom:2.0 from the repository. [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime (sele cted for runtime) [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for runtime ) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runt ime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-registry:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runtim e) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-manager-plexus: resolved to version 1.0-beta-3-20060330.123807 -1 from repository apache.snapshots [DEBUG] Retrieving parent-POM:
[jira] Commented: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=comments#action_63597 ] Dan Tran commented on MRELEASE-94: -- my bad, the cvs command do have the parent root pom. are you able to issue the command line cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/a01/proj/CVS -q comm it -R -F C:\DOCUME~1\ninet\LOCALS~1\Temp\scm-commit-message18612.txt loyaltyServ iceEJBRemote/pom.xml loyaltyService/pom.xml loyaltyCoreBusiness/pom.xml pom.xml loyaltyServiceEJB/pom.xml loyaltyCommon/pom.xml and your current dir is C:\workspace\ata\loyalty ?? Modified Parent POM is not commited --- Key: MRELEASE-94 URL: http://jira.codehaus.org/browse/MRELEASE-94 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-3 Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant Reporter: Todd Nine Priority: Blocker I can successfully tag all sub projects of a parent pom (with the standard directory structure), but I'm unable complete the release:prepare operation since the parent POM is not checked in. As a result I am unable to perform a multi-project release. Each child pom has the scm repotisotries declared in the pom. Attached is verbose output of the command. mvn -Duser.name=c200506 -X clean release:prepare [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter-documenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime)[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-monitor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:mav en-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtim e) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim e (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-descriptor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected f or runtime) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for ru ntime) [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected f or runtime) [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven.reporting:maven-reporting::2.0 f or project: null:maven-reporting-api:jar:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven.reporting:maven-reporting:pom:2.0 from the repository. [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime (sele cted for runtime) [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for runtime ) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runt ime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-registry:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runtim e) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-manager-plexus: resolved to version 1.0-beta-3-20060330.123807 -1 from repository apache.snapshots [DEBUG]
[jira] Commented: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=comments#action_63598 ] Dan Tran commented on MRELEASE-94: -- from the log, the cvs command did ignore the checkin of pom.xml at the root parent!!! hmmm more likely your cvs client is the main issue here. -D Modified Parent POM is not commited --- Key: MRELEASE-94 URL: http://jira.codehaus.org/browse/MRELEASE-94 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-3 Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant Reporter: Todd Nine Priority: Blocker I can successfully tag all sub projects of a parent pom (with the standard directory structure), but I'm unable complete the release:prepare operation since the parent POM is not checked in. As a result I am unable to perform a multi-project release. Each child pom has the scm repotisotries declared in the pom. Attached is verbose output of the command. mvn -Duser.name=c200506 -X clean release:prepare [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter-documenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime)[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-monitor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:mav en-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtim e) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim e (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-descriptor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected f or runtime) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for ru ntime) [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected f or runtime) [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven.reporting:maven-reporting::2.0 f or project: null:maven-reporting-api:jar:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven.reporting:maven-reporting:pom:2.0 from the repository. [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime (sele cted for runtime) [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for runtime ) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runt ime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-registry:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runtim e) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-manager-plexus: resolved to version 1.0-beta-3-20060330.123807 -1 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm-managers::1.0-beta -3-SNAPSHOT for project: null:maven-scm-manager-plexus:jar:1.0-beta-3-20060330.1 23807-1 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-managers: resolved
[jira] Commented: (MNG-2186) POM interpolation problem in maven-2.0.3
[ http://jira.codehaus.org/browse/MNG-2186?page=comments#action_62346 ]
Dan Tran commented on MNG-2186:
---
Map injection also encounters this problem in 2.0.3.
native-maven-plugin requires this features to setup path environment when
forking a test
POM interpolation problem in maven-2.0.3
Key: MNG-2186
URL: http://jira.codehaus.org/browse/MNG-2186
Project: Maven 2
Type: Bug
Components: Inheritence and Interpolation
Versions: 2.0.3
Environment: xp
Reporter: Dan Tran
Priority: Critical
my maven-2.0.3 shows ${project.build.directory}=target. Instead of the
fullpath
this surely breaks the reactor build/test.
here is an example pom
?xml version=1.0?
project
modelVersion4.0.0/modelVersion
!--
parent
groupIdtest/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
/parent
--
packagingjar/packaging
groupIdtest/groupId
artifactIdchild/artifactId
version1.0-SNAPSHOT/version
namechild/name
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idecho/id
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
echoproject.build.directory:${project.build.directory}/echo
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
Carlos also comfirmed
Confirmed :(
2.0.3 = project.build.directory:target
2.0.2 = project.build.directory:C:\Documents and
Settings\csanchez\Local Settings\Temp\target
--
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-2186) POM interpolation problem in maven-2.0.3
POM interpolation problem in maven-2.0.3
Key: MNG-2186
URL: http://jira.codehaus.org/browse/MNG-2186
Project: Maven 2
Type: Bug
Components: Inheritence and Interpolation
Versions: 2.0.3
Environment: xp
Reporter: Dan Tran
Priority: Critical
my maven-2.0.3 shows ${project.build.directory}=target. Instead of the fullpath
this surely breaks the reactor build/test.
here is an example pom
?xml version=1.0?
project
modelVersion4.0.0/modelVersion
!--
parent
groupIdtest/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
/parent
--
packagingjar/packaging
groupIdtest/groupId
artifactIdchild/artifactId
version1.0-SNAPSHOT/version
namechild/name
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idecho/id
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
echoproject.build.directory:${project.build.directory}/echo
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
Carlos also comfirmed
Confirmed :(
2.0.3 = project.build.directory:target
2.0.2 = project.build.directory:C:\Documents and
Settings\csanchez\Local Settings\Temp\target
--
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: (MSUREFIRE-79) Docs for systemProperties on website are wrong
[ http://jira.codehaus.org/browse/MSUREFIRE-79?page=comments#action_61152 ]
Dan Tran commented on MSUREFIRE-79:
---
The site is correct, the current code in svn uses Properties type for
systemProperties. What you proprose is Map type (I like it better that way
thou)
Docs for systemProperties on website are wrong
--
Key: MSUREFIRE-79
URL: http://jira.codehaus.org/browse/MSUREFIRE-79
Project: Maven 2.x Surefire Plugin
Type: Bug
Reporter: Jason Dillon
Priority: Critical
Site says:
{code}
project
...
build
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
systemProperties
property
namepropertyName/name
valuepropertyValue/value
/property
/systemProperties
/configuration
/plugin
...
/build
...
/project
{code}
Should be:
{code}
project
...
build
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
systemProperties
propertyNamepropertyValue/propertyName
/systemProperties
/configuration
/plugin
...
/build
...
/project
{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] Created: (CONTINUUM-626) Unable to checkout source if scmurl has spaces at the end
Unable to checkout source if scmurl has spaces at the end - Key: CONTINUUM-626 URL: http://jira.codehaus.org/browse/CONTINUUM-626 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.3 Environment: cvs, starteam Reporter: Dan Tran Fix For: 1.0.3 When scmurl has white space at the end, continuum fails to checkout source here is an example of cvs Provider message: The cvs command failed. Command output: --- cvs server: cannot find module `oi ' - ignored cvs [checkout aborted]: cannot expand modules --- When scmurl has leading white spaces, contiuum rejects it. Can we just do a trim()? -- 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: (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
