[jira] Commented: (ARCHETYPE-308) Should ask input for requiredProperty with defaultValue
[ http://jira.codehaus.org/browse/ARCHETYPE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265774#action_265774 ] Mykola Nikishov commented on ARCHETYPE-308: --- Any progress on this? Patch had been available for almost two years... > Should ask input for requiredProperty with defaultValue > --- > > Key: ARCHETYPE-308 > URL: http://jira.codehaus.org/browse/ARCHETYPE-308 > Project: Maven Archetype > Issue Type: Bug >Reporter: Grégory Joseph > Attachments: ARCHETYPE-200.patch > > > It seems that if a requiredProperty is defined with a defaultValue, the > generate mojo does not ask user input. In my opinion it should, just like it > does it for the version. > DefaultArchetypeFactory lines 156-168 seem to be the culprit and I'll attach > a patch that might fix this. -- 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] (MNGSITE-149) Maven 2.x Integration for Eclipse page mentions Eclipse IAM which is archived
Mykola Nikishov created MNGSITE-149:
---
Summary: Maven 2.x Integration for Eclipse page mentions Eclipse
IAM which is archived
Key: MNGSITE-149
URL: https://jira.codehaus.org/browse/MNGSITE-149
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Mykola Nikishov
[Maven 2.x Integration for Eclipse|http://maven.apache.org/eclipse-plugin.html]
mentions Eclipse IAM project:
{quote}With five releases already, and continuing to make one every other month
*it's quickly maturing*.{quote}
But this is not true any more because it [has been
archived|http://www.eclipse.org/iam/] in January 2012. Project's forum has been
moved to Archive section too.
So it's officially dead and Maven 2.x Integration for Eclipse should be
adjusted accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-149) Maven 2.x Integration for Eclipse page mentions Eclipse IAM which is archived
[
https://jira.codehaus.org/browse/MNGSITE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287927#comment-287927
]
Mykola Nikishov commented on MNGSITE-149:
-
[Termination Review
2011|http://wiki.eclipse.org/Technology/Subproject_Termination_Review_2011#Eclipse_IAM_.28Integration_for_Apache_Maven.29]
> Maven 2.x Integration for Eclipse page mentions Eclipse IAM which is archived
> -
>
> Key: MNGSITE-149
> URL: https://jira.codehaus.org/browse/MNGSITE-149
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Mykola Nikishov
>
> [Maven 2.x Integration for
> Eclipse|http://maven.apache.org/eclipse-plugin.html] mentions Eclipse IAM
> project:
> {quote}With five releases already, and continuing to make one every other
> month *it's quickly maturing*.{quote}
> But this is not true any more because it [has been
> archived|http://www.eclipse.org/iam/] in January 2012. Project's forum has
> been moved to Archive section too.
> So it's officially dead and Maven 2.x Integration for Eclipse should be
> adjusted accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINVOKER-25) invoke postBuildHookScript even if build failed
invoke postBuildHookScript even if build failed --- Key: MINVOKER-25 URL: http://jira.codehaus.org/browse/MINVOKER-25 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Affects Versions: 1.2 Reporter: Mykola Nikishov Priority: Critical Attachments: 0001-enable-negative-tests.patch I develop a plugin which is ok to break a build. Current workflow using maven-invoker-plugin looks like: - if my plug-in works as expected ;-) it breaks an IT build during integration-test phase - the MojoFailureException is thrown - the maven-invoker-plugin reports that build failed - a script defined in postBuildHookScript is never used As a result I have a false alarm - a broken build when everything is ok. I would like to have an opportunity to decide from a postBuildHookScript whether a build was successful or not. I've implemented desired functionality and attached a patch against trunk/[EMAIL PROTECTED] -- 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
