[JBoss JIRA] (JBIDE-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-13603.
--------------------------------
Resolution: Done
Fixed in JBDS build B361.
{code} $ find ~/jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361/studio -maxdepth 2 -name "org.eclipse.m2e.feature*" -o -name "org.eclipse.m2e.wtp.feature*"
/home/nboldt/jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361/studio/features/org.eclipse.m2e.wtp.feature_0.17.0.20130212-1819
/home/nboldt/jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361/studio/features/org.eclipse.m2e.feature_1.3.1.20130219-1424
{code}
> Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP
> ---------------------------------------------------
>
> Key: JBIDE-13603
> URL: https://issues.jboss.org/browse/JBIDE-13603
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, maven
> Affects Versions: 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Labels: respin-a, respin-b
> Fix For: 4.0.1.Final
>
>
> Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0.
> So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff.
> * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 :
> org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821
> (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions)
> * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 :
> org.eclipse.m2e.feature 1.3.1.20130219-0909.jar
> org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar
--
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
13 years
[JBoss JIRA] (JBIDE-13207) Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13207?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13207.
---------------------------------
Resolution: Done
pushed to master
> Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13207
> URL: https://issues.jboss.org/browse/JBIDE-13207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> Create EAP 6.0 runtime server make sure it has a defaeult scanner interval of "0".
> Start EAP 6.0
> Wait N seconds/do other stuff.
> Up comes a dialog saying:
> Inactive Deployment Scanner?
> Warning: One or more deployments scanners have scan-interval of 0.
> These scanners are inactive. If this is intentional, press 'Ok'
> And then there is a table witha scanner name and then an editable scanner interval.
> 1) There is *zero* infon on what this relates to - I would have expected at least a reference to the name of the server there is a problem with.
> 2) The dialog says I should press Ok if i'm ok - but there is no cancel button or instructions on what I otherwise can do.
> 3) The title talks about "scan-interval" the table says "Scanner Interval"
> 4) When changing the value and then closing the dialog with the red button or escape -> changes made to the config xml file - BAD!
> Suggestion:
> Title: Inactive Deployment Scanner found
> subtitle: Inactive Deployment scanner found
> Text: 'servername' contains one or more deployment scanners that are currently inactive (scan-interval=0).
> This means their folds will not be scanned for new deployments nor changes. If this is intentional, presss 'Ok',
> or if you want a different interval (recommended is: <thedefaultnumber>s ) change it in the table below and then press 'Ok'.
> Table: show the actual location the scanner is related to - otherwise users have no idea/context what scanner it is.
> Ok
> and if user press Escape or closes dialog without pressing ok -> no changes made anywhere!
--
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
13 years