[jira] (DOXIA-507) Using Jygments as syntax highlighter to implement better pegdown HTML formatter
[
https://jira.codehaus.org/browse/DOXIA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335967#comment-335967
]
Cédric Chantepie commented on DOXIA-507:
If a lexer if found in Jygments (Java port for Pygments) for a code block, this
one is formatted as:
{noformat}
CODE_FORMATTED_BY_JYGMENTS_AS_HTML
{noformat}
> Using Jygments as syntax highlighter to implement better pegdown HTML
> formatter
> ---
>
> Key: DOXIA-507
> URL: https://jira.codehaus.org/browse/DOXIA-507
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Markdown
>Affects Versions: 1.5
>Reporter: Cédric Chantepie
> Attachments: cchantep-doxia-md-jygments.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-507) Using Jygments as syntax highlighter to implement better pegdown HTML formatter
Cédric Chantepie created DOXIA-507: -- Summary: Using Jygments as syntax highlighter to implement better pegdown HTML formatter Key: DOXIA-507 URL: https://jira.codehaus.org/browse/DOXIA-507 Project: Maven Doxia Issue Type: Improvement Components: Module - Markdown Affects Versions: 1.5 Reporter: Cédric Chantepie Attachments: cchantep-doxia-md-jygments.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release
[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335955#comment-335955 ] Robert Scholte commented on MRELEASE-812: - Current status: SCM-686 was an attempt to fix this, but it did more harm than good. Projects which weren't located at the root of the project couldn't be released. SCM-709 should fix this. It is probably fixed with the current snapshot of the SCM project, but there's still no good feedback. > "prepare" does not commit before tagging and therefore deploys snapshot > instead of release > -- > > Key: MRELEASE-812 > URL: https://jira.codehaus.org/browse/MRELEASE-812 > Project: Maven Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.4 >Reporter: Andrei Pozolotin >Priority: Critical > Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt > > > thank you very much for new release! > http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E > it seems we need an emergency fix: > attached are 2 logs: > 1) mvn-2.3.2.txt invocation that works fine with 2.3.2 > 2) mvn-2.4.0.txt invocation that fails with 2.4 > problem: > "perform" does not commit tags, deploys snapshot instead of release > here is project parent: > http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom > build is invoked both times with this: > mvn --define resume=false release:prepare > mvn --define resume=false release:perform -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-175) Multiple artifacts found when using classifiers
[ https://jira.codehaus.org/browse/MEAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Tatam updated MEAR-175: Attachment: ear.patch This patch fixes the problem, but then breaks one of the unit tests. Not 100% sure if the unit test is wrong or if i don't fully understand all the different way that classifiers can be used > Multiple artifacts found when using classifiers > --- > > Key: MEAR-175 > URL: https://jira.codehaus.org/browse/MEAR-175 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Will Tatam > Attachments: ear.patch > > > If you have an artifact without a classifier and one with a classifier, then > the code will find both > e.g > myjar and myjar-javadocs > When you depend on myjar (classififer == null) then it finds the classified > version too and so fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-175) Multiple artifacts found when using classifiers
[ https://jira.codehaus.org/browse/MEAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335940#comment-335940 ] Will Tatam commented on MEAR-175: - [ERROR] Failed to execute goal org.apache.maven.plugins:maven-ear-plugin:2.8:generate-application-xml (default-generate-application-xml) on project ear: Artifact[war:group:artifact] has 2 candidates, please provide a classifier. -> [Help 1] I can't supply a classifier as i need both the basic (non-classified) artifact and the javadocs (which are inside the javadoc classified artifact) > Multiple artifacts found when using classifiers > --- > > Key: MEAR-175 > URL: https://jira.codehaus.org/browse/MEAR-175 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Will Tatam > > If you have an artifact without a classifier and one with a classifier, then > the code will find both > e.g > myjar and myjar-javadocs > When you depend on myjar (classififer == null) then it finds the classified > version too and so fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-175) Multiple artifacts found when using classifiers
[ https://jira.codehaus.org/browse/MEAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Tatam updated MEAR-175: Affects Version/s: 2.8 > Multiple artifacts found when using classifiers > --- > > Key: MEAR-175 > URL: https://jira.codehaus.org/browse/MEAR-175 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Will Tatam > > If you have an artifact without a classifier and one with a classifier, then > the code will find both > e.g > myjar and myjar-javadocs > When you depend on myjar (classififer == null) then it finds the classified > version too and so fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-175) Multiple artifacts found when using classifiers
Will Tatam created MEAR-175: --- Summary: Multiple artifacts found when using classifiers Key: MEAR-175 URL: https://jira.codehaus.org/browse/MEAR-175 Project: Maven Ear Plugin Issue Type: Bug Reporter: Will Tatam If you have an artifact without a classifier and one with a classifier, then the code will find both e.g myjar and myjar-javadocs When you depend on myjar (classififer == null) then it finds the classified version too and so fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
[
https://jira.codehaus.org/browse/MECLIPSE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335924#comment-335924
]
Yariv Amar edited comment on MECLIPSE-712 at 11/18/13 7:20 AM:
---
fixing this can help with multi module projects in eclipse. it would be great
if we the plugin supported this:
{code:XML}
org.apache.maven.plugins
maven-eclipse-plugin
2.9
1376227955734
10
org.eclipse.ui.ide.multiFilter
1.0-name-matches-false-false-*
{code}
this will make Eclipse ignore all the folders for sub-modules in the parent
project.
was (Author: yarix):
finx this can help with multi mpdule projects in eclipse. it would be great
if we the plugin supported this:
{code:XML}
org.apache.maven.plugins
maven-eclipse-plugin
2.9
1376227955734
10
org.eclipse.ui.ide.multiFilter
1.0-name-matches-false-false-*
{code}
> filteredResources in Eclipse .project is not supported and discarded by the
> Maven 2.x Eclipse Plugin
>
>
> Key: MECLIPSE-712
> URL: https://jira.codehaus.org/browse/MECLIPSE-712
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : .project
>Affects Versions: 2.8
> Environment: Maven 3, Windows 7, Eclipse Indigo Service Release 1
>Reporter: René de Bloois
> Attachments: screenshot-1.jpg
>
>
> There is a beautiful way to let Eclipse ignore the target folder:
> {code:xml|title=.project}
>
>
> ...
>
>
> 1328280594689
>
> 10
>
> org.eclipse.ui.ide.multiFilter
>
> 1.0-projectRelativePath-matches-true-false-target
>
>
>
>
> {code}
> Which in Eclipse means (in the Edit Resource Filter window): "Exclude all",
> "Folders", "not recursive", "Project Relative Path matches "target" case
> sensitive".
> This will cause Eclipse to completely ignore this folder and its contents.
> Problem is, after running mvn eclipse:eclipse, this section is removed from
> the .project file.
> It is also not possible to configure the maven eclipse plugin to add this
> filteredResources section.
> Maybe it could even be generated by default by the maven eclipse plugin?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
[
https://jira.codehaus.org/browse/MECLIPSE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335924#comment-335924
]
Yariv Amar commented on MECLIPSE-712:
-
finx this can help with multi mpdule projects in eclipse. it would be great if
we the plugin supported this:
{code:XML}
org.apache.maven.plugins
maven-eclipse-plugin
2.9
1376227955734
10
org.eclipse.ui.ide.multiFilter
1.0-name-matches-false-false-*
{code}
> filteredResources in Eclipse .project is not supported and discarded by the
> Maven 2.x Eclipse Plugin
>
>
> Key: MECLIPSE-712
> URL: https://jira.codehaus.org/browse/MECLIPSE-712
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : .project
>Affects Versions: 2.8
> Environment: Maven 3, Windows 7, Eclipse Indigo Service Release 1
>Reporter: René de Bloois
> Attachments: screenshot-1.jpg
>
>
> There is a beautiful way to let Eclipse ignore the target folder:
> {code:xml|title=.project}
>
>
> ...
>
>
> 1328280594689
>
> 10
>
> org.eclipse.ui.ide.multiFilter
>
> 1.0-projectRelativePath-matches-true-false-target
>
>
>
>
> {code}
> Which in Eclipse means (in the Edit Resource Filter window): "Exclude all",
> "Folders", "not recursive", "Project Relative Path matches "target" case
> sensitive".
> This will cause Eclipse to completely ignore this folder and its contents.
> Problem is, after running mvn eclipse:eclipse, this section is removed from
> the .project file.
> It is also not possible to configure the maven eclipse plugin to add this
> filteredResources section.
> Maybe it could even be generated by default by the maven eclipse plugin?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-65) Support MAR archives
[ https://jira.codehaus.org/browse/MEAR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335918#comment-335918 ] Anders Hammar commented on MEAR-65: --- Is this ticket obsolete and can be closed as "won't fix"? > Support MAR archives > > > Key: MEAR-65 > URL: https://jira.codehaus.org/browse/MEAR-65 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: N/A >Reporter: David J. M. Karlsen >Assignee: Stéphane Nicoll >Priority: Trivial > > Add support for adding MARs to the archive (mar), like the axis2 > addressing module @: > http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.2/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335916#comment-335916
]
Anders Hammar commented on MEAR-88:
---
I suggest closing this ticket as "won't fix".
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Priority: Trivial
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-163) Weird result in multi-profile build
[
https://jira.codehaus.org/browse/MEAR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Hammar closed MEAR-163.
--
Resolution: Not A Bug
I'm closing this as "not a bug" as I assume you have a project with "ear"
packaging. In that case you still have the default execution binding to the
m-ear-p which creates the 'normal' EAR-file (your wording).
Please ask for re-opening of this assumption is wrong. If you need
configuration help you should ask on the user mailing list.
> Weird result in multi-profile build
> ---
>
> Key: MEAR-163
> URL: https://jira.codehaus.org/browse/MEAR-163
> Project: Maven Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.8
> Environment: Windows 7 64Bit; Java 6 / 32 Bit
>Reporter: Wolfgang Grossinger
>
> I configured my pom to create 2 separate EAR-files (with 2 different
> classifiers) when a certain profile is active and get 2 weird things:
> 1.) I get a third 'normal' EAR-File too.
> 2.) I use true which has no effect, so at the end, I get
> 3 files with the same content and different names.
> The config looks like:
> {code:xml}
>
>org.apache.maven.plugins
>maven-ear-plugin
>
>
> web
> package
>
> ear
>
>
> 5
> web-${zps.build.identifier}
> true
> ZPSWEB
>
>
>
>
> at.gv.bmi
> zps-gwt
> /${zps.web.contextRoot}
>
>
> at.gv.bmi
> zps-integration
> true
>
>
>
>
>
> srv
> package
>
> ear
>
>
> 5
> srv-${zps.build.identifier}
> true
> ZPSSRV
>
>
> at.gv.bmi
> zps-gwt
> true
>
>
> at.gv.bmi
> zps-integration
> /${zps.srv.contextRoot}
>
>
>
>
>
>
> {code}
> Regards,
> Wolfgang
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5536) Wrong runtime classpath if inheriting dependencies specified by profile from parent
[ https://jira.codehaus.org/browse/MNG-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated MNG-5536: -- Priority: Critical (was: Major) > Wrong runtime classpath if inheriting dependencies specified by profile from > parent > --- > > Key: MNG-5536 > URL: https://jira.codehaus.org/browse/MNG-5536 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 3.1.1 > Environment: Win >Reporter: Tibor Digana >Priority: Critical > Attachments: with profiles and with parents.zip > > > The module DAO-BOM(pom) defines dependency within a profile. > Other module webapp(war) which indirectly inherits from DAO-BOM does not see > such dependency hibernate-core-4.2.6.Final.jar and dependency which was not > excluded hibernate-commons-annotations-4.0.2.Final.jar > Since the failure results in dependency and war plugin, it looks like the bug > is in Maven core and related to profiles. > I found this issue when I examied the workaround for > https://jira.codehaus.org/browse/MNG-2205 > The problem is that the build result is different in Maven 2.2.1 and Maven > 3.1.1 in webapp module. > The Maven 2.2.1 works as expected. > There are two issues with Maven 3.1.1 : > + Maven 3 ignored two Hibernate runtime artifacts which I expect in WAR file; > + classpath produced by maven-dependency-plugin:build-classpath does not have > those two runtime artifacts if includeScope=runtime. See the webapp POM. > The Zip file contains the project and four text files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
