[jira] Closed: (DOXIA-72) Allow multiple powered by logos with no border and no fixed size
[ http://jira.codehaus.org/browse/DOXIA-72?page=all ] fabrizio giustina closed DOXIA-72. -- Assignee: fabrizio giustina Resolution: Fixed Fix Version/s: 1.0 committed to svn, thanks. In addition to your patch I also adapted the default maven poweredBy logo in order to use the standard button/minibar size. The standard size for buttons is 88x31 pixels, see http://www.iab.net/standards/adunits.asp for reference. > Allow multiple powered by logos with no border and no fixed size > > > Key: DOXIA-72 > URL: http://jira.codehaus.org/browse/DOXIA-72 > Project: doxia > Issue Type: Improvement > Components: Site Renderer >Affects Versions: 1.0-alpha-8 > Environment: WinXP, Java5 >Reporter: Martin Zeltner > Assigned To: fabrizio giustina >Priority: Trivial > Fix For: 1.0 > > Attachments: maven-feather.png, patch_doxia-site_renderer.txt > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Allow multiple powered by logos with no border and no fixed size. > Changes in patch: >* Css adapted so powered by logo have no fixed size and no border >* VM template adapted so generated site is XHMTL 1.1 valid im multiple > logos are used. >* Maven feather enlarged with a black 1px wide border (see sep attachement) > Cheers, > Martin -- 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: (ARCHETYPE-39) Add tool for working with escaping in Velocity templates
[ http://jira.codehaus.org/browse/ARCHETYPE-39?page=comments#action_72768 ]
Guillaume Nodet commented on ARCHETYPE-39:
--
Is there any workaround for that ?
> Add tool for working with escaping in Velocity templates
>
>
> Key: ARCHETYPE-39
> URL: http://jira.codehaus.org/browse/ARCHETYPE-39
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Plugin
>Affects Versions: 1.0-alpha-4
>Reporter: Willie Vu
>
> e.g. I need to put ${archifactId} (without parameter replacement) into an
> assembly descriptor. I need to escape the dollar sign.
> This is the Escape Tool of Velocity -
> http://jakarta.apache.org/velocity/tools/javadoc/org/apache/velocity/tools/generic/EscapeTool.html.
> The embedded Velocity engine will be configured to use it, or archetype
> plugin allows further Velocity configuration.
--
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: (ARCHETYPE-39) Add tool for working with escaping in Velocity templates
[ http://jira.codehaus.org/browse/ARCHETYPE-39?page=comments#action_72770 ]
Joakim Erdfelt commented on ARCHETYPE-39:
-
Try using "$${artifactId}" instead.
This technique has proved useful for velocity templates i've created for custom
Archetypes and such.
> Add tool for working with escaping in Velocity templates
>
>
> Key: ARCHETYPE-39
> URL: http://jira.codehaus.org/browse/ARCHETYPE-39
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Plugin
>Affects Versions: 1.0-alpha-4
>Reporter: Willie Vu
>
> e.g. I need to put ${archifactId} (without parameter replacement) into an
> assembly descriptor. I need to escape the dollar sign.
> This is the Escape Tool of Velocity -
> http://jakarta.apache.org/velocity/tools/javadoc/org/apache/velocity/tools/generic/EscapeTool.html.
> The embedded Velocity engine will be configured to use it, or archetype
> plugin allows further Velocity configuration.
--
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: (ARCHETYPE-39) Add tool for working with escaping in Velocity templates
[ http://jira.codehaus.org/browse/ARCHETYPE-39?page=comments#action_72772 ]
Guillaume Nodet commented on ARCHETYPE-39:
--
I need to use resource filtering to build my archetype.
So I need a way to escape one velocity level, and a way to escape two verlocity
levels.
So in my src/main/resources/archetype-resources/pom.xml, i have something like
\${artifactId}
...
. ..
${servicemix-version}
...
\$${basedir}/target/generated-sources
When this file is bundled in the archtype, i want it to be
${artifactId}
...
. ..
3.0-SNAPSHOT
...
\${basedir}/target/generated-sources
So that the project created using this archtype will be
my-archetype
...
. ..
3.0-SNAPSHOT
...
${basedir}/target/generated-sources
The problem is that i found no way to have a ${artifactId} generated after the
resource filtering,
because :
$${artifactId} => $${artifactId}
${artifactId} => org.apache.servicemix.tooling.servicemix-archetype
\${artifactId} => \org.apache.servicemix.tooling.servicemix-archetype
$\${artifactId} => $\org.apache.servicemix.tooling.servicemix-archetype
\$${artifactId} => \$${artifactId}
> Add tool for working with escaping in Velocity templates
>
>
> Key: ARCHETYPE-39
> URL: http://jira.codehaus.org/browse/ARCHETYPE-39
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Plugin
>Affects Versions: 1.0-alpha-4
>Reporter: Willie Vu
>
> e.g. I need to put ${archifactId} (without parameter replacement) into an
> assembly descriptor. I need to escape the dollar sign.
> This is the Escape Tool of Velocity -
> http://jakarta.apache.org/velocity/tools/javadoc/org/apache/velocity/tools/generic/EscapeTool.html.
> The embedded Velocity engine will be configured to use it, or archetype
> plugin allows further Velocity configuration.
--
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-2517) The binary distribution produced by assembly plugin contains .svn directory
The binary distribution produced by assembly plugin contains .svn directory --- Key: MNG-2517 URL: http://jira.codehaus.org/browse/MNG-2517 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.1 Environment: trunk, assembly plugin 2.2-SNAPSHOT Reporter: Vincent Siveton Result in zip file: maven-2.1-SNAPSHOT\conf \.svn\ \settings.xml -- 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-2517) The binary distribution produced by assembly plugin contains .svn directory
[ http://jira.codehaus.org/browse/MNG-2517?page=all ] Vincent Siveton updated MNG-2517: - Attachment: MNG-2517.txt Patch to include settings.xml > The binary distribution produced by assembly plugin contains .svn directory > --- > > Key: MNG-2517 > URL: http://jira.codehaus.org/browse/MNG-2517 > Project: Maven 2 > Issue Type: Bug > Components: Command Line >Affects Versions: 2.1 > Environment: trunk, assembly plugin 2.2-SNAPSHOT >Reporter: Vincent Siveton > Attachments: MNG-2517.txt > > > Result in zip file: > maven-2.1-SNAPSHOT\conf > \.svn\ > \settings.xml -- 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: (MWAR-61) Document how to set manifest classpath and exclude dependency from WEB-INF/lib
[ http://jira.codehaus.org/browse/MWAR-61?page=comments#action_72773 ] Mike Perham commented on MWAR-61: - Michael, just because you add them to the manifest doesn't mean they will be auto-excluded. WEB-INF/lib/*.jar > Document how to set manifest classpath and exclude dependency from WEB-INF/lib > -- > > Key: MWAR-61 > URL: http://jira.codehaus.org/browse/MWAR-61 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: David Jencks > Assigned To: Brett Porter > Fix For: 2.0.2 > > Attachments: war-plugin-manifestcp-doc.patch > > > I had to get some help from evenisse to figure out how to generate the > manifest classpath yet not include all the dependencies in WEB-INF/lib. I > still don't know how to get a dependency into WEB-INF/lib but not the > manifest classpath when generating the manifest classpath, but this should > help anyone just trying to use a manifest cp in an ear. -- 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-140) Assembly descriptor docs are incorrect for dependencySets/dependencySet/excludes
Assembly descriptor docs are incorrect for dependencySets/dependencySet/excludes
Key: MASSEMBLY-140
URL: http://jira.codehaus.org/browse/MASSEMBLY-140
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Jason Dillon
Priority: Minor
The docs ( http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
) state:
|| excludes | When subelements are present, they define a set of
files and directory to exclude. |
Which is not correct, the {{}} sub-elements are module references in
the format of {{:}}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1061) Upload qdox 1.6 on m2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1061?page=comments#action_72783 ] Guillaume Nodet commented on MAVENUPLOAD-1061: -- The bundle has been updated with all the informations provided in the maven 1 project. > Upload qdox 1.6 on m2 repo > -- > > Key: MAVENUPLOAD-1061 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1061 > Project: maven-upload-requests > Issue Type: Task >Reporter: Guillaume Nodet > -- 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-207) Implementing update and checkout command
[ http://jira.codehaus.org/browse/SCM-207?page=all ] Thorsten Riek closed SCM-207. - Resolution: Fixed I've got not enough time to implement tests for the consumers too. > Implementing update and checkout command > - > > Key: SCM-207 > URL: http://jira.codehaus.org/browse/SCM-207 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-vss >Affects Versions: 1.0-beta-3 >Reporter: Thorsten Riek > Fix For: 1.0 > > Attachments: SCM-207-02-maven-scm-provider-vss.patch, > SCM-207-maven-scm-provider-vss.patch > > > Implemented with VSS GET command. Update ignores writable resources. Checkout > overwrites writable resources. -- 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: (SCM-223) VSS add command
[ http://jira.codehaus.org/browse/SCM-223?page=all ] Thorsten Riek updated SCM-223: -- Attachment: SCM-223-02-maven-scm-provider-vss.patch Add and Edit commands with tests > VSS add command > --- > > Key: SCM-223 > URL: http://jira.codehaus.org/browse/SCM-223 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-vss >Reporter: Thorsten Riek > Attachments: SCM-223-02-maven-scm-provider-vss.patch, > SCM-223-maven-scm-provider-vss.patch > > > Some minor changes and VSS add command implementation. -- 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-151) Surefire plugin fails if JUnit is not available
[ http://jira.codehaus.org/browse/MSUREFIRE-151?page=comments#action_72787 ] Jon SlinnHawkins commented on MSUREFIRE-151: I am also having this problem. However it manifests itself slightly differently. I have a set of approved libraries for use across all of our development projects. one being junit. to ease the management of approved libs, we have created an inhouse groupid for them, but still using the original artifactId and version. if i include the inhouse junit jar i get the error described above. The only way i can get surefire to run is to use the junit/junit (groupId/artifactId). Surely having the junit jar on the classpath should suffice no matter what it's groupId is. Does the Surefire plugin reference the groupId/artifactId explicitly > Surefire plugin fails if JUnit is not available > --- > > Key: MSUREFIRE-151 > URL: http://jira.codehaus.org/browse/MSUREFIRE-151 > Project: Maven 2.x Surefire Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Simon Kepp Nielsen >Priority: Critical > Fix For: 2.3 > > Attachments: error.txt, no-test-framework-patch.txt > > > The Surefire Plugin fails with the following message, if JUnit is not > available on the test classpath: > [INFO] No Java test frameworks found > This means, that you have to include JUnit in the classpath, even for > projects that do not have any unit-tests (e.g. ressource projects or your > first Hello World 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
