[jira] Created: (MINVOKER-74) Allow to specify alternative POMs during multi-module builds
Allow to specify alternative POMs during multi-module builds
Key: MINVOKER-74
URL: http://jira.codehaus.org/browse/MINVOKER-74
Project: Maven 2.x Invoker Plugin
Issue Type: New Feature
Affects Versions: 1.3
Reporter: Benjamin Bentmann
One sometimes wants to build the individual modules of a multi-module project
setup in isolation, say for something like
{noformat}
/
sub-1/
sub-2/
pom.xml
{noformat}
invoke "install" on "sub-1" but only "validate" on "sub-2".
--
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: (MINVOKER-74) Allow to specify alternative POMs during multi-module builds
[
http://jira.codehaus.org/browse/MINVOKER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-74.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.4
Added new invoker property {{invoker.project}} in
[r735456|http://svn.eu.apache.org/viewvc?view=rev&revision=735456].
> Allow to specify alternative POMs during multi-module builds
>
>
> Key: MINVOKER-74
> URL: http://jira.codehaus.org/browse/MINVOKER-74
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 1.4
>
>
> One sometimes wants to build the individual modules of a multi-module project
> setup in isolation, say for something like
> {noformat}
> /
> sub-1/
> sub-2/
> pom.xml
> {noformat}
> invoke "install" on "sub-1" but only "validate" on "sub-2".
--
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: (MINVOKER-75) Trigger further builds upon any indexed invoker property
Trigger further builds upon any indexed invoker property
Key: MINVOKER-75
URL: http://jira.codehaus.org/browse/MINVOKER-75
Project: Maven 2.x Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Benjamin Bentmann
Priority: Minor
For an {{invoker.properties}} with:
{noformat}
invoker.profiles.1 = foo
invoker.profiles.2 = bar
{noformat}
only one build will be triggered because there is no property
{{invoker.goals.2}} defined as currently required. To avoid respecifying the
goals, the plugin should trigger another build if any supported invoker
property is defined for the current build number.
--
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: (MINVOKER-75) Trigger further builds upon any indexed invoker property
[
http://jira.codehaus.org/browse/MINVOKER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-75.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.4
Done in [r735459|http://svn.eu.apache.org/viewvc?view=rev&revision=735459].
> Trigger further builds upon any indexed invoker property
>
>
> Key: MINVOKER-75
> URL: http://jira.codehaus.org/browse/MINVOKER-75
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.4
>
>
> For an {{invoker.properties}} with:
> {noformat}
> invoker.profiles.1 = foo
> invoker.profiles.2 = bar
> {noformat}
> only one build will be triggered because there is no property
> {{invoker.goals.2}} defined as currently required. To avoid respecifying the
> goals, the plugin should trigger another build if any supported invoker
> property is defined for the current build number.
--
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: (MSITE-262) site.xml not inherited if build run from parent
[ http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161405#action_161405 ] Dennis Lundberg commented on MSITE-262: --- You need to specify version 2.0-beta-7 for Maven Site Plugin. It has nothing to do with which version of Maven you are using. > site.xml not inherited if build run from parent > --- > > Key: MSITE-262 > URL: http://jira.codehaus.org/browse/MSITE-262 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: inheritance >Affects Versions: 2.0-beta-6 >Reporter: Cameron Jones >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: MSITE-262.zip > > > I've seen that the site.xml is not being inherited in a module when the build > is run from the parent - when run from the module itself the inheritance > works correctly. -- 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: (DOXIA-177) Invalid XHTML because of wrong position of table caption
[ http://jira.codehaus.org/browse/DOXIA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-177. - Resolution: Fixed Fixed it in [r735478|http://svn.apache.org/viewvc?rev=735478&view=rev] > Invalid XHTML because of wrong position of table caption > > > Key: DOXIA-177 > URL: http://jira.codehaus.org/browse/DOXIA-177 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Lukas Theussl >Assignee: Vincent Siveton > Fix For: 1.1 > > Attachments: DOXIA-177.diff > > > Currently a table caption is most of the time emitted after the table body > (mainly because apt puts the caption after the table). However, for a valid > xhtml-1.0, the table caption has to come before the first table row. > Since we don't have a mechanism yet to enforce the order of parsing events > (see DOXIA-132), and I am not sure if this can be achieved in general, any > sink should be flexible enough to deal with any reasonable order of events, > to produce some valid output. -- 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: (MERCURY-41) OpenPGP file seem to be OS-specific, add separate file for each OS in ITs
[ http://jira.codehaus.org/browse/MERCURY-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-41: Fix Version/s: (was: 1.0.0-alpha-3) 1.0.0-alpha-4 > OpenPGP file seem to be OS-specific, add separate file for each OS in ITs > - > > Key: MERCURY-41 > URL: http://jira.codehaus.org/browse/MERCURY-41 > Project: Mercury > Issue Type: Improvement >Affects Versions: 1.0.0-alpha-2 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-4 > > > ITs run on OS X, but fail on others. Traced one of the bugs to key storage > file being OS-specific. > For now - don't use PGP in ITs except for OS X -- 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: (MERCURY-54) make absense of metadata in the repository clearer to the client.
[ http://jira.codehaus.org/browse/MERCURY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-54. --- Resolution: Fixed changed the way exceptions processed in VRR, so that user can see them yet multiple repos are processed correctly > make absense of metadata in the repository clearer to the client. > -- > > Key: MERCURY-54 > URL: http://jira.codehaus.org/browse/MERCURY-54 > Project: Mercury > Issue Type: Improvement > Components: Repository >Affects Versions: 1.0.0-alpha-3 >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Fix For: 1.0.0-alpha-3 > > > For some reason - only a null exception is thrown. > Find a way to convey this information to the client code. > One way would be an event ? -- 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-156) Prompt for customizing commit comment during release preparation
[ http://jira.codehaus.org/browse/MRELEASE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161449#action_161449 ] Andreas Dejung commented on MRELEASE-156: - I have the same problem. I tried the scmCommentPrefix and set it to space. This get rid of the [maven-release-plugin] but the "prepare release" part remains :( So this is a blocker for all svn precommit hook users. A see a fix to have a parameter to say do not change my tag message at all. Thanks for looking at this Andreas > Prompt for customizing commit comment during release preparation > > > Key: MRELEASE-156 > URL: http://jira.codehaus.org/browse/MRELEASE-156 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.0-beta-4 >Reporter: Dário Oliveros > > Hi there, > I've been trying to use maven-release-plugin to prepare a release, but > whenever I do that, it fails since I have a SVN precommit hook that > integrates with an issue tracking system which in turn waits for a comment > containing an issue number. Since release plugin adds its own comment, such > as "[maven-release-plugin] prepare release ...", this integration fails. So > I was wondering if this could be prompted in the same way for the release and > next development iteration versions. > Thanks, > Dário -- 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
