[magnolia-dev] [JIRA] (MGNLRSSAGG-186) Add read permission for rss workspace to "rss-aggregator-base" role
Peili Liang updated MGNLRSSAGG-186 Add read permission for rss workspace to "rss-aggregator-base" role Change By: Peili Liang (24/Oct/14 5:11 AM) Fix Version/s: 2.3.2 Fix Version/s: 2.3.x 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-166) Use SupplementalModel mechanism to correct information in third-party dependency POMs
Grégory Joseph updated BUILD-166 Use SupplementalModel mechanism to correct information in third-party dependency POMs Change By: Grégory Joseph (23/Oct/14 6:42 PM) Attachment: supplemental-models.xml 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-166) Use SupplementalModel mechanism to correct information in third-party dependency POMs
Grégory Joseph updated BUILD-166 Use SupplementalModel mechanism to correct information in third-party dependency POMs Change By: Grégory Joseph (23/Oct/14 6:42 PM) Attachment: supplemental-models.xml 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-166) Use SupplementalModel mechanism to correct information in third-party dependency POMs
Grégory Joseph updated BUILD-166 Use SupplementalModel mechanism to correct information in third-party dependency POMs Seems to work ! I had to do a couple of adjustments to the file: tags need to be enclosed within (a project can have multiple licenses) the tag in is plural. Every single element that we add in supp-models should behave exactly like in a "real" POM file, thus follow this XSD: http://maven.apache.org/xsd/maven-4.0.0.xsd (it's actually validated) - the comments tag that you've been using, documented as "Addendum information pertaining to this license." might thus not be 100% adequate – if you want to use this for documenting our own changes, perhaps a simple would do. Change By: Grégory Joseph (23/Oct/14 6:35 PM) Attachment: supplemental-models.xml 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-25) Clirr reports should be generated against latest *final* versions
Grégory Joseph updated BUILD-25 Clirr reports should be generated against latest *final* versions Change By: Grégory Joseph (23/Oct/14 6:19 PM) Fix Version/s: POMs 31 Fix Version/s: POMs 30 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-184) Clover: re-enable coverage of test classes
Grégory Joseph created BUILD-184 Clover: re-enable coverage of test classes Issue Type: New Feature Assignee: Grégory Joseph Created: 23/Oct/14 6:04 PM Description: For BUILD-75, we had to set includesTestSourceRoots to false. With BUILD-174 and BUILD-76, it looks like we can set it true again. IIUC, this means we can see per-test coverage results. Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3212) BasicTextCodeField validation kicks in on each input change
Federico Grilli
updated MGNLUI-3212
BasicTextCodeField validation kicks in on each input change
Change By:
Federico Grilli
(23/Oct/14 5:58 PM)
Description:
I created a GroovyValidator which checks for the formal source code correctness upon saving a Groovy script. The validator is attached to a basic text code field. If I start writing invalid Groovy code the validator does not complain and that's fine, because ideally that should happen only upon saving the form. Once I save the form the validator rightly complains and shows an error. The annoying thing now is that trying to fix the code will trigger validation for each input change thus cluttering the UI with error messages. See attached screenshot
. After further debugging I actually found out that validation is triggered at each StateChangeEvent fired by the field which currently has the focus (see {{com.vaadin.ui.AbstractField.getErrorMessage()}} at line 1034 where the condition is true by default). The only reason validation errors are not displayed immediately but only upon saving a form is found at {{info.magnolia.ui.vaadin.form.FormSection.getErrorMessage()}} line #109. That state variable is false until a SaveAction e.g. {{info.magnolia.ui.form.action.SaveFormAction}} changes its value at line #87. From then on validation errors are shown in "real-time".I guess, it would be cool to have greater control over how we display errors on the UI or have a sensible default strategy, e.g. no validation performed automatically but only on submitting a form. In case of errors, validation is disabled until the next form submission. Just my zwei Rappen.
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
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLACTIVATION-96) Transactional activation does not work if the dam workspace is not in the same repo than mgnl-system and mgnl-version
Nicolas Barbé updated MGNLACTIVATION-96 Transactional activation does not work if the dam workspace is not in the same repo than mgnl-system and mgnl-version Change By: Nicolas Barbé (23/Oct/14 5:43 PM) Attachment: repositories.xml 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLACTIVATION-96) Transactional activation does not work if the dam workspace is not in the same repo than mgnl-system and mgnl-version
Nicolas Barbé created MGNLACTIVATION-96 Transactional activation does not work if the dam workspace is not in the same repo than mgnl-system and mgnl-version Issue Type: Bug Affects Versions: 5.3 Assignee: Unassigned Created: 23/Oct/14 5:34 PM Description: Using a transactional activation, Magnolia creates a new version in the mgnl-version workspace on the author and a backup of the activated node on the public. Those two workspaces are in the default magnolia repository. If the activation is triggered on an asset (in the dam) and the dam workspace is located inside another repository, then Magnolia won't be able to clone this node. Steps to reproduce: 1. Configure one author and public instance, out of the box config is ok. 2. Add the transactional activation module: info.magnolia magnolia-module-exchange-transactional 3. Make sure activation works. 4. Now move the dam workspace to a different repo (see attachment) 5.a. Try the activation again using command versioned:activate => Author will failed cause mgnl-version and dam are not in the same repo 5.b. Try the activation again using command default:activate => Public will failed cause mgl-system and dam are not in the same repo Note: This issue can be reproduced with any kind of ws Why it does not work To retrieve the root node of mgnl-system, CopyUtil.copyToSystem needs a hierarchyManager. This hm is given by the method MgnlContext.getSystemContext().getHierarchyManager(SYSTEM_REPO) (ReceiveFilter l.881) which points to the one in the default magnolia repo. Project: Magnolia Activation Module Priority: Neutral Reporter: Nicolas Barbé 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-129) Groovy script editor subapp should be wide by default
Christopher Zimmermann updated MGNLGROOVY-129 Groovy script editor subapp should be wide by default Change By: Christopher Zimmermann (23/Oct/14 4:43 PM) Description: Code editing is more comfortable in a wide dialog.Easily accomplished with a configuration value , see linked ticket . 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-138) Pre-configure dmg/app signing in parent poms
Grégory Joseph updated BUILD-138 Pre-configure dmg/app signing in parent poms Change By: Grégory Joseph (23/Oct/14 4:31 PM) Fix Version/s: POMs 31 Fix Version/s: POMs 30 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-129) Groovy script editor subapp should be wide by default
Christopher Zimmermann updated MGNLGROOVY-129 Groovy script editor subapp should be wide by default Change By: Christopher Zimmermann (23/Oct/14 4:33 PM) Fix Version/s: 2.3.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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-27) Provide assembly for modules using appassembler
Grégory Joseph updated BUILD-27 Provide assembly for modules using appassembler Change By: Grégory Joseph (23/Oct/14 4:32 PM) Fix Version/s: POMs 31 Fix Version/s: POMs 30 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-183) Set installAtEnd to true for maven-install-plugin
Grégory Joseph created BUILD-183 Set installAtEnd to true for maven-install-plugin Issue Type: New Feature Assignee: Grégory Joseph Created: 23/Oct/14 4:28 PM Description: http://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-129) Groovy script editor subapp should be wide by default
Christopher Zimmermann updated MGNLGROOVY-129 Groovy script editor subapp should be wide by default Change By: Christopher Zimmermann (23/Oct/14 3:54 PM) Summary: Groovy script editor subapp should open be wide by default 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-129) Groovy script editor subapp should open wide by default
Christopher Zimmermann created MGNLGROOVY-129 Groovy script editor subapp should open wide by default Issue Type: Improvement Assignee: Unassigned Created: 23/Oct/14 3:53 PM Description: Code editing is more comfortable in a wide dialog. Easily accomplished with a configuration value. Project: Magnolia Groovy Module Labels: quickwin Priority: Neutral Reporter: Christopher Zimmermann Security Level: Public 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-122) Upgrade release plugin to 2.5.1
Grégory Joseph updated BUILD-122 Upgrade release plugin to 2.5.1 Change By: Grégory Joseph (23/Oct/14 3:47 PM) Description: If anything helps: http://jira.codehaus.org/browse/MRELEASE#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panelIt could help with [ MRELEASE-812 |http://jira.codehaus.org/browse/MRELEASE-812] See http://wiki.magnolia-cms.com/display/DEVINT/Release+process#Releaseprocess-Beforeyoustart It also helps with multi-module projects where the parent pom is _not_ the reactor and is in a subdirectory of the reactor. See [MRELEASE-767| http://jira.codehaus.org/browse/MRELEASE-767 ] and [MRELEASE-885| http://jira.codehaus.org/browse/MRELEASE-885 ]. 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-122) Upgrade release plugin to 2.5.1
Grégory Joseph updated BUILD-122 Upgrade release plugin to 2.5.1 Change By: Grégory Joseph (23/Oct/14 3:44 PM) Summary: Upgrade release plugin to 2. 4.1 or 2. 5.1 ? 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-127) Enable integration tests in other projects
Grégory Joseph updated BUILD-127 Enable integration tests in other projects Change By: Grégory Joseph (23/Oct/14 3:43 PM) Fix Version/s: POMs 31 Fix Version/s: POMs 30 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-148) Merge build-tools with poms lifecycle
Grégory Joseph updated BUILD-148 Merge build-tools with poms lifecycle Change By: Grégory Joseph (23/Oct/14 3:35 PM) Description: The plugins and the "tools" currently have completely independent lifecycles. Getting rid of the plugins would simplify our build for parent poms. We currently have a semi-circular dependency that forces to build and release, in this order:* "super" parent pom* plugins / tools* "concrete" parent poms that configure the above plugins.The "tools" are merely files which we bundle in a jar which we use to further configure parent poms. Those could IMO follow the same lifecycle and versioning as the parent poms do. *Resolution*:The different parts of our build projects have been migrated to Git and merged into a single reactor project. However, they still have different lifecycles (i.e plugins don't need to be released with every version of the poms)We might further change this with BUILD- 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-148) Merge build-tools with poms lifecycle
Grégory Joseph
updated BUILD-148
Merge build-tools with poms lifecycle
Change By:
Grégory Joseph
(23/Oct/14 3:36 PM)
Description:
The plugins and the "tools" currently have completely independent lifecycles. Getting rid of the plugins would simplify our build for parent poms. We currently have a semi-circular dependency that forces to build and release, in this order:* "super" parent pom* plugins / tools* "concrete" parent poms that configure the above plugins.The "tools" are merely files which we bundle in a jar which we use to further configure parent poms. Those could IMO follow the same lifecycle and versioning as the parent poms do.*Resolution*:The different parts of our build projects have been migrated to Git and merged into a single reactor project. However, they still have different lifecycles (i.e plugins don't need to be released with every version of the poms)We might further change this with BUILD-
182. Meanwhile, the build is using the {{-pl}}, {{-am}} and {{-amd}} flags of Maven. See README.txt for details.
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
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-163) New groupIDs and artifactIDs for parent poms, Maven plugins and build resources
Grégory Joseph updated BUILD-163 New groupIDs and artifactIDs for parent poms, Maven plugins and build resources Change By: Grégory Joseph (23/Oct/14 3:32 PM) Priority: Neutral Critical 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-182) Review/remove our Maven plugins
Grégory Joseph updated BUILD-182 Review/remove our Maven plugins Change By: Grégory Joseph (23/Oct/14 3:33 PM) Fix Version/s: POMs 31 Fix Version/s: POMs 30 Fix Version/s: Build Resources 1.6 Fix Version/s: Site Skin 1.3 Fix Version/s: Maven Assemblies 1.3 Fix Version/s: SetProperty Maven plugin 1.2 Fix Version/s: Magnolia Bundle Maven Plugin 1.1 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-267) Library conflict between Workflow with JBMP 6 and Weblogic/Websphere
Milan Divilek updated MGNLWORKFLOW-267 Library conflict between Workflow with JBMP 6 and Weblogic/Websphere Change By: Milan Divilek (23/Oct/14 3:32 PM) Labels: support 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-163) New groupIDs and artifactIDs for parent poms, Maven plugins and build resources
Grégory Joseph updated BUILD-163 New groupIDs and artifactIDs for parent poms, Maven plugins and build resources Change By: Grégory Joseph (23/Oct/14 3:32 PM) Parent: BUILD-148 Issue Type: Sub-task New Feature 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-148) Review/remove our Maven plugins
Grégory Joseph updated BUILD-148 Review/remove our Maven plugins Change By: Grégory Joseph (23/Oct/14 3:32 PM) Summary: Review /remove our Maven plugins , merge build-tools with poms lifecycle ? 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-148) Merge build-tools with poms lifecycle
Grégory Joseph updated BUILD-148 Merge build-tools with poms lifecycle Change By: Grégory Joseph (23/Oct/14 3:34 PM) Summary: Review/remove our Maven plugins Merge build-tools with poms lifecycle Description: The plugins and the "tools" currently have completely independent lifecycles. Getting rid of the plugins would simplify our build for parent poms. We currently have a semi-circular dependency that forces to build and release, in this order:* "super" parent pom* plugins / tools* "concrete" parent poms that configure the above plugins.The "tools" are merely files which we bundle in a jar which we use to further configure parent poms. Those could IMO follow the same lifecycle and versioning as the parent poms do. 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-130) Upgrade to Maven 3.x
Grégory Joseph
updated BUILD-130
Upgrade to Maven 3.x
Change By:
Grégory Joseph
(23/Oct/14 3:29 PM)
Description:
We're finally moving to Maven 3.xMaven 3.2.3 fixes a bunch of issues we've had in the past:- various
(
quick temp description
plugins, poms) inheritance related issues- performance,
to
gather info before doing anything
a certain extent- scope:import can be simplified !It is also needed for Nexus staging (BUILD-151
)
Stuff
We'll need
to
take into account
*
adapt our
parent poms
and site generation (see BUILD-19, BUILD-29, BUILD-148 and BUILD-135)
*
check a bunch of
plugins
** in
, n
particular the release plugin !*
generated sites - http://maven.apache.org/plugins/maven-site-plugin/maven-3.html** See BUILD-135*
check
archetypes*
docSettings -
Maven
settings
download from Nexus as documented
: updated wiki
at
http
https
://
documentation
wiki
.magnolia-cms.com/display/
DOCS
DEVINT
/Maven+
init don
tips#Maventips-Settingsxml, we
'
t work; but this newer version of the plugin doesn't seem
ll need
to
work with Maven 3.1 either
update https
:
{noformat}mvn org.sonatype.plugins:nexus-m2settings-maven-plugin:1.4.6:download -DnexusUrl=http:
//
nexus
documentation
.magnolia-cms.com
-DtemplateId=magnolia-community-public -Dsecure=false
/display/DOCS/Maven+init
{noformat}
(however it's probably what we'll need when we upgrade Nexus)
Most important changes from Maven 2 are documented at
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
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
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-174) Update Clover plugins to 4.0.2
Grégory Joseph updated BUILD-174 Update Clover plugins to 4.0.2 Change By: Grégory Joseph (23/Oct/14 3:18 PM) Summary: Update Clover plugins to 4.0.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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-274) recursive publication shows wrong requestor
Espen Jervidalo created MGNLWORKFLOW-274 recursive publication shows wrong requestor Issue Type: Bug Affects Versions: 5.4.2 Assignee: Unassigned Created: 23/Oct/14 2:00 PM Description: To reproduce: log in with eric, go to pages app, publish a subtree log in with peter, go to pending tasks, requester is superuser and not eric reason: we use asynchronous actions for recursive publication, which IMO is not needed when using workflow. see: info.magnolia.module.workflow.commands.LaunchWorkflowCommand#getParameters /modules/pages/apps/pages/subApps/browser/actions/activateRecursive@asynchronous Fix Versions: 5.4.x Project: Magnolia Workflow Module Priority: Neutral Reporter: Espen Jervidalo 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-128) Add basic autocompletion feature in console
Christopher Zimmermann reopened MGNLGROOVY-128 Add basic autocompletion feature in console Change By: Christopher Zimmermann (23/Oct/14 1:54 PM) Resolution: Fixed Status: Closed Reopened 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3201) Favorites form is completely rebuilt at each update
Aleksandr Pchelintcev reopened MGNLUI-3201 Favorites form is completely rebuilt at each update Change By: Aleksandr Pchelintcev (23/Oct/14 1:10 PM) Resolution: Fixed Status: In QA Reopened 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLTAGS-45) Reconfigure availability of de/activation and other actions
Peili Liang updated MGNLTAGS-45 Reconfigure availability of de/activation and other actions Change By: Peili Liang (23/Oct/14 1:04 PM) Fix Version/s: 1.0.2 Fix Version/s: 1.0.x 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-181) Provide m2e lifecycle for our own plugins
Grégory Joseph created BUILD-181 Provide m2e lifecycle for our own plugins Issue Type: Task Assignee: Grégory Joseph Created: 23/Oct/14 12:14 PM Description: It should be possible for our plugins to provide the info m2e needs to stop complaining. http://wiki.eclipse.org/M2E_plugin_execution_not_covered Fix Versions: SetProperty Maven plugin 1.2, Magnolia Bundle Maven Plugin 1.1, POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-180) Update Maven(plugin) API deps for our Maven plugins
Grégory Joseph created BUILD-180 Update Maven(plugin) API deps for our Maven plugins Issue Type: Task Assignee: Grégory Joseph Created: 23/Oct/14 10:25 AM Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public 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 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
